Reading through this thread, I've been introduced to a lot of excellent takes on this issue that I hadn't thought about before. In thinking about how to balanc

Reading through this thread, I've been introduced to a lot of excellent takes on this issue that I hadn't thought about before. In thinking about how to balance the two sides, I wonder if maintaining a master branch and a "community" branch would be one way to do it; all pull requests for new features could be added to the community branch, and the branch would always contain all the features of the master, but with the caveat that community would be untested. This would allow me to focus on the project goals as I see fit, but rely on the community to bug test and update the additional features. It would offload the work of maintenance without the need to split the codebase for every single individual feature request. Curious if something like this is used for any larger projects! I'm sure it wouldn't always work but maybe on certain types of projects it could.