Updating date, status etc to publish today
authorcharles
Tue, 30 Sep 2014 19:21:57 +0400
changeset 122 622235dd5cba
parent 121 4af9ab4df4ce
child 123 1b0923a94ba3
Updating date, status etc to publish today
cover.html
--- a/cover.html	Sat Sep 13 23:45:18 2014 +0200
+++ b/cover.html	Tue Sep 30 19:21:57 2014 +0400
@@ -19,7 +19,7 @@
     <div class="head"><a href="http://www.w3.org/"><img alt="W3C" src="https://www.w3.org/Icons/w3c_home"
           height="48" width="72"></a>
       <h1>W3C Draft Process Document</h1>
-      <h2 class="notoc">14 September 2014 Editor's Draft</h2>
+      <h2 class="notoc">30 September 2014 Editor's Draft</h2>
       <dl>
         <dt>Latest Editor's version:</dt>
         <dd> <a href="https://dvcs.w3.org/hg/AB/raw-file/default/cover.html">https://dvcs.w3.org/hg/AB/raw-file/default/cover.html</a></dd>
@@ -61,7 +61,7 @@
     <p>For more information about the W3C mission and the history of W3C, please
       refer to <a href="http://www.w3.org/Consortium/">About W3C</a> [<a href="#ref-mission">PUB15</a>].</p>
     <h2 class="notoc"><a id="status">Status of this Document</a></h2>
-    <p>This is the 14 September 2014 Editor's draft for the proposed next
+    <p>This is the 30 September 2014 Editor's draft for the proposed next
       version of the W3C Process Document. This document is based on the 1
       August 2014 Process, developed between the <a href="/2002/ab/">W3C
         Advisory Board</a> and the <a href="http://www.w3.org/community/w3process/">Revising
@@ -70,16 +70,11 @@
       preparation for adopting a revised process in 2015.</p>
     <p>W3C, including all existing chartered groups, follows the <a href="http://www.w3.org/Consortium/Process/">most
         recent operative Process Document</a> announced to the Membership.</p>
-    <p>In <em>this draft</em>, Section 5 (Activities) has been almost
-      completely removed, with a few requirements moved to other parts of the
-      process. Two short pieces remain temporarily, pending a decision about
-      whether to maintain the requirements they include. There are also a small
-      number of references to Activities elsewhere. The editor is of the opinion
-      that these can be resolved with editorial clarification, but they are
-      identified in case anybody disagrees and feels that real issues should be
-      raised.</p>
-    <p>This draft will be considered by the Advisory Board at its face to face
-      meeting on 16/17 September. Public comment is also invited on the draft.</p>
+    <p>In <em>this draft</em>, Chapter 5 (Activities) has been removed, with a
+      few requirements maintained in other parts of the process. Section 6.2.1.7
+      "Good standing in a working group" has also been removed.</p>
+    <p>This draft is offered to the W3C Advisory Comittee for review, as an
+      interim Working Draft. Public comment is also invited on the draft.</p>
     <p>Please send comments about this document to the <a href="http://www.w3.org/community/w3process/">Revising
         W3C Process Community Group</a> (<a href="http://lists.w3.org/Archives/Public/public-w3process/">Mailing
         list archive</a>, publicly available) or to [email protected] (<a href="http://lists.w3.org/Archives/Member/process-issues">Member-only
@@ -1004,7 +999,8 @@
         the appropriate process. For instance, the Director <span class="rfc2119">MAY</span>
         appoint a new group Chair when the current Chair changes affiliations
         (e.g., if there is a risk of conflict of interest, or if there is risk
-        that the Chair's new employer will be over-represented within a W3C activity).</p>
+        that the Chair's new employer will be over-represented within a W3C
+        activity).</p>
       <p>The following are some scenarios where disclosure is appropriate:</p>
       <ul>
         <li>Paid consulting for an organization whose activity is relevant to
@@ -1956,10 +1952,10 @@
             Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].</p>
         <h3>6.3 <a id="GroupsCG">Coordination Groups</a></h3>
         <p>W3C activities interact in many ways. There are dependencies between
-          groups within the same area, in different areas, and between W3C activities
-          and the activities of other organizations. Examples of dependencies
-          include the use by one technology of another being developed
-          elsewhere, scheduling constraints between groups, and the
+          groups within the same area, in different areas, and between W3C
+          activities and the activities of other organizations. Examples of
+          dependencies include the use by one technology of another being
+          developed elsewhere, scheduling constraints between groups, and the
           synchronization of publicity for the announcement of deliverables.
           Coordination Groups are created to manage dependencies so that issues
           are resolved fairly and the solutions are consistent with W3C's
@@ -3422,7 +3418,8 @@
             id="ActivityDevelopment">t</a><a id="ActivityCreation">i</a><a id="ActivityModification">v</a><a
             id="ActivityExtension">i</a><a id="ActivityTermination">t</a><a id="ActivityProposal">ies</a>
           <a id="Activities">f</a>rom the Process (as resolved multiple times
-          since 2007) </li>
+          since 2007)</li>
+        <li>Remove 6.2.1.7 (Good standing in a Working Group)</li>
       </ul>
     </div>
   </body>