2 brainstorm ideas: Crowfunding and Musescore backlog (prioritized list of features to code next)
I have two ideas at a brainstorm level that are related to each other and that I would like to exchange thoughts about.
If I understand correctly one bottleneck in MuseScore development is the lack of programmers that actively and regularly contribute.
And another impression I got is that the backlog - the list of features to code next - is basically decided by those programmers, based on their own preferences and areas of expertise and time to allocate in the project.
One thing I wonder is if it would be possible to have an online backlog where users can vote which features to implement next. In this way would Musescore always implement the feature that a majority of people are missing at every moment. Maybe each user can vote for his top 5 desired features out of a list of 100.
And coupled to that, I wonder if it would be feasible to group the top...10 features ? 20 ? or so.. in a crowdfunding project so that Musescore can get money to hire extra developers required to code those features. And then repeate the procedure maybe once a year or more often.
The core development team of Musescore could do rough estimates of how many programmings hours a certain feature could take to an experienced senior programmer, and then estimate the cost for the feature.
There are many websites where freelancing programmers offers their services, and maybe the core development team of Musescore already know external consultants that could be hired for a certain feature implementation.
What do you think ? Is such thing realistic? feasible ?