Hello Peter, thanks for your work
Am 20.07.19 um 16:07 schrieb Damjan Jovanovic: > That's a great idea, thank you! > > 1.1 - 1.5: test/ requires main/ to build, for Ant scripts. main/ requires > ext_libraries/ if not more. > Why can't we use one repository for everything, like the Github mirror > already does? I also prefer one repository like Github is. I already test buildung from Github repo under Debian 9 and it works in general. I can't see any difference of the repo. Regards Mechtilde > > Regards > Damjan > > On Sat, Jul 20, 2019 at 2:16 PM Peter Kovacs <pe...@apache.org> wrote: > >> Hello all, >> >> >> I had a talk with Gavin today, informing myself about the migration from >> SVN to Git. Since we have already a github mirror process we can not use >> the self service. >> >> I copied the chat to Cwiki, in order everyone can review what have been >> spoken about. [0] >> >> Summary: >> >> We have to open a ticket at infra and order the migration. The migration >> in general will consist of the following steps (taken from slack, chat >> protocol): >> >> The Infra steps in short >> >> 1. Verify Github repos is upto date and correct >> 2. we mark SVN read only >> 3. we clone the Github repos into Gitbox >> 4. we make them both writable >> >> # We can have multiple Repositories. >> >> # Gavin also whish that the depreciated CMS can be shut down in 3 month. >> I promised we look into it and try to accomplish in the time. There are >> no deadlines yet. >> >> >> I suggest the following migration Approach: >> >> 1) We migrate OpenOffice Code to git >> >> 1.1.) OpenOffice main will move into one repository >> >> 1.2) OpenOffice ext_source and ext_libraries will be split, and each >> dependency gets its own repository. >> >> 1.3) extras/l10n will become an own repositry >> >> 1.4) test will become an own repository. >> >> 1.5) we adjust our build environment to reflect the new structure. I.e. >> You need only checkout core and bootstrap can download everything else. >> unzip step can be skipped. >> >> 2) We migrate CMS to a new solution. We have the option to go for the >> alterantive, honestly I would like to migrate to a easy to use sollution >> like neo CMS and migrate the mwiki too. >> >> We need to be able to lower the barrier for non tech work where ever we >> can. >> >> 3) PMC folder should be migrated into CWiki. >> >> >> >> All the Best >> >> Peter >> >> Older Discussions on the migration on [1],[2] >> >> [0] >> >> https://cwiki.apache.org/confluence/display/OOOUSERS/Git+Migration+-+Chat+Protocol+with+Gavin >> >> [1] >> >> https://lists.apache.org/thread.html/c972affc61caf4844e7c82f7be9edf10fcd50753884cbaa7399999d1@%3Cdev.openoffice.apache.org%3E >> >> [2] >> >> https://lists.apache.org/thread.html/4db20d193cc30850e63dc03378a20462d1e5c113e566fffd6c776d1c@%3Cdev.openoffice.apache.org%3E >> >> >> >> >> > -- Mechtilde Stehmann ## Apache OpenOffice ## Freie Office Suite für Linux, MacOSX, Windows ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F
signature.asc
Description: OpenPGP digital signature
