You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@harmony.apache.org by Tim Ellison <t....@gmail.com> on 2009/05/01 15:03:39 UTC
Re: [general] Notice and license files
We currently include a copy of LICENSE and NOTICE in every one of our
JARs, but we don't include the THIRD_PARTY_NOTICES.txt.
I've got a patch to combine the 3rd party notices file into the license
file, but it makes our boot JARs noticeably bigger.
I can't put my finger on the ASF policy, but I believe it *is* best
practice to include the license and notice in each jar.
The only alternative I can think of is to copy the LICENSE file into
each module, and only include each THIRD_PARTY_NOTICE section that
applies to that module.
WDYT? any other ideas?
( In the meantime I'll commit the changes I have got do that we are back
in compliance. )
Regards,
Tim
Tim Ellison wrote:
> As you know, we have a third party license file [1] that contains
> required licenses and attributions for Harmony's dependencies.
>
> We include this file in our distributions, but it is not conventional to
> have such a file in Apache downloads, they are normally included in the
> LICENSE or NOTICE or README files. I'd like to delete our file [1] and
> move the text into the 'standard' locations.
>
> As I read the wiki page [2] and discussion link, it seems that these
> licenses should be simply appended onto the end of the LICENSE file.
>
> These are the licenses in our third party license file:
>
> License Notice for ICU4C version 3.4
> License Notice for ICU4J version 4.0
> License Notice for FDLIBM version 5.2
> License Notice for ZLIB version 1.2.3
> Visual C++ Runtime Files
> License Notice for Bouncy Castle version 1.41
> License Notice for MX4J 3.0.2.
> Notice for The Independent JPEG Group's JPEG software
> Notice for Little CMS
> Notice for libpng
> Notice for Unicode Character Database
> Notice for IETF RFCs prior to 2005
> Notice for IETF RFCs from 2005 onwards
> Notice for RSA Public-Key Cryptography Standards
> Notice for the Eclipse JDT Core Batch Compiler
> Notice for Apache Yoko
> License notice for the DejaVu fonts package
> License notice for ASM
>
>
> [1]
> http://svn.apache.org/viewvc/harmony/enhanced/classlib/trunk/THIRD_PARTY_NOTICES.txt?view=markup
> [2] http://wiki.apache.org/legal/3party/notice
>
> Regards,
> Tim
>
Re: [general] Notice and license files
Posted by sebb <se...@gmail.com>.
On 07/05/2009, Tim Ellison <t....@gmail.com> wrote:
> Oliver Deakin wrote:
> > Perhaps it would make sense to break down the big
> > THIRD_PARTY_NOTICES.txt into a separate file for each notice. Then,
> > using some magic at build time, each module could only pull the notices
> > for the dependencies it actually uses into it's jar. This has a couple
> > of benefits - we only need to maintain 1 copy of each third party notice
> > at the top level and we also minimise the number of notices in each jar
> > file so they don't expand in size any more than they need to.
The phrase "number of notices" presumably means "number of entries in
the NOTICE file", as there should only be one NOTICE file in each jar.
> I think the expression is "thanks for volunteering" :-)
>
> Seriously though, I agree that optimizing the required license/notices
> for each JAR makes sense; but that's unlikely to make it to the top of
> my to-do list soon.
SVN is regarded as a distribution, so that must also have a NOTICE and
LICENSE file at the top level (i.e. trunk, each branch and tag) which
obviously needs to include all the 3rd party notices.
> Regards,
>
> Tim
>
>
Re: [general] Notice and license files
Posted by Tim Ellison <t....@gmail.com>.
Oliver Deakin wrote:
> Perhaps it would make sense to break down the big
> THIRD_PARTY_NOTICES.txt into a separate file for each notice. Then,
> using some magic at build time, each module could only pull the notices
> for the dependencies it actually uses into it's jar. This has a couple
> of benefits - we only need to maintain 1 copy of each third party notice
> at the top level and we also minimise the number of notices in each jar
> file so they don't expand in size any more than they need to.
I think the expression is "thanks for volunteering" :-)
Seriously though, I agree that optimizing the required license/notices
for each JAR makes sense; but that's unlikely to make it to the top of
my to-do list soon.
Regards,
Tim
Re: [general] Notice and license files
Posted by Oliver Deakin <ol...@googlemail.com>.
Hi Tim,
Perhaps it would make sense to break down the big
THIRD_PARTY_NOTICES.txt into a separate file for each notice. Then,
using some magic at build time, each module could only pull the notices
for the dependencies it actually uses into it's jar. This has a couple
of benefits - we only need to maintain 1 copy of each third party notice
at the top level and we also minimise the number of notices in each jar
file so they don't expand in size any more than they need to.
Regards,
Oliver
Tim Ellison wrote:
> We currently include a copy of LICENSE and NOTICE in every one of our
> JARs, but we don't include the THIRD_PARTY_NOTICES.txt.
>
> I've got a patch to combine the 3rd party notices file into the license
> file, but it makes our boot JARs noticeably bigger.
>
> I can't put my finger on the ASF policy, but I believe it *is* best
> practice to include the license and notice in each jar.
>
> The only alternative I can think of is to copy the LICENSE file into
> each module, and only include each THIRD_PARTY_NOTICE section that
> applies to that module.
>
> WDYT? any other ideas?
>
> ( In the meantime I'll commit the changes I have got do that we are back
> in compliance. )
>
> Regards,
> Tim
>
>
> Tim Ellison wrote:
>
>> As you know, we have a third party license file [1] that contains
>> required licenses and attributions for Harmony's dependencies.
>>
>> We include this file in our distributions, but it is not conventional to
>> have such a file in Apache downloads, they are normally included in the
>> LICENSE or NOTICE or README files. I'd like to delete our file [1] and
>> move the text into the 'standard' locations.
>>
>> As I read the wiki page [2] and discussion link, it seems that these
>> licenses should be simply appended onto the end of the LICENSE file.
>>
>> These are the licenses in our third party license file:
>>
>> License Notice for ICU4C version 3.4
>> License Notice for ICU4J version 4.0
>> License Notice for FDLIBM version 5.2
>> License Notice for ZLIB version 1.2.3
>> Visual C++ Runtime Files
>> License Notice for Bouncy Castle version 1.41
>> License Notice for MX4J 3.0.2.
>> Notice for The Independent JPEG Group's JPEG software
>> Notice for Little CMS
>> Notice for libpng
>> Notice for Unicode Character Database
>> Notice for IETF RFCs prior to 2005
>> Notice for IETF RFCs from 2005 onwards
>> Notice for RSA Public-Key Cryptography Standards
>> Notice for the Eclipse JDT Core Batch Compiler
>> Notice for Apache Yoko
>> License notice for the DejaVu fonts package
>> License notice for ASM
>>
>>
>> [1]
>> http://svn.apache.org/viewvc/harmony/enhanced/classlib/trunk/THIRD_PARTY_NOTICES.txt?view=markup
>> [2] http://wiki.apache.org/legal/3party/notice
>>
>> Regards,
>> Tim
>>
>>
>
>
--
Oliver Deakin
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU