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
GitHub for W3C Specifications, Philippe Le Hégaret, 17
December 2015 (Minutes).
Review (Member-only), Virginie Galindo, 13 October 2015 (Minutes,
and 20 October 2015(Minutes)
in PPT, slides
in PDF] - See also Blog
post for keeping your reviewer on track.
and Productivity (Member-only), Arnaud Le Hors, 29 January 2015 (minutes,
and Productivity (Member-only), by Arnaud Le Hors, 23 October 2014 (minutes)
Human Dimension (Member-only), Charles McCathie Nevile, 17 June 2014 (minutes)
Ralph Swick, Thursday, 24 April 2014, 10-noon ET (minutes)
- The ABCs
of W3C, Philippe Le Hégaret, January 2014 (minutes,
News for Chairs, Team Contacts and Editors
Note: The following information in this section is W3C Member-only.
Starting a Group
Running a Group
- W3C Editors home page and specifically
the Style for Group-internal
- 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
- Pubrules (publication
requirements) and links to related policies (e.g., namespaces,
management, and in-place
See also Pubrules
issue management / tracker
- March 2017: Obsoleting
and Rescinding W3C Specifications
References; considerations the Director takes into account when
evaluating normative references
of Formal Objections
- Publications can only happen on Tuesdays and Thursdays (Member-only
archive of announcement), unless you use the automated
- 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 email@example.com
- ...more advice on specification development
Speaking About Your Work
- Blogs, articles, Press interviews: Working Group participants, TAG Members, W3C Staff are among the world's experts in Web technologies and their impacts. Give heads-up, share relevant work, things you author, or press enquiries, by writing to the W3C Comm team (firstname.lastname@example.org) about how you may attribute your work (or not) to W3C.
- Use the Upcoming Talks form
(W3C Group participants, members of the W3C Team, and Office Staff); talks publicized on W3C home page, Public
Weekly Newsletter, W3C Social Media.
- Press release
- Creating and delivering effective presentations
- How to Make
Presentations Accessible to All
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.)
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.