No explanation for what being on a team means for new contributors
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 363
- Forks
- 369
- Avg merge
- 1d 54m
- Merged PRs (30d)
- 59
Description
Ideally we would have a section in the forge where we explain this, and then we could link that section from the README in case any new contributors find their way here (could happen if they join the triage team early on)
This was a major source of confusion for me coming from nixpkgs, where teams are mainly just exist as a list of who to contact about certain things and don't convey any additional authority.
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 with the README and the forge area mentioned in the issue. Document what being on a team means for new contributors, particularly whether team membership conveys authority, and link the new explanation from the README.
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
- 35/100