Re: [LAZY CONSENSUS] Move to new Website Git Repositories

> On Nov 18, 2020, at 1:23 PM, Andrea Pescetti wrote: > > Dave Fisher wrote: >> www.openoffice.org is switched over! > > Thank you! I've taken a look at the Italian site and: > > - Redirect from http://it.openoffice.org is still handled correctly > > - Some CSS is broken in the Italian site

Re: [LAZY CONSENSUS] Move to new Website Git Repositories

Dave Fisher wrote: www.openoffice.org is switched over! Thank you! I've taken a look at the Italian site and: - Redirect from http://it.openoffice.org is still handled correctly - Some CSS is broken in the Italian site menu (most notably for already clicked links); here it would be useful

Re: [LAZY CONSENSUS] Move to new Website Git Repositories

> On Nov 18, 2020, at 11:55 AM, Marcus wrote: > > Am 18.11.20 um 20:36 schrieb Dave Fisher: >> Wooot, Wooot! >> www.openoffice.org is switched over! > > Hurrah! :-) > >> Let me know if you find any problems! > > "https://www.openoffice.org; is showing a broken lock icon in the browser URL

Re: [LAZY CONSENSUS] Move to new Website Git Repositories

Hi Dave, Am 18.11.20 um 20:55 schrieb Dave Fisher: > And I published it and it is in production! > > Next time I’ll let you run the Publish Jenkins job which is manual. I was already heading over to https://ci-builds.apache.org/job/OpenOffice/job/OpenOffice-org-Publish-Site/ but you were

Re: [LAZY CONSENSUS] Move to new Website Git Repositories

Am 18.11.20 um 20:36 schrieb Dave Fisher: Wooot, Wooot! www.openoffice.org is switched over! Hurrah! :-) Let me know if you find any problems! "https://www.openoffice.org; is showing a broken lock icon in the browser URL line. The redirect to HTTPS will come later, right? Let me say it

Re: [LAZY CONSENSUS] Move to new Website Git Repositories

And I published it and it is in production! Next time I’ll let you run the Publish Jenkins job which is manual. > On Nov 18, 2020, at 11:53 AM, Matthias Seidel > wrote: > > Great! > > I already made a first commit. > > Matthias > > Am 18.11.20 um 20:36 schrieb Dave Fisher: >> Wooot, Wooot!

Re: [LAZY CONSENSUS] Move to new Website Git Repositories

Great! I already made a first commit. Matthias Am 18.11.20 um 20:36 schrieb Dave Fisher: > Wooot, Wooot! > > www.openoffice.org is switched over! > > Let me know if you find any problems! > > >> On Nov 18, 2020, at 9:11 AM, Dave Fisher wrote: >> >> Update. >> >> (1) openoffice.apache.org is

Re: [LAZY CONSENSUS] Move to new Website Git Repositories

Am 18.11.20 um 18:11 schrieb Dave Fisher: Update. (1) openoffice.apache.org is now migrated. Yeah! (2) openoffice.org Jenkins jobs no longer attach the very long build.log. If there are issues then it will necessary to login to Jenkins to find the errors. Thanks :-) (3) Waiting for

Re: [LAZY CONSENSUS] Move to new Website Git Repositories

Wooot, Wooot! www.openoffice.org is switched over! Let me know if you find any problems! > On Nov 18, 2020, at 9:11 AM, Dave Fisher wrote: > > Update. > > (1) openoffice.apache.org is now migrated. > > (2) openoffice.org Jenkins jobs no longer attach the very long build.log. If > there

Re: [LAZY CONSENSUS] Move to new Website Git Repositories

Update. (1) openoffice.apache.org is now migrated. (2) openoffice.org Jenkins jobs no longer attach the very long build.log. If there are issues then it will necessary to login to Jenkins to find the errors. (3) Waiting for Infra to help: - Switch www.openoffice.org over. - Mark Subversion

Re: [LAZY CONSENSUS] Move to new Website Git Repositories

