Re: New "need something" labels for issue triaging

Probably it should have been "needS something" but anyway...

On 20/05/2019 19:51, Neil Soiffer wrote:
> Thanks for the summary and also starting the labeling processes!
> That's the workflow I had in mind (especially you doing the work :-)
>
>     Neil
>
>
> On Thu, May 16, 2019 at 2:34 AM Frédéric Wang <fwang@igalia.com
> <mailto:fwang@igalia.com>> wrote:
>
>     Hi all,
>
>     As agreed in a previous meeting, I've created new labels for issue
>     triaging. Not that you can also filter out issues by label e.g. to
>     exclude those that have not been resolved yet:
>
>     Resolved issues needing specification update:
>     https://github.com/mathml-refresh/mathml/issues?q=is%3Aopen+is%3Aissue+label%3A%22need+specification+update%22+-label%3A%22need+resolution%22
>
>     Resolved issues needing tests:
>     https://github.com/mathml-refresh/mathml/issues?q=is%3Aopen+is%3Aissue+label%3A%22need+tests%22+-label%3A%22need+resolution%22
>
>     Resolved issues needing polyfills:
>     https://github.com/mathml-refresh/mathml/issues?q=is%3Aopen+is%3Aissue+-label%3A%22need+resolution%22+label%3A%22need+polyfill%22
>
>     Resolved issues needing implementation update:
>     https://github.com/mathml-refresh/mathml/issues?q=is%3Aopen+is%3Aissue+-label%3A%22need+resolution%22+label%3A%22need+implementation+update%22
>
>     Here is a proposed workflow:
>
>     (1) When an issue is put on an agenda and require to reach a
>     consensus,
>     one should set the "need resolution" label. Note: there are "need
>     resolution" issues that are not being discussed yet, I plan to put
>     them
>     in a future agenda.
>
>     (2) After a consensus is reached, one should remove the "need
>     resolution" label, put a comment about the decision (with reference to
>     minutes from https://lists.w3.org/Archives/Public/public-mathml4/) and
>     set all the other "need something" labels if they have not been set
>     already (in the doubt, please set all the labels so that someone else
>     will check later).
>
>     (4) Before removing "need tests" labels, one should land/update WPT
>     tests to https://github.com/web-platform-tests/wpt or explain why
>     that's
>     not needed.
>
>     (5) Before removing "need polyfills", one should land/update a
>     polyfill
>     to https://github.com/mathml-refresh/mathml-polyfills or explain why
>     that's not needed.
>
>     (6) Before removing need "specification update" one should ensure the
>     proper changes are done in the
>     https://github.com/mathml-refresh/mathml-core and
>     https://github.com/mathml-refresh/mathml (text, RelaxNG schemas,
>     operator dictionary etc) or explain why that's not needed.
>
>     (7) Before removing "need implementation update", one should
>     ensure the
>     proper changes have been made in Gecko/WebKit/Chromium or explain why
>     that's not needed.
>
>     Arguably, implementation work is not really the business of the MathML
>     CG working group so I guess it's fine to close the issue when the only
>     remaining task is "implementation update". Rob and I will report
>     them to
>     Chromium/Mozilla/WebKit bug trackers and try to fix them when we can.
>
>     -- 
>     Frédéric Wang
>
>
>

-- 
Frédéric Wang