You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Jürgen Schmidt <jo...@googlemail.com> on 2012/01/09 16:58:05 UTC
NOTICE, LICENSE, README etc.
Hi,
I tried to get an overview about the current state in an installed
office and the process of generating localized LICENSE files, README and
how the THIRSPARTYLICENSEREADME.html comes into the game...
Current situation on a
MacOS system
============
OpenOffice.org.app/Content/LICENSE
OpenOffice.org.app/Content/LICENSE.hmtl
OpenOffice.org.app/Content/README
OpenOffice.org.app/Content/README.html
OpenOffice.org.app/Content/basis-link/THIRDPARTYLICENSEREADME.html
Window system
=============
.../OpenOffice.org 3/license.html
.../OpenOffice.org 3/license.txt
.../OpenOffice.org 3/readme.html
.../OpenOffice.org 3/readme.txt
.../OpenOffice.org 3/readmes/readme_en-US.html
.../OpenOffice.org 3/readmes/readme_en-US.txt
.../OpenOffice.org 3/THIRDPARTYLICENSEREADME.html
readme files are always the same, readme.[txt|html] = readme.[txt|html]
Linux System
============
/org/openoffice.org/LICENSE
/org/openoffice.org/LICENSE.hmtl
/org/openoffice.org/README
/org/openoffice.org/README.html
/org/openoffice.org/THIRDPARTYLICENSEREADME.html
The input for these files comes from the main/readlicense_oo module
LICENSE
readlicense_oo/source/license/license_en-US.html
readlicense_oo/source/license/license_en-US.txt
readlicense_oo/source/license/license_en-US.rtf
README
readlicense_oo/docs/readme/readme.xrm
the "plattform" specific README will be generated out of the readme.xrm
file . Well don't ask why it is done this way. It looks quite complicate
...
THIRDPARTYLICENSEREADME
readlicense_oo/html/THIRDPARTYLICENSEREADME.html
I can't really find any information on [1] if we need localized versions
of the LICENSE, NOTICE, README files.
The whole process in the office is a little bit more complex today and
it raised some questions for me.
1. Do we want to keep localized versions of these files, or do we need
them?
2. Should we simply create one README for all or one for each plattform
and should check in this directly?
3. is related to the existing LICENSE [2] file in our source main
directory. In line 190 we have
###
...
Copyright [yyyy] [name of copyright owner]
...
###
How does it have to be for a release? I assume something like
###
...
Copyright 2011 Apache Software Foundation
...
###
4. THIRDPARTYLICENSEREADME.hmtl has to be merged into NOTICE (or already
had)
Juergen
[1]: incubator.apache.org/guides/releasemanagement.html
[2]:
http://svn.apache.org/viewvc/incubator/ooo/trunk/main/LICENSE?view=markup
Re: NOTICE, LICENSE, README etc.
Posted by Pedro Giffuni <pf...@apache.org>.
Hello;
As a suggestion I think we should have the build instructions
and the requirements available within the distribution, README
would be OK but INSTALL.TXT is probably better.
Pedro.
--- Mar 10/1/12, Andrea Pescetti <pe...@apache.org> ha scritto:
...
>
> The README is outdated and contains a brief FAQ and some
> stuff (like system requirements) that could probably be
> shortened or removed. It is localized, but the effort of
> rewriting it and translating it again would be worth only if
> we make it reachable from the GUI.
>
> Regards,
> Andrea.
>
Re: NOTICE, LICENSE, README etc.
Posted by Andrea Pescetti <pe...@apache.org>.
On 09/01/2012 Jürgen Schmidt wrote:
> On 1/9/12 5:31 PM, Rob Weir wrote:
>> But how does README differ from the Release Notes? Do we currently
>> have both and translate both?
> I have to confess I don't know it, will try to figure this out
If I recall correctly, the release notes are always version-specific and
best replaced by web pages or wiki pages; and it's important to localize
them but not to include them in the released package (after all, it
might happen that some post-release information gets added).
The README is outdated and contains a brief FAQ and some stuff (like
system requirements) that could probably be shortened or removed. It is
localized, but the effort of rewriting it and translating it again would
be worth only if we make it reachable from the GUI.
Regards,
Andrea.
Re: NOTICE, LICENSE, README etc.
Posted by Jürgen Schmidt <jo...@googlemail.com>.
On 1/9/12 5:31 PM, Rob Weir wrote:
> 2012/1/9 Jürgen Schmidt<jo...@googlemail.com>:
>> Hi,
>>
>> I tried to get an overview about the current state in an installed office
>> and the process of generating localized LICENSE files, README and how the
>> THIRSPARTYLICENSEREADME.html comes into the game...
>>
>> Current situation on a
>>
>> MacOS system
>> ============
>> OpenOffice.org.app/Content/LICENSE
>> OpenOffice.org.app/Content/LICENSE.hmtl
>> OpenOffice.org.app/Content/README
>> OpenOffice.org.app/Content/README.html
>> OpenOffice.org.app/Content/basis-link/THIRDPARTYLICENSEREADME.html
>>
>> Window system
>> =============
>> .../OpenOffice.org 3/license.html
>> .../OpenOffice.org 3/license.txt
>> .../OpenOffice.org 3/readme.html
>> .../OpenOffice.org 3/readme.txt
>> .../OpenOffice.org 3/readmes/readme_en-US.html
>> .../OpenOffice.org 3/readmes/readme_en-US.txt
>> .../OpenOffice.org 3/THIRDPARTYLICENSEREADME.html
>>
>> readme files are always the same, readme.[txt|html] = readme.[txt|html]
>>
>> Linux System
>> ============
>> /org/openoffice.org/LICENSE
>> /org/openoffice.org/LICENSE.hmtl
>> /org/openoffice.org/README
>> /org/openoffice.org/README.html
>> /org/openoffice.org/THIRDPARTYLICENSEREADME.html
>>
>>
>> The input for these files comes from the main/readlicense_oo module
>>
>> LICENSE
>> readlicense_oo/source/license/license_en-US.html
>> readlicense_oo/source/license/license_en-US.txt
>> readlicense_oo/source/license/license_en-US.rtf
>>
>> README
>> readlicense_oo/docs/readme/readme.xrm
>>
>> the "plattform" specific README will be generated out of the readme.xrm file
>> . Well don't ask why it is done this way. It looks quite complicate ...
>>
>> THIRDPARTYLICENSEREADME
>> readlicense_oo/html/THIRDPARTYLICENSEREADME.html
>>
>>
>> I can't really find any information on [1] if we need localized versions of
>> the LICENSE, NOTICE, README files.
>>
>
> We're not required to translate these files and I'd advise against
> doing this at least in the case of the LICENSE and NOTICE files. It
> is impossible to translate a license without applying our own
> interpretation of that license. That is like giving legal advice
> then. We should not being doing that.
ok, I agree and we can probably simplify the process here
>
> The README file is another story, and I'd be open to a different story there.
>
> But how does README differ from the Release Notes? Do we currently
> have both and translate both?
I have to confess I don't know it, will try to figure this out
>
>> The whole process in the office is a little bit more complex today and it
>> raised some questions for me.
>>
>> 1. Do we want to keep localized versions of these files, or do we need them?
>>
>
> I'd keep the required legal files (LICENSE and NOTICE) in their
> original form (English).
taken, see above
>
> For README, we need to consider the audience. We will have source and
> binary packages. For source packages, the README should be covering
> build pre-reqs, build flags, how to submit patches, generally a
> programmer-oriented README. For the binary package, the README is
> admin and end-user oriented.
good point, we need definitely a second one for the source release.
The generated approach allows for example to change the $PRODUCT_NAME
quite easily (probably not necessary anymore) and of course puts some
platform specific content into the file.
>
>> 2. Should we simply create one README for all or one for each plattform and
>> should check in this directly?
>>
>
> That could be fine.
well if we check in the files directly we have to check how a potential
translation of a plain text file works.
The source release README have to be in English only, yeah ;-)
>
>
>> 3. is related to the existing LICENSE [2] file in our source main directory.
>> In line 190 we have
>> ###
>> ...
>> Copyright [yyyy] [name of copyright owner]
>> ...
>> ###
>>
>> How does it have to be for a release? I assume something like
>> ###
>> ...
>> Copyright 2011 Apache Software Foundation
>> ...
>> ###
>>
>
> I don't think we change line 190. That is instructions for someone
> who wants to add ALv2 to their own code.
>
ah you are right, my fault not reading careful enough the context here
Juergen
>
>> 4. THIRDPARTYLICENSEREADME.hmtl has to be merged into NOTICE (or already
>> had)
>>
>
> Most of THIRDPARTYLICENSEREADME will go into LICENSE. That is where
> we aggregate the licenses for all of the code that we include in the
> release. Since we're including additional libraries in the binary
> package that are not included in the source package, this probably
> means that we will have two different LICENSE and NOTICE files that we
> will need to rename and package at build time, depending on whether we
> are building a binary package or a source package.
>
> NOTICE is for any required notice that the 3rd party license requires
> us to make. It does not include the full text of the license. For
> example, a license might require that we include a link to where
> someone can download the source code of the component. We'd put that
> in NOTICE. And the Oracle copyright that Andrew is removing from
> source files, that would move into NOTICE as well.
>
> -Rob
>
>>
>> Juergen
>>
>> [1]: incubator.apache.org/guides/releasemanagement.html
>> [2]:
>> http://svn.apache.org/viewvc/incubator/ooo/trunk/main/LICENSE?view=markup
>>
Re: NOTICE, LICENSE, README etc.
Posted by Rob Weir <ro...@apache.org>.
2012/1/9 Jürgen Schmidt <jo...@googlemail.com>:
> Hi,
>
> I tried to get an overview about the current state in an installed office
> and the process of generating localized LICENSE files, README and how the
> THIRSPARTYLICENSEREADME.html comes into the game...
>
> Current situation on a
>
> MacOS system
> ============
> OpenOffice.org.app/Content/LICENSE
> OpenOffice.org.app/Content/LICENSE.hmtl
> OpenOffice.org.app/Content/README
> OpenOffice.org.app/Content/README.html
> OpenOffice.org.app/Content/basis-link/THIRDPARTYLICENSEREADME.html
>
> Window system
> =============
> .../OpenOffice.org 3/license.html
> .../OpenOffice.org 3/license.txt
> .../OpenOffice.org 3/readme.html
> .../OpenOffice.org 3/readme.txt
> .../OpenOffice.org 3/readmes/readme_en-US.html
> .../OpenOffice.org 3/readmes/readme_en-US.txt
> .../OpenOffice.org 3/THIRDPARTYLICENSEREADME.html
>
> readme files are always the same, readme.[txt|html] = readme.[txt|html]
>
> Linux System
> ============
> /org/openoffice.org/LICENSE
> /org/openoffice.org/LICENSE.hmtl
> /org/openoffice.org/README
> /org/openoffice.org/README.html
> /org/openoffice.org/THIRDPARTYLICENSEREADME.html
>
>
> The input for these files comes from the main/readlicense_oo module
>
> LICENSE
> readlicense_oo/source/license/license_en-US.html
> readlicense_oo/source/license/license_en-US.txt
> readlicense_oo/source/license/license_en-US.rtf
>
> README
> readlicense_oo/docs/readme/readme.xrm
>
> the "plattform" specific README will be generated out of the readme.xrm file
> . Well don't ask why it is done this way. It looks quite complicate ...
>
> THIRDPARTYLICENSEREADME
> readlicense_oo/html/THIRDPARTYLICENSEREADME.html
>
>
> I can't really find any information on [1] if we need localized versions of
> the LICENSE, NOTICE, README files.
>
We're not required to translate these files and I'd advise against
doing this at least in the case of the LICENSE and NOTICE files. It
is impossible to translate a license without applying our own
interpretation of that license. That is like giving legal advice
then. We should not being doing that.
The README file is another story, and I'd be open to a different story there.
But how does README differ from the Release Notes? Do we currently
have both and translate both?
> The whole process in the office is a little bit more complex today and it
> raised some questions for me.
>
> 1. Do we want to keep localized versions of these files, or do we need them?
>
I'd keep the required legal files (LICENSE and NOTICE) in their
original form (English).
For README, we need to consider the audience. We will have source and
binary packages. For source packages, the README should be covering
build pre-reqs, build flags, how to submit patches, generally a
programmer-oriented README. For the binary package, the README is
admin and end-user oriented.
> 2. Should we simply create one README for all or one for each plattform and
> should check in this directly?
>
That could be fine.
> 3. is related to the existing LICENSE [2] file in our source main directory.
> In line 190 we have
> ###
> ...
> Copyright [yyyy] [name of copyright owner]
> ...
> ###
>
> How does it have to be for a release? I assume something like
> ###
> ...
> Copyright 2011 Apache Software Foundation
> ...
> ###
>
I don't think we change line 190. That is instructions for someone
who wants to add ALv2 to their own code.
> 4. THIRDPARTYLICENSEREADME.hmtl has to be merged into NOTICE (or already
> had)
>
Most of THIRDPARTYLICENSEREADME will go into LICENSE. That is where
we aggregate the licenses for all of the code that we include in the
release. Since we're including additional libraries in the binary
package that are not included in the source package, this probably
means that we will have two different LICENSE and NOTICE files that we
will need to rename and package at build time, depending on whether we
are building a binary package or a source package.
NOTICE is for any required notice that the 3rd party license requires
us to make. It does not include the full text of the license. For
example, a license might require that we include a link to where
someone can download the source code of the component. We'd put that
in NOTICE. And the Oracle copyright that Andrew is removing from
source files, that would move into NOTICE as well.
-Rob
>
> Juergen
>
> [1]: incubator.apache.org/guides/releasemanagement.html
> [2]:
> http://svn.apache.org/viewvc/incubator/ooo/trunk/main/LICENSE?view=markup
>
Re: R: NOTICE, LICENSE, README etc.
Posted by Dave Fisher <da...@comcast.net>.
On Jan 9, 2012, at 8:40 AM, Jürgen Schmidt wrote:
> On 1/9/12 5:26 PM, Pedro Giffuni wrote:
>> Hi Jurgen;
>>
>> --- Lun 9/1/12, Jürgen Schmidt<jo...@googlemail.com> ha scritto:
>>
>>> Hi,
>>>
>>> I tried to get an overview about the current state in an
>>> installed office and the process of generating localized
>>> LICENSE files, README and how the
>>> THIRSPARTYLICENSEREADME.html comes into the game...
>>>
>>> Current situation on a
>>>
>>> MacOS system
>>> ============
>>> OpenOffice.org.app/Content/LICENSE
>>> OpenOffice.org.app/Content/LICENSE.hmtl
>>> OpenOffice.org.app/Content/README
>>> OpenOffice.org.app/Content/README.html
>>> OpenOffice.org.app/Content/basis-link/THIRDPARTYLICENSEREADME.html
>>>
>>> Window system
>>> =============
>>> .../OpenOffice.org 3/license.html
>>> .../OpenOffice.org 3/license.txt
>>> .../OpenOffice.org 3/readme.html
>>> .../OpenOffice.org 3/readme.txt
>>> .../OpenOffice.org 3/readmes/readme_en-US.html
>>> .../OpenOffice.org 3/readmes/readme_en-US.txt
>>> .../OpenOffice.org 3/THIRDPARTYLICENSEREADME.html
>>>
>>> readme files are always the same, readme.[txt|html] =
>>> readme.[txt|html]
>>>
>>> Linux System
>>> ============
>>> /org/openoffice.org/LICENSE
>>> /org/openoffice.org/LICENSE.hmtl
>>> /org/openoffice.org/README
>>> /org/openoffice.org/README.html
>>> /org/openoffice.org/THIRDPARTYLICENSEREADME.html
>>>
>>>
>>> The input for these files comes from the
>>> main/readlicense_oo module
>>>
>>> LICENSE
>>> readlicense_oo/source/license/license_en-US.html
>>> readlicense_oo/source/license/license_en-US.txt
>>> readlicense_oo/source/license/license_en-US.rtf
>>>
>>> README
>>> readlicense_oo/docs/readme/readme.xrm
>>>
>>> the "plattform" specific README will be generated out of
>>> the readme.xrm file . Well don't ask why it is done this
>>> way. It looks quite complicate ...
>>>
>>> THIRDPARTYLICENSEREADME
>>> readlicense_oo/html/THIRDPARTYLICENSEREADME.html
>>>
>>>
>>> I can't really find any information on [1] if we need
>>> localized versions of the LICENSE, NOTICE, README files.
>>>
>>
>> While this can be done, the English version
>> of the LICENSE must always be available.
>>
>> http://www.apache.org/foundation/license-faq.html#Translation
> ok
>
> In case of a multilingual build (e.g en-US, de) I have both LICENSE and README files. I have to check if i have for example de only.
>
> But anyway we would need a translation of the LICENSE.
Please see this FAQ. [1] The English language version must always be included - it is the authoritative version.
Regards,
Dave
[1] http://www.apache.org/foundation/license-faq.html#Translation
>
>>
>>>
>>> 4. THIRDPARTYLICENSEREADME.hmtl has to be merged into
>>> NOTICE (or already had)
>>>
>>
>> I did some partial merges and I stripped the GPL'd stuff
>> from the THIRDPARTYLICENSEREADME.hmtl, but I it was meant
>> only for reference and I was not strict enough: there is
>> surely some stuff (Bitstream Vera fonts and Xalan at least)
>> that we don't use. Would it be difficult to rename that file
>> NOTICE.html and scratch it into the exact NOTICE file in html
>> format?
> not sure if understand you correct. You mean renaming THIRDPARTYLICENSEREADME.hmtl to NOTICE.html and use the same content (in html notation) as in the current NOTICE file?
>
> Well renaming is probably no problem. Or we can use the NOTICE file as it is directly. I can see no problem here right now but maybe I have overseen something.
>
> Juergen
>
>>
>> cheers,
>>
>> Pedro.
>>
>
Re: NOTICE, LICENSE, README etc.
Posted by Raphael Bircher <rb...@bluewin.ch>.
Am 09.01.12 19:50, schrieb Pedro Giffuni:
> --- Lun 9/1/12, Jürgen Schmidt<jo...@googlemail.com> ha scritto:
> ...
>> why both, a html and txt version. I would use the NOTICE
>> file instead of the THIRDPARTYLICENSEREADME.html only.
> For now it's probably easier to keep some .html version of
> the NOTICE before we find ugly surprises but feel free to
> just get rid of it. TBH, I have no idea why we have the
> license_us in .txt, .html and .rtf versions.
I beleve that is samething p pre historic from take over from Star
Office x.x. In same case OOo have had a "Change syndrom" No one like to
use the delete key ;-)
I'm for one file .html
Re: NOTICE, LICENSE, README etc.
Posted by Pedro Giffuni <pf...@apache.org>.
--- Lun 9/1/12, Jürgen Schmidt <jo...@googlemail.com> ha scritto:
...
> why both, a html and txt version. I would use the NOTICE
> file instead of the THIRDPARTYLICENSEREADME.html only.
For now it's probably easier to keep some .html version of
the NOTICE before we find ugly surprises but feel free to
just get rid of it. TBH, I have no idea why we have the
license_us in .txt, .html and .rtf versions.
cheers,
Pedro.
Re: NOTICE, LICENSE, README etc.
Posted by Jürgen Schmidt <jo...@googlemail.com>.
On 1/9/12 5:48 PM, Pedro Giffuni wrote:
>
>
> --- Lun 9/1/12, Jürgen Schmidt<jo...@googlemail.com> ha scritto:
> ...
>
>> not sure if understand you correct. You mean renaming
>> THIRDPARTYLICENSEREADME.hmtl to NOTICE.html and use the
>> same content (in html notation) as in the current NOTICE
>> file?
>
> Yes, just to be consistent with the Apache way: We don't
> need to reproduce complete license in the NOTICE file and
> if we can just generate the txt file from the html file
> we will keep it all in sync without much effort.
>
why both, a html and txt version. I would use the NOTICE file instead of
the THIRDPARTYLICENSEREADME.html only. Well we have to ensure that the
content is correct and complete. Any volunteers doing the check?
Juergen
>>
>> Well renaming is probably no problem. Or we can use the
>> NOTICE file as it is directly. I can see no problem here
>> right now but maybe I have overseen something.
>>
>
> Yes. FWIW, Opengrok found 13 occurences of THIRDPARTYLICENSEREADME.hmtl
>
> (but I removed it from the license_us* already)
>
> cheers,
>
> Pedro.
>
Re: NOTICE, LICENSE, README etc.
Posted by Pedro Giffuni <pf...@apache.org>.
--- Lun 9/1/12, Jürgen Schmidt <jo...@googlemail.com> ha scritto:
...
> not sure if understand you correct. You mean renaming
> THIRDPARTYLICENSEREADME.hmtl to NOTICE.html and use the
> same content (in html notation) as in the current NOTICE
> file?
Yes, just to be consistent with the Apache way: We don't
need to reproduce complete license in the NOTICE file and
if we can just generate the txt file from the html file
we will keep it all in sync without much effort.
>
> Well renaming is probably no problem. Or we can use the
> NOTICE file as it is directly. I can see no problem here
> right now but maybe I have overseen something.
>
Yes. FWIW, Opengrok found 13 occurences of THIRDPARTYLICENSEREADME.hmtl
(but I removed it from the license_us* already)
cheers,
Pedro.
Re: R: NOTICE, LICENSE, README etc.
Posted by Jürgen Schmidt <jo...@googlemail.com>.
On 1/9/12 5:26 PM, Pedro Giffuni wrote:
> Hi Jurgen;
>
> --- Lun 9/1/12, Jürgen Schmidt<jo...@googlemail.com> ha scritto:
>
>> Hi,
>>
>> I tried to get an overview about the current state in an
>> installed office and the process of generating localized
>> LICENSE files, README and how the
>> THIRSPARTYLICENSEREADME.html comes into the game...
>>
>> Current situation on a
>>
>> MacOS system
>> ============
>> OpenOffice.org.app/Content/LICENSE
>> OpenOffice.org.app/Content/LICENSE.hmtl
>> OpenOffice.org.app/Content/README
>> OpenOffice.org.app/Content/README.html
>> OpenOffice.org.app/Content/basis-link/THIRDPARTYLICENSEREADME.html
>>
>> Window system
>> =============
>> .../OpenOffice.org 3/license.html
>> .../OpenOffice.org 3/license.txt
>> .../OpenOffice.org 3/readme.html
>> .../OpenOffice.org 3/readme.txt
>> .../OpenOffice.org 3/readmes/readme_en-US.html
>> .../OpenOffice.org 3/readmes/readme_en-US.txt
>> .../OpenOffice.org 3/THIRDPARTYLICENSEREADME.html
>>
>> readme files are always the same, readme.[txt|html] =
>> readme.[txt|html]
>>
>> Linux System
>> ============
>> /org/openoffice.org/LICENSE
>> /org/openoffice.org/LICENSE.hmtl
>> /org/openoffice.org/README
>> /org/openoffice.org/README.html
>> /org/openoffice.org/THIRDPARTYLICENSEREADME.html
>>
>>
>> The input for these files comes from the
>> main/readlicense_oo module
>>
>> LICENSE
>> readlicense_oo/source/license/license_en-US.html
>> readlicense_oo/source/license/license_en-US.txt
>> readlicense_oo/source/license/license_en-US.rtf
>>
>> README
>> readlicense_oo/docs/readme/readme.xrm
>>
>> the "plattform" specific README will be generated out of
>> the readme.xrm file . Well don't ask why it is done this
>> way. It looks quite complicate ...
>>
>> THIRDPARTYLICENSEREADME
>> readlicense_oo/html/THIRDPARTYLICENSEREADME.html
>>
>>
>> I can't really find any information on [1] if we need
>> localized versions of the LICENSE, NOTICE, README files.
>>
>
> While this can be done, the English version
> of the LICENSE must always be available.
>
> http://www.apache.org/foundation/license-faq.html#Translation
ok
In case of a multilingual build (e.g en-US, de) I have both LICENSE and
README files. I have to check if i have for example de only.
But anyway we would need a translation of the LICENSE.
>
>>
>> 4. THIRDPARTYLICENSEREADME.hmtl has to be merged into
>> NOTICE (or already had)
>>
>
> I did some partial merges and I stripped the GPL'd stuff
> from the THIRDPARTYLICENSEREADME.hmtl, but I it was meant
> only for reference and I was not strict enough: there is
> surely some stuff (Bitstream Vera fonts and Xalan at least)
> that we don't use. Would it be difficult to rename that file
> NOTICE.html and scratch it into the exact NOTICE file in html
> format?
not sure if understand you correct. You mean renaming
THIRDPARTYLICENSEREADME.hmtl to NOTICE.html and use the same content (in
html notation) as in the current NOTICE file?
Well renaming is probably no problem. Or we can use the NOTICE file as
it is directly. I can see no problem here right now but maybe I have
overseen something.
Juergen
>
> cheers,
>
> Pedro.
>
R: NOTICE, LICENSE, README etc.
Posted by Pedro Giffuni <pf...@apache.org>.
Hi Jurgen;
--- Lun 9/1/12, Jürgen Schmidt <jo...@googlemail.com> ha scritto:
> Hi,
>
> I tried to get an overview about the current state in an
> installed office and the process of generating localized
> LICENSE files, README and how the
> THIRSPARTYLICENSEREADME.html comes into the game...
>
> Current situation on a
>
> MacOS system
> ============
> OpenOffice.org.app/Content/LICENSE
> OpenOffice.org.app/Content/LICENSE.hmtl
> OpenOffice.org.app/Content/README
> OpenOffice.org.app/Content/README.html
> OpenOffice.org.app/Content/basis-link/THIRDPARTYLICENSEREADME.html
>
> Window system
> =============
> .../OpenOffice.org 3/license.html
> .../OpenOffice.org 3/license.txt
> .../OpenOffice.org 3/readme.html
> .../OpenOffice.org 3/readme.txt
> .../OpenOffice.org 3/readmes/readme_en-US.html
> .../OpenOffice.org 3/readmes/readme_en-US.txt
> .../OpenOffice.org 3/THIRDPARTYLICENSEREADME.html
>
> readme files are always the same, readme.[txt|html] =
> readme.[txt|html]
>
> Linux System
> ============
> /org/openoffice.org/LICENSE
> /org/openoffice.org/LICENSE.hmtl
> /org/openoffice.org/README
> /org/openoffice.org/README.html
> /org/openoffice.org/THIRDPARTYLICENSEREADME.html
>
>
> The input for these files comes from the
> main/readlicense_oo module
>
> LICENSE
> readlicense_oo/source/license/license_en-US.html
> readlicense_oo/source/license/license_en-US.txt
> readlicense_oo/source/license/license_en-US.rtf
>
> README
> readlicense_oo/docs/readme/readme.xrm
>
> the "plattform" specific README will be generated out of
> the readme.xrm file . Well don't ask why it is done this
> way. It looks quite complicate ...
>
> THIRDPARTYLICENSEREADME
> readlicense_oo/html/THIRDPARTYLICENSEREADME.html
>
>
> I can't really find any information on [1] if we need
> localized versions of the LICENSE, NOTICE, README files.
>
While this can be done, the English version
of the LICENSE must always be available.
http://www.apache.org/foundation/license-faq.html#Translation
>
> 4. THIRDPARTYLICENSEREADME.hmtl has to be merged into
> NOTICE (or already had)
>
I did some partial merges and I stripped the GPL'd stuff
from the THIRDPARTYLICENSEREADME.hmtl, but I it was meant
only for reference and I was not strict enough: there is
surely some stuff (Bitstream Vera fonts and Xalan at least)
that we don't use. Would it be difficult to rename that file
NOTICE.html and scratch it into the exact NOTICE file in html
format?
cheers,
Pedro.