opencontainers / opencontainers/tob
CHARTER: No Confidence Motions?
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 91
- Forks
- 58
- PR merge metrics
- No merged PRs in 30d
Description
Right now if the TDC Maintainers feel that the TOB is not fulfilling their duty correctly, they have no recourse other than to go to the Linux Foundation (and I'm not sure how that process would even work). Should we have a "no confidence motion" concept in the Charter (such as a qualified super-majority of TDC Maintainers can trigger the TOB be dissolved and a special election for all seats)? Then again, we've never had any tensions between the TOB and TDC Maintainers so maybe this is purely a theoretical thing which isn't worth extra text in the Charter? But then again, if we ever need it then it'd be too late to ask the TOB to add it.
I am writing this as a separate issue, because it won't be included in my first round of charter refactoring but it is something that I wanted to open a discussion about.
Contributor guide
No contributing guide indexed for this repository
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 reading the Charter and the question in this issue about a no-confidence motion for the TOB. Determine whether the project wants such a mechanism, define its scope and approval threshold, and document an agreed Charter change if the discussion reaches a decision.
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
- Needs clarification
- Newbie friendliness
- 15/100