Re: Hello

[Alexandru Mandai]

Hi Matthias,
Thank you for your reply. I wanted to create an account on pottle, but it
said that New accounts cannot be created.
Also, I received some e-mails about a 4.1.8 beta, maybe I can help with it.
There was a link in the email containing an SDK (Software Development Kit).
https://home.apache.org/~mseidel/AOO-builds/AOO-418-Test/

Thanks for reading,
Multumesc pentru ca ati citit,
Alex

On Tue, Aug 18, 2020 at 3:57 PM Matthias Seidel 
wrote:

> Hi Alex,
>
> Am 17.08.20 um 20:03 schrieb Alexandru Mandai:
> > Hi,
> >
> > Thank you for the warm welcome and for pointing me in the right
> direction.
> >
> > I also have some basic c++ skills, if that’s needed.
>
> Every help is welcome!
>
> Regarding Python and C+: Discussions take place here on dev@.
>
> If you subscribe to L10n@ and request a Pootle account I can create that
> one for you. Romanian needs a bit of work... ;-)
>
> Regards,
>
>Matthias
>
> >
> >
> >
> > Thank you again, Multumesc din nou,
> >
> > Alex
> >
> > On Mon, Aug 17, 2020 at 8:57 PM Alex Mandai 
> > wrote:
> >
> >> Hi,
> >>
> >> Thank you for the warm welcome and for pointing me in the right
> direction.
> >>
> >> I also have some basic c++ skills, if that’s needed.
> >>
> >>
> >>
> >> Thank you again, Multumesc din nou,
> >>
> >> Alex
> >>
> >>
> >>
> >> *From: *Matthias Seidel 
> >> *Sent: *Monday, August 17, 2020 8:15 PM
> >> *To: *dev@openoffice.apache.org
> >> *Subject: *Re: Hello
> >>
> >>
> >>
> >> Hi Alex,
> >>
> >>
> >>
> >> You're welcome!
> >>
> >>
> >>
> >> Am 17.08.20 um 14:53 schrieb Alexandru Mandai:
> >>
> >>> Hi,
> >>> I just joined this mailing list and want to start working on the
> upcoming
> >>> release of OpenOffice.
> >>> I can translate it into Romanian.
> >>
> >>
> >> Translation for OpenOffice is coordinated on our L10N mailing list and
> >>
> >> done on our Pootle server.
> >>
> >>
> >>
> >> Please see:
> >>
> >>
> >>
> >> https://wiki.openoffice.org/wiki/Pootle_User_Guide
> >>
> >>
> >>
> >> for further details.
> >>
> >>
> >>
> >> Regards,
> >>
> >>
> >>
> >>Matthias
> >>
> >>
> >>
> >>>  I also know python, if that helps.
> >>> I was just wondering where can I start working on it.
> >>> Thank you, Multumesc,
> >>> Alex
> >>
> >>
> >>
> >>
>
>

Re: 4.1.8 on the 20th Anniversary? (was Re: 4.2.0 on the 20th Anniversary?)

[Jim Jagielski]

> On Aug 18, 2020, at 3:51 PM, Marcus  wrote:
> 
> Am 18.08.20 um 13:09 schrieb Jim Jagielski:
>> Should we think of doing a 4.1.8 beta?
> 
> do you have target group in mind? I mean, one that is really active and would 
> give us feedback?

Considering that the only recent version is 4.1.7, I would assume that target 
group.

> 
> At the moment I don't know anybody else than ourselves.
> 
> Marcus
> 
> 
> 
>>> On Aug 8, 2020, at 11:03 AM, Matthias Seidel  
>>> wrote:
>>> 
>>> Hi all,
>>> 
>>> Latest 4.1.8 Windows Test builds are also up:
>>> 
>>> https://home.apache.org/~mseidel/AOO-builds/AOO-418-Test/
>>> 
>>> Regards,
>>> 
>>>Matthias
>>> 
>>> Am 06.08.20 um 19:12 schrieb Pedro Lino:
 Thanks Jim
 
 Have been using the DEB x64 build under Ubuntu 18.04.4 x64 for real work 
 since lunch time and it is rock solid ;)
 Updated 4.1.7 without any issues.
 
 Cheers,
 Pedro
 
> On 08/06/2020 12:53 PM Jim Jagielski  wrote:
> 
> 
> I have a handful of builds for macOS and Linux 32+64bit available for 
> review/comment at
> 
>http://home.apache.org/~jim/AOO-builds/4.1.8-dev/
> 
> 
> 
>> On Aug 3, 2020, at 1:19 PM, Dave Fisher  wrote:
>> 
>> 
>> 
>>> On Aug 3, 2020, at 10:09 AM, Matthias Seidel 
>>>  wrote:
>>> 
>>> Hi Pedro,
>>> 
>>> Am 03.08.20 um 18:45 schrieb Pedro Lino:
 Hi Matthias
 
 
> On 08/03/2020 5:14 PM Matthias Seidel  
> wrote:
> Am 20.07.20 um 16:05 schrieb Pedro Lino:
>> +1
>> Please let me know what I can do (I am asking so this is not against 
>> the Apache Way)
> What you could do is to follow a complete release process and see 
> where
> you can help:
> 
> https://cwiki.apache.org/confluence/display/OOOUSERS/How+to+Cook+a+Release
 I can do that!
 
 Are you the Release Manager by lazy consensus? :)
>>> No...
 That page is still referring to SVN so a lot has to change...
>>> Well, a lot of commands still have to be in SVN because that's what we
>>> use for Apache infrastructure.
>> The parts that remain svn refer to https://dist.apache.org/ 
>>  > >
>> 
>> Regards,
>> Dave
>> 
>>> So we must find the parts that are Git now...
 I have no idea what are the equivalent commands from SVN to git (e.g. 
 to create a branch)
 
 Can you (or someone else) help fix this?
>>> Anyone can help! ;-)
>>> 
>>> Regards,
>>> 
>>>  Matthias
>>> 
 Cheers,
 Pedro
> 
> 
> -
> 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

Update OXT on extensions website

[Bidouille]

Hello,

Peter Lange has published DataPilotTools extension a long time ago:
https://extensions.openoffice.org/en/project/datapilot-tools-openofficeorg-calc

But this does not work with AOO 4.x
So, I build a new compatible version:
https://www.cjoint.com/doc/20_08/JHtncIxdzGs_DataPilotTools.oxt

Somebody has sufficient karma to update this OXT?

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Hello

[Matthias Seidel]

Hi Alex,

Am 19.08.20 um 12:53 schrieb Alexandru Mandai:
> Hi Matthias,
> Thank you for your reply. I wanted to create an account on pottle, but it
> said that New accounts cannot be created.

As I wrote you earlier, to request a Pootle account follow the
instructions here:

https://wiki.openoffice.org/wiki/Pootle_User_Guide/Registration_and_Login

We had to disable self-service because of to much spam accounts.

> Also, I received some e-mails about a 4.1.8 beta, maybe I can help with it.
> There was a link in the email containing an SDK (Software Development Kit).
> https://home.apache.org/~mseidel/AOO-builds/AOO-418-Test/

These are Test builds for Windows (incl. LanguagePack and SDK), not an
official Beta.

Feel free to download and test it. Unfortunately there is no Romanian
build at the moment.
I might add that next time...

Regards,

   Matthias

>
> Thanks for reading,
> Multumesc pentru ca ati citit,
> Alex
>
> On Tue, Aug 18, 2020 at 3:57 PM Matthias Seidel 
> wrote:
>
>> Hi Alex,
>>
>> Am 17.08.20 um 20:03 schrieb Alexandru Mandai:
>>> Hi,
>>>
>>> Thank you for the warm welcome and for pointing me in the right
>> direction.
>>> I also have some basic c++ skills, if that’s needed.
>> Every help is welcome!
>>
>> Regarding Python and C+: Discussions take place here on dev@.
>>
>> If you subscribe to L10n@ and request a Pootle account I can create that
>> one for you. Romanian needs a bit of work... ;-)
>>
>> Regards,
>>
>>Matthias
>>
>>>
>>>
>>> Thank you again, Multumesc din nou,
>>>
>>> Alex
>>>
>>> On Mon, Aug 17, 2020 at 8:57 PM Alex Mandai 
>>> wrote:
>>>
 Hi,

 Thank you for the warm welcome and for pointing me in the right
