Some backstory on this..
We had a project a couple semesters ago that provided a Python API to
Review Board that other programs could use, along with some useful
command line tools for operations such as creating, modifying, closing
review requests. Other useful things like easily applying a patch from
a review request.
A lot of progress was made, but it wasn't complete. That's where
Alexander's work comes in.
This will all be part of RBTools. Instead of post-review continuing to
grow into an even more giant swiss army knife, we'll be able to
provide little single-purpose scripts that can act as building blocks
for more complex behavior.
post-review will remain, but will be slimmed down, as the code it's
calling will exist in the API. Big maintenance win.
We'll have a branch soon with the in-development code as it gets reviewed.
This is all a precursor to the RBTools 1.0 release.
On Wednesday, April 27, 2011, Dan Savilonis <d...@n-cube.org> wrote:
> Hi Alexander,
> I read your proposal and I found it to be a bit vague. After I
> searched for your previous proposal message, I found you were
> discussing a new version of post-review, so I assume that that is
> still within the scope of this project? When you talk about new
> commands, can you cite some examples of currently-lacking
> functionality? While it's good to improve the internals of Review
> Board, I think it's most important to provide an improved experience
> for users. What will the new API allow that post-review doesn't now?
> Something like a GUI interface, while convenient (to some), doesn't
> provide a lot of value if it doesn't enhance the process for
> submitting and maintaining code reviews.
> So, I'd be most interested in hearing some specific examples of how
> the functionality will be improved, not just the interfaces
> Please do commit your changes as they are in progress to your own
> repository or branch. There is no harm in doing this, but every
> benefit for people to see the progress being made before it is
> On Apr 26, 2:41 am, Alexander Solovets <asolov...@gmail.com> wrote:
>> Hello, Review Board members!
>> My name is Alexander and I will work on my project about enhancing RB API
>> during GSoC'11. You may look through my proposal on GSoC official site. So
>> far I had conversation only with Christian Hammond and would like to meet
>> with the rest team. I already have a humble experience in contributing to
>> the open-source projects and I know that each of them has its own
>> mini-culture, so I'd like to know yours. I've already read "Getting started"
>> wiki section and wondering whether you have some sort of informal guidelines
>> about coding style, commit messages, etc.
>> It was unusual that nobody comment my proposal during the application review
>> period. So I greatly appreciate if you do it now (of course if there is
>> something to say). Also I'd like to hear your wishes about the final result.
>> At last, I should know how can I present my work. I can either work with
>> cloned repo and post the changes from time to time or commit directly to
>> main repo.
>> Thank you all for chosen me and for such exciting opportunity to work with
>> you! Review Board rocks!
>> Sincerely, Alexander
> Want to help the Review Board project? Donate today at
> Happy user? Let us know at http://www.reviewboard.org/users/
> To unsubscribe from this group, send email to
> For more options, visit this group at
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
Want to help the Review Board project? Donate today at
Happy user? Let us know at http://www.reviewboard.org/users/
To unsubscribe from this group, send email to
For more options, visit this group at