infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "C. Michael Pilato (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-7524) migrate Apache Subversion project over to the git repo
Date Tue, 01 Apr 2014 15:21:25 GMT

    [ https://issues.apache.org/jira/browse/INFRA-7524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13956632#comment-13956632
] 

C. Michael Pilato commented on INFRA-7524:
------------------------------------------

I'm not sure this discussion is trending towards a positive conclusion.  I'm starting to see
that this ticket is getting a bit of external attention -- which I suppose is understandable
-- but all that really means is that the world is watching not just what Subversion does with
its source code, but also how the Foundation handles potentially contentious PMC decisions.
 For the good of the project and the Foundation, let's step back a bit, cool down, and try
a more productive approach.

I can certainly understand why the Board might be concerned about the manner in which this
change was decided upon.  No doubt there will be many interested parties contacting the Foundation
about this move, which understandably could appear to some as a sort of "Uncle!" cry from
the project -- a semi-public confession that git has won the so-called version control war.
 And to the degree that the Board believes that to be true, they will naturally be concerned
about the project saving face.

But the PMC didn't make this decision on philosophical grounds.  Subversion is an amazing
version control system with broad acceptance within the Enterprise install base -- far greater
than any DVCS can boast.  It is because we want to better serve those users (and make good
on the latter part of our Vision Statement; see http://subversion.apache.org/#vision) that
we made a *technical* decision to change a bit of our development practices and tooling. 
We're still operating within the scope of what is permitted for ASF projects, and have no
plans to deviate from "The Apache Way" (which has been often confused with "The Subversion
Way", so closely do we adhere to and stand by it).  We (and by we, I mean the majority of
PMC members) simply believe that the best way to serve the Community with our Code is to adopt
the development practices and tools that are becoming the de facto standard for open source
development.

> migrate Apache Subversion project over to the git repo
> ------------------------------------------------------
>
>                 Key: INFRA-7524
>                 URL: https://issues.apache.org/jira/browse/INFRA-7524
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Git
>            Reporter: Greg Stein
>            Assignee: Jake Farrell
>
> Grrrr... vote passed. Not happy, but here we go:
> Infra: please migrate our repository at /repos/asf/subversion/ over to the Git repository
stuffs.
> We already have the mirror at git.apache.org. But that has always been there as a read-only
mirror (along with the copy over to GitHub). Will the git repo be at git-wip.apache.org? (is
it *still* considered -wip "work in progress"?)
> Not sure what else you guys need. Haven't exactly studied up on the migration process.
Please let me know.
> (tho I'm up late here now and need to sleep soon; others from the PMC will be able to
help)



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message