[discussion] svn migration plan
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/c972affc61caf4844e7c82f7be9edf10fcd50753884cbaa739d1@%3Cdev.openoffice.apache.org%3E [2] https://lists.apache.org/thread.html/4db20d193cc30850e63dc03378a20462d1e5c113e566fffd6c776d1c@%3Cdev.openoffice.apache.org%3E
Re: [discussion] svn migration plan
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? Regards Damjan On Sat, Jul 20, 2019 at 2:16 PM Peter Kovacs 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/c972affc61caf4844e7c82f7be9edf10fcd50753884cbaa739d1@%3Cdev.openoffice.apache.org%3E > > [2] > > https://lists.apache.org/thread.html/4db20d193cc30850e63dc03378a20462d1e5c113e566fffd6c776d1c@%3Cdev.openoffice.apache.org%3E > > > > >
Re: [discussion] svn migration plan
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 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/c972affc61caf4844e7c82f7be9edf10fcd50753884cbaa739d1@%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
Re: [discussion] svn migration plan
On 20.07.19 16:35, Mechtilde wrote: > 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. I do not believe having multiple repos will affect the process much, if we do this right. I did the cut at the folders, due the outside representation. It suggested they were independent. If they are not then lets leave them with the code. What I would really like to remove from the Code repo are the external libraries. They are a binary blob, and we put some patches on top them, making it hard to really look at the code. In an own repository these libraries would have a maintainable subset we can push from and too. -Maybe even backport security Issues if we are not able to update. As for Distribution specific versions that do deliver own maintained builds, you would not use those anyway. i guess at least. But we can leave the structure as is for now if you feel more save with that. I think we can split later too (i.e. if we think about splitting on UNO) I am not picky on this. It is just a suggestion to improve the situation for us. And we have the opporunity because we have to think about this anyhow. All the best Peter > > Regards > > Mechtilde >> Regards >> Damjan >> >> On Sat, Jul 20, 2019 at 2:16 PM Peter Kovacs 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/c972affc61caf4844e7c82f7be9edf10fcd50753884cbaa739d1@%3Cdev.openoffice.apache.org%3E >>> >>> [2] >>> >>> https://lists.apache.org/thread.html/4db20d193cc30850e63dc03378a20462d1e5c113e566fffd6c776d1c@%3Cdev.openoffice.apache.org%3E >>> >>> >>> >>> >>> - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [discussion] svn migration plan
Hi AOO devs, I just stumbled onto this thread. Coming from subversion.a.o, I'm saddened to see you've decided to switch to Git. Could someone please summarise the reasons for this decision, or give me a link to the discussion in the mail archives? I'd very much like to know if it was caused by some specific problem or missing feature in Subversion that we may be able to address. -- Brane
Re: [discussion] svn migration plan
Hi brane, The threads are linked in my first post. It is for me a workflow thing. I need a decentral versioning system instead of a central one. And I want github as public patch interface. Both do not work with svn. I add a reason that I heard at work. Young people do not know svn. They expect to work with git. IMHO it is a dumb argument but in my country the fresh people from university are dictating a little their working environment. Ahh and git has major pains reading OpenOffice svn repo. So I can't even use git as a client. All the best. Peter Am 21. Juli 2019 01:17:32 MESZ schrieb "Branko Čibej" : >Hi AOO devs, > >I just stumbled onto this thread. Coming from subversion.a.o, I'm >saddened >to see you've decided to switch to Git. Could someone please summarise >the >reasons for this decision, or give me a link to the discussion in the >mail >archives? I'd very much like to know if it was caused by some specific >problem or missing feature in Subversion that we may be able to >address. > >-- Brane
Re: [discussion] svn migration plan
On Sun, 21 Jul 2019, 01:42 Peter Kovacs, wrote: > Hi brane, > > The threads are linked in my first post. > Thanks ... Sorry I missed those. > It is for me a workflow thing. > I need a decentral versioning system instead of a central one. > Which particular "decentralised" feature do you miss most? For example, there's work going on to implement client-side shelving (similar to 'git stash'), it's experimental but available in various forms in the last 3 Subversion (minor) releases And I want github as public patch interface. > Both do not work with svn. > > I add a reason that I heard at work. Young people do not know svn. They > expect to work with git. > IMHO it is a dumb argument but in my country the fresh people from > university are dictating a little their working environment. > > Ahh and git has major pains reading OpenOffice svn repo. So I can't even > use git as a client. > I assume you mean git-svn? I'm not surprised. Thanks for taking the time to respond. Looks like nothing short of making svn just another git would make you change your mind. :) -- Brane > > All the best. > Peter > > Am 21. Juli 2019 01:17:32 MESZ schrieb "Branko Čibej" : > >Hi AOO devs, > > > >I just stumbled onto this thread. Coming from subversion.a.o, I'm > >saddened > >to see you've decided to switch to Git. Could someone please summarise > >the > >reasons for this decision, or give me a link to the discussion in the > >mail > >archives? I'd very much like to know if it was caused by some specific > >problem or missing feature in Subversion that we may be able to > >address. > > > >-- Brane >
Re: [discussion] svn migration plan
Hello Branko, Am 21.07.19 um 02:01 schrieb Branko Čibej: > On Sun, 21 Jul 2019, 01:42 Peter Kovacs, wrote: > >> Hi brane, >> >> The threads are linked in my first post. >> > > Thanks ... Sorry I missed those. > > >> It is for me a workflow thing. >> I need a decentral versioning system instead of a central one. >> > > > Which particular "decentralised" feature do you miss most? For example, > there's work going on to implement client-side shelving (similar to 'git > stash'), it's experimental but available in various forms in the last 3 > Subversion (minor) releases Most of the missing features were the reason why Git was developed. As Peter said SVN is centralized, Git is decentralized. With Git you can do your own home branch without publishing for testing. And then you can do a Merge Request (on Github it is named Pull Request) With Git you need one Repo e.g. with the two branches trunk and 42x. With SVN you have two branches to checkout. So you need double space to hold the repo locally for testing > > I assume you mean git-svn? I'm not surprised. > > Thanks for taking the time to respond. Looks like nothing short of making > svn just another git would make you change your mind. :) No. Kind regards -- 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
