I second that tangent. I think most of the "can we host this outside
of ASF and stay in the ASF" talk is really a veiled version of "do we
have to use SVN"? And while I understand that to some .NET devs TFS
would be an improvement, I think for the type of people that actively
contribute to OS, a move from SVN to TFS wouldn't really add value
compared to a move to a DVCS system.
Arne Claassen
MindTouch
San Diego, CA
http://twitter.com/sdether
On Nov 4, 2010, at 8:43 AM, Phil Haack wrote:
On a tangent, any plans to support DVCS like Git or hg?
Phil
-----Original Message-----
From: Grant Ingersoll [mailto:gsing...@apache.org]
Sent: Thursday, November 04, 2010 5:42 AM
To: lucene-net-user@lucene.apache.org
Subject: Re: Lucene.NET Community Status
On Nov 4, 2010, at 12:52 AM, Phil Haack wrote:
I have a couple of naive questions, so forgive me. I see that
Apache projects use SVN http://www.apache.org/dev/version-control.html
But is it required to host Apache projects in this svn? The reason
I ask is that a small change to hosting in a forge like
CodePlex.com would provide the project huge exposure to more .NET
developers. You could do this, but keep all other processes the same.
Yes, it is required. Our SVN is how we assure the ASF has
provenance over the code and how the community knows where the
official release is. You can mirror the code on CodePlex, just as
we do with our read-only GIT mirrors, but all commits need to happen
in ASF SVN by ASF committers.
-Grant
