governance: automatic removal rules are only protected by lazy consensus
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 717
- Forks
- 1.2k
- Avg merge
- 3d 15h
- Merged PRs (30d)
- 19
Description
Governance says:
The FAQ section is informational and can be changed by lazy consensus unless challenged. If no consensus can be reached, the matter may be resolved by majority vote.
And in the FAQ, there is:
How do I remove an inactive maintainer?
[...] A maintainer with no project activity for a year will be treated as if they had resigned. [...]
That would mean that, as it is part of the FAQ, that duration/rule it is under lazy consensus. That should be treated as a governance change instead.
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 by locating the Governance and FAQ sections quoted in the issue; no file or test is named. Check how the inactive-maintainer rule and consensus process are documented, then update the governance treatment so the rule is not changed under lazy consensus. Done means the documentation clearly classifies this automatic-removal rule as a governance change.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100