Labels
Labels
85 labels
- Issues related to accessibility
- PRs that have gone stale but could potentially be revived in the future
- Blocked by external circumstances or third parties
- Compatibility with physical braille hardware (e.g. braille terminals / refreshable braille displays)
- Accuracy or completeness of braille exported directly (not via MusicXML)
- Entering braille via 6-key input in the Braille panel
- Navigating in the Braille panel and/or keeping the braille position in sync with the score position
- Cosmetic or similar problems with the Braille panel, Preferences, or Export dialog
- Accuracy or completeness of braille shown in the Braille panel
- The behaviour is intentional. It's not a bug; it's a feature!
- Not reproducible by the internal team, or very difficult to reproduce by most testers
- Issues related to MuseScore's command line interface
- Issues relating to save scores to or managing scores in the cloud
- Issues particularly suitable for community contributors to work on
- Issues involving file corruption
- Issues involving a crash of MuseScore
- Pull requests that update a dependency file
- To be used for small bits of jank that shouldn't take much developer time to fix
- Related to developer experience (compiling, code base, CI), rather than end user experience
- Related to e.g. AppImage, FlatPak, Snap, 3rd-party packages, PortableApps.com
- Already covered by another issue / addressed in another PR
- Shape, position, or ability to notate musical symbols & text in the score
- Used to suggest improvements or new capabilities
- How data is stored in or retrieved from our native score format (MSCZ & anything inside it)
- Pull requests that update GitHub Actions code
- Issues suitable for first-time contributors. See https://github.com/musescore/MuseScore/contribute
- Expected to be doable for contributors with a little bit of experience with our codebase