W3C home > Mailing lists > Public > public-html-commits@w3.org > October 2009

html5/decision-policy decision-policy.html,1.9,1.10

From: Maciej Stachowiak via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 21 Oct 2009 00:37:37 +0000
To: public-html-commits@w3.org
Message-Id: <E1N0PCr-0001Qi-KB@lionel-hutz.w3.org>
Update of /sources/public/html5/decision-policy
In directory hutz:/tmp/cvs-serv5386

Modified Files:
	decision-policy.html 
Log Message:
Two changes:

1) Give a two week deadline for commenters to respond to editor's resolutions (once info is VERIFIED).
2) Clarify that issues closed without prejudice may only be re-raised with approval of chairs (to clarify defense against some potential bad faith attacks.)



Index: decision-policy.html
===================================================================
RCS file: /sources/public/html5/decision-policy/decision-policy.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -d -r1.9 -r1.10
--- decision-policy.html	14 Oct 2009 16:12:24 -0000	1.9
+++ decision-policy.html	21 Oct 2009 00:37:35 -0000	1.10
@@ -124,10 +124,10 @@
 <dd>Once bugs are RESOLVED, we will ask volunteers, including Team
 Contacts, to make sure they include all of the needed components of an
 editor's response, and to add any that are missing. Once this is done,
-the bug should move to the VERIFY state.</dd>
+the bug should move to the VERIFIED state.</dd>
 
 <dt>4. Commenter Satisfied?</dt>
-<dd> At this point in the process, the commenter should review the editor's response, and choose one of the following Step 5 actions.</dd>
+<dd> At this point in the process, the commenter should review the editor's response, and choose one of the following Step 5 actions. The commenter has two weeks to take action from the time the bug is put in VERIFIED state.</dd>
 
 <dt>5.a. Yes: Close Bug</dt>
 <dd>If the commenter is satisfied with the editor's response, the
@@ -135,7 +135,11 @@
 CLOSED. <b>** This is an endpoint for the process. **</b></dd>
 
 <dt>5.b. (No Response)</dt>
-<dd>If the commenter never responds in the bug in any way, at some point we'll assume no response is forthcoming, and indicate that in disposition of comments. <b>** This is an endpoint for the process. **</b></dd>
+<dd>If the commenter never responds in the bug in any way, after two
+weeks will will assume no response is forthcoming, and indicate that
+in disposition of comments. At this point the bug will be tagged with
+the NoReply keyword. <b>** This is an endpoint for the
+process. **</b></dd>
 
 <dt>5.c. Want Reconsideration: Reopen Bug</dt>
 <dd>If the commenter feels they have new information or arguments, or
@@ -210,9 +214,10 @@
 <tr><td>UNCONFIRMED, NEW, ASSIGNED, REOPENED</td> <td>Waiting for editor response.*</td></tr>
 <tr><td>REOPENED and WGDecision</td> <td>Waiting for editor to implement Working Group decision.*</td></tr> 
 <tr><td>RESOLVED</td><td>Editor has addressed issue, waiting for boilerplate.*</td></tr>
-<tr><td>VERIFIED (and none of the below)</td><td>Reporter has not responded.</td></tr>
+<tr><td>VERIFIED (and none of the below</td><td>Waiting for response from commenter.*</td></tr>
 <tr><td>VERIFIED and TrackerRequest</td><td>Reporter requested escalated to Working Group. Waiting for mechanics of escalation.*</tr>
 <tr><td>VERIFIED and TrackerIssue</td><td>Reporter escalated to Working Group. Waiting for Working Group decision.*</tr>
+<tr><td>VERIFIED and NoReply</td><td>Reporter has not responded after two weeks or more.</td></tr>
 <tr><td>CLOSED and FormalObjection</td><td>The issue is settled, and reporter formally objected to WG.</td></tr>
 <tr><td>CLOSED and Disagreed</td><td>The issue is settled, and the reporter disagreed, but not as Formal Objection</td></tr>
 <tr><td>CLOSED (and none of those)</td><td>The issue is settled, and the reporter agreed with the final outcome.</td></tr>
@@ -267,8 +272,10 @@
 will be marked CLOSED without prejudice and deferred to the next
 version of HTML. In this case, we affirm the editor's decision by
 default. The Basic Process then proceeds
-from <a href="#basic-step-7a">step 7a</a> <b>** This is an endpoint
-for the escalation process. **</b> </dd>
+from <a href="#basic-step-7a">step 7a</a>. An issue that is closed
+without prejudice in this way can only be re-raised with approval of
+the Chairs. <b>** This is an endpoint for the escalation
+process. **</b> </dd>
 
 <dt id="escalation-step-2b">2.b. Open Issue: Writing a Change Proposal</dt>
 <dd> An issue with someone working on a change proposal is in the OPEN state. If the change proposal is not done by the deadline, the issue will be closed without prejudice and deferred to the next version of HTML. The default deadline to complete a Change Proposal is one month from the time someone volunteers. The chairs may grant a longer deadline for complex issues on request. A proper Change Proposal must include the following four components:
Received on Wednesday, 21 October 2009 00:37:39 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 21 October 2009 00:37:41 GMT