Recall procedures for TAG and AB
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 262
- Forks
- 194
- PR merge metrics
- No merged PRs in 30d
Description
The Board has a removal procedure, but the TAG and AB do not, beyond the CEO's ability to discipline them.
Given the direct process role that they now play when Councils are convened, it seems appropriate to make the TAG and AB more accountable to the Membership by defining a procedure for recalling them.
Straw-man proposal: a recall can be instigated by a demand signed by 20 Member representatives, and it's executed as a requisite member vote.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with governing-docs/bylaws.md, especially the linked removal and requisite member vote sections, then compare them with the Process document's discipline provisions. The work is done when the Membership-approved recall procedure for TAG and AB is agreed and documented with clear initiation and voting rules.
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
- 25/100