On Wed, 27 Oct 2010 12:56:51 +0300 >>>>>> "Vladimir" == "Vladimir Panteleev" wrote:
Vladimir> IIRC even those commands differ across these DVCSes. In some details, yes. Vladimir> Anyway, when you want to do something non-trivial Vladimir> (branching/merging/history editing) you're forced to consult Vladimir> the documentation. Sure. But all those are quite similar in nature...Besides that, there are plugins which enable, to some extent, interoperability. There are e.g. bzr-{hg,svn,git} plugins so one can stay using bzr with other DVCS-es as well. Vladimir> It's not really about Git, it's about GitHub: That's another thing and does not have much with Git itself. Vladimir> 1. Repo creation is instant, doesn't need to go through a Vladimir> human approval process, etc. (big turn-off from DSource, Vladimir> SourceForge as I create and work on many small projects) Vladimir> 2. One-click forking - self-explanatory, you get a cheap Vladimir> clone of a project in your own namespace, to which you can Vladimir> push to to instantly publish your changes. Vladimir> 3. Pull requests - pretty self-explanatory, but integrated Vladimir> with the issue system. Vladimir> 4. You've probably seen one of GitHub's "network chart"? Vladimir> ( e.g.: http://github.com/jquery/jquery/network ) I believe you didn't try much of the competition like Launchpad, Bitbucket, Gitorious etc. What you are describing is neither very special nor specific to Github. Vladimir> And finally, IMHO a pretty convincing argument is that GitHub Vladimir> is one of the most popular open-source hosting websites. Not Vladimir> having to register and familiarize yourself with a project Vladimir> hosting website lowers the contribution barrier even lower. Try some of the above hosting solutions. Btw, I'll probably use www.indefero.net as soon as the monotone support gets in (probably next week). Sincerely, Gour -- Gour | Hlapicina, Croatia | GPG key: CDBF17CA ----------------------------------------------------------------
signature.asc
Description: PGP signature