Re: [jlreq] Coordinate github labels for discussions and notes (#248)

I would like to keep labels as simple as possible to reduce the maintenance work.

- re:‘jlreq’: Currently jlreq document related issus are tracked by three labels, ‘errata‘, ‘editorial‘ and ‘future‘ (and ‘amendment’?), depending on the scope of the change. The proposed ‘jlreq’ label is meant to be attached whenever one of these labels are used in order to build a hierarchical label structure. I would instead propose to attach “jlreq-doc:” (or jlreq-documents:) prefix to the names of existing labels. This way it is clearer that these labels are meant for future revisions of the jlreq document. This way you do not need to make sure to attach two labels e.g. ‘errata’ and ‘jlreq’, whenever you create a new issue, and you do not need to do a regular maintenance of making sure if ‘jlreq’ is attached as expected.
- re:’note’: In the mailing list there are cases that Bin-sensei or other members post a good summary of a subject, and they are worthy of translating and archiving on GitHub. These are not “issues” but references that people can look at or refer to when related issues arise. Also they can be good candidate materials for future update of jlreq document. I would suggest to label them “reference-materials”. This way it is crystal clear the purpose of these gh issues. ‘notes’ I think is too generic. I do not think we can translate all notes that are potentially worthy of translating but we would try to handle at least important ones.


-- 
GitHub Notification of comment by kidayasuo
Please view or discuss this issue at https://github.com/w3c/jlreq/issues/248#issuecomment-831163557 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 3 May 2021 10:13:25 UTC