this post was submitted on 28 Jul 2023
37 points (97.4% liked)

Rust

6035 readers
6 users here now

Welcome to the Rust community! This is a place to discuss about the Rust programming language.

Wormhole

[email protected]

Credits

  • The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 13 points 1 year ago (2 children)

We need clearer rules on which pull requests require code reviews.

Weird to me that any pull request would not require a code review.

[–] aloso 4 points 1 year ago (1 children)

True, code for critical IT infrastructure should always be reviewed. But from what I understand, this is difficult because there is one full-time developer (paid by the Rust Foundation) and a small number of volunteers, who don't have the time to review all the employee's changes.

[–] [email protected] 1 points 1 year ago (1 children)

Easy solution, give review rights to a few volunteers. Pick from the regular contributors.

[–] aloso 1 points 1 year ago (1 children)

On GitHub, everybody has the ability to review pull requests, even you. But there still aren't enough volunteers who review PRs.

[–] [email protected] 1 points 1 year ago (1 children)

Sure, but you should always have a core contributor required to review code before it gets merged. That's a feature GitHub offers, and it should be used. Block all PRs unless there's at least one review from a trusted contributor, and consider requiring a second review from any source.

[–] aloso 1 points 1 year ago (1 children)

That doesn't solve the issue that there are too few contributors. Requiring a review doesn't ensure that someone reviews the code.

[–] [email protected] 1 points 1 year ago

Requiring a review from a trusted contributor ensures that one of those trusted contributors reviews the code. The one main maintainer should add more people to that trusted circle, which will ensure that at least one of those will review all code that goes into the codebase.

If people see that code isn't being merged, someone will step up to request to be in that trusted circle.

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago)

Yeah. At my current and previous jobs, literally everything going into an actual product required a code review, and that's despite all the code being written by employees that you could generally trust. Even if my boss or literally the most experienced and trusted dev wrote a commit, it still needed a review.

It's feels weird submitting my own code without a review for side projects. So many bugs have been caught by reviewers that writing code that another person would use without it being reviewed feels just wrong.