ChairTraining

From W3C Wiki
Revision as of 21:35, 17 September 2013 by Charles (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Chair Training Curriculum

W3C Values

“W3C processes promote fairness, responsiveness, and progress: all facets of the W3C mission.” -- W3C Process, 1 Introduction

  • Respect
  • Overall goal of pushing the Web forward
  • Neutral
  • Fairness

Rules around groups: Process, IP, Anti-trust

  • participation policy and expectations
  • PWET training
  • process basics: issue tracking and reopening
  • decision processes
  • editing policies - commit then review, review then commit


  • Anti-trust
  • Conflict of Interest
  • Conflict of Interest as a Chair


  • Document license
  • Patent policy
  • External contributions
  • Horizontal reviews
  • Coordination with other Groups
  • Coordination with other standard bodies

Mechanics

  • Minutes taking
  • How to use archives
  • Getting action items done
    • Managing volunteers
  • Creating subgroup, task forces
  • Editorial Teams
  • Time
    • Time and attention management in meetings
    • Staying on schedule (milestones)
  • Use of mailing list, teleconferences and face-to-face meetings
  • How to work with the W3C Team Contact


  • Press Releases
  • How to work with Comm team
  • How to manage press and outside communications while you’re working
  • How to manage a Last Call, How to come up with CR exit criteria
  • Structuring outside comments and reviews
  • How to manage testing

Soft factors: values, and the art of chairing

"art of consensus"

  • how to organize your first meeting
  • how to do start a deliverable from scratch
  • how to run effective meetings / build agendas
  • how to frame an issue, how to frame a question
  • how to step down
  • roles in WG:
 * team contact,
 * Chair,
 * Co-Chair,
 * editor,
 * test suite leader,
 * domain lead,
 * Director
 * participant
 * reviewer
  • [How to distinguish between being a chair, and being a participant]
  • How to manage disruptive participants
  • How to manage factions (case studies?)
  • "leading by example"
  • How to connect out-of-band/private discussion with the rest of the group
  • When not to make a decision (due to lack of agreement)
  • Managing scope, extensions, rechartering, V vs V.next (the mythical version 2 trick :)
  • Using CR phase to start work on V.next
  • Use Cases and Requirements

Tooling

  • respec, anolis, etc.
  • WG homepage
  • IRC, Zakim, RRSAgent
  • CVS/HG/GIT
  • WBS
  • Doodle
  • /QA/
  • Event calendar
  • Tracker, bugzilla
  • etherpad, google doc, etc.

Methods of training delivery

  • TPAC annual session (see How to be a good chair session at TPAC 2012)
  • Separate training day
  • case based study session -- using experienced chairs to introduce a case that is then discussed in the group