Re: Status on Migration of OpenOffice.org from the Apache CMS

[Carl Marcum]

That's awesome Dave !!

Thanks for the hard work!

Best regards,
Carl

On 11/9/20 7:03 PM, Dave Fisher wrote:

Hi -

I almost have openoffice.apache.org  migrated. 
It builds. I’ll be doing setup and READMEs tomorrow.

Regards,
Dave


On Nov 9, 2020, at 3:38 PM, Marcus  wrote:

Am 09.11.20 um 21:11 schrieb Dave Fisher:

Woot!
The staging site is now finished with rfloatimg and product-* css applied 
properly.
Please take a look.

that's great. Thanks for this. :-)

I think I will have more time and concentration when the release is done - most 
likely on the weekend when I've some more time.

Maybe others can have a look earlier?


I’ll migrate and document the changes from the coming release manually.

Do you want to look for changes on your own or do you want a list of files - at 
least the ones I've changed?

Marcus




On Nov 6, 2020, at 11:41 AM, Dave Fisher  wrote:

API section is now available:

https://openoffice-org.staged.apache.org/api/ 


The second part folders are in:

https://github.com/apache/openoffice-org/tree/main/part2 


Regards,
Dave


On Nov 5, 2020, at 12:14 PM, Dave Fisher mailto:w...@apache.org>> wrote:


The Jenkins setup redux is priority (1)

The builds are ready.

https://ci-builds.apache.org/job/OpenOffice/view/OpenOffice.org/ 
 
>


The instructions are priority (2).

Instructions are in README.md files:

(1) Site instructions
https://github.com/apache/openoffice-org  
>

(2) Templates information
https://github.com/apache/openoffice-org/tree/main/templates 
 
>

(3) Migration scripts
https://github.com/apache/openoffice-org/tree/main/tools 
 
>

(4) Staging site branch
https://github.com/apache/openoffice-org/tree/asf-staging 
 
>

(5) Production site branch (not active)
https://github.com/apache/openoffice-org/tree/asf-site 
 
>


Please wait for those.


Staging site
https://openoffice-org.staged.apache.org  
>

Known issues.
(A) Right floating images on Why and Product pages.
(B) Application Icons on Product pages.
(C) Missing API section.

Please check it out!


-
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: Status on Migration of OpenOffice.org from the Apache CMS

[Dave Fisher]

Hi -

I almost have openoffice.apache.org  migrated. 
It builds. I’ll be doing setup and READMEs tomorrow.

Regards,
Dave

> On Nov 9, 2020, at 3:38 PM, Marcus  wrote:
> 
> Am 09.11.20 um 21:11 schrieb Dave Fisher:
>> Woot!
>> The staging site is now finished with rfloatimg and product-* css applied 
>> properly.
>> Please take a look.
> 
> that's great. Thanks for this. :-)
> 
> I think I will have more time and concentration when the release is done - 
> most likely on the weekend when I've some more time.
> 
> Maybe others can have a look earlier?
> 
>> I’ll migrate and document the changes from the coming release manually.
> 
> Do you want to look for changes on your own or do you want a list of files - 
> at least the ones I've changed?
> 
> Marcus
> 
> 
> 
>>> On Nov 6, 2020, at 11:41 AM, Dave Fisher  wrote:
>>> 
>>> API section is now available:
>>> 
>>> https://openoffice-org.staged.apache.org/api/ 
>>> 
>>> 
>>> The second part folders are in:
>>> 
>>> https://github.com/apache/openoffice-org/tree/main/part2 
>>> 
>>> 
>>> Regards,
>>> Dave
>>> 
 On Nov 5, 2020, at 12:14 PM, Dave Fisher >>> > wrote:
 
>> The Jenkins setup redux is priority (1)
 
 The builds are ready.
 
 https://ci-builds.apache.org/job/OpenOffice/view/OpenOffice.org/ 
  
 >
 
>> The instructions are priority (2).
 
 Instructions are in README.md files:
 
 (1) Site instructions
 https://github.com/apache/openoffice-org 
  
 >
 
 (2) Templates information
 https://github.com/apache/openoffice-org/tree/main/templates 
  
 >
 
 (3) Migration scripts
 https://github.com/apache/openoffice-org/tree/main/tools 
  
 >
 
 (4) Staging site branch
 https://github.com/apache/openoffice-org/tree/asf-staging 
  
 >
 
 (5) Production site branch (not active)
 https://github.com/apache/openoffice-org/tree/asf-site 
  
 >
 
>> Please wait for those.
 
 
 Staging site
 https://openoffice-org.staged.apache.org 
  
 >
 
 Known issues.
 (A) Right floating images on Why and Product pages.
 (B) Application Icons on Product pages.
 (C) Missing API section.
 
 Please check it out!
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 

Re: Status on Migration of OpenOffice.org from the Apache CMS

[Marcus]

Am 09.11.20 um 21:11 schrieb Dave Fisher:

Woot!

The staging site is now finished with rfloatimg and product-* css applied 
properly.

Please take a look.


that's great. Thanks for this. :-)

I think I will have more time and concentration when the release is done 
- most likely on the weekend when I've some more time.


Maybe others can have a look earlier?


I’ll migrate and document the changes from the coming release manually.


Do you want to look for changes on your own or do you want a list of 
files - at least the ones I've changed?


Marcus




On Nov 6, 2020, at 11:41 AM, Dave Fisher  wrote:

API section is now available:

https://openoffice-org.staged.apache.org/api/ 


The second part folders are in:

https://github.com/apache/openoffice-org/tree/main/part2 


Regards,
Dave


On Nov 5, 2020, at 12:14 PM, Dave Fisher mailto:w...@apache.org>> wrote:


The Jenkins setup redux is priority (1)


The builds are ready.

https://ci-builds.apache.org/job/OpenOffice/view/OpenOffice.org/ 
 
>


The instructions are priority (2).


Instructions are in README.md files:

(1) Site instructions
https://github.com/apache/openoffice-org  
>

(2) Templates information
https://github.com/apache/openoffice-org/tree/main/templates 
 
>

(3) Migration scripts
https://github.com/apache/openoffice-org/tree/main/tools 
 
>

(4) Staging site branch
https://github.com/apache/openoffice-org/tree/asf-staging 
 
>

(5) Production site branch (not active)
https://github.com/apache/openoffice-org/tree/asf-site 
 
>


Please wait for those.



Staging site
https://openoffice-org.staged.apache.org  
>

Known issues.
(A) Right floating images on Why and Product pages.
(B) Application Icons on Product pages.
(C) Missing API section.

Please check it out!



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

Re: Status on Migration of OpenOffice.org from the Apache CMS

[Dave Fisher]

Woot!

The staging site is now finished with rfloatimg and product-* css applied 
properly.

Please take a look.

I’ll migrate and document the changes from the coming release manually. 

Regards,
Dave
> On Nov 6, 2020, at 11:41 AM, Dave Fisher  wrote:
> 
> API section is now available:
> 
> https://openoffice-org.staged.apache.org/api/ 
> 
> 
> The second part folders are in:
> 
> https://github.com/apache/openoffice-org/tree/main/part2 
> 
> 
> Regards,
> Dave
> 
>> On Nov 5, 2020, at 12:14 PM, Dave Fisher > > wrote:
>> 
 The Jenkins setup redux is priority (1)
>> 
>> The builds are ready.
>> 
>> https://ci-builds.apache.org/job/OpenOffice/view/OpenOffice.org/ 
>>  
>> > >
>> 
 The instructions are priority (2).
>> 
>> Instructions are in README.md files:
>> 
>> (1) Site instructions
>> https://github.com/apache/openoffice-org 
>>  
>> > >
>> 
>> (2) Templates information
>> https://github.com/apache/openoffice-org/tree/main/templates 
>>  
>> > >
>> 
>> (3) Migration scripts
>> https://github.com/apache/openoffice-org/tree/main/tools 
>>  
>> > >
>> 
>> (4) Staging site branch
>> https://github.com/apache/openoffice-org/tree/asf-staging 
>>  
>> > >
>> 
>> (5) Production site branch (not active)
>> https://github.com/apache/openoffice-org/tree/asf-site 
>>  
>> > >
>> 
 Please wait for those.
>> 
>> 
>> Staging site
>> https://openoffice-org.staged.apache.org 
>>  
>> > >
>> 
>> Known issues.
>> (A) Right floating images on Why and Product pages.
>> (B) Application Icons on Product pages.
>> (C) Missing API section.
>> 
>> Please check it out!
>> 
>> Regards,
>> Dave
> 

Re: Status on Migration of OpenOffice.org from the Apache CMS

[Dave Fisher]

API section is now available:

https://openoffice-org.staged.apache.org/api/ 


The second part folders are in:

https://github.com/apache/openoffice-org/tree/main/part2 


Regards,
Dave

> On Nov 5, 2020, at 12:14 PM, Dave Fisher  wrote:
> 
>>> The Jenkins setup redux is priority (1)
> 
> The builds are ready.
> 
> https://ci-builds.apache.org/job/OpenOffice/view/OpenOffice.org/ 
> 
> 
>>> The instructions are priority (2).
> 
> Instructions are in README.md files:
> 
> (1) Site instructions
> https://github.com/apache/openoffice-org 
> 
> 
> (2) Templates information
> https://github.com/apache/openoffice-org/tree/main/templates 
> 
> 
> (3) Migration scripts
> https://github.com/apache/openoffice-org/tree/main/tools 
> 
> 
> (4) Staging site branch
> https://github.com/apache/openoffice-org/tree/asf-staging 
> 
> 
> (5) Production site branch (not active)
> https://github.com/apache/openoffice-org/tree/asf-site 
> 
> 
>>> Please wait for those.
> 
> 
> Staging site
> https://openoffice-org.staged.apache.org 
> 
> 
> Known issues.
> (A) Right floating images on Why and Product pages.
> (B) Application Icons on Product pages.
> (C) Missing API section.
> 
> Please check it out!
> 
> Regards,
> Dave

Re: Status on Migration of OpenOffice.org from the Apache CMS

[Dave Fisher]

>> The Jenkins setup redux is priority (1)

The builds are ready.

https://ci-builds.apache.org/job/OpenOffice/view/OpenOffice.org/ 


>> The instructions are priority (2).

Instructions are in README.md files:

(1) Site instructions
https://github.com/apache/openoffice-org 


(2) Templates information
https://github.com/apache/openoffice-org/tree/main/templates 


(3) Migration scripts
https://github.com/apache/openoffice-org/tree/main/tools 


(4) Staging site branch
https://github.com/apache/openoffice-org/tree/asf-staging 


(5) Production site branch (not active)
https://github.com/apache/openoffice-org/tree/asf-site 


>> Please wait for those.


Staging site
https://openoffice-org.staged.apache.org 


Known issues.
(A) Right floating images on Why and Product pages.
(B) Application Icons on Product pages.
(C) Missing API section.

Please check it out!

Regards,
Dave

Re: Status on Migration of OpenOffice.org from the Apache CMS

[Marcus]

Am 04.11.20 um 00:04 schrieb Dave Fisher:

Wait a bit more.


On Nov 3, 2020, at 2:56 PM, Marcus  wrote:

Am 03.11.20 um 22:57 schrieb Dave Fisher:

Current status in line!

On Nov 2, 2020, at 10:45 AM, Jim Jagielski  wrote:

Dave, your work in this migration is greatly, greatly, appreciated  !

Thank you very much.


thank you very much for this big effort. Even when I can see the countless 
commits you have done until now, I can only roughly imagine how big and 
invaluable this work is.


On Nov 2, 2020, at 1:42 PM, Dave Fisher  wrote:

Hi -

I am in the process of migrating content from SVN to Git.

All content has been migrated aside from
(1) The api pages. I ran into a limitation on the number of pages (~16384) in Jbake. 
I excluded those since there are roughly 8000 pages. I think that these pages should 
be made part of the openoffice.apache.org  site. 
Anything else to move there?


In the past we had the following separation:

www.openoffice.org
Everything for and about the OpenOffice software

openoffice.apache.org
Everything for and about the OpenOffice project

When we agree to go on with this, then I thin kthe API still belongs to the 
w.oo.o site.


OK then - I’ll need to consider options. We may need a twice baked site. This 
is priority (4)




(2) Jbake uses Freemarker-java for Markdown support. It uses a Pegdown dialect 
that does not support class and id setting in the Markdown. I’ll need to 
remigrate the product and why pages to switch to a line of plain html. I’ve 
tested the concept.


There are some 333 files to address. Most are “easy”, but I still need to 
figure out the product pages with their icon images. This is priority (3) (and 
instructions will need adjustment.)


(3) I deleted four EXE files from within the pl site’s Archive. I don’t think 
we should host exe files.


Full ACK


Staging is getting interesting @ https://openoffice-org.staged.apache.org 


I migrated documentation and ran into a problem with a 330 MB file:
content/documentation/conceptualguide/conceptualguideOOo3_audiobook_0-1alpha.zip

Github only allows files up to 100 MB. I will not migrate this file. I got 
around the problem by erasing history. If anyone cares then perhaps I can find 
a workaround, but I would rather not.

Github: https://github.com/apache/openoffice-org 

Gitbox: https://gitbox.apache.org/repos/asf?p=openoffice-org.git;a=summary 


Take a look, but let me finish migrating content before making changes through 
GitHub.

READMEs are not yet finalized.

Once I complete these then I can let people play with changes using Github.
I also have to retest and complete the Jenkins jobs.
There is now an OpenOffice folder on the new ci-builds.apache.org 
 master.


Are there already instructions how the new site works and how it can be edited? 
Or do we need to wait a bit more?


The Jenkins setup redux is priority (1)

The instructions are priority (2).

Please wait for those.

I’m done for today.


thats OK, you have done already much. It would be right when you take a 
break of 1-2 days. :-)


Thanks again

Marcus


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

Re: Status on Migration of OpenOffice.org from the Apache CMS

[Dave Fisher]

Hi Marcus,

Wait a bit more.

> On Nov 3, 2020, at 2:56 PM, Marcus  wrote:
> 
> Am 03.11.20 um 22:57 schrieb Dave Fisher:
>> Current status in line!
>>> On Nov 2, 2020, at 10:45 AM, Jim Jagielski  wrote:
>>> 
>>> Dave, your work in this migration is greatly, greatly, appreciated  !
>> Thank you very much.
> 
> thank you very much for this big effort. Even when I can see the countless 
> commits you have done until now, I can only roughly imagine how big and 
> invaluable this work is.
> 
 On Nov 2, 2020, at 1:42 PM, Dave Fisher  wrote:
 
 Hi -
 
 I am in the process of migrating content from SVN to Git.
>> All content has been migrated aside from
>> (1) The api pages. I ran into a limitation on the number of pages (~16384) 
>> in Jbake. I excluded those since there are roughly 8000 pages. I think that 
>> these pages should be made part of the openoffice.apache.org 
>>  site. Anything else to move there?
> 
> In the past we had the following separation:
> 
> www.openoffice.org
> Everything for and about the OpenOffice software
> 
> openoffice.apache.org
> Everything for and about the OpenOffice project
> 
> When we agree to go on with this, then I thin kthe API still belongs to the 
> w.oo.o site.

OK then - I’ll need to consider options. We may need a twice baked site. This 
is priority (4)

> 
>> (2) Jbake uses Freemarker-java for Markdown support. It uses a Pegdown 
>> dialect that does not support class and id setting in the Markdown. I’ll 
>> need to remigrate the product and why pages to switch to a line of plain 
>> html. I’ve tested the concept.

There are some 333 files to address. Most are “easy”, but I still need to 
figure out the product pages with their icon images. This is priority (3) (and 
instructions will need adjustment.)

>> (3) I deleted four EXE files from within the pl site’s Archive. I don’t 
>> think we should host exe files.
> 
> Full ACK
> 
 Staging is getting interesting @ https://openoffice-org.staged.apache.org 
 
 
 I migrated documentation and ran into a problem with a 330 MB file:
 content/documentation/conceptualguide/conceptualguideOOo3_audiobook_0-1alpha.zip
 
 Github only allows files up to 100 MB. I will not migrate this file. I got 
 around the problem by erasing history. If anyone cares then perhaps I can 
 find a workaround, but I would rather not.
 
 Github: https://github.com/apache/openoffice-org 
 
 Gitbox: https://gitbox.apache.org/repos/asf?p=openoffice-org.git;a=summary 
 
 
 Take a look, but let me finish migrating content before making changes 
 through GitHub.
 
 READMEs are not yet finalized.
>> Once I complete these then I can let people play with changes using Github.
>> I also have to retest and complete the Jenkins jobs.
>> There is now an OpenOffice folder on the new ci-builds.apache.org 
>>  master.
> 
> Are there already instructions how the new site works and how it can be 
> edited? Or do we need to wait a bit more?

The Jenkins setup redux is priority (1)

The instructions are priority (2).

Please wait for those.

I’m done for today.

Regards,
Dave

> 
> Thanks
> 
> Marcus
> 
> 
> -
> 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: Status on Migration of OpenOffice.org from the Apache CMS

[Marcus]

Am 03.11.20 um 22:57 schrieb Dave Fisher:

Current status in line!


On Nov 2, 2020, at 10:45 AM, Jim Jagielski  wrote:

Dave, your work in this migration is greatly, greatly, appreciated  !


Thank you very much.


thank you very much for this big effort. Even when I can see the 
countless commits you have done until now, I can only roughly imagine 
how big and invaluable this work is.



On Nov 2, 2020, at 1:42 PM, Dave Fisher  wrote:

Hi -

I am in the process of migrating content from SVN to Git.


All content has been migrated aside from

(1) The api pages. I ran into a limitation on the number of pages (~16384) in Jbake. 
I excluded those since there are roughly 8000 pages. I think that these pages should 
be made part of the openoffice.apache.org  site. 
Anything else to move there?


In the past we had the following separation:

www.openoffice.org
Everything for and about the OpenOffice software

openoffice.apache.org
Everything for and about the OpenOffice project

When we agree to go on with this, then I thin kthe API still belongs to 
the w.oo.o site.



(2) Jbake uses Freemarker-java for Markdown support. It uses a Pegdown dialect 
that does not support class and id setting in the Markdown. I’ll need to 
remigrate the product and why pages to switch to a line of plain html. I’ve 
tested the concept.

(3) I deleted four EXE files from within the pl site’s Archive. I don’t think 
we should host exe files.


Full ACK


Staging is getting interesting @ https://openoffice-org.staged.apache.org 


I migrated documentation and ran into a problem with a 330 MB file:
content/documentation/conceptualguide/conceptualguideOOo3_audiobook_0-1alpha.zip

Github only allows files up to 100 MB. I will not migrate this file. I got 
around the problem by erasing history. If anyone cares then perhaps I can find 
a workaround, but I would rather not.

Github: https://github.com/apache/openoffice-org 

Gitbox: https://gitbox.apache.org/repos/asf?p=openoffice-org.git;a=summary 


Take a look, but let me finish migrating content before making changes through 
GitHub.

READMEs are not yet finalized.


Once I complete these then I can let people play with changes using Github.

I also have to retest and complete the Jenkins jobs.

There is now an OpenOffice folder on the new ci-builds.apache.org 
 master.


Are there already instructions how the new site works and how it can be 
edited? Or do we need to wait a bit more?


Thanks

Marcus


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

Re: Status on Migration of OpenOffice.org from the Apache CMS

[Dave Fisher]

Current status in line!

> On Nov 2, 2020, at 10:45 AM, Jim Jagielski  wrote:
> 
> Dave, your work in this migration is greatly, greatly, appreciated!

Thank you very much.
> 
>> On Nov 2, 2020, at 1:42 PM, Dave Fisher  wrote:
>> 
>> Hi -
>> 
>> I am in the process of migrating content from SVN to Git.

All content has been migrated aside from

(1) The api pages. I ran into a limitation on the number of pages (~16384) in 
Jbake. I excluded those since there are roughly 8000 pages. I think that these 
pages should be made part of the openoffice.apache.org 
 site. Anything else to move there?

(2) Jbake uses Freemarker-java for Markdown support. It uses a Pegdown dialect 
that does not support class and id setting in the Markdown. I’ll need to 
remigrate the product and why pages to switch to a line of plain html. I’ve 
tested the concept.

(3) I deleted four EXE files from within the pl site’s Archive. I don’t think 
we should host exe files.


>> 
>> Staging is getting interesting @ https://openoffice-org.staged.apache.org 
>> 
>> 
>> I migrated documentation and ran into a problem with a 330 MB file:
>> content/documentation/conceptualguide/conceptualguideOOo3_audiobook_0-1alpha.zip
>> 
>> Github only allows files up to 100 MB. I will not migrate this file. I got 
>> around the problem by erasing history. If anyone cares then perhaps I can 
>> find a workaround, but I would rather not.
>> 
>> Github: https://github.com/apache/openoffice-org 
>> 
>> Gitbox: https://gitbox.apache.org/repos/asf?p=openoffice-org.git;a=summary 
>> 
>> 
>> Take a look, but let me finish migrating content before making changes 
>> through GitHub.
>> 
>> READMEs are not yet finalized.

Once I complete these then I can let people play with changes using Github.

I also have to retest and complete the Jenkins jobs.

There is now an OpenOffice folder on the new ci-builds.apache.org 
 master.

Regards,
Dave

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

Re: Status on Migration of OpenOffice.org from the Apache CMS

[Jim Jagielski]

Dave, your work in this migration is greatly, greatly, appreciated  !

> On Nov 2, 2020, at 1:42 PM, Dave Fisher  wrote:
> 
> Hi -
> 
> I am in the process of migrating content from SVN to Git.
> 
> Staging is getting interesting @ https://openoffice-org.staged.apache.org 
> 
> 
> I migrated documentation and ran into a problem with a 330 MB file:
> content/documentation/conceptualguide/conceptualguideOOo3_audiobook_0-1alpha.zip
> 
> Github only allows files up to 100 MB. I will not migrate this file. I got 
> around the problem by erasing history. If anyone cares then perhaps I can 
> find a workaround, but I would rather not.
> 
> Github: https://github.com/apache/openoffice-org 
> 
> Gitbox: https://gitbox.apache.org/repos/asf?p=openoffice-org.git;a=summary 
> 
> 
> Take a look, but let me finish migrating content before making changes 
> through GitHub.
> 
> READMEs are not yet finalized.
> 
> Regards,
> Dave


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