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

[housekeeping] Reorganise github labels #233

Closed
carlosjeurissen opened this issue Jun 23, 2022 · 2 comments
Closed

[housekeeping] Reorganise github labels #233

carlosjeurissen opened this issue Jun 23, 2022 · 2 comments
Labels
status: duplicate Duplicate issue

Comments

@carlosjeurissen
Copy link
Contributor

carlosjeurissen commented Jun 23, 2022

The labels can use some cleanup and structure. Currently we have:
agenda, bug, Chrome: follow-up, discussion, documentation, duplicate, enhancement, future topics, good first issue, help wanted, inconsistency, invalid, question, spec clarification, task, topic: automated testing, topic: csp, topic: remote code, topic: secureStorage, topic: service worker, wontfix

My proposal is to start with removing the following unused labels:
bug
duplicate
"help wanted"
wontfix

And start prefixing similar labels to increase structure. Starting with
api: someApiName labels
These labels are used for specific APIs, like secureStorage, action.

Then we have the status labels. Which can include:
status: needs-discussion, status: consensus-reached, status: widely-implemented and status: needs-mv-upgrade
Related issue: #205

This issue is created to start the discussion on how we can better organise the community labels.

@Rob--W
Copy link
Member

Rob--W commented Jun 23, 2022

I've removed "bug" and "help wanted" since they're clearly not useful for this repo.

"duplicate" and "wontfix" are potentially meaningful, but since there are no existing issues with the label, and the there is no real value in tracking these statuses separately, I've just removed it.

@xeenon
Copy link
Collaborator

xeenon commented Aug 31, 2022

Lets use #244 for this going forward.

@xeenon xeenon closed this as completed Aug 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: duplicate Duplicate issue
Projects
None yet
Development

No branches or pull requests

3 participants