rust-lang / rust-lang/libs-team
Come up with a team charter
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 178
- Forks
- 28
- Avg merge
- 15m
- Merged PRs (30d)
- 1
Description
We should write up a team charter for Libs that outlines what we do and how we do it. From that charter we can work some process into this repo in the form of labels, projects (columns in the Libs Team project), issues, docs, and a regular calendar that help us keep track of what we're working on.
The project linked to this issue is a bit of a scratchboard of things we currently do and think we should do.
UPDATE (2020-07-07): We've got a working draft document that should become an RFC here
If you've got any comments or would like to participate please check it out!
UDATE (2020-09-11): There's now an RFC establishing a Libs charter here
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
The working draft is linked in HackMD, and the resulting charter is referenced in rust-lang/rfcs pull request 2979. Start by reviewing those documents and the Libs Team project scratchboard; the work is complete when the team charter and its related repository processes are established.
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
- Mostly clear
- Newbie friendliness
- 20/100