From W3C Wiki

Welcome to the public AB Wiki

The W3C Advisory Board (AB) provides ongoing guidance to the W3C Team on issues of strategy, management, legal matters, process, and conflict resolution. This page documents current AB projects, and is open to suggestions from W3C members and non-members.

Logo: W3C AB (updated with 2023 w3c icon, and updated blue)

Are you a member of the W3C Advisory Committee? You may be interested in this page:

AB Workflow

🙌 Overview & role: Being on the AB | AB Guide | Reaching consensus | AB and BoD roles

📆 Meetings: Official Calendar | Scheduling & Logistics | Upcoming Agenda & Summaries (Member-only)

🌐 Public Resources: AB Priority Projects | Public Issue Tracker

🔵 Member-only: AB Home Page | Member Issue Tracker (archive) | Member Wiki | w3c-ac-forum@ list

🟪 AB-internal: Wiki | Issue Tracker | ab@ mailing list

Open AB Projects

Many critical Advisory Board projects are conducted in the open, transparent to the broader W3C community, who are also invited to participate:

W3C Process Maintenance Community Group

Main article: process

W3C process improvements are discussed in the community group:

Positive Work Environment Community Group

The Positive Work Environment group maintains the W3C Code of Ethics and Professional Conduct (CEPC) and related procedures and practices.

Vision Task Force

The VisionTF is a temporary Task Force by the AB through the end of June 2023 to work on the 2023 Vision Priority Project with interested W3C members. It was extended through October 2023 to continue work on the 2024 Vision Priority Project.

Working Group Effectiveness Task Force

The AB takes an active interest in improving W3C working group effectiveness by documenting and communicating existing good practices that help significantly, above and beyond formal processes, for everyone (especially chairs) participating in working groups.

See the Working Group Effectiveness Task Force (TF) home page:

Ongoing Projects

Miscellaneous Projects

AB Wiki Editing Itself

Things to work on wiki-editing workflow for (Tantek, additional volunteers)

  • long lived projects having their own undated URLs
  • using redirects for per year priorities
  • incorporate stuff in AB/2013-2014 into specific subpages for more navigable archival.

Cultural conventions for attribution

Main article: AB/attribution

The new HTMLWG charter allows for working group members to contribute HTML5 Extension specifications using CC-by, and then places attribution requirements on any derivative works.

These attribution requirements are a good start for growing cultural conventions for attribution both inside W3C, and beyond W3C, towards a goal of making attribution founded in cultural norms rather than legal (copyright) requirements, potentially allowing for use of CC0 for contributions to W3C in the future.

See AB/attribution for draft suggested best practices for attribution.

Open AB

The AB is working on (as is evident by this wiki page) doing more and more of its work in the open.

Currently Open AB work is occurring in a few places:

Following the AB

The Advisory Board has a Mastodon account: @ab@w3c.social

Nearly the entire AB has access and can post anything regarding AB-related matters. The methodology is to empower individual responsibility and trust by default, especially in such a small group.

If you are a member of the AB, contact Tantek Çelik on a secure communications channel and he'll gladly share access to @ab@w3c.social.

Previously, the AB had a Twitter account: @W3CAB but it is not really used any more. It was inspired by use of a shared Twitter account by the CSSWG (any CSSWG member may "have the keys" to @CSSWG) and it's been hugely successful in engaging the broader developer community.

  • 2013-09-18 access broadly shared with AB members in person W3C AB meeting at MIT.
  • 2013-06-04 @W3CAB Twitter created.


The Advisory Board has been discussing acknowledging the individuals who have made great contributions for the Web community. And the Wiki page records some initial exploration in this direction.

W3C Community and Tools

W3C Chairs Training

The Advisory Board has established Chair Training as a priority for 2014. At TPAC2013, Chairs had a breakfast meeting and expressed what additional information and skills they required to improve their effectiveness. The W3C Team developed a list of areas which have now evolved into a quarterly Chair Training program.

  1. W3C, Process, and the W3C Team, Philippe Le Hegaret, 23 January 2014
    1. Audio Recording of "W3C, Process, and the W3C Team"
    2. Anchor sections by Art Barstow
  2. Tools, Ralph Swick, 24 April 2014
    1. Audio Recording of "Tools"
  3. The Human Dimension, Charles McCathie Nevile, 17 June 2014
    1. Audio Recording of "The Human Dimension"
  4. Focus and Productivity, Arnaud Le Hors, 23 October 2014
  5. Focus and Productivity, Arnaud Le Hors, 29 January 2015
    1. Audio Recording of "Focus and Productivity"
  6. Horizontal reviews, Virginie Galindo, September 2015
    1. Horizontal review, session 1 (13 October 2015)
    2. Audio Recording of Horizontal review, session 1
    3. Horizontal review, session 2 (20 October 2015)
  7. New W3C process, its philosophy, and how to use it for agility, Steve Zilles, February/March 2015
  8. TBC: Making rapid progress in developing specs in W3C despite the W3C process
  9. IPR Management in a Github age - repo manager training, Kaz Ashimura, Sep 21 2017
    1. Video recording of "repo manager training"

Use of GitHub at W3C

Main article: GitHub

The AB looks at use of GitHub at W3C specifically in terms of impacts on process and IP concerns.

Some W3C groups use use GitHub to develop specifications or edit non-normative documents. While the strategy for using Tracker and/or Bugzilla and/or GitHub is left to WG decision, there are some good practices that can be gathered. That section is pointing to effort to federate experiences and good practices.

Remote Participation

The AB is looking at issues related to remote participation in W3C meetings.

OpenWeb Tools at W3C

The AB has discussed how to increase the use of OpenWeb Tools at W3C itself (a form of dogfooding). Many (most?) presentations at W3C workshops (e.g. the Workshop on Social Standards: The Future of Business) use non-open-web technologies/formats. W3C should work on good practices to encourage more use of OpenWeb Tools instead of, or at least before non-open-web technologies/formats.

Side Projects

In addition to the above some members of the AB work on additional side projects related to W3C process, culture, etc.

Historical Documents

See AB/Priorities for links to past AB projects by year from 2013 to the present.

Past projects formerly linked on this page:

See Also