Hi - I’ve created https://issues.apache.org/jira/browse/INFRA-2 for Wednesday. > On Nov 16, 2020, at 1:35 PM, Andrea Pescetti wrote: > > On 15/11/2020 Andrea Pescetti wrote: >> yes for openoffice-project, not yet for openoffice-org. > > I'm changing this to a "yes" for both sites after

Re: [LAZY CONSENSUS] Move to new Website Git Repositories

On 15/11/2020 Andrea Pescetti wrote: yes for openoffice-project, not yet for openoffice-org. I'm changing this to a "yes" for both sites after the recent changes. Both sites are now almost identical to their CMS counterpart. Well done! One thing I'd appreciate, but this goes off-topic, is

Re: [LAZY CONSENSUS] Move to new Website Git Repositories

Sent from my iPhone > On Nov 15, 2020, at 3:20 PM, Marcus wrote: > > Am 15.11.20 um 21:07 schrieb Matthias Seidel: >> OK, I see them in Chrome, but not in Firefox. ;-) >> Which makes it an even smaller issue... > > as I've reported the 2 original issues, I've tested again (Firefox on

Re: [LAZY CONSENSUS] Move to new Website Git Repositories

Hi Dave, In the end it was a browser cache issue in Firefox. After reloading, the staged version is 100% identical with the online version. So, no further disturbance from me.. ;-) Great work from your side! Regards,    Matthias Am 15.11.20 um 21:02 schrieb Dave Fisher: > >> On Nov 15, 2020,

Re: [LAZY CONSENSUS] Move to new Website Git Repositories

Am 15.11.20 um 21:07 schrieb Matthias Seidel: OK, I see them in Chrome, but not in Firefox. ;-) Which makes it an even smaller issue... as I've reported the 2 original issues, I've tested again (Firefox on Linux) and now I don't see a single pixel that is moving when switching between both

Re: [LAZY CONSENSUS] Move to new Website Git Repositories

+1 > On Nov 15, 2020, at 12:37 PM, Dave Fisher wrote: > > Hi - > > Unless there are objections I think we should move to the new CMS for > openoffice-project and openoffice-org this week in about 72 hours. > > Proposed schedule is Wednesday for both. > > Regards, > Dave >

Re: [LAZY CONSENSUS] Move to new Website Git Repositories

OK, I see them in Chrome, but not in Firefox. ;-) Which makes it an even smaller issue... Nothing that should stop us now. Regards,    Matthias Am 15.11.20 um 21:02 schrieb Dave Fisher: > >> On Nov 15, 2020, at 11:54 AM, Matthias Seidel >> wrote: >> >> Hi Dave, >> >> Am 15.11.20 um 20:43

Re: [LAZY CONSENSUS] Move to new Website Git Repositories

> On Nov 15, 2020, at 11:54 AM, Matthias Seidel > wrote: > > Hi Dave, > > Am 15.11.20 um 20:43 schrieb Dave Fisher: >> Hi - >> >> The fix is done. The trouble was that css/ooo.css was overriding css rather >> than being overridden. > > Now it looks almost identical. > > The divider

Re: [LAZY CONSENSUS] Move to new Website Git Repositories

Hi Dave, Am 15.11.20 um 20:43 schrieb Dave Fisher: > Hi - > > The fix is done. The trouble was that css/ooo.css was overriding css rather > than being overridden. Now it looks almost identical. The divider between Blogs and News is missing, but that is *really* a minor point. Thanks!

Re: [LAZY CONSENSUS] Move to new Website Git Repositories

Hi - The fix is done. The trouble was that css/ooo.css was overriding css rather than being overridden. Regards, Dave > On Nov 15, 2020, at 11:29 AM, Dave Fisher wrote: > > Hi - > > I found the trouble and will be making a fix in about 30 minutes. > > Regards, > Dave > >> On Nov 15, 2020,

Re: [LAZY CONSENSUS] Move to new Website Git Repositories

