The repository for "The Art of Consensus", W3C's Chair's Guidebook.

Documentation on how to participate in W3C WGs is split between multiple wikipages, github repos and emails. This means new members find difficulty in finding information as to how to participate and maybe give up trying. This repository is the place to pull all of those together.

Feel free to join #general in irc or slack (invite).

Pull requests are welcome from the Community. This Guide is for you after all.

The general edition of the Guidebook is managed by @w3c/guidebook but many areas are maintained by separate individuals or teams (check out the commits history of a file to see who).

The Guidebook uses the W3C Jekyll theme. See the README to run Jekyll locally.

Note that latest versions of Ruby might created a dependency issue. It is recommended to use the Ruby version mentioned in the Github workflow.

• /chair/
  • Instructions on how to chair WGs and IGs including managing meetings, setting up the homepage, maintaining the calendar.
• /council/
  • Anything related to councils.
• /documentreview/
  • How to do wide review.
• /editor/
  • W3C Editors' Home Page.: How to author a specification, including ReSpec or other spec making programs.
• /github/
  • How to use Git and GitHub at W3C.
• /manual-of-style/
  • The W3C Manual of Style for editors.
• /meetings/
  • Anything related to organizing meetings, including events.
• /process/
  • Anything related to additional guidelines when following the process.
  • You may involve @w3c/w3process-editors.
• /process/tilt/
  • Anything related to technical Team decision and verification, except for transitions.
  • Managed by @w3c/tilt
• /standards-track/.
  • Best Practices for Bringing Work to the W3C Recommendation Track.
• /teamcontact/
  • Guidance on the role of the team contact, and what to expect from them.
• /transitions/
  • Organize a Technical Report Transition.
  • Managed by @w3c/transitions.
• /other/
  • Related to permanent groups.

Note: now that we have a repository for the guidebook, simply add your documentation to it, rather than creating new repositories.