I'll take the action item to remove anyone in the rotation who is not
actively working on Webkit / is not a committer.

In the past, I've floated the idea in the past of having a "Webkit deputy"
who helps the gardener keep the canary green.  I'm not sure if that would
help, though.

Regards,
Glenn


On Wed, Sep 23, 2009 at 8:40 AM, David Levin <le...@chromium.org> wrote:

> I find that being a WebKit gardener is always dancing on a minefield
> regardless of my familiarity with the WebKit code base. Look at yesterday
> for an example.
> In addition, we have several gardeners who are not actively working on
> WebKit (amanda@ has 0 WebKit commits, pinkerton@ has a few all in 2008).
>
> Lastly, can we add anyone to the rotation who has ideas how WebKit
> gardeners should/can do their job better? (This will help them in getting
> more ideas.)
>
> Dave
>
>
> On Wed, Sep 23, 2009 at 7:53 AM, Dimitri Glazkov <dglaz...@chromium.org>wrote:
>
>> On Wed, Sep 23, 2009 at 7:46 AM, Mike Pinkerton <pinker...@chromium.org>
>> wrote:
>> >> It is hard to be a WebKit gardener if you do not have WebKit commit
>> access.
>> >> Sometimes the gardener has to commit a quick bustage fix upstream or
>> roll
>> >> back a fellow Chromium committers change to WebKit.
>> >> -Darin
>> >
>> > Correct, it is hard, but many/most of us who are webkit
>> > sheriffs/gardeners are not webkit committers (for example, the entire
>> > mac group). I don't understand your point. Are you saying that only
>> > webkit committers should be on the webkit sheriff rotation?
>>
>> In my experience, better familiarity with WebKit code base is a huge
>> advantage for a gardener. I am almost tempted to say that if you're
>> not actively working on WebKit, being a gardener will be a foreign and
>> "dancing-on-a-minefield"-type task.
>>
>> :DG<
>>
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com 
View archives, change email options, or unsubscribe: 
    http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---

Reply via email to