rust-lang / rust-lang/datafrog
bring this crate into conformance with compiler-team crate policy
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 899
- Forks
- 45
- PR merge metrics
- No merged PRs in 30d
Description
The compiler team is working on a standard policy around its external crates (see https://github.com/rust-lang/compiler-team/pull/19) -- we need to bring this crate into conformance, though the policy is not yet finalized, so it's not 100% clear what this means.
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 by reading the compiler-team crate policy proposal in https://github.com/rust-lang/compiler-team/pull/19 and identify the requirements that apply to datafrog. The issue cannot be considered done until the policy is finalized and this crate conforms to its resulting requirements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100