Draft [transition-request] PR for the W3C Process Document (revised)

All,

The Advisory Board and its Process Document Task Force would like to request the transition to PR of



    Title

        World Wide Web Consortium Process Document

    URL

        http://www.w3.org/Consortium/Process/

    Editors' draft

        https://dvcs.w3.org/hg/AB/raw-file/default/cover.html

    Proposed publication date: Tuesday, 6 May 2014



    Abstract

The mission of the World Wide Web Consortium (W3C) is to lead the World Wide Web to its full potential by developing common protocols that promote its evolution and ensure its interoperability. The W3C Process Document describes the organizational structure of the W3C and the processes related to the responsibilities and functions they exercise to enable W3C to accomplish its mission. This document does not describe the internal workings of the Team or W3C's public communication mechanisms.



For more information about the W3C mission and the history of W3C, please refer to About W3C<http://www.w3.org/Consortium/> [PUB15].





Record of the decision to request the transition

------------------------------------------------

WBS Ballot: https://www.w3.org/2002/09/wbs/7756/ProcessDoc/results



Report of important changes to the document

-------------------------------------------

There has been some editorial clarification, but no significant changes were made since the Last Call. See https://dvcs.w3.org/hg/AB/rev/41f97f342b7d for details of these changes.



The major changes made to Chapter 7 since the 2005 version of the Process Document are listed in the Status Section of the (revised) document: https://dvcs.w3.org/hg/AB/raw-file/default/cover.html#status .





Evidence that the document satisfies group's requirements

---------------------------------------------------------

Almost three years ago, the Advisory Board began looking for ways to make

specification development more agile. In the November 2012 TPAC Meeting, the Advisory Board realized that some of the major issues related to agility were in the complexity of Last Call, Candidate Recommendation and Proposed Recommendation. Because these are completely specified in Chapter 7 of the current W3C Process, we have focused on the requirements that can be addressed in a modified Chapter 7. The remaining process issues (those not directly related to Chapter 7) have been tabled until a future revision of the W3C Process.





Evidence that dependencies with other groups met

------------------------------------------------

There are no recorded dependencies with other groups.





Evidence that the document has received wide review

---------------------------------------------------

This was the second Last Call. The previous one had over 75 comments whose resolution is documented in http://www.w3.org/community/w3process/track/issues

(those with Document Life Cycle (ch 7) as the "Product")







Evidence that issues have been formally addressed

-------------------------------------------------

There were no comments received on the final Last Call document, but during the Last Call period, there were comments received on a prior version of the document. These comments have been addressed or issues (deferred to a future update to the Process Document) have been raised. See http://lists.w3.org/Archives/Public/public-w3process/2014Apr/0034.html .





Objections

----------

There were no objections.





Implementation information

--------------------------

The implementation plan is described at the end of the message announcing the final Last Call: https://lists.w3.org/Archives/Member/chairs/2014JanMar/0138.html





Patent disclosures

------------------

Patents are not relevant to this document.





Steve Zilles

Chair, AB Process Document Task Force