GSoC/GCI Archive
Google Summer of Code 2012

Review Board

Web Page: http://code.google.com/p/reviewboard/wiki/Student_Project_Ideas

Mailing List: https://groups.google.com/forum/?fromgroups#!forum/reviewboard

Review Board is a powerful open source web-based code review tool that offers developers an easy way to handle code reviews. It's used in several open source projects, including parts of KDE, as well as many startups and large companies, including Twitter and Yahoo, helping them to write better code and more stable products. Review Board is built on top of Python and Django. It works on Linux, Windows and MacOS X, and supports a wide variety of source code management systems, including Subversion, CVS, Perforce, Git, Mercurial, Bazaar, and ClearCase. You can find out more information about Review Board at http://www.reviewboard.org. If you're a student participating in Review Board, please read our Summer of Code information page. We also offer Review Board hosting for projects participating in Summer of Code.

Projects

  • "Latest changes" feed in user Dashboard The user dashboard is the starting point in the review workflow, thus its purpose should be to present as much relevant information and allow to the user to prioritize and easily navigate to the requests he finds most interesting. Currently, the dashboard is composed of a request table, the only available information, besides the summary, being available as custom columns with binary data (has/hasn’t received a ShipIt, has/hasn’t been commented). My proposal is to add a new view to the dashboard which displays the latest changes to any requests considered interesting by the user as an action feed.
  • RBTools Improvement Currently RBTools consists of a single monolithic script used for interacting with Review Board. Maintaining this script has become difficult, and some effort has been put towards creating a new tool set. This involves the creation of a more “Git like” set of commands, and an improved Python API. Much of the progress has been made by former students, and the code is either incomplete or out of date. I would like to focus cleaning up the command side of the new RBTools, and help in completing the API.