|
CurrentIdeas
Current ideas for the project
Global
Code ReviewScenarioHow?Someone review changesets, as reported by a SCM tool (SVN for the prototype, but it expected to be abstracted in the future to allow extensions for many others). That could be extended to review a set of consecutive changeset, a diff between two arbitary revision or simply a set of selected files of one revision. The review basically consists of "inline comments" made over whatever line of any file modified in the changeset. It also contains a "general comments" section, on which, well, general discussion about the changeset could happen. Finally, the reviewer can mark the review as passed, failed, or none. A passed review just sends a notice. A failed review should generate a new ticket on a external tracker (Roundup for the prototype, expected to be abstacted to allow extensions too). A review that is neither passed nor failed should send a notice and it keeps hanging around until the reviewer mark it as passed or failed. That should be useful when the reviewer has some questions that are best answered on the context of the review tool (that is, using "inline comments" to ask questions) but he is unsure that this particular issue is really a problem. The author(s) of the reviewed code (and, in general, anybody) can add inline and general comments at any time. The resulting conversations will be presented as stacked comments (because threaded comments seems overkill to me at this time). Similar Projects / Products
Other linksSource BrowsingNothing is defined at the moment. Just some ideas:
Project PlanningNothing is defined at the moment. Just some ideas:
|
Sign in to add a comment