[Buildroot] Write Access to buildroot?

[Ulf Samuelsson <ulf.samuelsson@atmel.com>]

Peter Korsgaard skrev:
>>>>>> "Ulf" == Ulf Samuelsson <ulf.samuelsson@atmel.com> writes:
>>>>>>             
>
> Hi,
>
>  Ulf> In the openembedded project all the developers have
>  Ulf> write access to the development tree and can create
>  Ulf> their own branches within the tree.
>
>  Ulf> This makes it a lot easier to test other peoples patches.
>
> I don't agree, typing git add remove <foo> is trivial. That's the
> glory of the distributed nature of git.
>
>  Ulf> If you look at the statistics for the user repositories,
>  Ulf> you see that there are 5 people with user repositories,
>  Ulf> including mine, and last updates were from
>
>  Ulf> correa:          3 months ago,
>  Ulf> wberrier:       2 months ago,
>  Ulf> tpetazzoni:   9 days ago
>  Ulf> ulf:                 33 hours ago
>  Ulf> jacmet:         -
>
> which corresponds pretty nicely with the list of active developers:
>
> git shortlog -s -n 2009.05..
>     73  Peter Korsgaard
>     31  Thomas Petazzoni
>      9  Maxim Grigoriev
>      8  Will Newton
>      7  Sven Neumann
>      5  Gustavo Zacarias
>      4  Nigel Kukard
>      2  Bernhard Reutner-Fischer
>      2  Daniel Mack
>      2  Ulf Samuelsson
>      1  Alex Dobrynin
>      1  Evan Zelkowitz
>      1  H Hartley Sweeten
>      1  Lionel Landwerlin
>      1  Markus Heidelberg
>      1  Pwalters
>      1  laurent laffont
>
> Bernhard has his repo on repo.or.cz for historical reasons.
>
>  Ulf> This does not indicate a high level of popularity to me.
>  Ulf> Maybe people are keeping trees in other locations, but
>  Ulf> that means that they are hidden from most users.
>
> No, it indicates that buildroot is a small project with limited amount
> of active developers (and luckily a lot of outside contributers).
>
>  Ulf> In reality, the way Buildroot works today seems to be that
>  Ulf> people are sending patches to the mailing-list.
>
> And that's exactly what they should do. We *WANT* to see the patches
> on the mailing list so they can get reviewed.
>   
I do not see a contracdiction here.
You can have multiple persons work on one thing, and
once it is ready, the patches can be automatically
generated and sent to the mailing list.

What is the drawback of letting people work together
by allowing them to share a git.

People can share a git anyway, by using another git server,
but that makes it less visible to Buildroot users, so I would
like to avoid that.

> We also don't want to require outsiders to learn git in order to
> contribute patches.
>   
It it very different to require people to learn git, from
blocking people that wants to use git, to work together.

BR
Ulf Samuelsson