Skip to content

Commit

Permalink
Cleaned up
Browse files Browse the repository at this point in the history
  • Loading branch information
@plehegar
plehegar committed Jan 15, 2019
1 parent 88ad2e7 commit fd20e4e
Showing 1 changed file with 15 additions and 15 deletions.
30 changes: 15 additions & 15 deletions charter-template.html
View file
Original file line number Diff line number Diff line change
@@ -1,13 +1,13 @@
<!DOCTYPE html>
<html lang="en-US">
<head>
<meta charset="utf-8" />
<meta charset="utf-8">

<title><i class="todo">[name]</i> (Working|Interest) Group Charter</title>

<link rel="stylesheet" href="https://www.w3.org/2005/10/w3cdoc.css" type="text/css" media="screen" />
<link rel="stylesheet" type="text/css" href="https://www.w3.org/Guide/pubrules-style.css" />
<link rel="stylesheet" type="text/css" href="https://www.w3.org/2006/02/charter-style.css" />
<link rel="stylesheet" href="https://www.w3.org/2005/10/w3cdoc.css" type="text/css" media="screen">
<link rel="stylesheet" type="text/css" href="https://www.w3.org/OldGuide/pubrules-style.css">
<link rel="stylesheet" type="text/css" href="https://www.w3.org/2006/02/charter-style.css">
<style>
ul#navbar {
font-size: small;
Expand Down Expand Up @@ -63,7 +63,7 @@
</ul>
</aside>
<p>
<a href="https://www.w3.org/"><img alt="W3C" height="48" src="https://www.w3.org/Icons/w3c_home" width="72" /></a>
<a href="https://www.w3.org/"><img alt="W3C" height="48" src="https://www.w3.org/Icons/w3c_home" width="72"></a>
</p>
</header>

Expand All @@ -76,9 +76,9 @@ <h1 id="title"><i class="todo">[name]</i> (Working|Interest) Group Charter</h1>
<div class="noprint">
<p class="join"><a href="https://www.w3.org/2004/01/pp-impl/#####/join">Join the <i class="todo">[name]</i> (Working|Interest) Group.</a></p>
</div>
<p style="padding: 0.5ex; border: 1px solid green"> This proposed charter is available
on <i class="todo"><a href="https://github.com/w3c/@@">GitHub</a>.

<p style="padding: 0.5ex; border: 1px solid green"> This proposed charter is available
on <i class="todo"><a href="https://github.com/w3c/@@">GitHub</a>.

Feel free to raise <a href="https://github.com/w3c/@@/issues">issues</a></i>.
</p>
Expand Down Expand Up @@ -130,7 +130,7 @@ <h1 id="title"><i class="todo">[name]</i> (Working|Interest) Group Charter</h1>
</th>
<td>
<strong>Teleconferences:</strong> <i class="todo">topic-specific calls may be held</i> or <i class="todo">somthing else</i>
<br />
<br>
<strong>Face-to-face:</strong> we will meet during the W3C's annual Technical Plenary week; additional face-to-face meetings may be scheduled by consent of the participants, usually no more than 3 per year.
</td>
</tr>
Expand Down Expand Up @@ -161,7 +161,7 @@ <h3>Success Criteria</h3>
<p><i class="todo">For specifications of technologies that directly impact user experience, such as content technologies, as well as protocols and APIs which impact content: </i>
Each specification should contain a section on accessibility that describes the benefits and impacts, including ways specification features can be used to address them, and
recommendations for maximising accessibility in implementations.</p>
<p><span class='todo'>Consider adopting a healthy testing policy, such as:</span> To promote interoperability, all changes made to specifications should have <a href='https://github.com/w3c/testing-how-to/#test-as-you-commit-pointer-event-whatwg-webperf'>tests</a>.</p>
<p><span class='todo'>Consider adopting a healthy testing policy, such as:</span> To promote interoperability, all changes made to specifications should have <a href='https://github.com/w3c/testing-how-to/#test-as-you-commit'>tests</a>.</p>
</div>
</section>

