Am 19.08.20 um 20:50 schrieb Dave Fisher: > >> On Aug 19, 2020, at 11:45 AM, Matthias Seidel <matthias.sei...@hamburg.de> >> wrote: >> >> Am 19.08.20 um 18:55 schrieb Dave Fisher: >>>> On Aug 19, 2020, at 9:14 AM, Matthias Seidel <matthias.sei...@hamburg.de> >>>> wrote: >>>> >>>> Am 19.08.20 um 18:10 schrieb Dave Fisher: >>>>> Sent from my iPhone >>>>> >>>>>> On Aug 19, 2020, at 8:37 AM, Matthias Seidel >>>>>> <matthias.sei...@hamburg.de> wrote: >>>>>> >>>>>> Am 19.08.20 um 01:18 schrieb Dave Fisher: >>>>>>> Do those ancient versions of OpenOffice handle redirection? >>>>>> Redirection will be done on the (web) server side. >>>>> Then we can do redirection within the httpd.conf for OpenOffice.org. >>>>> >>>>> Infra holds that in puppet. I’ll look for it and link it. >>>>> >>>>>> Until then we need to preserve the existing pages where OOo expects them. >>>>> Let’s change that before migration. >>>> Where do you want to put these pages? >>> I would want to put them on ooo-updates if that would work. >> The update feed is broken for longer now... >> We still need to find a working solution. > Do we have a bug that describes how the update feed is broken?
One bug? ;-) This has been discussed so often and for so long I don't even know where to start... https://bz.apache.org/ooo/show_bug.cgi?id=127789 Most of the comments are pure speculation but: https://bz.apache.org/ooo/show_bug.cgi?id=127789#c39 is interesting. Although Pedro is wrong about the regression in code it shows that the update feeds located on openoffice.org can be reached. This might be due to the old web server we are using. The update feeds hosted in Apache SVN are not working for most of our users. Andrea knows more about it but basically AOO (4.1.x) is not able to connect to the update feed via https due to outdated SSL components. (Changing the update URL to http works but is a dirty hack and has no effect on released versions) Regards, Matthias P.S.: Update feeds for extensions (hosted on SourceForge) are a separate problem. > > Regards, > Dave > >> But no objections to put everything in a single place. >> >> Regards, >> >> Matthias >> >>> Regards, >>> Dave >>> >>>> Regards, >>>> >>>> Matthias >>>> >>>>> Regards, >>>>> Dave >>>>>>> Sent from my iPhone >>>>>>> >>>>>>>>> On Aug 18, 2020, at 2:51 PM, Matthias Seidel >>>>>>>>> <matthias.sei...@hamburg.de> wrote: >>>>>>>> >>>>>>>> Hi Dave, >>>>>>>> >>>>>>>> Sorry, but update feeds for OOo are still located at openoffice.org >>>>>>>> (see the link). That's why I wrote "specific". >>>>>>>> >>>>>>>> They MUST be kept until we find a better place and can redirect there. >>>>>>>> >>>>>>>> Regards, >>>>>>>> >>>>>>>> Matthias >>>>>>>> >>>>>>>> Am 18.08.20 um 23:20 schrieb Dave Fisher (Confluence): >>>>>>>>> There's 1 new edit on this page >>>>>>>>> >>>>>>>>> <page-icon.png> >>>>>>>>> Website Migrations >>>>>>>>> <avatar_31245e5a1b94c8bc00026894234e3162.png> >>>>>>>>> Dave Fisher edited this page >>>>>>>>> >>>>>>>>> >>>>>>>>> Here's what changed: >>>>>>>>> ... >>>>>>>>> openoffice.apache.org is a markdown site in the Apache CMS. >>>>>>>>> Needs redesign like new banner and change from left navigation. >>>>>>>>> Not complex. >>>>>>>>> Probably makes sense to migrate Migrate some of the developer >>>>>>>>> resources on openoffice.org like Java docs, UNO etc to this site. >>>>>>>>> www.openoffice.org is our premier user / marketing site. It has >>>>>>>>> complexities which can be handled it was moved as a port in December >>>>>>>>> 2011 with minimal change. >>>>>>>>> Template uses SSI to handle consistent banner, top navigation, and >>>>>>>>> translation of several elements. >>>>>>>>> 100 native language websites - some maintained and more not >>>>>>>>> maintained. Some have unusual encoding. >>>>>>>>> Download pages have a unique and special structure. >>>>>>>>> The why pages are translated, but ... >>>>>>>>> All the legacy pages are in an original html that is reformatted by >>>>>>>>> the CMS. These pages should be discarded or transformed during >>>>>>>>> migration. >>>>>>>>> Not part of the ww site anymore Specific update feeds must be kept >>>>>>>>> (see: >>>>>>>>> https://wiki.openoffice.org/wiki/Update_Service#Available_Update_Feeds) >>>>>>>>> Suggested approach. >>>>>>>>> Design new site layout. >>>>>>>>> Create new layout from the design. >>>>>>>>> Identify rationale about what is >>>>>>>>> Dropped. >>>>>>>>> Rewritten manually. >>>>>>>>> (de) >>>>>>>>> from the de-pages the following sub pages should be taken over (and >>>>>>>>> manually rewritten): >>>>>>>>> http://www.openoffice.org/de/about-ooo/about-mailinglist.html >>>>>>>>> http://www.openoffice.org/de/probleme.html >>>>>>>>> http://www.openoffice.org/de/foren.html >>>>>>>>> http://www.openoffice.org/de/marketing/referenzkunden.html >>>>>>>>> http://www.openoffice.org/de/doc/index.html >>>>>>>>> http://www.openoffice.org/de/doc/faq/index.html >>>>>>>>> http://www.openoffice.org/de/dev/pre_submission_de.html >>>>>>>>> in addition, there must be new local pages for marketing, e.g. for >>>>>>>>> downloading German-language marketing material (press kit, flyers, >>>>>>>>> ...) and for announcing local dates (fairs and other events) >>>>>>>>> Copied from the html. >>>>>>>>> Copied from the MediaWiki as mdtext. >>>>>>>>> Go to page history >>>>>>>>> >>>>>>>>> View page >>>>>>>>> >>>>>>>>> Stop watching space • >>>>>>>>> Manage notifications >>>>>>>>> <footer-desktop-logo.png> >>>>> --------------------------------------------------------------------- >>>>> 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 >>> > > --------------------------------------------------------------------- > 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
