It is true that we've created no derivative Jetty or HSQLDB works. But the Apache License 4(d) section does not explicitly mention Jetty and HSQLDB as not requiring NOTICE text, and my understanding is that the license terms for those components require the text I have included in NOTICE. I am checking with Solr/Lucene to find out why they concluded they needed that text, but that may take a while. They too are not including this because they've created derivative works. My guess is that it has something to do with the following Apache policy:
# The remainder of the NOTICE file is to be used for required third-party notices. The NOTICE file may also include copyright notices moved from source files submitted to the ASF. Karl On Sat, Jan 8, 2011 at 6:36 AM, ant elder <antel...@apache.org> wrote: > That NOTICE file still contains additional text about Jetty and > HSQLDB, why is that needed? The Apache License section 4d describes > what must be included in the NOTICE and AIUI it says you only need to > include in your NOTICE the notices from Jetty and HSQLDB if you > distribute derivitave works of them. Thats not what you're doing you > are distributing copies of the them not Derivative Works so nothing is > needed in your NOTICE file. > > ...ant > > On Sat, Jan 8, 2011 at 11:05 AM, Karl Wright <daddy...@gmail.com> wrote: >> Rather than spin a whole new RC and upload it, which takes me two >> hours, I've attached the revised proposed NOTICE and LICENSE here, so >> people can comment directly. >> >> Karl >> >> On Sat, Jan 8, 2011 at 5:51 AM, Karl Wright <daddy...@gmail.com> wrote: >>> The current NOTICE file has exactly what you specify, plus a preamble >>> describing components and their licenses. I will remove the preamble >>> - it was based on the Solr/Lucene NOTICE which I was told to use as an >>> example. >>> >>> The LICENSE file, on the other hand, should currently have everything >>> that's in the NOTICE file in expanded form. If you think I should >>> move the preamble to the LICENSE file as well, this would be the time >>> to indicate that. Otherwise, the preamble will just be deleted. >>> >>> Karl >>> >>> >>> On Sat, Jan 8, 2011 at 5:06 AM, ant elder <ant.el...@gmail.com> wrote: >>>> On Fri, Jan 7, 2011 at 11:13 AM, Karl Wright <daddy...@gmail.com> wrote: >>>> >>>>> - I have made no changes to NOTICE and LICENSE, because the incubator >>>>> and community advice seemed contradictory. I would like a general >>>>> sense of how many people feel that the current NOTICE and LICENSE >>>>> files are unacceptable before I make changes. >>>> >>>> The NOTICE file is still incorrect and includes a lot of unnecessary >>>> stuff. Understanding how to do releases with the correct legal files >>>> is one of the important parts of incubation and as this is the first >>>> release for the poddling i think this needs to be sorted out. >>>> >>>> For the NOTICE file, start with the following text (between the ---'s): >>>> >>>> --- >>>> Apache ManifestCF >>>> Copyright 2010 The Apache Software Foundation >>>> >>>> This product includes software developed by >>>> The Apache Software Foundation (http://www.apache.org/). >>>> --- >>>> >>>> and then add _nothing_ unless you can find explicit policy documented >>>> somewhere in the ASF that says it is required. If someone wants to add >>>> something ask for the URL where the requirement is documented. The >>>> NOTICE file should only include required notices, the other text thats >>>> in the current NOTICE file could go in a README file, see >>>> http://www.apache.org/legal/src-headers.html#notice >>>> >>>> For the LICENSE file, it should start with the AL as the current one >>>> does, and then include the text for all the other licenses used in the >>>> distribution. Those license that are currently in the NOTICE file >>>> should be moved to the LICENSE file and then you need to verify that >>>> all the 3rd party dependencies in the src and binary distributions are >>>> also in the LICENSE files of those distributions. >>>> >>>> ...ant >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >>>> For additional commands, e-mail: general-h...@incubator.apache.org >>>> >>>> >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org