> If you have enough users to have "too many issues to handle," then you're big enough that you need an official governance and contribution structure I'm sure

> If you have enough users to have "too many issues to handle," then you're big enough that you need an official governance and contribution structure I'm sure e.g. Ruby on Rails and Bootstrap would like some pointers on how to setup "an official governance and contribution structure" to handle their the long issue and PR lists. > Why refuse to let other people help? Very few if any wants to use their free time to work through an issue list like that. Someone might do it once and write a blog post about it, but unless someone does it all the time it does not help much. Open source might be perceived as a free commodity, but like a public toilet, no one likes to cleanup and especially for free. Likewise, help in the form of P.R.s doesn't much help either unless it is aligned with the overall vision of the project. It more often than not isn't.