- From: Chris Lilley via GitHub <sysbot+gh@w3.org>
- Date: Tue, 23 Jan 2024 12:03:56 +0000
- To: public-css-archive@w3.org
Firstly, yes we need something like this and there are issues and PR that are severely outstanding. Now on to the details: I see that CSS WG is listed as having "no triage labels" which I presume means we don't have _all_ of the ones [listed](https://speced.github.io/spec-maintenance/triage-labels/). We do have, and use, triage labels **Agenda+** (and also others, which are not [listed](https://speced.github.io/spec-maintenance/triage-labels/)):  Notice that in addition to **Agenda+** we have **Agenda+ F2F** , **Agenda+ Whiteboard**, and **Agenda+ TPAC** (which means we need face to face time and a whiteboard, not just a phone conference. The TPAC one, and also **Agenda+ I18n**, also imply the need for cross-working-group discussion. Which is one special case of something which seems to be missing from the proposed organizational scheme: _multi-stakeholder consensus_. One could easily add **Agenda+ A11y** or **Agenda+ Privacy** for example, for common pairwise groupings. But, and I am thinking specifically of [one long-running example here](https://github.com/w3c/csswg-drafts/issues/5421), there are cases where an issue is blocked, for _years_, because (in this case) I18n wants one thing, and Privacy wants the exact opposite thing, an we can't move forward because _all_ the proposed solutions fundamentally disenfranchise some group of constituents. Which brings me to another example: **Needs Reporter Feedback.** I agree by the way that this label is needed. But again it implies a simple two-party stakeholder situation: the reporter, and the WG. More commonly, in my experience, is that an issue (and even potential solution) is raised by a reporter from Implementer **A**, and what we need is feedback from Implementers **B**, **C** and **D** which is what takes the time as issue prioritization is not the same among all implementers. Often an issue has been around for a while but internally **A** suddenly promoted it to super urgent and needs a solution like, yesterday so they can ship it while **B** is _working on it_ but with a 3 to 6 month timescale and **C** doesn't want to do it _at all_ but certainly doesn't want the WG to settle on the solution proposed by **A**. -- GitHub Notification of comment by svgeesus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9820#issuecomment-1905895770 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 23 January 2024 12:03:59 UTC