replaces tracking bug T2209: [DO NOT USE] HTML validity (tracking).
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T192655 Replace all "tracking" tasks with tags/projects (if unbounded), relabel them to outcome tasks (if bounded), or kill them entirely (if pointless) | |||
| Declined | None | T102492 Replace tracking bug T2209 by new project tag "HTML" |
Event Timeline
Comment Actions
I don't think the HTML is the best name here.
We have other tracking bugs which would fall under such general name like T21719: [DO NOT USE] HTML5 features (tracking) [superseded by #HTML5], T12467: Use semantic HTML (tracking), T4542: [DO NOT USE] HTML Tidy issues (tracking) [superseded by the #Tidy tag]
Comment Actions
I'm not sure even "HTML validity" would be useful to track. Just as much as "PHP" isn't useful, it's too generic and not actionable in a way that others aren't already.
Bugs relating to HTML validity should be filed under their respective component and/or team tags.
If the objective is to allow discovery of easy tasks, we've got good first task for that already.
Comment Actions
I also propose to decline this (and close that tracking task). Feels very generic. I'm happy to stand corrected if someone can offer use cases why someone would "start" from the workboard of such an "HTML[-validity]" project tag to do... something?