This page is Public
Chair Training Modules
- New W3C Recommendation Track, Steve Zilles (TBC)
- Making rapid progress in developing specs in W3C despite the W3C process (TBC)
- Using GitHub for W3C Specifications, Philippe Le Hégaret, 17 December 2015 (Minutes.
- Horizontal Review, Virginie Galindo, 13 October 2015 (Minutes, recording) and 20 October 2015(Minutes) slides in PPT, slides in PDF] - See also Blog post for keeping your reviewer on track.
- Focus and Productivity, Arnaud Le Hors, 29 January 2015 (minutes, recording)
- Focus and Productivity, by Arnaud Le Hors, 23 October 2014 (minutes)
- The Human Dimension, Charles McCathie Nevile, 17 June 2014 (minutes)
- Tools, Ralph Swick, Thursday, 24 April 2014, 10-noon ET (minutes)
- The ABCs of W3C, Philippe Le Hégaret, January 2014 (minutes, audio)
News for Chairs, Team Contacts and Editors
Starting a Group
Running a Group
- W3C Editors home page and specifically the
Style for Group-internal Drafts
- Advancement on the Recommendation Track:
- Section 6.1 Technical Reports of the W3C Process
- Transition requirements for all W3C maturity levels (First Public
Draft, Last Call, CR, PR, REC, etc.)
- Get Wide Review,
- Pubrules (publication requirements) and links to
related policies (e.g., namespaces,
MIME type registration,
and in-place modifications)
See also Pubrules issue management / tracker
- March 2017:
Obsoleting and Rescinding W3C Specifications
- Normative References; considerations the Director takes into account when evaluating normative references
- Publications can only happen on Tuesdays and Thursdays (Member-only archive of announcement), unless you use the automated publication system
- September 2015: W3C Comm Team no longer post Homepage News stories for regular WDs publications, unless explicitly requested at publication request.
- W3C Documents and license related to
API definitions, code samples, or examples
- Discussion about specifications tooling and versioning on firstname.lastname@example.org
- ...more advice on specification
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 email@example.com) and comm team. For service
enhancements or new systems projects, please contact firstname.lastname@example.org with a detailed description of
your needs. Outages appear on the System Status page. See collected wisdom below for less mature tools.
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
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. (People
with CVS access to pages are
welcome to make changes to pages signed by me, as long as they
Note: Not all pages are maintained with the same
frequency. Some may be quite outdated. Please contact me if you note
something that needs urgent attention, or if you want to propose updates.
Coralie Mercier, guidebook editor
$Id: Overview.html,v 1.653 2017/05/23 09:10:29 xueyuan Exp $