You should! One of the biggest challenges for any open source project is to figure out how to become multi-generational and turnover-proof, instead of fizzling

You should! One of the biggest challenges for any open source project is to figure out how to become multi-generational and turnover-proof, instead of fizzling out when the initial developer generation moves on. There are a lot of lessons to learn about organization and governance to get to that point, and about how to recruit and imbue newcomers with a sense of shared responsibility and emancipate them to step up and take on that responsibility. I used to process many of the developer access rights requests for the KDE community for some time and wrote a few of the documents regulating that process, along with baking some of the things we learned into the KDE Manifesto. It took us a lot of thinking about the trust mechanics involved and has definitely been among the most rewarding things I've done in FOSS so far. And I'm really happy we've consistently been one of the largest organizations to participate in things like GSoC and Code-In (in number of students) and try to do a lot of mentoring in general.