Starting Point

• So called "/Guide"

Then concrete guidelines for you all depending on your roles...

For Chairs

• Chair's role
• Starting a Group
• Running a Group
• Guidance for Multiple Chairs
• Liaison's role
  • Note: Per section "Liaisons" of the Process Document, liaisons MUST be coordinated by the W3C Team Staff due to requirements for public communication; patent, copyright, and other IPR policies; confidentiality agreements; and mutual membership agreements.

For Editors

• Editor's role (Member-only), Editor, Author, Contributor Policies
• Specification Development, Manual of Style
• Tips for getting to Recommendation faster
• Test Suites
• ReSpec, SpecRef
• GitHub:
  • W3C on GitHub
  • Using GitHub for W3C specifications (slides)
  • Using GitHub for Spec Work (documentation)
  • GitHub Repository Manager
  • Adds preview and diff links to pull requests (Config Helper)

For Particiants

• Guidelines and Policies
• Code of Ethics and Professional Conduct
• Process and Patent Policy
• Systems and Tools, Mailing Lists
• Speaking About Your Work, Creating effective presentations
• Timezone management and Group Calendars

IRC for Telcos

1. Join your IRC channel by visiting https://irc.w3.org/
2. After joining your IRC channel:
   • Invite bots:
     /invite zakim <channel>
/invite rrsagent <channel>
   • Specify the scribe, e.g.: scribenick: kaz
   • Specify topics, e.g.: topic: Issues
   • Record what people said, e.g.: kaz: that should be fine
3. After the meeting:
   • Permission of the minutes: rrsagent, make log public
   • Generate the minutes: rrsagent, draft minutes

Further information on IRC

• Quick guide
• Minutes taking manual
• Zakim manual
• RRSAgent manual

Spec Development - 1

• General info: Editors' Home Page, Style for Group-internal Drafts
• W3C Process Document as the basis:
  • W3C Process for Busy People
  • Section 6.1 Technical Reports of the Process Document
• Transition requirements for all W3C maturity levels
  • First Public Draft, Last Call, CR, PR, REC, etc.
  • Try also our step finder and look at milestones calculator.

Spec Development - 2

• How to do Wide Review
  • Horizontal reviews
  • Hoizontal review tracker
• Latest recommendations:
  1. When we have published a First Public Working Draft, we should work through available "self-review" materials and request review of our results in Accessibility, Architecture, Internationalization, Privacy and Security.
  2. Long enough before we request a transition to CR, we should do the same again, identifying substantive specification changes since the first review.

Spec Development - 3

• Pubrules checker (publication requirements)
• Note:
  • Static HTML required for publication including the Pubrules checker.
    • See also: README.md within the wot-thing-description repo
  • Publication date:
    • Manual publications for FPWD/CR/PR only on Tuesdays and Thursdays.
    • Automated publication system (Echidna) available everyday for ordinary WDs/Notes.

Spec Development - 4

• Related policies:
  
  • W3C internal procedure:
    • Namespaces
    • Version management
    • In-place modifications
    • Normative References
    • Guide on W3C license
  • Collaboration with IANA:
    • MIME type registration

See also

• Project Management Team page