Maybe add to `maintainer.md` – "On any `lifecycle stable` repository Ensure that a minimum of 2 tech staff"
Open
Nobody has claimed this yet.
documentation
lifecycle
maintenance
- Dominant language
- No language data
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
After we close #6 and understand what a "stable" API means, we may want to add to our maintainer.md definition something along the lines of:
"On any {lifecycle stable OR production OR whatever that definition ends up being} repository, the maintainer must do their best to ensure that a minimum of 2 people on the tech team are able to use the code using the stated API".
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 reading issue #6 to understand the proposed definition of a stable API, then review maintainer.md. The work is done when the repository lifecycle criterion and the requirement for at least two technically capable team members are agreed and accurately documented.
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