Comment on the proposed labels
Open
Nobody has claimed this yet.
enhancement
question
- Dominant language
- HTML
- Stars
- 148
- Forks
- 41
- Avg merge
- 1m
- Merged PRs (30d)
- 7
Description
(Ie, on https://w3c.github.io/issue-metadata.html)
While adopting the labels, I have made two changes for the repository; I would think it is better:
- (this is minor) I have added the label 'propose closure': ie, proposal to close an issue (but the WG has to accept this). This procedural step has proven to be fairly useful in some groups where we worked with github
- the proposal contains over 30 labels, it is not easy to find one's way through them. I have systematically added a prefix to the main categories, ie,
hr:for horizontal review,ms:for milestones, etc. For consistency, I also usedwr:instead ofWR-for wide review. I think such prefixes help a lot; eg, it allows a proper alphanumeric sorting of the labels.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the proposed labels at https://w3c.github.io/issue-metadata.html and comparing them with the two repository changes described in the issue. Done means the maintainers have decided whether to adopt the “propose closure” label and the category prefixes; the issue does not name implementation files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100