Just to raise the embers a little bit: our idea was to create a win-win-win situation for maintainers, new contributors and the community. On the one hand there might be maintainers and experienced contributors dedicated to demanding activities for the Project (infrastructure, packages, web development, communication, promotion) but with too much on their plate to fully enjoy what they do, or who'd like to do more but cannot afford to because they only have time or energy to keep things functional. On the other hand there might be potential volunteers a bit overwhelmed by the perspective of onboarding an already running activity, or who don't really know what there is to do, or who simply need to be shown the basics. And finally there is the Project, with integration issues, navigability issues, promotion issues and a huge stock of very well intended people kind of waiting at the gates (from what I've experienced on Telegram, Reddit, Discord). So our idea is to try out a different approach, with workshops, sprint sessions and possibly, encouraging a "mentor <-> apprentice" model in some key areas. Each of these social event can be a test-bed for the next: if workshops do well, can try sprint sessions, which if they go well, can be considered a reason in favor of a mentor-apprentice workflow. Coming back to Doug's post: if we do this, we need to make sure there is enough people involved in these important activities willing to share their experience and skills in a pedagogical setting, in one of these 3 ways mentioned above, and for now especially workshops. The time they invest now is likely to be repaid several times over in the long run. And that scales up community-wide, we're talking exponential benefits in terms of securing oS's future.