w3c / w3c/process

Elections aren't always contested

Open
#1,132 14 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Type: bug
Dominant language
HTML
Stars
262
Forks
194
PR merge metrics
No merged PRs in 30d

Description

The 2025 TAG election wasn't run because the number of candidates was equal to the number of positions.

This does our community no favors. We're lucky this time in that the people involved all seem good, but that's no guarantee. Having a contest for positions is healthy.

Rather than allow positions to be filled without contest, I recommend that the process require that positions with one seat include at least two people and positions with N seats require some number of candidates, more than N (I suggest floor((N + 1)/3)+1 if you want to get fancy; I'd like a lower denominator, but this is a recognition of recent reality), before an election can be held.

The failure mode is obvious: if the threshold cannot be met then the position(s) won't be filled. I suggest that this is already a problem and that it doesn't require extra special handling. We could get N-1 candidates. However, if a fix is desired, I would suggest that the AC be consulted to approve an election, or assignment without vote, proceeding with fewer than the target number.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the current election requirements in the W3C Process Document and review the 14-comment discussion on this issue. Compare the proposed candidate thresholds and fallback handling with the existing process, then confirm that a specific, agreed rule and its failure mode are documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
documentation
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.