<br><br><div class="gmail_quote">On Wed, Jan 7, 2009 at 4:28 PM, Jeff Mitchell <span dir="ltr"><<a href="mailto:kde-dev@emailgoeshere.com">kde-dev@emailgoeshere.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">Magnus Bergmark wrote:<br>
> That depends on the model of development. With a centralized repo,<br>
> almost every developer should have push access to it, yes. However,<br>
> one-shot contributors shouldn't get push access to the repo, but should<br>
> instead send in patches or pull requests (in case of GitHub).<br>
<br>
</div>Yes, obviously. I was speaking in terms of our current development model.<br>
<div class="Ih2E3d"></div></blockquote><div><br>Oh, I though you guys used a traditional centralized model with SVN. My bad. Usually that is something that can be safely assumed with regards to OpenSource and SVN. :-)<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d"><br>
> I still doesn't understand what you are trying to say here. All branches<br>
> in the public repo is visible in your local clone.<br>
<br>
</div>That's because you're thinking of the rails repo, whereas my example is<br>
the "normal" github method, where everyone has their own account and<br>
forks off the main repo. If you look at it in that context it will<br>
probably make sense, and it's why the everyone-shares-one-account model<br>
is the only usable way for any decent sized project on Github.<br>
</blockquote><div><br>How would multiple repos be easier on a non-GitHub host? I'm pretty sure that most people usually clone from the same repository in Gitorious and <a href="http://get.or.cz">get.or.cz</a>, so to do the same on GitHub is a non-difference. We are both agreeing that handling the case where people also have forks is harder. <br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<snip, snip, snip, because you keep repeating what I had already said><br>
<div class="Ih2E3d"></div></blockquote><div><br>I'm sorry.<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">
<br>
> Why is it useful for Github to do the merge for you?<br>
><br>
><br>
> Well, it's useful if you get a long list of small commits. Now, this may<br>
> not happen here, but in many projects, people can contribute with small<br>
> commits like spelling fixes and it would be easy if you didn't have to<br>
> fetch your repo, add the other fork as a remote, fetch the remote, get<br>
> the specific commit, cherry-pick it into your own repo, push it and then<br>
> remove the remote repo.<br>
<br>
</div>Umm...or you can just have people send it in with format-patch. No need<br>
to overly complicate things for a spelling fix. In fact, the above<br>
method is overly complicated for users as well as developers. Much<br>
easier to simply have them clone the public repo, make their change, and<br>
use format-patch to send in the change.<br>
</blockquote><div><br>Yes, that is correct. format-patch is obviously a better choice here. Still, the UI on GitHub handles this even more easy IMHO, and one method does not remove the possibility of using the other.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
This gets even more complicated for users later. For a fresh fork of<br>
Amarok they just took there wouldn't be a problem...they could just<br>
assume that they are up-to-date, make their change, push to their repo,<br>
and send a pull request.<br>
<br>
If they keep their fork of the repo, it will get out of date. So<br>
instead of a simple git pull, they have to git pull from the remote ref,<br>
merge into their "upstream" branch, push that up to their account, then<br>
send the pull request.<br>
<br>
It's not that difficult, but it is more complicated.</blockquote><div><br>True. Taking user training into consideration is also important. Newbies may forget to update their repository before sending the pull request and this might introduce some overhead. <br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">
> > GitHub is like any ordinary repo hosting server, anything you can do<br>
> > with your own bare-bones git hosting can be done on GitHub.<br>
><br>
> Not actually true. But I'll let it slide.<br>
><br>
><br>
> Could you please elaborate. Let's say you create a repo and then just<br>
> forget about the web site. What will be different from your SSH access<br>
> to a repo on server X and the SSH access to the repo on GitHub's server?<br>
<br>
</div>You can't do HTTP, for instance. And from what I've heard you can't<br>
integrate it with Trac or Jira, but that's just hearsay. Github also<br>
has a bunch of ways to do CIA-like things, or send commit notifications<br>
to email addresses or IMs, but you lose the flexibility you get when you<br>
can control all of the hooks yourselves.<br>
<div class="Ih2E3d"></div></blockquote><div><br>I heard that Git hosting over HTTP was something you didn't want (http < git < ssh), but I'm ignorant about that.<br><br>They have a general post-recieve URL that they will POST to when someone pushes changes to the repo there. Please see the guide for this at <a href="http://github.com/guides/post-receive-hooks">http://github.com/guides/post-receive-hooks</a>. True, it's more flexible with a straight script entry box, but with a proper handler for this callback, it will be about as powerful.<br>
<br>However, I will agree on this point, though. As long as you aren't using Lighthouse, Basecamp, CIA, etc. it will be harder to use this feature since you have to custom code this for their specific callback type, and also make sure that the place this is POSTed to is accessible, which then could have been the custom hosting anyway since hosting can happen over HTTP. It is possible, but combersome.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d"><br>
> Yes, people are easily amused by visualizations and the word<br>
> "collection", regardless<br>
> of whether it actually means anything (and in Amarok, it doesn't...you<br>
> have collections instead of file hierarcies).<br>
<br>
</div>No, collections are nothing like file hierarchies. And I don't think<br>
people are easily amused by the word "collection". Bad example.<br>
<div class="Ih2E3d"></div></blockquote><div><br>Yeah, I know. :-)<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">
<br>
> "social" makes it just a bit easier to make small time contributions.<br>
<br>
</div>Yes, and here's where I disagree. I think it makes it just a bit harder<br>
<div class="Ih2E3d">to make small time contributions.<br>
</div></blockquote><div><br>I guess we can agree on disagreeing there.<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">
<br>
</div><div class="Ih2E3d">> I do, and I hope you understand that I'm not 100% for GitHub either. I'm<br>
> that kind of person that believes in using the best tool for the job. I<br>
> will change my stance in a heartbeat if I could see a valid reason<br>
> GitHub is not adequate. I'm also aware that I'm not part of the project<br>
> yet, so I have nothing to say in the matter. I'm not trying to decide<br>
> for anyone, just make sure that people get the facts straight. :-)<br>
<br>
</div>Please feel free to point out to me (in a private email) where my facts<br>
have been incorrect.<br>
<div><div></div><div class="Wj3C7c"></div></div></blockquote><div><br>Shouldn't be needed. You are backing up your claims.<br><br>I can say this: I think moving to GitHub is not in your interests anymore, since you still need to sync with svn regurarly, and AFACT from the scm mailing list, the plans to move KDE to Git is moving along. You should probably just use the solution they will be using (which is self-hosted Gitorious, if I recall correctly) when the time comes and you don't have to sync to svn anymore.<br>
</div></div><br>-- <br>Magnus Bergmark - magnus DOT bergmark AT gmail DOT com<br>GPG/PGP: 0x7BE84794DB6AA648<br>Fingerprint: 0E6F D2DB F0EF 534A 2184 52AF 7BE8 4794 DB6A A648<br>