Peter raises an point about how to move forward. I was very active with MuseScore around 2008-2013. These days I'm busy with other things and have less time for MuseScore. All that to say that my advice may need updating by others who are more involved right now.
Generally, it is best to start with a very small improvement in the area that you are interested in working on. That way you'll get to know all the key players in your area and they will get to know you and your work first hand. You'll also get to walk through the who process with a relatively simple code improvement (which means faster review times, etc.). Historically (pre-2010) Werner Schweer was the key decider for all things code. At the time he had written the vast majority of the codebase (more than 95 percent). He occasionally chimes in on discussions but usually prefers to focus on coding. He continues to be the lead developer. Nicholas Froment (who goes by the online nickname Lasconic) is probably the second biggest coder, and very active on IRC and discussions. If Lasconic approves of what you are doing, it is a very good sign. Nicolas is the Chief Technology Officer. Thomas Bonte is the other key decision maker but most of his decisions related to musescore.com, translations of the software and documentation, the website infrastructure, and promoting MuseScore and MuseScore.com as the Chief Executive Officer. For more about these people see: https://musescore.com/team Then there will be key decision makers for specific areas of musescore. A good way to identify them is to look at who has made code contributions in the areas you are interested in. Eventually it may be a good idea to collect these names in a document similar to what we have done for distribution maintainers: https://musescore.org/en/developers-handbook/distribution-maintainers David On 4/9/2016 11:25 AM, Peter Eastman wrote: > I really need to know whether and how to move forward with this. I think it > would be a useful feature. It's certainly one that I would like to have! > But I haven't gotten a lot of encouragement, much less advice on how to > design/implement it. I'm not sure how to interpret that. > > I don't really understand how the MuseScore development community works. Is > there someone who's in charge? Who are the core developers? How do > decisions get made? > > Perhaps this proposal doesn't fit with their vision for the product. If so, > that's fine. I totally understand. I just need to know! I don't want to > put a lot of work into this, only to find out that it will never be used. > On the other hand, if I am going to move ahead with this, I need to discuss > the design and implementation with someone who knows the code much better > than I do. > > I'm just not sure where things stand, or what I should be doing now. I need > clarification. > > Thanks! > > Peter > > > > -- > View this message in context: > http://dev-list.musescore.org/Playback-abstraction-layer-tp7579762p7579780.html > Sent from the MuseScore Developer mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > Find and fix application performance issues faster with Applications Manager > Applications Manager provides deep performance insights into multiple tiers of > your business applications. It resolves application problems quickly and > reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/ > gampad/clk?id=1444514301&iu=/ca-pub-7940484522588532 > _______________________________________________ > Mscore-developer mailing list > Mscore-developer@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mscore-developer > ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/ gampad/clk?id=1444514301&iu=/ca-pub-7940484522588532 _______________________________________________ Mscore-developer mailing list Mscore-developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mscore-developer
