Process pp links (#240)

Fixes #237

chair/role.html

@@ -29,26 +29,26 @@ <h4>Related Resources</h4>
 <p>
 The <a href="https://www.w3.org/Process#ref-for-team%E2%91%A2%E2%91%A6">W3C Team</a> appoints (or re-appoints) a Chair (or more than one co-Chair) for every Working
 Group and Interest Group ("Group"). The Chair's primary role is to
-facilitate <a href="/Consortium/Process/#Consensus">consensus</a>-building among Group members. The Chair works together with
+facilitate <a href="/policies/process/#Consensus">consensus</a>-building among Group members. The Chair works together with
  the W3C <a href=
 "../teamcontact/role.html">Staff Contact</a>. Key roles of the Group
 Chair are listed below. Additional information on the role of the
-Group Chair is in the <a href="/Consortium/Process/#general-requirements">W3C Process
+Group Chair is in the <a href="/policies/process/#general-requirements">W3C Process
 Document</a>.
   <h2>Chair Buddy System</h2>
   <p>The <a href="https://github.com/w3c/wg-effectiveness">Working Group effectiveness Task Force</a> helped establish a Chair Buddy System by which experienced buddy-mentors help buddy-mentees.</p>
   <p>Interested parties should subscribe to <a href="mailto:chairbuddies@w3.org">chairbuddies@w3.org</a> (<a href="https://lists.w3.org/Archives/Member/member-chairbuddies/">Member-only archive</a>) and visit the dedicated <a href="buddy.html">Chair Buddy System page</a>.</p>
   <h2>Role of the Group Chair</h2>
 <h3>Creates Group charter and convenes Group</h3>
 <ul>
-<li><a href="/Consortium/Process/#WGCharterDevelopment">Develops Group charter</a> together with the Staff
+<li><a href="/policies/process/#WGCharterDevelopment">Develops Group charter</a> together with the Staff
 Contact.</li>
-<li>Is familiar with the <a href="/Consortium/Process">W3C
+<li>Is familiar with the <a href="/policies/process/">W3C
 Process</a>, the <a href="/policies/code-of-conduct/">W3C Code of Conduct</a>,
  the <a href="/policies/antitrust/">Antitrust and competition policy</a>,
 and <a href="/Guide">Guidebook</a>.</li>
 <li>Convenes Group and ensures Group members oriented to <a href=
-"/Consortium/Process">W3C Process</a> <i>with assistance of Staff
+"/policies/process/">W3C Process</a> <i>with assistance of Staff
 Contact.</i></li>
 <li>Schedules deliverables and sets milestones towards completion
 of deliverables.</li>

council/council.html

@@ -39,7 +39,7 @@ <h4>Nearby</h4>
           <a href="https://www.w3.org/Member/wiki/DirectorFOdashboard">Formal Objection dashboard</a> (Member-only link)
         </li>
         <li>
-          <a href="/Consortium/Process/">W3C Process Document</a>
+          <a href="/policies/process/">W3C Process Document</a>
         </li>
         <li>
           <a href="https://lists.w3.org/Archives/Public/public-new-work/">Archives of new work advance notices</a>
@@ -222,25 +222,25 @@ <h2 id="referral"><a href="#referral">Referral to W3C Council</a></h2>
   <li>
     <p>The W3C Council determines who will rule on this objection and who will chair the Council.</p>
     <ul>
-      <li><p>See <a href="https://www.w3.org/Consortium/Process/#council-participation">Council Participation, Dismissal, and Renunciation</a> and
-        <a href="https://www.w3.org/Consortium/Process/#council-chairing">Council Chairing</a>.</p></li>
+      <li><p>See <a href="/policies/process/#council-participation">Council Participation, Dismissal, and Renunciation</a> and
+        <a href="/policies/process/#council-chairing">Council Chairing</a>.</p></li>
       <li><p>Every person serving on the W3C Council is expected to be sufficiently knowledgeable that they feel comfortable with the decision of the W3C Council.
         The breadth of the W3C Council membership, and therefore the participation of each of its members, is key to the Council’s ability to provide an appropriate
         balance of viewpoints.</p></li>
     </ul>
   </li>
   <li>
-    <p>In extraordinary circumstances, the W3C Council may vote to <a href="https://www.w3.org/Consortium/Process/#council-delegation">delegate</a> or
-      <a href="https://www.w3.org/Consortium/Process/#council-short-circuit">short-circuit</a> its decision.</p>
+    <p>In extraordinary circumstances, the W3C Council may vote to <a href="/policies/process/#council-delegation">delegate</a> or
+      <a href="/policies/process/#council-short-circuit">short-circuit</a> its decision.</p>
   </li>
   <li>
-    <p>The W3C Council <a href="https://www.w3.org/Consortium/Process/#council-deliberations">deliberates and reaches a decision</a> to sustain or overrule the original decision.</p>
+    <p>The W3C Council <a href="/policies/process/#council-deliberations">deliberates and reaches a decision</a> to sustain or overrule the original decision.</p>
     <ul>
       <li><p>If the W3C Council members deem that the written summaries are sufficient, they are not required to discuss with participants further, although they may
         do so if they wish. They may consult with deciders and objectors if they wish. See thoroughness and fairness below.</p></li>
       <li><p>Once consultations are completed, the Chair of the W3C Council assesses the consensus of the Council, or if consensus cannot be found,
         calls for a vote of the W3C Council to sustain or overrule the Formal Objection.</p></li>
-      <li><p>The W3C Council <a href="https://www.w3.org/Consortium/Process/#council-decision">publishes its decision and its rationale</a>.</p></li>
+      <li><p>The W3C Council <a href="/policies/process/#council-decision">publishes its decision and its rationale</a>.</p></li>
       <li><p>Whether the decision is to sustain or overrule, the W3C Council may include additional guidance for any of the participants involved.</p></li>
       <li><p>If the objection is sustained, the relevant group (i.e., Working Group, or Team developing a charter) may resume work to develop a different proposal for their document.</p></li>
     </ul>

editor/editors-draft.html

@@ -47,7 +47,7 @@ <h4>Resources</h4>
   <li><a href="../transitions">Organize Recommendation Track
   Transition</a></li>
   <li><a
-	  href="https://www.w3.org/Consortium/Process/#Reports">Recommendation
+	  href="/policies/process/#Reports">Recommendation
   Track Process</a></li>
   <li><a href=".">W3C Editors' Home Page</a></li>
   <li><a href="../manual-of-style/">Manual of Style</a></li>

editor/index.html

@@ -69,7 +69,7 @@ <h2>
         <li>The <a href="../manual-of-style/">W3C Manual of Style</a> is a collection of rules you're invited to follow to make your document clearer and adapted to the common style at W3C.</li>
         <li>Begun in 1992 and only a little out of date, the <a href="../../Provider/Style/">Style Guide for online hypertext</a> by Tim Berners-Lee is a good start on writing for the Web; see also Jakob Nielsen's <a href="http://www.useit.com/alertbox/9710a.html">How Users Read on the Web</a></li>
         <li>The <a href="../../TR/qaframe-spec/">QA Framework: Specification Guidelines</a> from the W3C Quality Assurance Activity are a work in progress that became a Candidate Recommendation in November 2003.</li>
-        <li>The Team has guidelines for a <a href="editors-draft.html">style for group-internal drafts</a> to avoid confusion with documents published on the <a href="/TR">TR page</a>. Please also review the related <a href="https://www.w3.org/Consortium/Process/#revising-wd">Working Group Heartbeat Requirement</a> of the W3C Process.</li>
+        <li>The Team has guidelines for a <a href="editors-draft.html">style for group-internal drafts</a> to avoid confusion with documents published on the <a href="/TR">TR page</a>. Please also review the related <a href="/policies/process/#revising-wd">Working Group Heartbeat Requirement</a> of the W3C Process.</li>
       </ul>
       <p><a href="http://www.w3.org/People/Bos/DesignGuide/introduction">Bert Bos's essay on W3C's design principles</a> and <a href="http://www.w3.org/1999/09/specification">Tim Berners-Lee's essentials of a specification</a> may also be a useful reading.</p>
       <p>During the internal development of a specification, make sure to distinguish official drafts from internal ones using the <a href="editors-draft.html">style for Group-internal Drafts</a>.</p>

incubation.html

@@ -141,7 +141,7 @@ <h1 id="submission">Member Submission</h1>
                     and if royalty-free commitments to known patents are made along with the submission.
 
                 </p>
-                <p><button><a href="https://www.w3.org/Consortium/Process/#Submission">Member Submission Process</a></button></p>
+                <p><button><a href="/policies/process/#Submission">Member Submission Process</a></button></p>
             </section>
             <section>
                 <h1 id="workshop">W3C Workshop</h1>

index.html

@@ -212,7 +212,7 @@ <h3 id="Deliverables">Specification Development</h3>
         <li>Advancement on the Recommendation Track:
           <ul>
             <li><a href="https://github.com/w3c/wg-effectiveness/blob/master/process.md">W3C Process for Busy People</a></li>
-            <li><a href="https://www.w3.org/Consortium/Process/#rec-advance">Section 6.3 Technical
+            <li><a href="/policies/process/#rec-advance">Section 6.3 Technical
                 Reports</a> of the W3C Process</li>
             <li>Considerations for <a href="process/joint-deliverables.html">joint deliverables</a></li>
             <li><a href="https://www.w3.org/Guide/transitions/">Transition requirements</a> for all W3C
@@ -273,7 +273,7 @@ <h2 id="ref">Reference</h2>
     <div class="rightcol">
       <h4 id="patents">Patent Policy</h4>
       <ul>
-        <li><a href="https://www.w3.org/Consortium/Patent-Policy/">W3C
+        <li><a href="/policies/patent-policy/">W3C
             Patent Policy</a></li>
         <li>Commentary: <a href="https://www.w3.org/2003/12/22-pp-faq.html">FAQ</a>,
           <a href="https://www.w3.org/2004/02/05-patentsummary.html">Summary</a>,
@@ -294,7 +294,7 @@ <h4 id="testsuites">Test Suites</h4>
       </ul>
       <h4 id="processdoc">Process</h4>
       <ul>
-        <li><a href="https://www.w3.org/Consortium/Process/">Operative W3C Process Document</a></li>
+        <li><a href="/policies/process/">Operative W3C Process Document</a></li>
 	<li>
     <span id='banning'></span> <!-- s/banning/suspension/ : keep this old ID for backcompat now -->
     <a id="suspension" href="process/suspension.html">Guidelines to suspend or remove participants from groups</a></li>
@@ -344,7 +344,7 @@ <h4 id="policies">Guidelines and Policies</h4>
       </ul>
     </div>
     <p style="clear: both"><strong>Note on Member Submissions: </strong> Per <a
-        href="https://www.w3.org/Consortium/Process/#SubmissionScope">section
+        href="/policies/process/#SubmissionScope">section
         "Scope of Member Submissions" of the Process Document</a>, "when a
       technology overlaps in scope with the work of a chartered Working Group,
       Members SHOULD participate in the Working Group and contribute the
@@ -394,7 +394,7 @@ <h4 id="roles">Roles</h4>
             Author, Contributor Policies</a></li>
         <li><a href="teamcontact/role.html">team contact's role</a></li>
         <li><a href="teamcontact/liaison-role.html">Liaison's role</a>. <strong>Note:</strong>
-          Per <a href="https://www.w3.org/Consortium/Process/#Liaisons">section "Liaisons"</a> of
+          Per <a href="/policies/process/#Liaisons">section "Liaisons"</a> of
           the Process Document, liaisons MUST be coordinated by the Team due to
           requirements for public communication; patent, copyright, and other
           IPR policies; confidentiality agreements; and mutual membership
@@ -428,7 +428,7 @@ <h4 id="historical">Historical</h4>
     <h2 style="clear: right" id="care-and-feeding">About
         the Guidebook</h2>
     <p>This Guidebook is intended to complement the <a href="https://www.w3.org/Consortium/Agreement/Appendix">W3C
-        Membership Agreement</a> and the <a href="https://www.w3.org/Consortium/Process/">W3C
+        Membership Agreement</a> and the <a href="/policies/process/">W3C
         Process</a>. This index page is <strong>Public</strong>, although a
       small number of resources linked from this page may be visible only to the
       W3C Membership or Team.</p>

meetings/continuity.html

@@ -219,7 +219,7 @@ <h3 id='selectingvideoconferencing'>Selecting a video conferencing service</h3>
       <h2 id='workshops'>W3C Workshops</h2>
 
       <p>
-            We continue to conduct fully distributed <a href="https://www.w3.org/Consortium/Process/#GAEvents">workshops</a> with virtual presence sessions.
+            We continue to conduct fully distributed <a href="/policies/process/#GAEvents">workshops</a> with virtual presence sessions.
 		We are adapting the existing model (program committee issues call for participation
 		and invites presentations based on submitted position statements) and experiment with new models.
 		In any format, materials should be posted and archived accessibly. Participants should be notified of plans for audio/video recording and confidentiality level.

meetings/organize.html

@@ -53,10 +53,10 @@ <h4>On This Page&nbsp;&rarr;&nbsp;</h4>
 
       <h2 id='timezones'>Dealing with timezones</h2>
 
-      <blockquote cite='https://www.w3.org/Consortium/Process/#distributed-meeting'>
+      <blockquote cite='/policies/process/#distributed-meeting'>
             <p>A distributed meeting is one where most of the attendees are expected to participate from remote locations
                (e.g., by telephone, video conferencing, or IRC).</p>
-            <p>&mdash; <a href='https://www.w3.org/Consortium/Process/#distributed-meeting'>W3C Process Document</a></p>
+            <p>&mdash; <a href='/policies/process/#distributed-meeting'>W3C Process Document</a></p>
       </blockquote>
       <p>A Chair should build consensus about the time slots for distributed meetings and should
 	 reevaluate that consensus on a regular basis. A good practice is to re-evaluate at the semi-annual spring and fall shifts in daylight saving time, and upon significant changes in membership or participation.
@@ -87,7 +87,7 @@ <h2 id='timezones'>Dealing with timezones</h2>
                a decision.</li>
       </ul>
 
-      <p>The <a href="https://www.w3.org/Consortium/Process/#GeneralMeetings">W3C Process</a>
+      <p>The <a href="/policies/process/#GeneralMeetings">W3C Process</a>
 	  provides rules about the timing of meeting announcements and agenda publication.
       </p>
       </li>

other/elected-body-communication-guidelines.html

@@ -36,7 +36,7 @@ <h1>Guidelines for communicating as a member of a W3C elected body</h1>
       <h4>Nearby</h4>
       <ul>
         <li>
-          <a href="/Consortium/Process/">W3C Process Document</a>
+          <a href="/policies/process/">W3C Process Document</a>
         </li>
         <li>
           <a href="/policies/code-of-conduct/">W3C Code of Conduct</a>
@@ -49,7 +49,7 @@ <h4>Nearby</h4>
 
 <h2 id="intro">W3C elected bodies</h2>
 
-<p>The <a href="https://www.w3.org/Consortium/Process/#AB">AB</a> and the <a href="https://www.w3.org/Consortium/Process/#TAG">TAG</a> are defined in the W3C Process, as are the <a href="https://www.w3.org/Consortium/Process/#AB-TAG-participation">rules of participation</a> for both groups.</p>
+<p>The <a href="/policies/process/#AB">AB</a> and the <a href="/policies/process/#TAG">TAG</a> are defined in the W3C Process, as are the <a href="/policies/process/#AB-TAG-participation">rules of participation</a> for both groups.</p>
 
 <h2 id="values">W3C values and behaviours</h2>
 
@@ -59,7 +59,7 @@ <h2 id="guidelines">Communication guidelines</h2>
 
 <p>As the W3C process says:</p>
 
-<blockquote>Advisory Board and TAG participants have a special role within W3C. They are elected by the membership and <a href="https://www.w3.org/Consortium/Process/#TAG-appointments">appointed by the Team</a> with the expectation that they will use their best judgement to find the best solutions for the web, not just for any network, technology, vendor, or user.</blockquote>
+<blockquote>Advisory Board and TAG participants have a special role within W3C. They are elected by the membership and <a href="/policies/process/#TAG-appointments">appointed by the Team</a> with the expectation that they will use their best judgement to find the best solutions for the web, not just for any network, technology, vendor, or user.</blockquote>
 
 <p>As leaders within the W3C community, the opinions of members of elected bodies carry particular weight, whether they are expressed within our community or elsewhere.</p>
 

participant/group.html

@@ -150,12 +150,12 @@ <h3 id="github">GitHub</h3>
 <h3 id="w3c_process">W3C Process</h3>
 <ul>
   <li><a href="https://github.com/w3c/wg-effectiveness/blob/master/process.md">W3C Process for Busy People</a></li>
-  <li><a href="https://www.w3.org/Consortium/Process/">World Wide Web Consortium Process Document (Latest operative version)</a></li>
+  <li><a href="https://www.w3.org/policies/process/">World Wide Web Consortium Process Document (Latest operative version)</a></li>
 </ul>
 
 <h3 id="patent_policy">Patent Policy</h3>
 <ul>
-  <li><a href="https://www.w3.org/Consortium/Patent-Policy/">W3C Patent Policy</a></li>
+  <li><a href="/policies/patent-policy/">W3C Patent Policy</a></li>
   <li><a href="https://www.w3.org/2003/12/22-pp-faq.html">Patent Policy FAQ</a></li>
 </ul>
 

participant/resources.html

@@ -87,7 +87,7 @@ <h3 id="github">GitHub</h3>
 
 <h3 id="patent_policy">Patent Policy (especially for WGs)</h3>
 <ul>
-  <li><a href="https://www.w3.org/Consortium/Patent-Policy-20040205/">W3C Patent Policy (5 February 2004)</a></li>
+  <li><a href="/policies/patent-policy/">W3C Patent Policy</a></li>
   <li><a href="https://www.w3.org/2003/12/22-pp-faq.html">Patent Policy FAQ</a></li>
 </ul>
 

process/ac-appeal.html

@@ -40,15 +40,15 @@ <h1>Appealing a W3C Decision<hh1>
       <h4>Nearby</h4>
       <ul>
         <li>
-          <a href="/Consortium/Process/">W3C Process Document</a>
+          <a href="/policies/process/">W3C Process Document</a>
         </li>
       </ul>
     </div>
 
     <div id="Content">
 
 <p>The W3C process document allows Advisory Committee representatives to
-  initiate an <a href="https://www.w3.org/Consortium/Process/#advisory-committee-appeal">Advisory
+  initiate an <a href="/policies/process/#advisory-committee-appeal">Advisory
   Committee Appeal</a>.
   This document provides an <a href="@@">email template</a> to start the appeal.</p>
 <pre class='example'>

process/adv-notice.html

@@ -7,7 +7,6 @@
 <link rel="stylesheet" type="text/css" href="../assets/main.css">
 <link rel="shortcut icon" href="https://www.w3.org/Icons/WWW/Literature.gif">
 <link rel="start" title="Guidebook for W3C Collaborators" href="https://www.w3.org/Guide/">
-<link rel="copyright" title="Copyright" href="https://www.w3.org/Consortium/Legal/2002/ipr-notice-20021231#Copyright">
 <!-- Originally at https://www.w3.org/2005/09/adv-notice.html -->
 </head>
 <body>
@@ -24,7 +23,7 @@ <h1>How to send advance notice of work<br>to the Advisory Committee</h1></div>
 
 <p>This document describes the <a href="https://www.w3.org/staff/strat/">Strategy
 Team</a>'s <a href="#policy">implementation</a> of
-the <a href="https://www.w3.org/Consortium/Process/#WGCharterDevelopment">Process
+the <a href="/policies/process/#WGCharterDevelopment">Process
 Document requirements</a> related to advance notice to the Advisory
 Committee of charters in development. See the
 <a href="#bg">background</a> for the advance notice policy and
@@ -109,7 +108,7 @@ <h2 id="policy">Sending advance notice to the Advisory Committee</h2>
 
 <h2 id="bg">Background for this document</h2>
 
-<p>The <a href="https://www.w3.org/Consortium/Process/#WGCharterDevelopment">Process Document requirements</a> for
+<p>The <a href="/policies/process/#WGCharterDevelopment">Process Document requirements</a> for
 advance notice were introduced in response to requests from Members to
 be more in the loop earlier for work in development. These
 requirements were added to provide additional transparency to

process/alternate-ac.html

@@ -40,7 +40,7 @@ <h1>Alternate Advisory Committee Representatives<hh1>
       <h4>Nearby</h4>
       <ul>
         <li>
-          <a href="/Consortium/Process/">W3C Process Document</a>
+          <a href="/policies/process/">W3C Process Document</a>
         </li>
       </ul>
     </div>