This page is Public

Also On This Page → 

Chair Training Modules

Current and Upcoming


Starting a Group

Running a Group

Specification Development

Speaking About Your Work


Tools in this section and the previous are in wide use and are supported by the systems team (ask for help on and comm team. For service enhancements or new systems projects, please contact with a detailed description of your needs. Outages and scheduled operations appear on the W3C System Status page. See collected wisdom below for less mature tools.

Patent Policy

Test Suites


Systems and Tools

Mailing Lists

Guidelines and Policies

Note on Member Submissions: Per section "Scope of Member Submissions" of the Process Document, "when a technology overlaps in scope with the work of a chartered Working Group, Members SHOULD participate in the Working Group and contribute the technology to the group's process rather than seek publication through the Member Submission process." Read more about how to send a Member Submission request (Member-only).

Collected Wisdom, Advice

Many of these resources were contributed by your colleagues; we invite you to write down and share your experiences as well. Discussion of issues that groups face take place on the chairs mailing list (Member-only archive). You may also find chairs meetings back to 1997 an interesting source of wisdom.

Advice on Specification Development



Advice on Meetings, Decisions, Issue Tracking


About the Guidebook

This Guidebook is intended to complement the W3C Membership Agreement and the W3C Process. This index page is Public, although a small number of resources linked from this page may be visible only to the W3C Membership or Staff.

You are expected to be familiar with the parts of this Guidebook that affect your work. Working Group chairs should get a "tour" from their team contact. Then take a look again, for example, if you're going to hold a face-to-face meeting; read the section on meetings and work with its owner, Susan, to be sure you understand what's written there, and to record any valuable knowledge you pick up along the way.

As editor of the guidebook, I will do my best to see that it gets better over time. This does not mean that I do all the editing myself! I collaborate with other collaborators who signed and dated the pages they maintain. And we need to know when information needs updating.

Note: Not all pages are maintained with the same frequency. Some may be quite outdated. Please add your issues to the GitHub repository of this Guidebook if you have any specific comments and/or proposals to improve this Guidebook.

Philippe Le Hégaret, guidebook editor
Yep, it's on GitHub.