W3C home > Mailing lists > Public > public-tracking@w3.org > September 2013

logistics for gathering new change proposals

From: Nicholas Doty <npdoty@w3.org>
Date: Tue, 17 Sep 2013 00:59:27 -0700
Message-Id: <EE439DCD-935A-406E-927A-F570DA6B7E84@w3.org>
To: "public-tracking@w3.org List" <public-tracking@w3.org>
Also, hello again WG, I promised on Wednesday's call to write up logistics for gathering new issues/change proposals.

The chair has asked for any new issues, with change proposals, by October 2nd [0][1]. To manage any additional change proposals, we will use a similar process to that executed in June [2].

# Adding a new change proposal

If you have a new change proposal, please:
 1) send that proposal to the public-tracking mailing list (and CC npdoty)
 2) note in the subject that this is a "new change proposal"
 3) provide a clear rationale for the change
 4) clearly note the text change from the current editors' draft
 5) if your proposal draws on an existing issue, identify that existing issue by number ("issue-1", say)

W3C staff will, as I did in June, manage these proposals by consolidating them with related change proposals or raising new issues as necessary. We will update and, as necessary, add to the list of (in some cases, grouped) change proposals maintained on the wiki [3]. Participants should feel free to consolidate proposals and make friendly amendments directly on the wiki; anyone with a W3C account can update pages on the wiki.

# Raising issues

We will open issues as necessary to track change proposals (although in many cases multiple change proposals will be grouped to the same issue). Anyone in the Working Group may raise an Issue at any time (as always!). However, for issues to be assured consideration during our push to Last Call, an Issue must be raised before October 2nd, have a cogent rationale, and have a clear text change proposal. If you wish to raise an issue but don't have a change proposal, that may be better as a question for the group to consider in a later milestone or version. To that end, we've noted separate Compliance Current (the list we've been working on as "Compliance June") [4] and Compliance Next (for which I'm making use of the long-running product) [5] in the Tracker to collect such issues.

If you wish to re-raise an issue already decided by the group, note that we do not commonly re-open issues (or raise issues substantially the same as issues already decided); issues may be re-opened when new information is provided and at the discretion of the chair.

# Editorial suggestions

Editorial suggestions or friendly amendments to the editors' draft probably don't need to be tracked as issues/change proposals. Those comments are welcome (requested, even) on the mailing list. Include "editorial" in the subject line to cue the editors. Editors will continue to work through the editorial suggestions raised this summer, many of which have not been implemented yet.

Questions are welcome on or off list.

[0] http://lists.w3.org/Archives/Public/public-tracking/2013Sep/0010.html
[1] http://lists.w3.org/Archives/Public/public-tracking/2013Sep/0027.html
[2] http://lists.w3.org/Archives/Public/public-tracking-announce/2013Jun/0003.html
[3] http://www.w3.org/wiki/Privacy/TPWG#Change_proposals
[4] http://www.w3.org/2011/tracking-protection/track/products/5
[5] http://www.w3.org/2011/tracking-protection/track/products/1

Received on Tuesday, 17 September 2013 07:59:35 UTC

This archive was generated by hypermail 2.3.1 : Friday, 3 November 2017 21:45:18 UTC