Tracker: Rename "Development" type to "DX" (for "Developer eXperience")
Reported version
3.x-dev
Type
musescore.org
Frequency
Once
Severity
S5 - Suggestion
Reproducibility
Always
Status
active
Regression
No
Workaround
No
Project
"DX" is short for "Developer eXperience". It is analogous to UX (User eXperience), but it mainly affects developers rather than users. The DX type would be used for issues that aim to make it easier to build and maintain MuseScore's code.
Developer experience doesn't affect users directly, but having good DX can lead to faster development of features that do matter to users, and less time wasted fixing build errors, etc.
Build errors are not DX issues, but they might be symptoms of DX issues.
Comments
It turns out that "DX" issues might be covered by the existing "Development" issue type. However, "Development" is a generic terms that could apply to any issue, and judging by the wide range of existing Develoment issues, there seems to be a considerable level of confusion about what it should actually be used for. Therefore, I propose renaming the "Development" issue type to "DX" to make it clear that it tracks things that are more important to developers than users.
I've cleaned those up ;-)