- From: Chris Lilley via GitHub <sysbot+gh@w3.org>
- Date: Tue, 23 Jan 2024 20:07:59 +0000
- To: public-css-archive@w3.org
> The countervailing pressures are that 1) it'd be good to align on some common labels that all web groups can share, and 2) my summary dashboard is going to have to simplify the structure to fit all groups into a common display. Oh, absolutely. And my strong preference is that all groups use the exact same spelling and the same colors for those labels, too. People in multiple groups with be glad of the usability boost that provides. > Or we could decide that if an issue needs feedback from non-WG folks, and the WG doesn't think it's important enough to actively hound those folks to finish the feedback, then the issue probably shouldn't have a WG-side SLO. Right, in some cases an issue is open because "it would be nice to let this implementer know" or "that survey of web technologies might usefully gather stats on feature foo, next year" and I don't want that to negatively impact a SLO rating score, but also don't want such issues prematurely closed to boost the metric. > I also want to make sure we're clear on how many issues should have an SLO/deadline. I'd expect that most issues would _not_ have an SLO, and you'd intentionally mark an issue as urgent or important when the right stakeholders agree to work on it more intensely. That wasn't clear, so thanks for saying so. Also in the interests of being clear: I think the overall idea is _great_, and love how it is data driven based on analyzing GitHub issues across all of W3C (and beyond). But I am also aware that once a thing is important, and gets an automated metric, mostly people focus on improving the metric not improving the thing, which can lead to antipatterns like premature issue closure, not using tags like **"Needs more tests"** that would delay closure, and so on. So I want to help get it right. -- GitHub Notification of comment by svgeesus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9820#issuecomment-1906839576 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 20:08:02 UTC