OE git repository organization

OE git repository organization

[Cliff Brake]

Now that we have the capability to do per branch permissions, etc, I
would like to discuss what makes sense going forward for repository
admin.  My initial thoughts:

- put all user branches in openembedded-user
- restrict branch creation on the main openembedded repo to commonly
used branches

We can also do things like give users permission to branches that
start with their name, etc.  This would allow rewriting history on
user branches, etc.  That said, it may make more sense to just do user
branches on github as some are already doing.

Thanks,
Cliff

-- 
=================
http://bec-systems.com

Re: OE git repository organization

[Chris Larson]

On Tue, Dec 21, 2010 at 2:53 PM, Cliff Brake <cliff.brake@gmail.com> wrote:
> Now that we have the capability to do per branch permissions, etc, I
> would like to discuss what makes sense going forward for repository
> admin.  My initial thoughts:
>
> - put all user branches in openembedded-user
> - restrict branch creation on the main openembedded repo to commonly
> used branches
>
> We can also do things like give users permission to branches that
> start with their name, etc.  This would allow rewriting history on
> user branches, etc.  That said, it may make more sense to just do user
> branches on github as some are already doing.

This is a good idea, at least for those who want to use it.  It would
certainly clean up the branch mess we have in the main repository
today.  We may want to limit tag creation to specific people, to avoid
cluttering the tag namespace.
-- 
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics

Re: OE git repository organization

[Khem Raj]

On Tue, Dec 21, 2010 at 2:12 PM, Chris Larson <clarson@kergoth.com> wrote:
> On Tue, Dec 21, 2010 at 2:53 PM, Cliff Brake <cliff.brake@gmail.com> wrote:
>> Now that we have the capability to do per branch permissions, etc, I
>> would like to discuss what makes sense going forward for repository
>> admin.  My initial thoughts:
>>
>> - put all user branches in openembedded-user
>> - restrict branch creation on the main openembedded repo to commonly
>> used branches
>>
>> We can also do things like give users permission to branches that
>> start with their name, etc.  This would allow rewriting history on
>> user branches, etc.

hmmm yeah and one could use these branches to share patches without overhead of
branching policy we have today.


 That said, it may make more sense to just do user
>> branches on github as some are already doing.
>
> This is a good idea, at least for those who want to use it.  It would
> certainly clean up the branch mess we have in the main repository
> today.  We may want to limit tag creation to specific people, to avoid
> cluttering the tag namespace.

I agree on that.

> --
> Christopher Larson
> clarson at kergoth dot com
> Founder - BitBake, OpenEmbedded, OpenZaurus
> Maintainer - Tslib
> Senior Software Engineer, Mentor Graphics
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>

Re: OE git repository organization

[Marco Cavallini]

Cliff Brake ha scritto, Il 21/12/2010 22:53:
> Now that we have the capability to do per branch permissions, etc, I
> would like to discuss what makes sense going forward for repository
> admin.  My initial thoughts:
> 
> - put all user branches in openembedded-user
> - restrict branch creation on the main openembedded repo to commonly
> used branches
> 
> We can also do things like give users permission to branches that
> start with their name, etc.  This would allow rewriting history on
> user branches, etc.  That said, it may make more sense to just do user
> branches on github as some are already doing.
> 
> Thanks,
> Cliff
> 

Fine

/marco