Define a best practice around periodic repository reviews
Open
@jdhoffa is already working on this.
Since Jan 25, 2024.
quarterly
- Dominant language
- No language data
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Summary of a discussion had between myself and @Antoine-Lalechere @cjyetman @MonikaFu @jacobvjk
Quarterly Reviews:
The idea of periodic reviews to discuss maintainer roles, repository statuses, and potentially lifecycle changes was proposed to ensure alignment and appropriate resource allocation.
##Time Allocation:
There's a suggestion for dedicated maintenance time (such as a maintenance day) to ensure repositories are kept up-to-date and to allow maintainers to focus on their repositories.
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.
Assessment
This issue has not been assessed yet.