Expand Down Expand Up @@ -235,7 +235,7 @@ <h3>Timeline</h3>

<section id="coordination">
<h2>Coordination</h2>
<p>For all specifications, this <i class="todo">(Working|Interest)</i> Group will seek <a href="https://www.w3.org/Guide/Charter.html#horizontal-review">horizontal review</a> for accessibility, internationalization, performance, privacy, and security with the relevant Working and Interest Groups, and with the <a href="https://www.w3.org/2001/tag/" title="Technical Architecture Group">TAG</a>. Invitation for review must be issued during each major standards-track document transition, including <a href="https://www.w3.org/Consortium/Process/#RecsWD" title="First Public Working Draft">FPWD</a> and at least 3 months before <a href="https://www.w3.org/Consortium/Process/#RecsCR" title="Candidate Recommendation">CR</a>, and should be issued when major changes occur in a specification.</p>
<p>For all specifications, this <i class="todo">(Working|Interest)</i> Group will seek <a href="https://www.w3.org/Guide/process/charter.html#horizontal-review">horizontal review</a> for accessibility, internationalization, performance, privacy, and security with the relevant Working and Interest Groups, and with the <a href="https://www.w3.org/2001/tag/" title="Technical Architecture Group">TAG</a>. Invitation for review must be issued during each major standards-track document transition, including <a href="https://www.w3.org/Consortium/Process/#RecsWD" title="First Public Working Draft">FPWD</a> and at least 3 months before <a href="https://www.w3.org/Consortium/Process/#RecsCR" title="Candidate Recommendation">CR</a>, and should be issued when major changes occur in a specification.</p>
<p class="issue"><b>Issue:</b> The paragraph above replaces line-item liaisons and dependencies with individual horizontal groups. There's been a suggestion to name and individually link the specific horizontal groups inline, instead of pointing to a page that lists them.</p>
<p class="issue"><b>Issue:</b> The requirement for an invitation to review after FPWD and before CR may seem a bit overly restrictive, but it only requires an invitation, not a review, a commitment to review, or even a response from the horizontal group. This compromise offers early notification without introducing a bottleneck.</p>

Expand Down Expand Up @@ -327,7 +327,7 @@ <h2>
All decisions made by the group should be considered resolved unless and until new information becomes available or unless reopened at the discretion of the Chairs or the Director.
</p>
<p>
This charter is written in accordance with the <a href="https://www.w3.org/Consortium/Process/policies#Votes">W3C Process Document (Section 3.4, Votes)</a> and includes no voting procedures beyond what the Process Document requires.
This charter is written in accordance with the <a href="https://www.w3.org/Consortium/Process/#Votes">W3C Process Document (Section 3.4, Votes)</a> and includes no voting procedures beyond what the Process Document requires.
</p>
</section>

Expand Down Expand Up @@ -379,7 +379,7 @@ <h2>
<h3>
Charter History
</h3>
<p class="issue"><b>Note:</b>Display this table and update it when appropriate. Requirements for charter extension history are documented in the <a href="https://www.w3.org/Guide/Charter#extension">Charter Guidebook (section 4)</a>.</p>
<p class="issue"><b>Note:</b>Display this table and update it when appropriate. Requirements for charter extension history are documented in the <a href="https://www.w3.org/Guide/process/charter.html#extension">Charter Guidebook (section 4)</a>.</p>

<p>The following table lists details of all changes from the initial charter, per the <a href="https://www.w3.org/Consortium/Process/#CharterReview">W3C Process Document (section 5.2.3)</a>:</p>

Expand Down Expand Up @@ -447,7 +447,7 @@ <h3>
</section>
</main>

<hr />
<hr>

<footer>
<address>
Expand All @@ -467,7 +467,7 @@ <h3>

<abbr title="World Wide Web Consortium">W3C</abbr> <a href="https://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="https://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="https://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.
</p>
<hr />
<hr>
<p><a href="https://github.com/w3c/charter-drafts">Yes, it's on GitHub!</a>.</p>
</footer>

Expand Down

0 comments on commit fd20e4e

Please sign in to comment.