>> direction.
 I also have some basic c++ skills, if that’s needed.



 Thank you again, Multumesc din nou,

 Alex



 *From: *Matthias Seidel 
 *Sent: *Monday, August 17, 2020 8:15 PM
 *To: *dev@openoffice.apache.org
 *Subject: *Re: Hello



 Hi Alex,



 You're welcome!



 Am 17.08.20 um 14:53 schrieb Alexandru Mandai:

> Hi,
> I just joined this mailing list and want to start working on the
>> upcoming
> release of OpenOffice.
> I can translate it into Romanian.

 Translation for OpenOffice is coordinated on our L10N mailing list and

 done on our Pootle server.



 Please see:



 https://wiki.openoffice.org/wiki/Pootle_User_Guide



 for further details.



 Regards,



Matthias



>  I also know python, if that helps.
> I was just wondering where can I start working on it.
> Thank you, Multumesc,
> Alex



>>



smime.p7s
Description: S/MIME Cryptographic Signature

Re: [CONF] Apache OpenOffice Community > Website Migrations

[Matthias Seidel]

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.

Until then we need to preserve the existing pages where OOo expects them.

>
> Sent from my iPhone
>
>> On Aug 18, 2020, at 2:51 PM, Matthias Seidel  
>> 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
>>>  
>>> 
>>> Website Migrations
>>> 
>>> 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
>>> 



smime.p7s
Description: S/MIME Cryptographic Signature

Re: [CONF] Apache OpenOffice Community > Website Migrations

[Dave Fisher]

Sent from my iPhone

> On Aug 19, 2020, at 8:37 AM, Matthias Seidel  
> 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.

Regards,
Dave
> 
>> 
>> Sent from my iPhone
>> 
 On Aug 18, 2020, at 2:51 PM, Matthias Seidel  
 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
 
 
 Website Migrations
 
 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
 
> 


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: [CONF] Apache OpenOffice Community > Website Migrations

[Matthias Seidel]

Am 19.08.20 um 18:10 schrieb Dave Fisher:
>
> Sent from my iPhone
>
>> On Aug 19, 2020, at 8:37 AM, Matthias Seidel  
>> 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?

Regards,

   Matthias

>
> Regards,
> Dave
>>> Sent from my iPhone
>>>
> On Aug 18, 2020, at 2:51 PM, Matthias Seidel  
> 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
>
> 
> Website Migrations
> 
> 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
> 
>
> -
> 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

Re: [CONF] Apache OpenOffice Community > Website Migrations

[Dave Fisher]

> On Aug 19, 2020, at 9:14 AM, Matthias Seidel  
> 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  
>>> 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.

Regards,
Dave

> 
> Regards,
> 
>Matthias
> 
>> 
>> Regards,
>> Dave
 Sent from my iPhone
 
>> On Aug 18, 2020, at 2:51 PM, Matthias Seidel 
>>  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
>> 
>> 
>> Website Migrations
>> 
>> 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
>> 
>> 
>> -
>> 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

Re: [CONF] Apache OpenOffice Community > Website Migrations

[Matthias Seidel]

Am 19.08.20 um 18:55 schrieb Dave Fisher:
>
>> On Aug 19, 2020, at 9:14 AM, Matthias Seidel  
>> 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  
 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.

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 
>>>  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
>>>
>>> 
>>> Website Migrations
>>> 
>>> 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
>>> 
>>> -
>>> 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

Re: [CONF] Apache OpenOffice Community > Website Migrations

[Dave Fisher]

