Give the CSSWG a custom triage heuristic.

[jyasskin]

Since they don't have any auto-labeling system or
issue templates, if an issue has a label, then
someone with the ability to triage it has touched
it, so we can consider it triaged.

Fixes #22.

@fantasai, @astearns, this takes CSS from 733 untriaged issues to 51. Does this seem like the right change to make instead of marking all open issues with Priority: Eventually?

https://speced.github.io/spec-maintenance/w3c/csswg-drafts/ vs

w3c/csswg-drafts Issues

• 51 out-of-SLO untriaged issues
• 10 issues on the agenda that have been waiting too long

Untriaged

• Add 'Privacy and Security Considerations' section: out of SLO for 7.7 years
• Using <i> elements as <dfn> autolinks: out of SLO for 6.9 years
• [extend-rule] : out of SLO for 6.4 years
• CSSWG specs need usable test suite docs: out of SLO for 6 years
• [css-???] Standardise a binary representation for CSS: out of SLO for 5.3 years
• Small problems with CSS, JAVA & HTML that seems not possible without photo editor: out of SLO for 4.9 years
• Separation of style and content: out of SLO for 4.9 years
• Composing class names inside media queries: out of SLO for 4.7 years
• [css-icon] CSS isn't used for icons - it should be: out of SLO for 4.5 years
• Need a definition for what it means for something to be painted on screen: out of SLO for 4 years
• [resize-observer-1] Invoke callback with observer as 2nd argument and this value: out of SLO for 3.6 years
• [web-animations-1] Add hold phase to animation #4325: out of SLO for 3.5 years
• [css-animations-2] Describe behavior for changes to animation-timeline: out of SLO for 3.3 years
• [css-transforms-1] Fix mistakes in Example 5 (closes #4767): out of SLO for 3.3 years
• [css-transforms-1] Fix 5520: out of SLO for 3.3 years
• [scroll-animations-1] Specify liveness of element references: out of SLO for 3.2 years
• [css-font-loading-3] Remove unused ForEachCallback: out of SLO for 3.2 years
• [css-cascade-5] Fix cross-link to CSSOM-1 for "final CSS style sheets" concept: out of SLO for 2.6 years
• [css-transitions-1] Define before/after-change style in terms of base: out of SLO for 2.4 years
• [css-pseudo-4] [css-highlight-api-1] Integrate custom highlights into css-pseudo-4: out of SLO for 2.3 years
• A proposal for controlling screen brightness: out of SLO for 2.1 years
• CSS Toggles Proposal: out of SLO for 2.1 years
• [css-toggle] scope enum bikeshed: change from narrow/wide to shallow/deep: out of SLO for 2.1 years
• Give authors the ability to style form validation messages: out of SLO for 1.9 years
• [mediaqueries-5] Move the definition of display-mode back to APPMANIFEST. Closes #7306.: out of SLO for 1.8 years
• [css-nav-1] Scope event definition to target interface: out of SLO for 1.7 years
• [css-scoping-module]: host-selector specificity replication removal: out of SLO for 1.5 years
• Define guidelines for preprocessors, libraries, frameworks: out of SLO for 1.5 years
• [css-contain-2] Improve definition of contentvisibilityautostatechange event: out of SLO for 1.5 years
• [css-contain-2] Adds missing attribute values. : out of SLO for 1.3 years
• [resize-observer] Update initial value of lastReportedSizes #3664: out of SLO for 1.3 years
• why mediaqueries?: out of SLO for 1 year
• [css-scroll-snap-2] scroll-start clamps to scroll range not scrollpor…: out of SLO for 8.9 months
• Allow authors to configure a few settings from within CSS (CSS @config): out of SLO for 7.1 months
• [css-contain-3] Define the block contents of @container with <rule-list>: out of SLO for 6.2 months
• [web-animations-1] Define 'start time' for animation effects: out of SLO for 6.2 months
• [selectors-4] Replace :user-valid/:user-invalid definition with HTML spec: out of SLO for 5.7 months
• [web-animation-2] Avoid using a dictionary for range in animation IDL: out of SLO for 5.4 months
• [css-pseudo-4] Add discussion of properties from the originating element: out of SLO for 4.9 months
• [css-syntax-3] Rename <an+b> to <an-b>: out of SLO for 4.4 months
• [css-cascade-5] page and view-transition at rules should cascade: out of SLO for 3.4 months
• [css-logical] Add block-start and block-end values to caption-side property: out of SLO for 3.2 months
• [css-pseudo-4] Clarify text decorations in ::spelling-error and ::grammar-error: out of SLO for 3.1 months
• [cssom-view] Add 'onmove' event handler for the Window object: out of SLO for 2.9 months
• [css-view-transitions-1] Defer restoring persisted state until after capturing old state: out of SLO for 2.8 months
• [cssom] [css-fonts] [css-page] Sort out properties and descriptors.: out of SLO for 2.6 months
• [css-shapes][editorial] Define production rule for <basic-shape>: out of SLO for 2.3 months
• [css-shapes-2]: apply minor comments to shape() syntax: out of SLO for 1.4 months
• New property to control the direction of slider controls: out of SLO for 1.2 months
• improve styling of <details>/<summary> elements: out of SLO for 3.9 weeks
• [css-sizing-4] Define stretch sizing properly, rather than (incorrectly) indirecting thru stretch alignment.: out of SLO for 3.4 weeks
• [cssom-1] Simplify setting MediaList.mediaText: on maintainers' plate for 4 days
• [css-ui] Changing UA styles based on the computed value of the appearance property: on maintainers' plate for 4 hours
• css-color unspecified target contrast ratios with contrast-color() should use the users preference : on maintainers' plate for 2 hours

[astearns]

Yes, I think this is a good change as these 51 are likely the most in need of attention. When we get through this list we can look at further updates. There is probably a set of issues that have a label (added by the original issue author) but where no one else has looked at them. That might be the next bucket to tackle.

I see that there are both issues and PRs in this list. Is that intended?

[jyasskin]

Yes, right now the tool treats issues and PRs identically, and I haven't found a reason to second-guess that behavior. :)

[svgeesus]

• Add 'Privacy and Security Considerations' section: out of SLO for 7.7 years

Fixed

[svgeesus]

And this one, which should have been closed in 2018

• Using <i> elements as <dfn> autolinks w3c/csswg-drafts#1230

[svgeesus]

And this one

• CSSWG specs need usable test suite docs w3c/csswg-drafts#2438

[svgeesus]

Also

• [css-???] Standardise a binary representation for CSS w3c/csswg-drafts#3334

[svgeesus]

Looks Good To Me