W3C home > Mailing lists > Public > public-html-commits@w3.org > May 2010

html5/decision-policy decision-policy-v2.html,1.8,1.9

From: Maciej Stachowiak via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 04 May 2010 17:57:46 +0000
To: public-html-commits@w3.org
Message-Id: <E1O9MNO-000383-V0@lionel-hutz.w3.org>
Update of /sources/public/html5/decision-policy
In directory hutz:/tmp/cvs-serv12009

Modified Files:
Log Message:
Addressed "HTML5 editor should propose changes within email list".

Index: decision-policy-v2.html
RCS file: /sources/public/html5/decision-policy/decision-policy-v2.html,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -d -r1.8 -r1.9
--- decision-policy-v2.html	4 May 2010 17:53:00 -0000	1.8
+++ decision-policy-v2.html	4 May 2010 17:57:44 -0000	1.9
@@ -316,13 +316,24 @@
 <dt id="escalation-step3">3. Discussion</dt>
-<dd>The Change Proposal (or multiple Proposals) may be discussed and
+<dd><p>The Change Proposal (or multiple Proposals) may be discussed and
 revised for a reasonable period. Authors of Change Proposals are
 strongly encouraged to seek consensus and revise their Change
 Proposals to gain more support. Change Proposals that do not see wide
 support are unlikely to succeed. Once an outcome is clear or no more
 productive discussion is happening, the chairs proceed to the next
+<b>Note:</b> Editors may make changes that impact an issue under
+discussion, but that the editor is expected to identify on the mailing
+list any changes that may affect submitted Change Proposals. If there
+is an issue but no pending Change Proposal, then the editor is
+encouraged but not required to identify changes that may affect the
+issue. In the case of some issues, it may be difficult to even
+identify what changes would affect it without seeing a Change
 <dt>4. Call for Consensus</dt>
 <dd>If the chairs believe it is clear whether the existing spec or
Received on Tuesday, 4 May 2010 17:57:49 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:09:50 UTC