> On Aug 19, 2020, at 11:45 AM, Matthias Seidel  
> wrote:
> 
> Am 19.08.20 um 18:55 schrieb Dave Fisher:
>> 
>>> On Aug 19, 2020, at 9:14 AM, Matthias Seidel  
>>> 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  
> 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?

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 
  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
 
 
 Website Migrations
 
 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
 
 -
 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

Re: [CONF] Apache OpenOffice Community > Website Migrations

[Matthias Seidel]

Am 19.08.20 um 20:50 schrieb Dave Fisher:
>
>> On Aug 19, 2020, at 11:45 AM, Matthias Seidel  
>> wrote:
>>
>> Am 19.08.20 um 18:55 schrieb Dave Fisher:
 On Aug 19, 2020, at 9:14 AM, Matthias Seidel  
 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 
>>  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 
>  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
>
> 
> Website Migrations
> 
> 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, 
>>

Re: [CONF] Apache OpenOffice Community > Website Migrations

[Dave Fisher]

> On Aug 19, 2020, at 12:12 PM, Matthias Seidel  
> wrote:
> 
> Am 19.08.20 um 20:50 schrieb Dave Fisher:
>> 
>>> On Aug 19, 2020, at 11:45 AM, Matthias Seidel  
>>> wrote:
>>> 
>>> Am 19.08.20 um 18:55 schrieb Dave Fisher:
> On Aug 19, 2020, at 9:14 AM, Matthias Seidel  
> 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 
>>>  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)

I made some comments. Like Pedro I suspect a regression in the code.

Do you know where the update code is?

> 
> 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 
>>  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
>> 
>> 
>> Website Migrations
>> 
>> 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/marke

Re: [CONF] Apache OpenOffice Community > Website Migrations

[Matthias Seidel]

Hi Dave,

Am 19.08.20 um 22:11 schrieb Dave Fisher:
>
>> On Aug 19, 2020, at 12:12 PM, Matthias Seidel  
>> wrote:
>>
>> Am 19.08.20 um 20:50 schrieb Dave Fisher:
 On Aug 19, 2020, at 11:45 AM, Matthias Seidel  
 wrote:

 Am 19.08.20 um 18:55 schrieb Dave Fisher:
>> On Aug 19, 2020, at 9:14 AM, Matthias Seidel 
>>  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 
  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)
> I made some comments. Like Pedro I suspect a regression in the code.

It stopped working about two years ago (for 4.x.x)
And it is working for 4.2.x and trunk with the same update feeds.

I am still not convinced... ;-)

>
> Do you know where the update code is?

Sorry, maybe some developer knows?

>
>> 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 
>>>  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
>>>
>>> 
>>> Website Migrations
>>> 
>>> 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.
>>> (d

Re: [CONF] Apache OpenOffice Community > Website Migrations

[Dave Fisher]

> On Aug 19, 2020, at 1:24 PM, Matthias Seidel  
> wrote:
> 
> Hi Dave,
> 
> Am 19.08.20 um 22:11 schrieb Dave Fisher:
>> 
>>> On Aug 19, 2020, at 12:12 PM, Matthias Seidel  
>>> wrote:
>>> 
>>> Am 19.08.20 um 20:50 schrieb Dave Fisher:
> On Aug 19, 2020, at 11:45 AM, Matthias Seidel 
>  wrote:
> 
> Am 19.08.20 um 18:55 schrieb Dave Fisher:
>>> On Aug 19, 2020, at 9:14 AM, Matthias Seidel 
>>>  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 
>  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)
>> I made some comments. Like Pedro I suspect a regression in the code.
> 
> It stopped working about two years ago (for 4.x.x)
> And it is working for 4.2.x and trunk with the same update feeds.
> 
> I am still not convinced... ;-)

The other thought is the version of openssl and/or curl used and which versions 
got which upgrades.

> 
>> 
>> Do you know where the update code is?
> 
> Sorry, maybe some developer knows?

Need to look at the history of

(1) openssl
(2) curl
(3) and the code that uses those.

Regards,
Dave

> 
>> 
>>> 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 
  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
 
 
 Website Migrations
 
 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 tra