david at kineticode
Apr 4, 2009, 8:48 PM
Post #10 of 22
On Apr 4, 2009, at 1:50 PM, bharder wrote:
>> So, why wouldn't we do this? We would never need to add committers
>> again, and it's much easier for anyone to start participating.
> Though... this is typcial of distributed SCMs, not only git.
What's nice about GitHub is the social aspect to it. Anyone can "fork"
a project, creating a repo of the project for their very own, and
commit to it as if they owned it. Then, when they're ready to get
their changes into the canonical repository, they can just send a
"pull request." I think that this makes the barrier to joining the
project and contributing (not to mention maintaining your own
distribution, as, e.g., Digital Craftsmen might want to do) much,
That said, gitorious might have the same features. I honestly have no
idea; all the Perl people I respect are jumping all over GitHub, which
says a lot to me. Anyone have experience with Gitorious?
>> it is -still- not a native Windows-friendly version (in fact, there
>> are two forks, as I understand, trying solve this; one native to
>> Windows, one for Cygwin).
> I'm personally quite a fan of fossil (http://fossil-scm.org), or
> secondly, mercurial (http://www.selenic.com/mercurial/wiki/).
This doesn't bother me in the slightest. Who uses Bricolage on
Windows? You can't even run the test suite there, can you?
> Fossil has an integrated wiki, and ticket system (indeed, Richard
> Hipp, principle author of fossil is also the author of CVSTrac).
> It's portable (I run on NetBSD, Linux, MacOS X, and Windows), a
> single binary, and I trust it.
If it's as ugly as sqlite.org, feh.
> Mercurial is also a single program (Python script), and _was_ my
> favourite until I discovered fossil.
There's a reason Mercurial is on its way out, no?
> I'd say either fossil or mercurial are easier to use than git (my
> opinion), and this reduces the barrier to entry. Both are also
> portable (further reducing barrier to entry). Fossil has the
> additional benefits of integrated wiki and ticket system, which
> follow the repository.
Git is not at all hard to use. It was tricky for me because I have to
think about it differently than I do SVN, but if you're familiar with
Mercurial or Fossil, I wouldn't think you'd have that problem.
> Not sure if there are other considerations for moving to git, or if
> github itself sweetens the deal any... I'd be curious to know, though!
Yeah, GitHub is pretty sweet. See also http://use.perl.org/~schwern/journal/38478