html5/decision-policy decision-policy-v2.html,1.20,1.21

Update of /sources/public/html5/decision-policy
In directory hutz:/tmp/cvs-serv26502

Modified Files:
	decision-policy-v2.html 
Log Message:
Please clarify procedure and recourse for non-working group members when they are unsatisfied with a bug resolution
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10524


Index: decision-policy-v2.html
===================================================================
RCS file: /sources/public/html5/decision-policy/decision-policy-v2.html,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -d -r1.20 -r1.21
--- decision-policy-v2.html	16 May 2011 09:32:42 -0000	1.20
+++ decision-policy-v2.html	16 May 2011 09:35:43 -0000	1.21
@@ -23,6 +23,11 @@
 
 <p>For products of the HTML Working Group, particularly HTML5, we expect a high volume of Last Call comments. We expect most comments can be resolved in a satisfactory way by the editor of the affected draft. However, there are a few reasons we need to formalize our process a little bit. First, we are required by W3C Process to track and formally respond to all Last Call comments, and to produce a disposition of comments document in order to exit Last Call. Second, some comments will not be satisfactory as initially fielded by the editor, and will need to be resolved by a decision of the Working Group. Third, it needs to be very clear to commenters how to get their input formally considered.</p>
 
+<p>Non-members are encouraged to join the working group so they can
+fully participate in this process. But extenuating circumstances for
+not joining the group will be considered by the Chairs on a
+case-by-case basis.</p>
+
 <p>While the primary purpose of this process is for Last Call, we'd like to start on the process of migrating the Working Group over to the process right away. We've already informally been asking commenters to follow some of these steps.</p>
 
 <p>The way we will make decisions involves two subprocesses:

Received on Monday, 16 May 2011 09:35:50 UTC