Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Open Source Projects - Beyond Code

You're reading from   Open Source Projects - Beyond Code A blueprint for scalable and sustainable open source projects

Arrow left icon
Product type Paperback
Published in Apr 2023
Publisher Packt
ISBN-13 9781837636884
Length 240 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
John Mertic John Mertic
Author Profile Icon John Mertic
John Mertic
Arrow right icon
View More author details
Toc

Table of Contents (20) Chapters Close

Preface 1. Part 1: Getting Ready to Go Open Source FREE CHAPTER
2. Chapter 1: The Whats and Whys of Open Source 3. Chapter 2: What Makes a Good Open Source Project? 4. Chapter 3: Open Source License and IP Management 5. Chapter 4: Aligning the Business Value of Open Source for Your Employer 6. Chapter 5: Governance and Hosting Models 7. Part 2: Running an Open Source Project
8. Chapter 6: Making Your Project Feel Welcoming 9. Chapter 7: Growing Contributors to Maintainers 10. Chapter 8: Dealing with Conflict 11. Chapter 9: Handling Growth 12. Part 3: Building and Scaling Open Source Ecosystems
13. Chapter 10: Commercialization of Open Source 14. Chapter 11: Open Source and the Talent Ecosystem 15. Chapter 12: Marketing for Open Source – Advocacy and Outreach 16. Chapter 13: Transitioning Leadership 17. Chapter 14: Sunsetting an Open Source Project 18. Index 19. Other Books You May Enjoy

Copyrights and contribution sign-off

When people think about license and IP management, the conversation often focuses on outbound licensing – that is, what license the code from the project uses. But just as important (or even more important) are the terms that the code comes into the project under, because if it doesn’t come in under the license and/or terms that will work with the license the code is released under, it makes it difficult on downstream users to use the code.

In smaller projects, this is often overlooked, as you often will only see a few contributors to the code base, so project maintainers tend not to pay much attention to contribution sign-off. But this can quickly get out of control, especially if you have someone come to the project and say, “Hey, that code looks like something someone pulled from my commercial product.” It gets awkward quickly here at this point, as the project is suddenly scrambling to see who added the code, hoping...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime