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

html5/decision-policy decision-policy.html,1.1,1.2

From: Maciej Stachowiak via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 07 Oct 2009 08:02:21 +0000
To: public-html-commits@w3.org
Message-Id: <E1MvRTZ-0000CL-DV@lionel-hutz.w3.org>
Update of /sources/public/html5/decision-policy
In directory hutz:/tmp/cvs-serv657

Modified Files:
	decision-policy.html 
Log Message:
Fix broken links.


Index: decision-policy.html
===================================================================
RCS file: /sources/public/html5/decision-policy/decision-policy.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- decision-policy.html	7 Oct 2009 07:56:41 -0000	1.1
+++ decision-policy.html	7 Oct 2009 08:02:19 -0000	1.2
@@ -24,8 +24,8 @@
 <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:
-the <a href="#basic-process">Basic Process</a> and
-the <a href="#escalation-process">Escalation Process</a>. The Basic
+the <a href="#basic">Basic Process</a> and
+the <a href="#escalation">Escalation Process</a>. The Basic
 Process works primarily through Bugzilla; we believe most comments on
 drafts can be addressed this way, without the need to involve the full
 working group. For some issues though, the input of the Full Working
@@ -62,7 +62,7 @@
 </section>
 
 <section>
-<h2>Basic Process</h2>
+<h2 id="basic">Basic Process</h2>
 
 <p>The Basic Process describes the overall handling of an issue; we
 believe most steps can be handled without close involvement of the
@@ -78,7 +78,7 @@
 <dt>0. (Optional) Email</dt>
 <dd>Issues can be brought up initially by email, if discussion is needed before the issue is clear enough to file a bug. Commenters may go directly to the next step if they are very clear on their issue already.</dd>
 
-<dt id="basic-step1">1. Bugzilla Bug</dt>
+<dt id="basic-step-1">1. Bugzilla Bug</dt>
 <dd><p>Issues should
 be <a href="http://www.w3.org/Bugs/Public/enter_bug.cgi?product=HTML%20WG">filed
 as bugs in W3C Bugzilla</a> to be formally considered. If the
@@ -142,7 +142,7 @@
 reconsider, it's ok to move the bug to the REOPENED state. Commenters
 should exercise reasonable judgment on whether to use this option or
 5.d., in particular, its usually not a good idea to repeatedly reopen
-the same bug. The issue then returns to <a href="#basic-step1">step 1</a>.</dd>
+the same bug. The issue then returns to <a href="#basic-step-1">step 1</a>.</dd>
 
 <dt>5.d. No: Escalate to Issue</dt>
 <dd>If the commenter is dissatisfied with the resolution and does not
@@ -157,10 +157,10 @@
 <dd>Issues escalated to the tracker will be decided by Working Group Decision. The <a href="#escalation">Escalation Process</a> describes how Working Group decisions are made.</dd>
 
 <dt id="basic-step-7a">7.a. Affirm Editor's Response</dt>
-<dd>The Working Group Decision that results from the Escalation Process may be to affirm the editor's response. In this case proceed to <a href="#basic-step8">step 8</a>.</dd>
+<dd>The Working Group Decision that results from the Escalation Process may be to affirm the editor's response. In this case proceed to <a href="#basic-step-8">step 8</a>.</dd>
 
 <dt id="basic-step-7b">7.b. Overrule Editor's Response</dt>
-<dd>The Working Group Decision that results from the Escalation Process may be to overrule the editor's response. In this case proceed to <a href="#basic-step10">step 10</a>.</dd>
+<dd>The Working Group Decision that results from the Escalation Process may be to overrule the editor's response. In this case proceed to <a href="#basic-step-10">step 10</a>.</dd>
 
 <dt id="basic-step-8">8. Does Commenter Wish to Formally Object?<dt>
 <dd>The commenter should decide at this point if they wish to enter a Formal Objection against the Working Group decision.</dd>
@@ -278,7 +278,7 @@
 <p>If a Change Proposal is not complete by the deadline (default one month), proceed to <a href="#escalation-step-2a">step 2.a</a>.
 </dd>
 
-<dt id="#escalation-step3">3. Discussion</dt>
+<dt id="escalation-step3">3. Discussion</dt>
 <dd>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
Received on Wednesday, 7 October 2009 08:02:25 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 7 October 2009 08:02:25 GMT