We do not need google analytics for this information: https://uls.apache.org/exports/ URI Pageviews /index.html 2156 /download/index.html1186 /api/docs/java/ref/index.html 1081 /why/index.html 872 /social/index.html 756 /support/index.html 728 /news/index.html698

Re: [LAZY CONSENSUS] Move to new Website Git Repositories

Hi - I found the trouble and will be making a fix in about 30 minutes. Regards, Dave > On Nov 15, 2020, at 11:13 AM, Matthias Seidel > wrote: > > Hi Andrea, > > Am 15.11.20 um 20:03 schrieb Andrea Pescetti: >> Matthias Seidel wrote: >>> Yes for openoffice-project. >>> openoffice-org has

Re: [LAZY CONSENSUS] Move to new Website Git Repositories

Hi Andrea, Am 15.11.20 um 20:03 schrieb Andrea Pescetti: > Matthias Seidel wrote: >> Yes for openoffice-project. >> openoffice-org has some optical glitches that should be ironed out >> before. > > Same for me (both). So: yes for openoffice-project, not yet for > openoffice-org. > > The staged

Re: [LAZY CONSENSUS] Move to new Website Git Repositories

Matthias Seidel wrote: Yes for openoffice-project. openoffice-org has some optical glitches that should be ironed out before. Same for me (both). So: yes for openoffice-project, not yet for openoffice-org. The staged layout for openoffice-org has clear issues. Also, openoffice-org is so

Re: [LAZY CONSENSUS] Move to new Website Git Repositories

> On Nov 15, 2020, at 10:08 AM, Gavin McDonald wrote: > > Hi, > > On Sun, Nov 15, 2020 at 6:59 PM Matthias Seidel > wrote: > >> Hi Dave, >> >> Am 15.11.20 um 18:54 schrieb Dave Fisher: >>> On Nov 15, 2020, at 9:40 AM, Matthias Seidel < >> matthias.sei...@hamburg.de> wrote:

Re: [LAZY CONSENSUS] Move to new Website Git Repositories

Hi, On Sun, Nov 15, 2020 at 6:59 PM Matthias Seidel wrote: > Hi Dave, > > Am 15.11.20 um 18:54 schrieb Dave Fisher: > > > >> On Nov 15, 2020, at 9:40 AM, Matthias Seidel < > matthias.sei...@hamburg.de> wrote: > >> > >> Hi Dave, > >> > >> Am 15.11.20 um 18:37 schrieb Dave Fisher: > >>> Hi - >

Re: [LAZY CONSENSUS] Move to new Website Git Repositories

Hi Dave, Am 15.11.20 um 18:54 schrieb Dave Fisher: > >> On Nov 15, 2020, at 9:40 AM, Matthias Seidel >> wrote: >> >> Hi Dave, >> >> Am 15.11.20 um 18:37 schrieb Dave Fisher: >>> Hi - >>> >>> Unless there are objections I think we should move to the new CMS for >>> openoffice-project and

Re: [LAZY CONSENSUS] Move to new Website Git Repositories

> On Nov 15, 2020, at 9:40 AM, Matthias Seidel > wrote: > > Hi Dave, > > Am 15.11.20 um 18:37 schrieb Dave Fisher: >> Hi - >> >> Unless there are objections I think we should move to the new CMS for >> openoffice-project and openoffice-org this week in about 72 hours. > > Yes for

Re: [LAZY CONSENSUS] Move to new Website Git Repositories

Hi Dave, Am 15.11.20 um 18:37 schrieb Dave Fisher: > Hi - > > Unless there are objections I think we should move to the new CMS for > openoffice-project and openoffice-org this week in about 72 hours. Yes for openoffice-project. openoffice-org has some optical glitches that should be ironed

[LAZY CONSENSUS] Move to new Website Git Repositories

Hi - Unless there are objections I think we should move to the new CMS for openoffice-project and openoffice-org this week in about 72 hours. Proposed schedule is Wednesday for both. Regards, Dave - To unsubscribe, e-mail: