W3C Process Document repository

This repository is for the editor's draft of the World Wide Web Consortium Process Document.

The Process document is updated most years by the W3C. Discussion happens in the context of the W3C Process Community Group https://www.w3.org/community/w3process/.

The editor's draft can be viewed at https://w3c.github.io/w3process/.

The Process being prepared for release in 2020 includes a singificant number of large changes, which can be broadly categorized into:

• A convertion of the document from plain HTML to the bikeshed specification preprocessor (mostly just markup changes, some editorial changes)
• Miscellaneous fixes, some editorial, some small, some medium
• A reorganization of section 6, to disentangle definitions of maturities from transition between states (editorial)
• Significant revisions and additions to the Recommendation Track

As some of these changes overlap, in order to facilitate review, the following snapshots of various stages of the evolution have been prepared, as well as diffs between these various stages.

Process 2020 drafts at various stages	Diffs from stage to stage
1. Process 2019
	diff from 1. to 2.
2. … converted to bikeshed …
	diff from 2. to 3.
3. …with miscellaneous fixes…
	diff from 3. to 4.
4. …with section 6 refactoring…
	diff from 4. to 5.
5. …with REC track revision (latest)

---

Branches under development

master branch: / Preview

director-free branch: / Preview / Diff

registries branch: / Preview / Diff

---

Bikeshed

This document is maintained using Bikeshed. See the section about markup in Bikeshed's documentation for full details about the syntax.

Only the source (index.bs) should be committed, as this repository is configured to run bikeshed server-side and push the result to the gh-pages branch.

To run Bikeshed locally, Follow the instructions in Bikeshed's documentation. Once Bikeshed is installed, just type bikeshed to compile the document.

---

Setting up Branches

To set up long-lived topic branches which get built server side and published to github.io, follow these steps:

1. On the master branch edit deploy.sh to add the name of your topic branch to the TOPIC_BRANCHES array. Example:

   TOPIC_BRANCHES=("topic1" "topic2" "topic3")

2. (Optional Step) Edit the README.md file to add a "Build Status" line for your topic branch. See the existing "Build Status" for the master branch as a model.

3. Commit the change(s) above, and push to github.com/w3c/w3process (not your personal fork). Example:

   git add deploy.sh README.md
   git commit -m "Register topic branch for topic3"
   git push upstream master

4. Create a new branch from the master branch (after the previous commit), using the same name as the one you used in the TOPIC_BRANCHES array, and push it to github.com/w3process (not your personal fork). Example:

   git checkout -b topic3
   git push upstream topic3