diesel-rs/diesel

More code reviewers wanted!

Open

#1,186 opened on Sep 21, 2017

View on GitHub
 (118 comments) (23 reactions) (0 assignees)Rust (1,003 forks)batch import
good first issuehelp wantedmentoring available

Repository metrics

Stars
 (12,054 stars)
PR merge metrics
 (Avg merge 30d 16h) (30 merged PRs in 30d)

Description

With the push to 1.0, the current pool of reviewers is starting to run low on bandwidth. We're looking for more people to help get involved with code review. You don't need to be familiar with Diesel's internals to help. Most people who have been on the Diesel core team got started by doing code review. If you're unsure what a piece of code does or why it's being done a certain way, just ask! (Make sure that the commit message doesn't answer that question already though). Don't feel like you can't ask a question just because other reviewers might already know the answer. We're happy to help you get up to speed.

Contributor guide

Research direction
Review the contributing guidelines and look for recent pull requests with the 'needs review' label to start reviewing.
Tech stack
rust
Domain
backend
Issue type
Chore
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustCode review experience
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85