commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From John Keyes <j...@integralsource.com>
Subject Re: [all] ALv2
Date Thu, 19 Feb 2004 10:36:06 GMT
Using the '.txt' extension is acceptable.  I broached the subject
with Roy T. Fielding (co-author of the apply-license document)
and he clarified the position.

-John K

On 18 Feb 2004, at 09:22, Henri Yandell wrote:

>
> bear in mind the maven system is looking for LICENSE.txt I believe, so
> it'll need changing to see LICENSE instead. Hopefully not work.
>
> We also ought to have the NOTICE.txt be included in it somehow, 
> possibly
> through some custom maven.xml'ing on the license report.
>
> Hen
>
> On Wed, 18 Feb 2004, John Keyes wrote:
>
>> I've just read
>>    http://www.apache.org/dev/apply-license.html
>>
>> [1] LICENSE
>>      To apply the ALv2 to a new software distribution, include one 
>> copy
>>      of the license text by copying the file:
>>
>>      http://www.apache.org/licenses/LICENSE-2.0.txt
>>
>>      into a file called LICENSE in the top directory of your
>>      distribution.  If the distribution is a jar or tar file, try to
>>      add the LICENSE file first in order to place it at the top of
>>      the archive.
>>
>> We currently use the filename LICENSE.txt, to follow the steps
>> suggested in the guide we should drop the txt extension.
>>
>> [2] NOTICE
>>      In addition, a NOTICE file should be included in the same
>>      directory as the LICENSE file. The NOTICE should include only
>>      those attribution notices that are required by any part of the
>>      entire distribution. For Apache projects and those redistributing
>>      ASF software, the NOTICE file must contain the sentence:
>>
>>        This product includes software developed by
>>        The Apache Software Foundation (http://www.apache.org/).
>>
>> All projects using ALv2 should also include a NOTICE file.
>>
>> Both LICENSE and NOTICE files MUST be included in the distributions.
>>
>> [3] Documentation and Source
>>
>>    The license is applied to each source file (code and documentation,
>>    but excluding the LICENSE and NOTICE files) by including a short
>>    copyright notice at the top, as demonstrated by the boilerplate 
>> notice
>>    provided in the appendix.
>>
>> I haven't licensed documentation previously so this was a wake up
>> call for me.  This should probably be raised with the maven xdoc
>> people as the generated HTML will not include the license (you
>> could argue that the .class files don't include the license
>> comment either).
>>
>> [4] Jakarta-Commons LICENSE
>>
>> The jakarta-commons dir contains two files with very similar contents,
>> LICENSE and LICENSE.txt.  Following the guidelines above LICENSE 
>> should
>> remain.
>>
>> Comments?
>>
>> -John K
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message