Open source / The craft of review
Your tools should belong to you.
Why we’re building OpenReview in the open, one pull request at a time.
THE ANATOMY OF A BETTER REVIEW
LESS FRICTION AT EVERY STEP.
Developers spend a remarkable amount of their lives inside tools they cannot inspect or influence. We think the place where you discuss, question, and improve your code should be different.
OpenReview is an open-source code review platform built for developers and teams who want a faster, cleaner way to review code. Building in the open is part of that promise.
01 — Understand the tool.
Trust is easier to build when the details are visible. You should be able to read how a feature works, understand why a decision was made, and trace an unexpected behavior back to its source.
Source access does not mean everyone must read every line. It means the option exists. It means explanations can point to something concrete. It means a community can help make the tool better informed and more accountable.
For a code review tool, that transparency feels especially appropriate. The same practice we encourage in your projects—inviting other people to examine a decision—is how we want to build ours.
02 — Shape what comes next.
The people closest to a workflow notice its friction first. A repeated click, a lost thread, a confusing state: these details are easy to miss from a distance and impossible to ignore when you encounter them every day.
“Good tools belong to their community.”
Contributions are not only code. A clear bug report, a thoughtful design critique, or an explanation of a real team’s workflow can change the direction of a feature. We want that context in the conversation.
Start small. Describe the problem before proposing the implementation. Show us the moment where the tool gets in your way, and help us understand what a better outcome would look like.
03 — Build it together.
We are not trying to make the loudest tool in your stack. We are trying to make a calmer place for an important part of your work: understanding a change and deciding, together, whether it is ready.
That means caring about the details. Readable diffs. Conversations with context. Resolutions that are easy to follow. An interface that makes the work feel lighter instead of adding another layer to it.
You can follow the project, read the source, and contribute on GitHub. Open an issue. Ask a question. Tell us what your team needs.
The next good idea can come from anyone. We would like to leave the door open.
Keep reading / Engineering