In order to ease notifying folks with a common expertise or interest, the WHATWG uses GitHub teams. The WHATWG uses teams in the following manner:
- Anyone can join any team they desire. To join just let someone know or file an issue.
- Everyone tries to ensure the appropriate teams are mentioned on relevant issues/pull requests.
- Teams have no formal authority, though we might add them as contributors to repositories for ease of collaboration. For all repositories we care about protecting the main branch primarily. The bar for write access to other branches is much much lower.
- Teams have no responsibility either. If you ping a team and get no feedback, moving things forward responsibly is still on you.
- To propose a new team, file an issue. We will approve most teams unless they are a niche or overlap with an existing team.
At the time of writing, the following teams exist:
- a11y — Accessibility-related matters
- canvas — The canvas element, and its APIs
- components — Custom elements, shadow trees, and related technologies
- cross-origin-isolation — Developing Cross-Origin-Opener-Policy (COOP) and Cross-Origin-Embedder-Policy (COEP) and friends
- css — Where WHATWG and CSS intersect
- documentation — Documentation for features in WHATWG standards
- dom — For those interested in helping designing and maintaining the DOM Standard
- forms — Folks interested in taking forms further
- fs — People who work on the File System standard
- html-parser — The HTML Parser
- http — HTTP-related matters
- i18n — Internationalization-related matters
- loader — The loader concept
- media — The HTML media elements and their API
- modules — Javascript modules
- perf — Matters of performance
- rendering — The rendering section
- security — Security-related matters
- sg — Steering group
- storage — Buckets! (And other storage matters.)
- triage — Folks with the Triage permission for all WHATWG repositories
- whatnot — People attending the WHATNOT meeting