www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Herbert Duerr (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (INFRA-5590) Creating a Git-Mirror of the Openoffice code base
Date Tue, 12 Nov 2013 15:54:19 GMT

     [ https://issues.apache.org/jira/browse/INFRA-5590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Herbert Duerr reopened INFRA-5590:

Reopening after the 4.0.x releases as discussed in the mailing lists.

> Creating a Git-Mirror of the Openoffice code base
> -------------------------------------------------
>                 Key: INFRA-5590
>                 URL: https://issues.apache.org/jira/browse/INFRA-5590
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: Git
>            Reporter: Herbert Duerr
> The OpenOffice project would benefit from having an official git mirror of its codebase.
Following http://www.apache.org/dev/git and the mailing list thread on http://mail-archives.apache.org/mod_mbox/openoffice-dev/201211.mbox/%3C50B88C50.7020506%40apache.org%3E
here are the requested infos:
> - Name of the codebase: "Apache OpenOffice"
> - Name of the requested Git mirror: "openoffice.git"
> - Subversion path of the codebase: "openoffice" (was "incubator/ooo")
> - Subversion layout: There is the standard "trunk, branches, tags" layout, but there
also exist top-level directories such as devtools, ooo-site, pmc, site, symphony, and trunk-orig.
Since these do not really belong to the codebase (as released in source tarballs) these extra
directories can and should be omitted in the git-mirror if they complicate things too much.
> Another complication comes from the fact that most branches are one-level deep, but some
are two levels deep (e.g. branches/alg/aw080). Yet another complication comes from the recent
change from incubator/ooo to openoffice/
> The sizes of current trunk/main + trunk/ext_libraries are 900MB + 128K, the size of the
localization data in trunk/extras is another 860MB. The localization data compresses well
but can be considered an own entity, if this makes things easier or more manageable (e.g.
the old OOo project had separate repositories for the code and the l10 data). The tarballs
in trunk/ext_sources used another big chunk of up to 200MB, but they can be omitted altogether,
as these external dependencies are fetched after the configure step from their respective
original or more reliable backup locations.

This message was sent by Atlassian JIRA

View raw message