Re: How to work collaboratively with Gerrit?

On Tue, Aug 24, 2010 at 08:37, Pat Notz <[EMAIL PROTECTED]> wrote:
> On Tue, Jul 20, 2010 at 7:56 AM, Shawn Pearce <[EMAIL PROTECTED]> wrote:
>>
>> Within Google (and at least one other company using Gerrit) we have
>> recently setup a bleeding edge master version of Gerrit Code Review
>> and are using the personal sandbox branch concept:
>>
>>  Push Branch  +3  refs/sandbox/${username}/*
>>  Code Review  +2  refs/sandbox/${username}/*
>>  Submit           +1 refs/sandbox/${username]/*
>>
>> This gives each developer their own area to work in.  But its
>> primarily meant for backing up your laptop or your workstation
>> overnight, or to help you move a patch between the two before its
>> ready to get sent to a reviewer.  We aren't really using it as an area
>> for peer collaboration.
>>
>
> I'm considering doing something similar.  Do you still like this idea
> after a month or so of usage?

I don't know.  I don't use them.  A quick survey of our internal
server shows 1 sandbox branch.  1.  :-\

> Also, if you wanted to support collaboration on these branches, would
> it make sense to allow others to give others upload permission like
> this:
>
> Read Access     +2 refs/sandbox/*
>
> and, possibly,
>
> Code Review      +2 refs/sandbox/*
>
> ?
>
> With these two additions it seems like users would still maintain
> control of their branches but could collaborate with other devs.

Yes, that does make sense.

-- 
To unsubscribe, email [EMAIL PROTECTED]
More info at http://groups.google.com/group/repo-discuss?hl=en