Am 01.10.19 um 21:43 schrieb Matthias Seidel: > Am 01.10.19 um 20:18 schrieb Marcus: >> Am 01.10.19 um 19:31 schrieb Dave Fisher: >>> Heads up that I’m starting to do the migration, >>> >>>> Repos name must start with OpenOffice. >> thanks a lot for starting this beast of migration. >> >>>> I propose these: >>>> >>>> OpenOffice-DevWebsite >>>> OpenOffice-OrgWebsite >> May I ask you to use shorter names and all in lower case: >> >> ooo-dev-site >> ooo-org-site >> >> I prefer this as it looks easier to remember and to use. > +1 > > Matthias
Thinking about it, we may have to use "openoffice" because of the GitHub space, so openoffice-dev-site openoffice-org-site would be my favorites. Matthias > >> Thanks >> >> Marcus >> >> >> >>> I’ll be tackling the project site first. >>> >>> I plan to make use of https://S.apache.org/asfyaml so that we will >>> have staging and production. >>> >>> I may use the Apache CMS scripts for page generation. Infra-VP does >>> not have trouble with those being on a Jenkins or Buildbot node. I >>> may use jBake which I’ve used with the Incubator site. It may use both. >>> >>> Changes will be done in GIT and the CMS WebGUI will not be used. >>> Committers will be able to change the git repos. There will be >>> instructions on the local build as well. I’m starting with the local >>> build. >>> >>> This will take sometime. >>> >>> If someone wants to redesign our Websites Look & Feel then proposals >>> welcome. I may play with it myself... >>> >>> Regards, >>> Dave >>> >>>>> I have one more question. Jörg has mentioned that a lot of outside >>>>> links point to the current web pages. What do we do with this? Do we >>>>> make an announcement that this will happen and maybe give people some >>>>> sort of hint to update their link lists? >>>> If we track what we change then we can create https redirection rules. >>>> >>>> Best Regards, >>>> Dave >>>> >>>>> >>>>> All the Best >>>>> >>>>> Peter >>>>> >>>>>> On 24.09.19 22:54, Dave Fisher wrote: >>>>>> Hi Kay, >>>>>> >>>>>> I promised to look into this migration after Apachecon. >>>>>> >>>>>> I’ve been thinking through a plan the last few days. >>>>>> >>>>>> See inline. >>>>>> >>>>>> Sent from my iPhone >>>>>> >>>>>>> On Sep 24, 2019, at 1:38 PM, Kay Schenk <kay.sch...@gmail.com> >>>>>>> wrote: >>>>>>> >>>>>>> Hi -- >>>>>>> >>>>>>> The last item I saw on this topic was this one concerning the new >>>>>>> CMS >>>>>>> >>>>>>> https://www.mail-archive.com/dev@openoffice.apache.org/msg36504.html >>>>>>> >>>>>>> and I recall you mentioning at one point that it was desirable to >>>>>>> do some housecleaning on the www.openoffice.org web site due to >>>>>>> size and no longer pertinent information. >>>>>>> >>>>>>> Some questions at this point -- >>>>>>> >>>>>>> * was a new "CMS" chosen? If so what is it and where can we find >>>>>>> additional information? >>>>>> Not exactly. Here is the plan. >>>>>> >>>>>> (1) Copy OpenOffice.apache.org svn to a new git repository. >>>>>> >>>>>> (2) Learn to use the new infra supported yaml tags to try a few >>>>>> different build techniques. I am familiar with JBake from the >>>>>> incubator build but Pelican is possible. >>>>>> >>>>>> (3) Finish the project site. >>>>>> >>>>>> (4) Rinse and repeat with the OpenOffice.org site >>>>>> >>>>>>> The current site, as Dave pointed out earlier, uses a lot of the >>>>>>> current CMS capabilities in terms of page rendering, dealing with >>>>>>> the many languages of the site etc. to render the static content. >>>>>> We’ll figure that out. >>>>>> >>>>>> If someone wants to redesign the site we can work through it in >>>>>> parallel. >>>>>>> * How long will svn continue to function for both >>>>>>> www.openoffice.org and openoffice.apache.org? >>>>>> The CMS is fragile and if it falls down it could become a blocking >>>>>> issue. Infra will warm is if things are immanent. I did discuss >>>>>> our migration briefly with an infra person at ACNA19. >>>>>> >>>>>>> * It seems it would be advantageous to do a LOT of housecleaning >>>>>>> on www.openoffice.org before migration >>>>>>> >>>>>>> I don't have ANY ideas about archiving www.openoffice.org. It is >>>>>>> quite large. I could certainly help in about a month with the >>>>>>> "housecleaning" aspect of both sites assuming they remain svn >>>>>>> accessible for a while. But I'm assuming we might want archives >>>>>>> of both even before that. Yes? >>>>>> Tag the SVN repository before starting its cleanup. Feel free to >>>>>> keep a local copy. >>>>>> >>>>>> I recommend doing cleanup on a local copy and checking in the >>>>>> results. >>>>>> >>>>>> So, three parallel threads. >>>>>> >>>>>> (1) Cleanup >>>>>> (2) Redesign if needed. >>>>>> (3) Move to git and away from CMS >>>>>> >>>>>> Regards, >>>>>> Dave >>>>>> >>>>>>> -- MzK >>>>>>> >>>>>>> >>>>>>> >>>>>>>> On 9/19/19 10:01 PM, Peter Kovacs wrote: >>>>>>>> Hello all, >>>>>>>> >>>>>>>> >>>>>>>> Can everyone interested in this topic give a short status? >>>>>>>> >>>>>>>> Short ping on the current availability. And list any impediments or >>>>>>>> difficulties that he currently sees where others can help with. >>>>>>>> >>>>>>>> I would very much like to see this take some drive. And I would >>>>>>>> love to >>>>>>>> see George delivering something, so we can review committer >>>>>>>> status in >>>>>>>> the near future. (As I do with any other volunteer knocking on >>>>>>>> our door.) >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> >>
smime.p7s
Description: S/MIME Cryptographic Signature
