i haven't used it [yet], but i'm -1 on being the first project in the asf to go with it without some input from the infrastructure people. for instance, aside from the history import aspect, how does it mesh with viewcvs? the equivalent of anoncvs? and do we really want to put the burden of maintaining two cms systems on collab, plus prototype all the infrastructural glue necessary to fit in with the existing cvs repositories?
ViewCVS can now handle SVN repositories. C. Mike Pilato from the Subversion team added the necessary bits. I'm not sure how stable it is - I've heard it will be in the next ViewCVS release, and I'm sure we could provide feedback and fixes. (This is in addition to normal browsing of the repository.)
With Subversion, anonymous access is easy and free. That is just a GET of the repository. The only operations that require authentication are write operations (at least in how we would deploy it). It also has the advantage that any committers to commons don't *need* an associated account on cvs.apache.org - this may allow us to have a lower barrier of entry. There is no longer a distinction between 'anoncvs' and 'ssh' repositories. IMHO, that's a tremendous win.
And, substantial work has been made to cvs2svn recently. If we have a repository to convert, I'll volunteer to add any missing bits to the cvs2svn translator that it doesn't already recognize. (Should be no problem with serf as that is a very basic CVS repository.)
i say not. let's wait for the infrastructure team to work on it. we can volunteer to be one of their early adopters, but i don't think we should go it alone.
Sander and I have volunteered in the past to maintain a SVN repository on icarus. I'll reiterate my offer. When we've brought SVN up on the infrastructure@ lists, people wanted to see an early adopter before we deploy it. I think it makes sense for us to be that early adopter. And, regardless, I believe the CollabNet team is very familiar with Subversion.
The biggest problem is that we need SSL keys for icarus, and my requests for assistance on that front from infrastructure@ has been met with dead silence and apathy. This is one of the reasons why I'm pushing for some type of infrastructure committee. Either we need to create our own CA, or we need to purchase Verisign certs. -- justin
