You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by John Keyes <jo...@integralsource.com> on 2004/02/18 01:59:46 UTC
[all] ALv2
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
Re: [all] ALv2
Posted by Stephen Colebourne <sc...@btopenworld.com>.
I can never figure why a java programming list strips java attachments :-((
reattached by trick
Stephen
----- Original Message -----
From: "Stephen Colebourne" <sc...@btopenworld.com>
> [collections] and [convert] done.
>
> My Java program for assisting with this is attached. Requires CVS HEAD
[io]
> and manual hacking of paths.
>
> xdocs need editing by hand, I added LICENSE-INCLUDE2.txt at the top.
>
> Maybe worth someone checking basics of [collections], as its first commons
> proper one.
>
> Stephen
Re: [all] ALv2
Posted by Stephen Colebourne <sc...@btopenworld.com>.
[collections] and [convert] done.
My Java program for assisting with this is attached. Requires CVS HEAD [io]
and manual hacking of paths.
xdocs need editing by hand, I added LICENSE-INCLUDE2.txt at the top.
Maybe worth someone checking basics of [collections], as its first commons
proper one.
Stephen
Re: [all] ALv2
Posted by Stephen Colebourne <sc...@btopenworld.com>.
I've worked on the basis of
"If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must...."
and taken 'text file' as implying I can use a txt extension.
The pain will be getting the NOTICE into the jars etc.
Stephen
----- Original Message -----
From: "Simon Kitching" <si...@ecnetwork.co.nz>
> On Wed, 2004-02-18 at 13:59, John Keyes wrote:
> > We currently use the filename LICENSE.txt, to follow the steps
> > suggested in the guide we should drop the txt extension.
>
> > The jakarta-commons dir contains two files with very similar contents,
> > LICENSE and LICENSE.txt. Following the guidelines above LICENSE should
> > remain.
> >
> > Comments?
>
> It seems more sensible to me for the files to have a .txt extension.
> This doesn't harm unix/linux types and is much more friendly to
> microsoft users.
>
>
>
> ---------------------------------------------------------------------
> 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
Re: [all] ALv2
Posted by Simon Kitching <si...@ecnetwork.co.nz>.
On Wed, 2004-02-18 at 13:59, John Keyes wrote:
> We currently use the filename LICENSE.txt, to follow the steps
> suggested in the guide we should drop the txt extension.
> The jakarta-commons dir contains two files with very similar contents,
> LICENSE and LICENSE.txt. Following the guidelines above LICENSE should
> remain.
>
> Comments?
It seems more sensible to me for the files to have a .txt extension.
This doesn't harm unix/linux types and is much more friendly to
microsoft users.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [all] ALv2
Posted by John Keyes <jo...@integralsource.com>.
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
Re: [all] ALv2
Posted by Henri Yandell <ba...@generationjava.com>.
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