w3c / w3c/process

Should we create an Emeritus status for prior AB/TAG/BoD members

Open
#689 10 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

In w3c/w3process#688, @chaals mentioned the following:

However, I think there are better mechanisms available than ensuring some people get to hang around when the membership have hanged their mind about what they are looking for.

As an ex-member of the AB, and a member of W3C, I'm perfectly able to provide my input - whether asked for it or not. And like others in that position, I do so. Groups can, and sometimes does, ask specific people outside the group for input, if they feel it would be helpful.

This echoes a different conversation about giving AB and TAG members access to the w3c-ac-forum@ mailing list after their term is over even if they aren't an AC Rep.

So here's my suggestion: what if we created some kind of emeritus status for past AB, TAG, and BoD members, with full access to w3c-ac-forum@ and member-only GitHub repos, perhaps with an additional dedicated mailing list, and with a sense that they're providing in exchange some form of custody of institutional memory and can act as a resource for current governing bodies in exchange?

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 by reviewing the discussion in w3c/w3process#688 and the proposal in this issue, including the suggested mailing-list and repository access. Done means reaching agreement on the emeritus role, its privileges and responsibilities, then documenting the resulting process change.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.