I also worked on an open source project that grew enough that people started to demand lot of features, the author there took an amazing decision, he asked everyone to split up the work to be able to sustain the development.
  • When someone asked for a feature he asked who he knew to be knowledgeable to discuss it, then he waited till get enough people consensus.
  • Then he asked some developers to work on it if he couldn't, they all where external, so it has flaky participation but had always enough people taking over.
  • Once everything was done he left the pull request review to another party again, often including the ones asking and discussing the feature.
  • When everything was done, the merge was done by him after everything was covered by the unit tests he required to have from the other developers.
He basically decentralised the development, so he could keep going on holidays with his family and relax when he wasn't working on features he wanted himself.
This is but one way to do things, this goes as a mix-and-match for each of us, but I think we should look more at how every growing project take on the management to learn a bit more ourselves.