w3c / w3c/w3c.github.io

Comment on the proposed labels

Open
#46 1 comment 0 reactions 0 assignees View on GitHub

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:

  1. (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
  2. 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 used wr: instead of WR- 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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.