There are lots of examples out there, lots of frameworks that grew because of the community. Not only posting issues, but actually coding for the open-source platform.
Now, I’m sure there are lots of people, who can invest a bit of time in the platform they love, and help these guys out. From my understanding we currently have 2-3 FTE on Meteor. This is sad. Imagine there are 100 people that want to help, and invest 10-15 hours a month.
We need a Meteor documentation. Not how to use it, but how it is architected. The code is documented, but it took me so much time in order to understand how they did oplog… maybe because I’m a bit slow, I don’t know, but I now I think I know by heart the code in: https://github.com/meteor/meteor/tree/master/packages/mongo because I wanted to move oplog to Redis. https://github.com/cult-of-coders/redis-oplog
We need a “community-help” label for issues. So guys like @benjamn, @abernix, @sashko, etc can simply say: this is not a super important thing to do right now, we need it but later, so let others try and do it “Community Help”, and leave a small guide-line on what to tackle, where to look. I would really like to do that in my spare time! Ofcourse, if writing the guide-line and time to explain it takes more than actually fixing it, maybe it’s not a good idea
Let’s discuss other ideas here. Thanks!