More code reviewers wanted!

[sgrif]

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.

[juliusdelta]

Nice. Is the best way to get started to just review and add comments/questions to PRs?

[sgrif]

Yup. If you'd like I can add you to the github group which gets pinged for code review

[juliusdelta]

Sure that’d be great!

[toddWannaCode]

I am really interested in this but I am just getting started with diesel.

[killercup]

@toddWannaCode that's absolutely fine! Most PRs are quite isolated in scope so you don't need to know everything beforehand. :) Feel free to have a look at and review PRs to get a feel for it, and if you like it, ping me (or another core team member) and we'll add you to the reviewers team.

[leshow]

I'd be interested in jumpiing into some code reviews, if you folks are still looking for people.

[killercup]

Absolutely! Want me to add you to the Reviewers team? Evan Cameron <notifications@github.com> schrieb am So. 24. Sep. 2017 um 23:22:

…

I'd be interested in jumpiing into some code reviews, if you folks are still looking for people. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1186 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABOX5OL_jjKy7inV3oLryKG0EqflFLaks5slsgOgaJpZM4Pf3MF> .

[toddWannaCode]

Hey I would be like to be a member of the Reviewers team. Thanks. @killercup

[killercup]

@toddWannaCode, welcome to the league of extraordinary reviewers! :)

[leshow]

@killercup Sure, sounds good.

[killercup]

@leshow, welcome to the Four Nine Horsemen of the Code Review!

[ecasilla]

Count me in also. I would love to help anyway I can.

[killercup]

@ecasilla, thank you for joining the Order of Magnitude!

[ecasilla]

@killercup How will the mentoring work exactly is there a gitter for the core team?

[sgrif]

@ecasilla You can ask questions either in the public gitter or as comments on the PRs you're trying to review (feel free to ask questions after things have been closed/merged as well)

[gsquire]

I don't have much experience in the codebase but I'd like to help review.

[jbcden]

I'm a bit late to the party and I haven't really gotten a chance to use diesel, but I'm trying to get into Rust more and would love to help with reviews!

[bahlo]

Hey, I'd also like to be in the review team.

[retep007]

Hi, count me in

[sgrif]

@retep007 I've added you to the team -- You'll get pinged on future PRs, but feel free to review any of the open PRs in the mean time. There's quite a few open right now.

[sgrif]

(Note: Everyone who's replied to this has been added shortly after replying, I'm only singling that person out because there happens to have been an extremely high volume of PRs opened in the past 24 hours and I assumed the were around right now)

[sgrif]

I should also mention -- If anyone tries to review a PR, and feels like they don't understand enough to properly review it, please ask questions on the PR. We don't mind explaining things that aren't clear, and hearing what needs more context before the PR is opened is extremely helpful.

[logotie]

Hello all, is there any chance I could please be added also? I am however very much a beginner with Rust :)

[sgrif]

Hey folks, just a heads up, I did some cleanup tonight. Anyone who hasn't commented on an issue in the past month will have been removed. If you'd like to be re-added, please comment again on this issue.