Skip to content

W3C Community Group process

Jump to bottom
Eric Jahn edited this page Jul 17, 2026 · 5 revisions

Consensus Driven Model

W3C Community Groups operate on a flexible, consensus-driven model. Here is exactly how they handle discussions and make decisions:

  1. Self-Determined Structures (Group Charters) Unlike official W3C Working Groups, Community Groups have a massive amount of operational freedom. The W3C does not impose a strict hierarchy on them. Instead, a CG will typically write its own Charter or Operational Agreement that defines:
  • The scope of their technical work.
  • Who the group Chairs/facilitators are.
  • How they prefer to communicate (e.g., GitHub issues, mailing lists, or teleconferencing).
  • Their specific process for making decisions.
  1. Consensus-Seeking Decision Making The core philosophy of any W3C group is consensus, not a simple majority vote.
  • Consensus means a substantial number of individuals support a decision, and nobody strongly objects.
  • Instead of counting "ayes" and "nays," group Chairs work to understand minority objections, adapt the proposal, and find a compromise everyone can "live with".
  1. "Call for Consensus" (CfC) When a group wants to finalize a decision (like adopting a new spec draft or changing a guideline), they don't hold a roll-call vote. Instead, the Chair issues a Call for Consensus (CfC) via the group's public mailing list or GitHub repository.
  • The proposal is posted with a strict deadline (usually at least a few working days to a week).
  • If no formal objections are raised by the deadline, the proposal is considered approved by consensus.
  1. The W3C Community Group Process While the day-to-day meeting style is relaxed, all CGs must still adhere to the overarching W3C Community and Business Group Process. This ensures legal and ethical guardrails, requiring:
  • Intellectual Property Commitments: Members must sign a Contributor License Agreement (CLA) so the spec can eventually transition into a formal, royalty-free open web standard.
  • Public Transparency: All formal communications, meeting minutes, and specifications must be permanently archived and publicly viewable.
  • Code of Conduct: All interactions must follow the W3C's strict policies against harassment and disruption.

How Long Chairs Serve For?

By default, W3C Community Group (CG) Chairs serve indefinitely. They remain in the role until they voluntarily step down, the group closes down, or the group actively decides to replace them.

Because CGs are designed to be lightweight and self-governing, exactly how long a Chair serves depends entirely on the group's internal dynamic.

How It Works in Practice

  1. The "Until You Burn Out" Model (Most Common) For the vast majority of smaller or highly specialized Community Groups, the person who founded the group or volunteered at the beginning stays the Chair for years. There are no automatic expiration dates or mandatory re-election cycles required by the W3C.

  2. Custom Group Charters (The Organized Approach) Larger, highly active Community Groups (like the Credentials Community Group) often write specific election rules into their own custom group charters to keep things democratic.

A group might decide to hold annual or biannual elections to keep leadership fresh.

They can set their own rules for term limits, though most allow popular Chairs to run for re-election indefinitely.

  1. The Emergency Ouster (The Fallback Rules) What happens if a Chair goes completely missing, becomes a bottleneck, or the group just wants a change but there is no scheduled election?

The W3C provides a fallback "emergency" mechanism to replace a Chair at any time:

Call for Election: Any participant can call for a new election to replace the Chair.

The Threshold: If at least 5 participants from 5 distinct organizations support the call, a formal, W3C-backed election is automatically triggered.

The Cool-Down: To prevent groups from descending into endless political drama, a forced election like this can only be initiated once every 60 days.

Summary: A W3C Community Group Chair serves as long as they want to, unless the group's custom charter dictates a fixed term or the members band together to vote them out.

The Takeaway: If Robert’s Rules are a formal courtroom trial, W3C Community Groups are an open-source engineering workshop. They build alignment through asynchronous GitHub threads, collaborative editing, and informal agreement rather than gavels and formal motions.

Clone this wiki locally