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

Stepping back comfortably

Even with the best transition plan done, it’s hard to “cold turkey” step back from a project. Stepping back is a gradual process, where the new maintainers and leaders can take over the activities while reducing their dependencies on the maintainers they plan to replace. Many maintainers tend to err on the side of caution when stepping back; after all, they put lots of energy and passion into the project and want to be certain that it will be in good hands (not always, of course; some maintainers might be so burnt out by the project that they are just thrilled to find someone to take it off their hands… hehe).

Presuming a maintainer wants to ensure a smooth transition, there are a few things they should do. We’ll look at them in the upcoming subsections.

Being appropriately available

The most important thing is to ensure their previous maintainers don’t completely disappear. But this has to be done with caution...

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 €18.99/month. Cancel anytime