Thanks Matthias... I didn't know if the control over publishing with -- https://cms.apache.org/ still worked or not.
I will investigate on my own soon. On Thu, Aug 1, 2019 at 11:38 AM Matthias Seidel <matthias.sei...@hamburg.de> wrote: > Hi Kay, > > Am 31.07.19 um 23:49 schrieb Kay Schenk: > > Hi all. > > A few questions -- > > * what's the status of the current OO website repositories -- both > > https://openoffice.apache.org/ and https://www.openoffice.org/ > > in terms of updates? Are they both, as of today, still svn checkout? > > It is still functional for both sites... > > However the staging does not work on https://openoffice.apache.org/ due > to the permanent https redirection. > But I can live with that... ;-) > > > > > * and since the CMS is broken (?), do updates to through svn go live > > instantly or ???? > I did a commit yesterday, all went fine (but did not publish yet). > > > > * where are the instructions for the new "tool"? > > We are still discussing about a new system at the moment. > > Regards, > > Matthias > > > > > Thanks. > > > > On Tue, Jul 30, 2019 at 4:29 PM Dave Fisher <w...@apache.org> wrote: > > > >> > >>> On Jul 30, 2019, at 3:29 PM, Peter Kovacs <pe...@apache.org> wrote: > >>> > >>> > >>> On 31.07.19 00:18, Matthias Seidel wrote > >>>>> I don't understand: > >>>>> Why is migration necessary at all? > >>>> I already told you on users-de@. ASF Infra can not support the old > >> (self > >>>> baked) CMS anymore. > >>> they replace it with another self baked solution... :/ > >> No, they prefer Pelican: https://github.com/getpelican/pelican it will > >> support Github’s markdown and allow the preview of content within > GitHub. > >> > >> "the pelican setup sees the commit to master, builds the site, pushes to > >> the asf-site branch, which the gitpubsub sees, and pulls that change to > the > >> active website" > >> > >> There will be two major challenges. > >> > >> (1) Creating our theme so that we continue to handle the NL translated > >> elements in the header. An example page theme template is quite similar > to > >> what the CMS uses: > >> > https://github.com/getpelican/pelican/blob/master/pelican/themes/notmyidea/templates/page.html > >> (2) How to adapt the legacy html into the new template. > >> > >> I plan to help, but only after ApacheCon NA. If someone else starts the > >> process then I would gladly review and discuss. > >> > >> Regards, > >> Dave > >> > >>> With less overhead maybe. > >>> > >>> > >>> --------------------------------------------------------------------- > >>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > >>> For additional commands, e-mail: dev-h...@openoffice.apache.org > >>> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > >> For additional commands, e-mail: dev-h...@openoffice.apache.org > >> > >> > > -- "And in the end, only kindness matters." -- Jewel, "Hands" ________________________________________ MzK
