The document discusses taking over open source projects from their original creators. It emphasizes the importance of finding a competent successor to hand off a project to once interest is lost. It provides tips for taking over a project such as organizing it, creating a workflow, recruiting contributors, making releases, and always making progress to build a reputation of caring for the project and its community. The overall message is that open source projects need ongoing leadership and care even after their original creators move on.

1. loving
managing resurrecting
inheriting
rebooting
caring
Taking Over
Someone Else’s Open Source Projects
Daniel Doubrovkine
@dblockdotorg

2. All characters appearing in this
work are fictitious. Any
resemblance to real persons,
living, dead or imprisoned, is
purely coincidental.

5. "When you lose interest in a program, your
last duty to it is to hand it off to a competent
successor.”!
!
- “The Cathedral and the Bazaar”, Eric S. Raymond

7. I (we) need it.

8. No

9. Nobody wants to be in charge.

10. Step up.

11. Get in touch.

12. People are human.

13. Fork it.

14. Own it.

15. .com !
.io

18. Real work begins.

19. Organize it.

31. Recruit the hopeless.

32. Make a release.

33. Pickup everything.

34. Create workflow.

35. A reputation of caring.

36. Create owners.

37. Ignore chickens.

38. Always make progress.

41. “We have more source code
than we need.”

42. Thanks!
Community.
@dblockdotorg / dblock@dblock.org / artsy.net