From dev-return-65844-archive-asf-public=cust-asf.ponee.io@openoffice.apache.org Tue Oct 1 17:31:06 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 5FCEF180608 for ; Tue, 1 Oct 2019 19:31:06 +0200 (CEST) Received: (qmail 39996 invoked by uid 500); 1 Oct 2019 17:31:05 -0000 Mailing-List: contact dev-help@openoffice.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@openoffice.apache.org Delivered-To: mailing list dev@openoffice.apache.org Received: (qmail 39985 invoked by uid 99); 1 Oct 2019 17:31:05 -0000 Received: from Unknown (HELO mailrelay1-lw-us.apache.org) (10.10.3.42) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Oct 2019 17:31:05 +0000 Received: from [10.0.0.3] (c-76-103-41-34.hsd1.ca.comcast.net [76.103.41.34]) by mailrelay1-lw-us.apache.org (ASF Mail Server at mailrelay1-lw-us.apache.org) with ESMTPSA id 19D895A6D for ; Tue, 1 Oct 2019 17:31:05 +0000 (UTC) From: Dave Fisher Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: [status] Static webside migration Date: Tue, 1 Oct 2019 10:31:01 -0700 References: <0b2abbf8-879d-2c9a-4709-fcb5b49502c8@Apache.org> <82e09e09-ecc4-ee60-fb57-828a7c57a5e4@gmail.com> <25A84D5F-A27E-4C73-AAF9-771346EFD6B9@apache.org> <71a48380-d7bc-33ae-bce8-8b6c6d01a2f0@Apache.org> <67561B47-F7DF-4169-A501-0C7A8D1E2C3A@comcast.net> To: dev@openoffice.apache.org In-Reply-To: <67561B47-F7DF-4169-A501-0C7A8D1E2C3A@comcast.net> Message-Id: X-Mailer: Apple Mail (2.3445.104.11) Hi - Heads up that I=E2=80=99m starting to do the migration, > Repos name must start with OpenOffice. >=20 > I propose these: >=20 > OpenOffice-DevWebsite > OpenOffice-OrgWebsite I=E2=80=99ll 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=E2=80=99ve 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=E2=80=99m 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 >=20 >>=20 >> I have one more question. J=C3=B6rg 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? >=20 > If we track what we change then we can create https redirection rules. >=20 > Best Regards, > Dave >=20 >>=20 >>=20 >> All the Best >>=20 >> Peter >>=20 >>> On 24.09.19 22:54, Dave Fisher wrote: >>> Hi Kay, >>>=20 >>> I promised to look into this migration after Apachecon. >>>=20 >>> I=E2=80=99ve been thinking through a plan the last few days. >>>=20 >>> See inline. >>>=20 >>> Sent from my iPhone >>>=20 >>>> On Sep 24, 2019, at 1:38 PM, Kay Schenk = wrote: >>>>=20 >>>> Hi -- >>>>=20 >>>> The last item I saw on this topic was this one concerning the new = CMS >>>>=20 >>>> = https://www.mail-archive.com/dev@openoffice.apache.org/msg36504.html >>>>=20 >>>> 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. >>>>=20 >>>> Some questions at this point -- >>>>=20 >>>> * was a new "CMS" chosen? If so what is it and where can we find = additional information? >>> Not exactly. Here is the plan. >>>=20 >>> (1) Copy OpenOffice.apache.org svn to a new git repository. >>>=20 >>> (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. >>>=20 >>> (3) Finish the project site. >>>=20 >>> (4) Rinse and repeat with the OpenOffice.org site >>>=20 >>>> 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=E2=80=99ll figure that out. >>>=20 >>> 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. >>>=20 >>>> * It seems it would be advantageous to do a LOT of housecleaning on = www.openoffice.org before migration >>>>=20 >>>> 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. >>>=20 >>> I recommend doing cleanup on a local copy and checking in the = results. >>>=20 >>> So, three parallel threads. >>>=20 >>> (1) Cleanup >>> (2) Redesign if needed. >>> (3) Move to git and away from CMS >>>=20 >>> Regards, >>> Dave >>>=20 >>>> -- MzK >>>>=20 >>>>=20 >>>>=20 >>>>> On 9/19/19 10:01 PM, Peter Kovacs wrote: >>>>> Hello all, >>>>>=20 >>>>>=20 >>>>> Can everyone interested in this topic give a short status? >>>>>=20 >>>>> Short ping on the current availability. And list any impediments = or >>>>> difficulties that he currently sees where others can help with. >>>>>=20 >>>>> 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.) >>>>>=20 >>>>>=20 >>>>> Thanks >>>>>=20 >>>>> All the Best >>>>>=20 >>>>> Peter >>>>>=20 >>>>>=20 >>>>> = --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org >>>>> For additional commands, e-mail: dev-help@openoffice.apache.org >>>>>=20 >>>> = --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org >>>> For additional commands, e-mail: dev-help@openoffice.apache.org >>>>=20 >>=20 >>=20 >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org >> For additional commands, e-mail: dev-help@openoffice.apache.org >>=20 --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org For additional commands, e-mail: dev-help@openoffice.apache.org