How should the TAC handle overdue PR decisions?
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 152
- Forks
- 86
- Avg merge
- 5d 14h
- Merged PRs (30d)
- 9
Description
While the TAC has a documented decision process for open PRs,...
...this document doesn't address is what we do in case the waiting period ends and we still don't have enough approvals. I'm not sure there is really a solution to this though, other than not re-electing TAC members who are failing to respond in a timely manner...
Originally posted by @lehors in https://github.com/ossf/tac/pull/402#pullrequestreview-2396112496
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
Read process/TAC-Decision-Process.md, especially the issue/pull-request types section, and review the discussion linked from pull request #402. Determine whether the waiting-period gap has a documented resolution; done means the TAC's handling of overdue decisions is clearly recorded in the process documentation.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100