Uploaded image for project: 'Infrastructure'
  1. Infrastructure
  2. INFRA-3628

Import SourceForge respositories to apache for incubator project Jena

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Fix Version/s: Initial Clearing
    • Component/s: Subversion
    • Labels:
      None

      Description

      Jena is project in incubation with an existing codebase, currently on SourceForge in 3 different repositories, SVN and CVS (2 SF projects). We have software grants on file at Apache for the majority of this code (in fact, for almost all of it). We'd appreciate the help migrating it to Apache infrastructure.

      We have several repositories, we'd like to import as-is, ideally with history, to create a record of the software pre-Apache.

      Our SourceForge repositories are:

      CVS: jena.cvs.sourceforge.net:/cvsroot/jena
      CVS: joseki.cvs.sourceforge.net:/cvsroot/joseki
      SVN: https://jena.svn.sourceforge.net/svnroot/jena

      Our initial thoughts were to place each repository in its own area under a common root to denote the imported code:

      https://svn.apache.org/repos/asf/incubator/jena/import/...
        so
      https://svn.apache.org/repos/asf/incubator/jena/import/jena-cvs
      https://svn.apache.org/repos/asf/incubator/jena/import/jena-svn
      https://svn.apache.org/repos/asf/incubator/jena/import/joseki-cvs

      There are modules with the same name in the CVS and SVN repositories: some modules moved from CVS to SVN with the same name - we don't need to integrate them as part of the move.

      In case it helps, the rsync backups are:
       jena.cvs.sourceforge.net::cvsroot/jena/*
       jena.svn.sourceforge.net::svn/jena/*
       joseki.cvs.sourceforge.net::cvsroot/joseki/*

      They are: 1.2G, 2.3G and 409M respectively.

      After the import, we will be extracting the active modules and building a new project structure, leaving the "import" area as the permanent record of out starting point at Apache. The import/ area becomes effectively a read-only archive.

      If this is not a sensible way for doing the imports, or there is better practice, or we're just being plain daft, please let us know.

          Andy
          jena-dev@incubator.apache.org


        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                pctony Tony Stevenson
                Reporter:
                andy.seaborne Andy Seaborne
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: