-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Meta] Issue Organization #73
Comments
Hi @codello , thats a good suggestion. I'll change the labels accordingly since I came up with the lables.
I would like to have you for labeling, we can help each other out. And yes, we need some suited issue templates. @basisbit could you give codello the rights to add labels in this repo? |
@codello I've updated the public project. Can you see it? Everyone should see it:
|
Thanks @marwin89. I can see the public board and will have a more detailed look at it later. I don't currently have permissions yet to update anything (neither in the board not labels for issues). |
@marwin89 I guess the GitHub role |
@basisbit , yes triage is good. + I would like to have @codello also update the project, I'm not sure if this requires him to be a member of ultrastar deluxe organization. At the moment I can't add him to the project "UltraStar Song Format (Official)", but for instance @Baklap4 - so maybe give him the same rights like Baklap4? 🤔 |
pending invite ✅ |
Accepted, thank you! I don't yet have write access to the project, @marwin89 maybe you are able to add me now? |
@codello yes, now I was able to add you to the project. ✅ Do you need anything else? Otherwise I would close this issue. You can re-open if needed. |
The issues in this repo relate to different parts of the UltraStar ecosystem. Many issues of course deal with the specification of the file format but there are others that deal with the website (#12, #41), with tooling (#18, #52) or with processes related to the file format (#32, #66). I would like to suggest that we make more use of labels to differentiate these kinds of issues.
Currently labels are used inconsistently (at least as far as I can tell). Some things are labelled as "new feature", some as "improvement" and others not at all. The "in-discussion" label seems a little redundant to me. On the other hand the "vote now" label is used consistently which is very good I think.
I think a more coherent labeling strategy can help find current and past issues. This could also be a good opportunity to create appropriate issue templates as I think the current ones (Bug Report / Feature Request) are more fitting for development of a software instead of a specification.
Once a labeling strategy is established, I'd be happy to create a PR for some issue templates. I can also provide a more extensive description of how I would envision labels being used in this repo (but maybe that's something for the maintainers to decide and doesn't need to be a public discussion?).
I'd also like to use this opportunity to offer my help in labeling/triaging issues if this help is wanted.
The text was updated successfully, but these errors were encountered: