openoffice-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus (OOo)" <>
Subject Re: [migration][web] Scripted Conversions.
Date Mon, 29 Aug 2011 09:36:10 GMT
Thanks for your great work.

I've a recommendation when adding+committing the "development" project.

As there are billions of release notes I would only commit the latest 
into SVN and pack the others into a ZIP file; split into Beta, RC, 
nightly build, etc.

Release notes from OOo 2.0 (from 2006?) are really no longer 
interesting. However, within the ZIP files we still have them and could 
link to.


Am 08/29/2011 01:30 AM, schrieb Dave Fisher:
> Yesterday I worked on conversion scripts for the website. They are now in ooo/site/trunk/tools/.
> readme.txt
> web-list.txt
> urlrewrite.sed
> The skeleton is now in good shape to handle Kenai based html. A change may be needed
to preserve some PDL license comments. Also the footer may need to be changed for PDL for
some pages. I have focused on two processes to be used on a project by project basis.
> (1) ${project}
> This is used to move a project from Kenai's svn to the correct place in ooo/site/trunk/content/openofficeorg/${project}
> A dos2unix is applied to fix some mixed line endings. If there is an AL 2.0 compatible
version of  dos2unix then I'd like to include it.
> If the project exists in AOOo then a diff is done to find files that differ. This can
be because they were changed in Kenai. More likely this will be customization that was required.
The why project will require it.
> (2) ${project}
> This applies a sed script to rewrite urls in the html for a project.
> s/http:\/\/\/openofficeorg\/www/g
> s/http:\/\/\/openofficeorg\/download/g
> s/http:\/\/\/openofficeorg\/support/g
> s/http:\/\/\/openofficeorg\/contributing/g
> s/http:\/\/\/openofficeorg\/projects/g
> s/http:\/\/\/openofficeorg\/why/g
> Other tools can be applied to find and properly take care of various licenses and copyrights.
> The project should consider using Apache RAT at some point when we are ready to check
for AL 2.0 headers as applied.
> (3) - I plan to convert to
> It will run another script like or for each project in
a project list file like web-list.txt.
> Once a project is copied then I recommend local builds until the new project is correct
before checking in the project. Raphael did this live and some intervention was required to
clear the buildbot for the project.
> One key part is finding bad url references to images and adding images to content/openofficeorg/
> Regards,
> Dave

View raw message