Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
  • Loading branch information
plehegar authored Jan 12, 2024
1 parent dc626fc commit 12c09de
Show file tree
Hide file tree
Showing 2 changed files with 253 additions and 30 deletions.
223 changes: 223 additions & 0 deletions details.html
Original file line number Diff line number Diff line change
@@ -0,0 +1,223 @@
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Details of How to Organize a Recommendation Track Transition</title>
<link rel="stylesheet" href="/StyleSheets/generic-base-1.css" type="text/css"/>
<link rel="stylesheet" href="https://www.w3.org/StyleSheets/generic-base-1.css" type="text/css" crossorigin="anonymous"/>
<link rel="stylesheet" type="text/css" href="https://www.w3.org/Guide/assets/main.css" crossorigin="anonymous" />
<link rel="shortcut icon" href="https://www.w3.org/Icons/WWW/Literature.gif" crossorigin="anonymous" />
</head>
<body>
<div id="header">
<span class="logo"><a href="/"><img src="/Icons/WWW/w3c_home_nb"
alt="W3C" height="48" width="72"/></a></span>
<div class="breadcrumb">
<a href="/participate/">Participate</a> &#x2192; <a href="/Guide/">The Art of
Consensus</a> &#x2192;
<h1>Organize a Recommendation Track Transition (Details)</h1>
</div>
<p class="baseline">This <strong>Guidebook</strong> is the collected
wisdom of the W3C Group Chairs and other collaborators.</p>
</div>

<div class="toc">
<h4>Also On This Page &#x2192;</h4>
<ul>
<li><a href="#roles">Roles</a> &bull;</li>
<li><a href="#commteam">Comm Team</a> &bull;</li>
<li><a href="#history">History</a></li>
</ul>
</div>

<div class="toolbox box" style="margin-bottom: 1em">
<h4>Publication Policies</h4>
<ul>
<li><a href="/pubrules">Technical Report Publication Policy</a></li>

<li><a href="/pubrules/doc">About pubrules</a></li>
<li><a href="/2005/05/tr-versions">Version Management in W3C Technical Reports</a></li>
<li><a href="/2005/07/13-pubrules-disclosure">Guidelines for linking to
disclosure pages</a></li>
<li><a href="/2005/07/13-nsuri">URIs for W3C Namespaces</a></li>
<li><a href="/2020/01/registering-mediatypes">How to Register a Media Type for a W3C Specification</a></li>
<li><a href="/2005/04/xpointer-policy">XPointer Scheme Name Registry Policy</a></li>
</ul>
<h4>Resources</h4>
<ul>
<li><a href="/Guide/transitions/">Organize Recommendation Track
Transition</a></li>
<li>Details of Rec Track transitions</li>
<li><a
href="/Consortium/Process/#Reports">Recommendation
Track Process</a></li>
<li><a href="/Guide/editor/">W3C Editors' Home Page</a></li>
<li><a href="/Guide/manual-of-style/">Manual of Style</a></li>
<li><a href="/2005/03/28-editor-style.html">Style Guidelines for Group-Internal Drafts</a></li>
</ul>
<h4>Tools</h4>
<ul>
<li><a href="https://validator.w3.org/checklink">Link checker</a></li>
<li><a href="https://validator.w3.org/">HTML Validator</a></li>
<li><a href="https://jigsaw.w3.org/css-validator/">CSS Validator</a></li>
</ul>
</div>

<p id="start">
This document explains the processes W3C uses internally to prepare
and carry out a transition of a document on the Recommendation
Track. This document complements the version of "How to Organize a
Recommendation Track Transition". Please
refer to the latest version of "How to Organize a Recommendation Track
Transition" with this URI:
<code>&lt;https://www.w3.org/Guide/transitions&gt;</code>.</p>

<p>This document does not address:</p>

<ol>
<li>Requirements for documents themselves; see <a
href="/pubrules/doc">Technical Report Publication Policy</a>
("pubrules") for this information.
</li>

<li>What required information must be public; this is covered in <a
href="/Consortium/Process/#requirements-and-definitions">
section 7.2</a> of the Process Document and in the governing patent
policy.</li>

<li>Possible next steps after each transition; see the description
of the <a href="/Consortium/Process/#Reports">Recommendation Track
Process</a>.</li>

<li>The Comm Team's policy regarding <a
href="/2003/01/republishing/">in-place modification of W3C
Technical Reports</a>.</li>
</ol>

<p><a name="Exceptions"
id="Exceptions">Exceptions</a> to these processes <span
class="rfc2119">MAY</span> be authorized by the <a
href="#director">Director</a> or authorized proxy.</p>

