Eventually, some sort of distributed source code management would be nice. I think it makes sense for open source projects for a lot of reasons. That being said, I think it is more important to use a SCM that is compatible with the environment of the current contributors. The revival of the gem by the contributors has been great. Especially for those of us that don't have the programming background to make code contributions to the project (like myself).
-Stephanie On Thu, Jul 3, 2008 at 11:01 AM, Sean Chittenden <[EMAIL PROTECTED]> wrote: >>>> Before we do that though I was wondering what others thought about of >>>> switching to Git? >>> >>> Well, I know git is the new cool think in town. But I'm on Windows, and >>> love TortoiseSvn, so I don't have any motivation to move to git (lousy >>> windows support and no gui). I suppose it was easy to have some git/svn >>> integration thing or some such I could be ok, but just seems like extra >>> work to me for little benefit (its not like there are very many >>> committers anyway). >> >> That's fine. I'm basically neutral on the issue for now. I think it's >> beyond the "new cool thing" at this point. It's the way the tide is >> headed. But there is certainly is no rush. > > git is demon spawn - don't get sucked into the ill-thought-out fad. > Mercurial, imho, is a better way to go and I would be a big proponent of > migrating to mercurial if support was available for it on rubyforge (*sends > an email asking if/when*). -sc > > -- > Sean Chittenden > [EMAIL PROTECTED] > > > > _______________________________________________ > libxml-devel mailing list > libxml-devel@rubyforge.org > http://rubyforge.org/mailman/listinfo/libxml-devel > _______________________________________________ libxml-devel mailing list libxml-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/libxml-devel
