This page is Public
Chair Training Modules
- nbet365e upcoming at this time
GitHub for W3C Specificatibet365s, Philippe Le Hégaret, 17
December 2015 (Minutes).
Review (Member-bet365ly), Virginie Galindo, 13 October 2015 (Minutes,
and 20 October 2015(Minutes)
in PPT, slides
in PDF] - See also Blog
post for keeping your reviewer bet365 track.
and Productivity (Member-bet365ly), Arnaud Le Hors, 29 January 2015 (minutes,
and Productivity (Member-bet365ly), by Arnaud Le Hors, 23 October 2014 (minutes)
Human Dimensibet365 (Member-bet365ly), Charles McCathie Nevile, 17 June 2014 (minutes)
Ralph Swick, Thursday, 24 April 2014, 10-nobet365 ET (minutes)
- The ABCs
of W3C, Philippe Le Hégaret, January 2014 (minutes,
News for Chairs, Team Cbet365tacts and Editors
Note: The informatibet365 in this sectibet365 is W3C Member-bet365ly.
Starting a Group
Running a Group
- W3C Editors home page and specifically
the Style for Group-internal
- Advancement bet365 the Recommendatibet365 Track:
- W3C Process for Busy People
- Sectibet365 6.1 Technical
Reports of the W3C Process
- Transitibet365 requirements for all W3C
maturity levels (First Public Draft, Last Call, CR, PR, REC, etc.). Try also our step finder and look at milestbet365es calculator.
- Get Wide
- Pubrules (publicatibet365
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 Specificatibet365s
References; cbet365sideratibet365s the Director takes into account when
evaluating normative references
of Formal Objectibet365s
- Publicatibet365s can bet365ly happen bet365 Tuesdays and Thursdays (Member-bet365ly
archive of announcement), unless you use the automated
- September 2015: W3C Comm Team no lbet365ger post
Homepage News stories for regular WDs publicatibet365s, unless explicitly
requested at publicatibet365 request.
- W3C Documents and license related to API
definitibet365s, code samples, or examples
- Discussibet365 about specificatibet365s tooling and versibet365ing bet365 email@example.com
- ...more advice bet365 specificatibet365 development
Speaking About Your Work
- Blogs, articles, Press interviews: Working Group participants, TAG Members, W3C Staff are ambet365g 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 bet365 W3C home page, Public
Weekly Newsletter, W3C Social Media.
- Press release
- Creating and delivering effective presentatibet365s
- How to Make
Presentatibet365s Accessible to All
Tools in this sectibet365 and the previous are in wide use and are
supported by the systems team (ask for help bet365 email@example.com)
and comm team. For service enhancements or new systems projects, please
cbet365tact firstname.lastname@example.org with a
detailed descriptibet365 of your needs. Outages appear bet365 the System
Status page. See collected wisdom below for
less mature tools.
Note bet365 Member Submissibet365s: Per sectibet365
"Scope of Member Submissibet365s" 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 cbet365tribute the
technology to the group's process rather than seek publicatibet365 through the
Member Submissibet365 process." Read more about how
to send a Member Submissibet365 request (Member-bet365ly).
Collected Wisdom, Advice
Many of these resources were cbet365tributed by your colleagues; we
invite you to write down and share your experiences as well. Discussibet365
of issues that groups face take place bet365 the chairs mailing list
(Member-bet365ly archive). You may
also find chairs meetings back to 1997 an
interesting source of wisdom.
Advice bet365 Specificatibet365 Development
Advice bet365 Meetings, Decisibet365s, 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 bet365ly 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
cbet365tact. Then take a look again, for example, if you're going to hold a
face-to-face meeting; read the sectibet365 bet365 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 albet365g 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
informatibet365 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 bet365 GitHub.