Skip to content
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: improve issue tracker #26882

Open
gterzian opened this issue Jun 12, 2020 · 5 comments
Open

Meta: improve issue tracker #26882

gterzian opened this issue Jun 12, 2020 · 5 comments

Comments

@gterzian
Copy link
Member

@gterzian gterzian commented Jun 12, 2020

I think it might be a bit hard for someone not deeply involved in the project to understand what the status of an open issue is.

I'm thinking people not looking for a "first issue", or for something with mentoring available, since those issues will be pretty clear, rather all the other issues that are opened, and sometimes comes with a bunch of comments but it's not clear what their status are.

In particular, it might be hard to know whether it's worth trying to fix the issue based on what has been written in it, or whether it's still effectively being triaged.

Perhaps we should add some labels, so someone wanting to work on an issue as a clearer idea of what to do(either further triage the issue, or actually start working on it based on the comments in the issue?)

@gterzian
Copy link
Member Author

@gterzian gterzian commented Jun 12, 2020

As an example: #26876

Based on my comments, I'd like to add some label like "triaged" or "has-potential-solution", something labelling the issue as something that has a proposed solution and that could be picked-up by someone wanting to work on it(but it's not necessarily as "easy" issue).

Then again, let's say someone disagrees with my comments, the "in-triage" label could be re-added and the labels I would have added removed.

Currently this is still possible to understand by reading the comments, but that requires some knowledge of the context I think, and it's also not filterable by people looking for a well-triaged issue to work on.

@CYBAI
Copy link
Collaborator

@CYBAI CYBAI commented Jun 12, 2020

My personal perspective is, it might be good to have a C-needs triage label.

In my understanding, A- labels like A-input, A-content/dom and so on are for triage so contributors should be able to know what the issue for by the A-label.

However, when it's an issue which has its own upstream, we might be able to add a new label like S-blocked-on-external for it? (IIUC, we will need to fix #26876 to webrender?)

I think adding a C-has potential solution (like C-has patch but not has a patch yet) is good which should let everyone know there's a potential solution in comments.

(btw, we might want to update https://github.com/servo/servo/wiki/Tag-label-names-and-definitions wiki page to align our existing labels?)

@atouchet atouchet added the B-meta label Jun 12, 2020
@jdm
Copy link
Member

@jdm jdm commented Jun 12, 2020

I agree, it sounds like it could be useful to have a label that means "there's a description of a possible solution".

@gterzian
Copy link
Member Author

@gterzian gterzian commented Jun 13, 2020

a label that means "there's a description of a possible solution".

How about C-ready-for-assignment?

@gterzian
Copy link
Member Author

@gterzian gterzian commented Jun 14, 2020

How about C-ready-for-assignment?

There is already a C-looking-for-assistance, which could be used for that purpose. Also there is a C-needs-investigation, which could be used to mark as an issue that, well, requires more investigation/triage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.