Patch Pilot report

[Martin Pool]

2009/11/23 Ian Clatworthy <ian.clatworthy at canonical.com>:
> Andrew Bennetts wrote:
>
>> Here's some scattered observations from the week:
>
> Thanks for writing up this report. Lots of good information here.

Yes, and thanks for doing it too.

I was wondering about the bottom line too:

 * How much time did this take?  It seemed like it was more than half
your working time?

 * Do you think it was worth it?  It seems so?

Also one of us should write it up on the project blog.

> It's tedious looking up which contributors have signed Canonical's contributors agreement.

Yes, it is.  It's interesting how some things we're aware of in the
background become more sharp when you concentrate on doing reviews all
week.

It should be possible to write an api client script that checks this,
and then to hook that into a bot that comments on reviews.

>> Generally speaking, that Launchpad page fails as a “what
>> should I [the patch pilot] look at next” page; any section of that page can have
>> patches deserving of attention from a patch pilot.  I touched patches from the
>> top and bottom of that page.
>
> The thing I love about LP reviews is that it works so nicely across
> every project on LP. The thing I dislike about it is that BundleBuggy
> was a better queue manager for bzr core reviews.

I agree, BB had somewhat better workflow by being quite clear about
what things you could/should act on next for each type of work.

I believe Tim is working on lp reviews so he might appreciate some
more feedback.  Or he might already know it and just not have got
around to fixing it yet.

-- 
Martin <http://launchpad.net/~mbp/>