Adding to Developer's Handbook

• Mar 12, 2016 - 18:03

I've been going through the MuseScore code base and working on figuring out which parts of the code do what, how the different parts interact, etc. Other than building and compiling, there doesn't seem to be a lot of documentation in the Developer's Handbook detailing the main code components for developers who are just diving in, and I was hoping to add more documentation in this area as I start to figure things out so that future developers might have an easier go. Would this be welcome? I'd probably need somebody more familiar with the project to review what I submit and ensure that I don't characterize anything incorrectly.


Comments

Do you still have an unanswered question? Please log in first to post your question.