As Pilato and Tony have noted: this is not the forum. If you, Rich, or any other Director/Officer have a problem with that, then bring it up at our April Board meeting. The Infrastructure team is moving on this ticket.
As the VP of the Apache Subversion project, I opened this ticket. The people who have the voting power would NOT CHANGE. Pushing this vote to would simply incite riot. But that does NOT deny the result of their vote. But that is not for me to decide, and it is not for you (Jim/Rich) to decide for us. As the VP, I gotta represent the project. Positives, and only little negatives.ĭon't get me wrong. There are no barriers to the migration here, and some of the stuff that Infra has done for integration with GitHub? Pretty cool. We allow ALL ASF committers access to our repository. We have no need for Subversion's fine-grained authorization. Our project stores some binaries, but we can make Git work for us.
For our backend, we don't need the super-huge repositories that Subversion supports. We want to get our stuff coded and released.
The short of it is: the Apache Subversion project chose this. Even though Greg didn't vote for it, it was taken by the PMC for the Subversion project: Jim Jagielski, co-founder of the Apache Foundation expressed concerns that the vote was taken by the PMC behind closed doors, instead of the open democracy that Apache is known for. Many of the commenters on the thread are less concerned about the irony of hosting SVN on Git as much as the private events that led to this occurring. Unlike the existing git-svn support, this uses Git natively between the client and server (and probably caches the Git repository locally on the client side) but continues to allow tools to locally operate on SVN checkouts. Existing SVN tools will be able to use this both as a local checkout repository format and as a means to commit to a central Git server in essence, it's a Git client with an SVN command line interface. This work is being developed in the ra-git branch, and provides (local) svn repository identifiers based on upstream git commits. New changes coming in the SVN client for 1.9 will allow the ra_git module to check out and work with Git repositories using the SVN client. The significant change is that in future the Git repository will be read-write for Apache committers, and the existing SVN repository will become locked. So the Apache SVN Git repository has been available for some time, and is browsable at GitHub already. The Apache foundation is even drafting an official response to the situation.Īlthough this seems like a big change, in fact the Git repositories at Apache have been mirroring projects for some time using the unidirectional git-svn bridge. In fact, the vote was taken on an internal/private mailing list, and the result was something that Greg was not happy with, suggesting that he might have to hang up the VP subversion hat. This will allow the development of the Subversion repository be developed with Git.Īlthough posted on April 1, the switch is not an April fool. In INFRA-7524 Greg Stein, founder of the Subversion project and previous winner of the O'Reilly Open Source award, has requested that the Apache Subversion project be migrated to Git. THANK YOU to all of you who actually BELIEVED. Our Subversion teammates showed a great sense of community and circling the wagons… Thank you all for making this work!!! And the Directors and Exec Officers came in with a perfect level of wrath. even my antagonist was in on the ruse :-) … the Infra team handled this with perfect aplomb. My major thanks to for the concept.Īnd plenty of thanks to all of my co-conspirators on this issue. Being closed "Not a problem", Greg comments:
APACHE SUBVERSION UPDATE
Update as many expected, this was an elaborate April Fools hoax made by many at the Apache Software Foundation.
0 kommentar(er)
