<div dir="ltr">Something I would like to stress, aside from philosophical considerations, is that the new process is working. There is not a single patch stuck in the queue (couple of old ones from Walter but they are just blocked on another set he submitted, which is going to land soon).<br>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On 9 June 2013 11:51, Daniel Narvaez <span dir="ltr"><<a href="mailto:dwnarvaez@gmail.com" target="_blank">dwnarvaez@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div class="im">On 9 June 2013 01:38, Bernie Innocenti <span dir="ltr"><<a href="mailto:bernie@sugarlabs.org" target="_blank">bernie@sugarlabs.org</a>></span> wrote:<br></div><div class="gmail_extra">
<div class="gmail_quote"><div class="im">
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>On 06/07/2013 09:10 AM, Daniel Narvaez wrote:<br>
> No, just glucose. You can see the exact list of modules on<br>
> <a href="https://github.com/sugarlabs/" target="_blank">https://github.com/sugarlabs/</a><br>
<br>
</div>By the way, what is "sugarlabs", a shared account?<br>
<br></blockquote><div><br></div></div><div>It's an organization<br><br><a href="https://github.com/blog/674-introducing-organizations" target="_blank">https://github.com/blog/674-introducing-organizations</a><br></div>
<div class="im"><div> </div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Wouldn't this subvert GitHub's philosophy that all forks are created<br>
equal, by creating one that looks more official than the others?<br></blockquote><div><br></div></div><div>In my experience the large majority of github repository has an official repo, very visibly linked from the project official website. For example<br>
<br><a href="http://nodejs.org/" target="_blank">http://nodejs.org/</a><br><br></div><div>People fork the official repo and send patches through pull requests.<br><br></div><div>Which is exactly what we are doing.<br></div>
<div class="im"><div> </div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
If it seems that this approach wouldn't be feasible for a project with<br>
many collaborators, check out <a href="http://git.kernel.org" target="_blank">http://git.kernel.org</a> . Most of the repos<br>
under kernel/git/ are clones of the kernel tree with various patches<br>
applied. The most "official" tree that I can think of is<br>
kernel/git/torvalds/linux.git, the one maintained by Linus. There are of<br>
course many other public forks of the Linux kernel hosted on other sites.<br></blockquote><div><br></div></div><div>I can't think of a single github repository that follows the kernel development model. I'm sure there but I'm also pretty sure it's not the normal development model for github repositories.<br>
</div><div class="im"><div> </div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
I'm making the assumption that switching to GitHub was motivated in part<br>
by the desire to adopt the bazaar development style. If it's not the<br>
case, then GitHub may not be a very good fit for a central repository<br>
shared by multiple committers.<br></blockquote><div><br></div></div><div>If with bazaar development model you mean kernel like, I don't think that was one of the reasons. But as I said I don't think github pushes that model either. It's pretty similar to gitorious really, just a better implementation of it :)<br>
</div><div> </div>In general I don't think kernel development practices are a good model for our community, as proved by the attempt to push their patch review practices and badly failing. We are a very different kind of communities.<br>
</div></div></div>
</blockquote></div><br><br clear="all"><br>-- <br>Daniel Narvaez<br>
</div>