<p>The key words <span class="rfc2119">MUST</span>, <span
class="rfc2119">MUST NOT</span>, <span
class="rfc2119">REQUIRED</span>, <span
class="rfc2119">SHALL</span>, <span class="rfc2119">SHALL
NOT</span>, <span class="rfc2119">SHOULD</span>, <span
class="rfc2119">SHOULD NOT</span>, <span
class="rfc2119">RECOMMENDED</span>, <span
class="rfc2119">MAY</span>, and <span
class="rfc2119">OPTIONAL</span> are to be interpreted as described
in <a href="https://www.rfc-editor.org/rfc/rfc2119.txt">RFC
2119</a>.</p>

<h2 id="roles">Roles</h2>

<ul>
<li>The <a name="Webmaster" id="Webmaster">Webmaster</a> publishes
documents.</li>

<li>Transition approvals are given by <a href="https://github.com/orgs/w3c/teams/transitions">@w3c/transitions</a>,
under the delegation from <a href="/Guide/process/tilt/">Technical issues Lead Team</a>.</li>

<li>Chair responsibilities may be carried out by either the Chair
or Team Contact.</li>

<li>The <a name="DocContact" id="DocContact">Document Contact</a> is
either the Team Contact of the group requesting publication, or the
document editor. Consult the <a href="mailto:[email protected]">W3C
Project Management Lead</a> if you're not sure who is the relevant
Document Contact.</li>

<li>The <a name="MaintainerContact" id="MaintainerContact">Maintainer
Contact</a> is a designated individual tasked with requesting
Director's approval in order to publish a candidate amended
Recommendation. Consult the <a href="mailto:[email protected]">W3C
Project Management Lead</a> if you're not sure who is the relevant
Maintainer Contact. (Note: as of January 2018, the maintainer
contact is <a href="mailto:[email protected]">plh</a>)</li>
</ul>

<p>See also the <a href="/Guide/editor/">W3C Editor's Home Page</a>
and Guidebook documentation of <a href="#roles">roles of W3C
participants</a>, including the <a href="/Guide/chair/role">Chair's
role</a> and the <a href="/Guide/teamcontact/role">Team Contact's
role</a>.</p>

<h2 id="commteam">Interactions with the W3C
Communications Team</h2>

<p>At various stages during the Recommendation Track process, the
W3C Communications Team assists Working Groups as follows:</p>

<ul>
<li>Organizing formal Advisory Committee reviews (including
scheduling and preparation of review forms).</li>

<li>Issuing a press release around a First Public Working Draft,
Candidate Recommendation, Recommendation, or other transition (for
example, to announce completion of important work or to raise
awareness at a conference). The Communications Team generally begins work
on a draft press release several weeks in advance of an anticipated
release, soliciting review within the Team. The Communications
Team may also request Working Group review of a draft press
release. In general, the Communications Team strives to make press
releases available in English, French, Japanese and Chinese. The W3C Offices
translate <a href="/press-releases/">W3C press releases</a> into additional
languages.</li>

<li>Soliciting testimonials in support of a document, usually more
than a month in advance of publication of a Recommendation.</li>

<li>Announcing publication to Members and the press.</li>

<li>Listing the publication on the W3C home page and in Member
publications. In general, the Communications Team
drafts home page announcements for publications (see
<a href="/news/">past news items</a>). Input from Team Contacts
for announcements of First Public Working Drafts is appreciated.</li>

<li>Writing speaking points for the press, generally with input
from the Working Group.</li>

<li>Coordinating spokespeople to answer technical questions from
the press.</li>
</ul>

<p>Please contact the Communications Team at [email protected]
(cc'ing the group's Team Contact) if you have any general questions
regarding the publications process.</p>

<h2 id="history">History of "How to Organize a Transition"</h2>

<p>20240112: Moved to Github. For future history, see the <a href='https://github.com/w3c/transitions/commits/main/details.html'>github log</a>.</p>

<p>20180416: Fixed broken fragments, updated links, general quality assurance and updates.</p>

<p>20170301: Revised for <a href="/Guide/transitions/">transitions documentation for Process 2017</a>.</p>

<p>20161101: Updated for reorganization 2016</p>

<p>20160804: Transitions 2005 and 2014 superseded by 2015.</p>

<p>20151123: Revised for <a href="/Guide/transitions/">transitions documentation for Process 2015</a>.</p>

<p>20140801: Revised for <a href="/Guide/transitions/">transitions documentation for Process 2014</a>.</p>

<p>20060131: Revised for
release with pubrules. <a href="https://lists.w3.org/Archives/Member/chairs/2006JanMar/0026.html">Released 31 January 2006</a> but created in August
2005.</p>

<p><a href="/2003/12/01-transitions">20031201</a>: Version sent for
review with 24 Dec 2003 Process Document.</p>

<p><a href="/2003/05/Transitions">20030501</a>: Version published
with June 2003 Process Document.</p>

<hr>
<p>Feedback is to <a href="https://github.com/orgs/w3c/teams/transitions">@w3c/transitions</a>
and is welcome on <a href="https://github.com/w3c/transitions/issues">GitHub</a></p>

</body>
</html>

Loading

0 comments on commit 12c09de

Please sign in to comment.