- MuseScore source code is available at GitHub (commits feed). The preferred way to contribute is via Pull Request. Read our Git Workflow page to learn how to make a pull request. You need to sign the MuseScore CLA for your request to be merged.
- Developers' handbook: All information regarding MuseScore development (including build/compile instructions for supported OS). If you have a musescore.org account, you can change these pages in a wiki style. Be bold and add your knowledge.
Plugin development: Reference information for writing MuseScore plugins (for 1.3 and older only)
Get help from other developers
To make your first contribution, or to talk about something you want to do to MuseScore, you can contact the other developers.
- Developer mailing list: Get in touch with all the MuseScore developers
- Developer IRC: Chat room '#musescore' on IRC network 'freenode'
Issue tracker: Post and track MuseScore bug reports, feature requests or tasks
If you are interested in helping test new features and for bugs, see comparison of stable, prerelease, and nightly builds. This helps improve the quality of the next stable release.
People all over the world use MuseScore, thanks to a vibrant community of translators. If you want to help with an existing translation, or start a new one, see the instructions below. Please ask any questions on the forums, or developers mailing list and share initial work - particularly to avoid further workload, should changes be required.
Handbook and website
If you are interested in translating the website, or the software manual, then introduce yourself on the Translation forum. We will then give you access to edit and create new pages for your language. Also see the extensive Translation instructions.
The MuseScore community uses a translation server, making it simpler to collaboratively localize MuseScore. If you want to start translating to a language that is not yet listed, leave a request on the Translation forum so the language can be added.