Resolve individual repository access.
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 363
- Forks
- 369
- Avg merge
- 1d 54m
- Merged PRs (30d)
- 59
Description
Part of RFC 2872 specifies that individuals should not be given permissions to repositories. We have a few individuals currently with access that we should resolve. They currently are:
- areweasyncyet.rs:
upsuper- Recommend: Create a team, figure out relationship with web-presence.
- backtrace-rs:
alexcrichton- Recommend: Remove Alex, he's been uninvolved for a few years.
- cargo-bisect-rustc:
ehuss- Recommend: Create a team, subteam of compiler (@ehuss assigned).
- cc-rs
NobodyXu- Recommend: Create a team, subteam of libs.
-
flate2-rsalexcrichtonbrson- Recommend: Remove Alex (specified he has handed off) and brson (hasn't been involved).
- google-summer-of-code
Kobzoljackh726- Recommend: Create a team? Working-group? Where to slot it?
- log
Thomasdezeeuw- Recommend: Create a team, subteam of libs.
- mdbook
Dylan-DPC- Recommend: Create a team, subteam of devtools (@ehuss assigned).
- pkg-config-rs
sdroege- Recommend: Create a team, subteam of libs.
- project-deref-patterns
traviscross- Recommend: Switch to lang-ops.
- rustc_codegen_cranelift
bjorn3- Recommend: Create a team, subteam of compiler.
- socket2
chansukesfacklerThomasdezeeuwcarllercheDarksonn- Recommend: Create a team, subteam of libs.
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 RFC 2872 and the repository list in this issue, including each unchecked recommendation and its current individual access. Confirm the appropriate team or ownership relationship for every repository, then verify that individual permissions have been replaced or removed and all checklist items are resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- authorization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 20/100