User:ApeKattQuest, MonkeyPython/INSTwave

instead of vaporwave

FISHWAVE! no. Instrument addition stuff!

first the ticket must be selected. usually I square related things of in "mini-version" type ticket, where related tickets are subtickets of that.

• for new instruments we have new feature/sub-newfeature
• for tickets that require updating or changing, description or adding aliases we have improvement/sub-newimprovement
• for actual errors we have bug
• task is seldom used but occasionally for large unspecific things like "research the difference between these concepts or "translate this wikipage"

when closing the ticket thus status is used

• for fixed finished tickets, just "fixed" and a comment with a link to the finished instrument if adding a new one/description of what has been done (eg "added all aliases and fixed description")
• for tickets that are duplicates, just "duplicate" and close them while pointing to the one we have in a comment and linking it "as a duplicate" of that one. recently I've also been upping the priority of tickets which receive duplicates.
• for tickets which are deemed to not be added (usually these are novelties (link to see how to add $ novelties)) just "won't fix" with a comment explaining why and a link to the appropriate guideline.
• if the ticket does not have enough information and a search on the internet has yielded no usable information, i close it with "incomplete" these can always be reopened if someone has more information and adds it!
• for situations where something is totally not actionable by me, not an instrument ticket etc, it would be closed as "invalid" (this doesn't happen very often and usually the ticket should be *moved* to the appropriate project)

ticket should have at fixing closing have a comment with a link to the instrument and the instrument add on musicbrainz should have a link to the associated ticket.