From W3C Wiki
< AB
Jump to: navigation, search

Meeting Schedule


The AB holds teleconference meetings twice monthly, currently:

Face to face meetings

The AB also meets and participates in several face to face meetings every year:

  • Winter AB meeting
  • Spring AC meeting participation, and adjacent AB meeting
  • Summer AB meeting (transition meeting usually after AB election)
  • Fall TPAC meeting participation, but NO AB meeting

Upcoming f2f meetings


  • none currently planned, possibly adjacent to a Spring AC meeting (if any), likely a Summer transition meeting after the mid-year AB election.

CFC Procedure

Outside of meetings, the AB may take decisions on specific, concrete proposals using the following Call for Consensus procedure:

  • The proposal must not change once put for testing
  • The call for consensus must stand alone (not as part of another issue / thread).
  • The issue/thread must be clearly labeled as a Call for Consensus, and must include "CFC" in the title.
  • The person who makes the call for proposal should close it, with a stated conclusion.
  • For a formal AB decision, the deadline to reply must be at least two weeks.
  • For a formal AB decision, Consensus is at least {number of AB Members (including chair) - 3} votes in favour and none against. [Note: This count assumes an AB of 9 - 11 elected members.]

Agenda Drafting

The AB drafts its agendas collaboratively for upcoming meetings:

  • Each upcoming meeting agenda is managed as a page in the AB wiki, so that it is editable by AB members as well as the chair.
  • Each agenda page collects agenda items as a list of links, e.g. to GH issues or to accessible presentation/document to review, with minimal explanatory commentary (because most of that should ideally be in the issue or document) together with a clearly stated purpose for the discussion and possibly a suggested duration
  • Collected agenda items may list the time constraints of key participants, but otherwise do not have assigned time slots
  • Agenda items will be arranged into a schedule by the chair shortly before the meeting, so that the schedule can take into account recent additions and progress in the discussions. If too many topics are proposed, the chair can defer less-urgent topics to the next meeting.

See Upcoming Agenda Topic Collection

Minutes Correction Protocol

As in many other W3C groups, AB meeting minute are scribed into IRC. Note that, as the AB sometimes discusses particularly sensitive topics, certain comments and sections may be elided. Post-facto editing is governed by the November 2011 protocol; quoting from the summary of 3-4 November 2011 AB face-to-face meeting record (W3C Member only link):

The Advisory Board, recognizing that the IRC minutes are not a verbatim transcription, adopted a protocol by which each speaker can have their recorded statements edited when he or she feels that what is recorded is either incorrect or needs clarification. Other AB participants can ask a participant to clarify his or her remarks, but cannot insist on a change. The protocol is to send requests in e-mail to the AB list, as the only mechanism to change the minutes generated from the IRC record. The goal is to increase both transparency and coherence.

Past Meetings

After the meeting, the meeting page will link to the minutes for future reference after they have been posted. See the full record of Minutes and Summaries of Past Meetings. Below are F2F wiki pages, most recent first: