Review Board

@reviewboard.org

10 Followers 4 Following

Powerful, extensible, and free code and document review for teams of all sizes, supporting a wide variety of code repositories and integrations. https://www.reviewboard.org

IMPORTANT UPDATE: Review Board's taking the game industry's lead and dropping all physical products. As of now, all code review whiteboards, projectors, and red/green/yellow highlighters are discontinued. All code reviews should now be conducted using the digital Review Board product freely available at ReviewBoard.org Plus and Enterprise plans are available to help you transition to this new digital future.
The review banner showing "Add General Comment" and "Ship It!" Quick Access buttons to the right of the "Review" menu. The gear menu for pinning actions is open, showing a "Pinned Actions" header followed by "Create Review" and "Edit Review" (which are both unpinned) and "Add General Comment" and "Ship It!" (which are both pinned).
A comment dialog full of spelling errors, Markdown formatting, and a code sample. The text says "Can you please make sure to spell-check your comments? We need to be professional," except with typos all throughout. Squiggly red lines highlight the typos. The browser's pop-up menu is shown for the misspelled word "professional", offering spelling suggestions and native writing assistance features.
A review by a user with an Architect role badge, along with a reply from a user who has Security Specialist and Team Lead roles.
The document viewer containing a presentation about hiring an office cat. In the header bar above the document are navigation and zoom controls. Floating on the right of the document is a toolbar for commenting controls. There are two draft comments in the document, a region and a text selection comment.
The review bar at the top, showing Add General Comment and Ship It actions. On the right is a menu showing the actions available to add (Create Review, Edit Review, Add General Comment, and Ship It).
Screenshot of a new banner for administrators under the Review menu saying "This review request has an unpublished draft" with a "View draft data" link.
An example post on Microsoft Teams. It shows a review request with the summary "Add an integration for MS Teams." The description says "This adds the Microsoft Teams integration option. Like the existing Slack integration option, this integration will post a message to an MS Teams chat channel after a review request has been updated." There's information on the source code repository and branch, and a screenshot uploaded to the review request.
A screenshot of the diff viewer in a single-column mobile mode, showing deleted and inserted lines, comments made on the lines, and indicators showing that the content in some lines moved to new locations.
A screenshot of a cute floating marshmallow ghost character with a wooden belt. Two versions of this character's color palette are being shown using a split-screen image diff.
A screenshot of a review request in Review Board in Dark Mode. This shows a summary of a change, description, and other information, along with some screenshot file attachments demonstrating the change being made.
Review Board's PDF document review, showing a diff of two PowerPoint presentations and highlighting the text that changed. The presentation topic is "Writing Enterprise WebApps in Bourne Shell." Both state "Bourn Shell: Why Not?" with bullet points "It's on every system" and "It's memory-safe". They differ in the third bullet point. The left says "You definitely won't completely nuke your system unexpectedly." The right says "You might not completely nuke your system unexpectedly, maybe." The differences in wording is highlighted in red on the left, green on the right.