| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| spec:issue-tracking [2014/12/09 15:48] – external edit 127.0.0.1 | spec:issue-tracking [2018/04/25 09:41] (current) – [Where to Track Issues] chrisl |
|---|
| Issues are tracked in the CSS Working Group by the spec editors using one of the following mechanisms (per the editors' preference): | Issues are tracked in the CSS Working Group by the spec editors using one of the following mechanisms (per the editors' preference): |
| |
| | * [[https://github.com/w3c/csswg-drafts/issues|GitHub issues]] (preferred) |
| * [[:spec|Wiki]] (fantasai notes from experience that if you track all issues in one page, it will eventually get [[:spec:css2.1|unweildy]], so consider a method for using sub-pages) | * [[:spec|Wiki]] (fantasai notes from experience that if you track all issues in one page, it will eventually get [[:spec:css2.1|unweildy]], so consider a method for using sub-pages) |
| * [[http://w3.org/Style/CSS/Tracker/|Tracker]] | * [[http://w3.org/Style/CSS/Tracker/|Tracker]] (historical) |
| * [[http://www.w3.org/Bugs/Public/|Bugzilla]] | * [[http://www.w3.org/Bugs/Public/|Bugzilla]] (historical) |
| * Inline in the spec itself | * Inline in the spec itself (please avoid for non-trivial issues) |
| |
| Each spec has a link in its header to where issues are tracked for the draft (e.g. see "Issues List:" in header of [[http://dev.w3.org/csswg/css3-ui/|CSS3-UI editor's draft]]). If all issues are tracked in the draft itself, this points to the editor's draft. | Each spec has a link in its header to where issues are tracked for the draft (e.g. see "Issues List:" in header of [[http://dev.w3.org/csswg/css3-ui/|CSS3-UI editor's draft]]). If all issues are tracked in the draft itself, this points to the editor's draft. |
| |
| In some cases, the issue is more complicated and some back and forth is required. But at some point, there should be a final response that represents the editors' (or WG's) position, requests confirmation that it's acceptable, and gives the commenter enough information to make an informed decision about whether that position is acceptable. | In some cases, the issue is more complicated and some back and forth is required. But at some point, there should be a final response that represents the editors' (or WG's) position, requests confirmation that it's acceptable, and gives the commenter enough information to make an informed decision about whether that position is acceptable. |
| | |
| | There is a [[https://wiki.csswg.org/tools/doc|Disposition of Comments tool]] to manage and present the Disposition of Comments |
| |
