incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Karl Wright <daddy...@gmail.com>
Subject Re: [VOTE] Release Apache ManifoldCF 0.1
Date Sat, 08 Jan 2011 15:36:55 GMT
I've confirmed the following:

(1) The Jetty notice text I've included came from the source Jetty NOTICE file.
(2) The HSQLDB notice text I've included is NOT the same as the HSQLDB
license text, and very likely came from an HSQLDB NOTICE file also.

So, if I'm doing it wrong, at least I'm being consistent.  There is NO
license information in NOTICE.txt, as it stands now.

Karl

On Sat, Jan 8, 2011 at 10:24 AM, Karl Wright <daddywri@gmail.com> wrote:
> I've made the 2011 change already.  But I'm having trouble reconciling
>  your instructions with this part of the Apache license:
>
>>>>>>>
>      (d) If the Work includes a "NOTICE" text file as part of its
>          distribution, then any Derivative Works that You distribute must
>          include a readable copy of the attribution notices contained
>          within such NOTICE file, excluding those notices that do not
>          pertain to any part of the Derivative Works, in at least one
>          of the following places: within a NOTICE text file distributed
>          as part of the Derivative Works; within the Source form or
>          documentation, if provided along with the Derivative Works; or,
>          within a display generated by the Derivative Works, if and
>          wherever such third-party notices normally appear. The contents
>          of the NOTICE file are for informational purposes only and
>          do not modify the License. You may add Your own attribution
>          notices within Derivative Works that You distribute, alongside
>          or as an addendum to the NOTICE text from the Work, provided
>          that such additional attribution notices cannot be construed
>          as modifying the License.
> <<<<<<
>
> To the best of my knowledge, both remaining proposed NOTICE clauses
> come from a NOTICE file or the equivalent in the source work.  The
> meaning of "Derivative Work" is obviously what the question is - does
> inclusion imply derivation?  Because, we are including it.
>
> The short notices you are recommending I can certainly put back in,
> but that goes directly against ant elder's request that they be
> removed.  Indeed, it sounded to me like he thought there should be
> nothing in NOTICE.txt other than the header.
>
> Karl
>
>
> On Sat, Jan 8, 2011 at 9:51 AM, sebb <sebbaz@gmail.com> wrote:
>> Note: the NOTICE year will need to be changed for the next release to 2010-2011.
>> For the current release I think it can remain as is - there don't seem
>> to have been any substantive changes made in 2011.
>>
>> The leading blank lines need to be removed.
>>
>> Otherwise, I concur with what Ant has mentioned elsethread.
>> The NOTICE file needs to be as short as possible; think of it as an About box.
>>
>> Generally at most one or two lines are needed per product (as for ASF code)
>> So for any products that *require* a notice, the following should be enough:
>>
>> ===========
>> This product contains MegaCorp FOO
>> Copyright (c) 1995-2000 by the MegaCorp Universal Corporation
>> ===========
>>
>> The full details go in the LICENSE file.
>>
>> On 8 January 2011 11:05, Karl Wright <daddywri@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 <daddywri@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.elder@gmail.com> wrote:
>>>>> On Fri, Jan 7, 2011 at 11:13 AM, Karl Wright <daddywri@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-unsubscribe@incubator.apache.org
>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>
>>>>>
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Mime
View raw message