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/, mostly in this Github repository, but also on the archived public mailing list.

• main branch (current draft of the CG): Preview
• ab-tag-discipline branch, where potential procedures for removal and recall of AB or TAG members are being worked out: preview

• Issues and PRs without a milestone
• Issues and PR included and targetted for the next release
• Issues and PR marked as Agenda+

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.

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

1. On the main 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 line for your topic branch. See the "Branches under development" section and use existing branches 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 main

4. Create a new branch from the main 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