GET INVOLVED

Bring what you know.
Help build what comes next.

You don’t have to write code to contribute. Experience with music, teaching, testing, words, and design all brings something useful to the project.

Musicians & educators

Share a need.

Describe something you want to do, your current approach, and where it gets difficult. A concrete example helps others understand the problem.

Testers

Make a problem clear.

When a test build is available, record the version, setup, steps to reproduce, and what you expected compared with what happened.

Writers

Make the next step easier.

Notice an unclear explanation? Suggest simpler wording, define an unfamiliar term, or outline an example that would have helped you.

Designers

Bring a fresh perspective.

Look for unclear controls, navigation barriers, and accessibility needs. Explain the task and why a proposed change would help.

Developers

Investigate and improve.

When source and issue links are available, read the repository’s contribution guidance, reproduce an issue, and discuss a focused change.

A USEFUL FIRST STEP

Start with one real example.

Note the task, who it matters to, and what could work better. Public contribution channels are still being prepared; this page will link to them when they’re available.

Get to know the tools