You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 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.
The text was updated successfully, but these errors were encountered:
Would it make since to use the GitHub Milestones feature for the things listed in the Milestones section? That would allow grouping of issues and a progress bar interface for easy reference.
So...a milestone might be named "FPWD - specname" where specnameis the short name of the specific (when that's even needed).
I do think the consistent naming and prefixes are helpful.
(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:
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.The text was updated successfully, but these errors were encountered: