Revisis was born of a desire to use a simple, intuitive and efficient system to review code. Using Revisis the team will be able to improve its code review process through a better documented workflow and less spent time per code reviewed.

High-level bundle features

• import patches/patchsets
• organize patchsets using more than one criteria (default: branch name)
• parse patches to display changes in a simple and clean interface
• allow comments in patches, using the following features:
  • group all related comments by patch
  • nest inline comments in patches
  • filter comments of a specific user in thread
• notification center: a system to notify team members about updates in sent/revised patches
• user profile: display some info about team members, statistics and recent activities
• define which criteria will be used to review a patch
• guarantee privileges to groups of users (in our own example a set of users able to comment on our main project, another in a shared library project, and with this create the possibility to revisis host multiple projects).
• view patchsets in different ways:
• by patch/commit
• by file
• all changes in one page
• filter (does not show) changes on non-text files (binary, pdf, etc)

Priorities

Which features are fundamental to a 'first release'?

• import patches/patchset (one of the main reasons to develop our own review tool)
• comments inline in the patches (the main reason to try a review tool instead of email)
• notification center( define how it will be done rss, email (dont like it, but maybe using smtp server + python smtplib?), just turn the patch title bold like in internet forums?)