You are viewing a plain text version of this content. The canonical link for it is here.
Posted to community@apache.org by Rich Bowen <rb...@rcbowen.com> on 2003/03/02 16:50:13 UTC

Re: Updating source files to have full ASF license

On Thu, 27 Feb 2003, Noel J. Bergman wrote:

> Just in case it would be of help to any other project(s), here is a link to
> a message I posted earlier tonight to james-dev@.  The message mentions the
> automated process by which I updated every Java file in James to have the
> full ASF License instead of a short form of the license that had previously
> referred to the full license contained in the package.
>
> The sed script attached to that message might be of some use, although it
> would need minor text changes depending upon the target project.

I have often thought it would be very very nice if the source files
could reference the license, and tell you where to get it, rather than
including the full text. This hugely increases the size of everything,
and provides no real benefit. If each file could reference a file
(included in the distribution) and a URL, surely that would be
sufficient? What is the rationale for the full text in each and every
file?

-- 
Rich Bowen - rbowen@rcbowen.com
Author - Apache Administrator's Guide
http://www.ApacheAdmin.com/

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


Re: Updating source files to have full ASF license

Posted by Erik Abele <er...@codefaktor.de>.
As far as I understand it, the license itself isn't compatible to be 
referenced from another file. It's quite 'direct' and always relates to 
the document it is in. IANAL but I think we would need another phrase in 
the license wich states something like the following:

"This license applies to any original work of authorship
(the "Original Work") whose owner (the "Licensor") has placed the 
following notice immediately following the copyright notice for the 
Original Work:

Licensed under the Apache Software License, Version 2.0"

Then, I think, it would be possible to reference the license via 
something like:

"Copyright (c) 2003 The Apache Software Foundation.  All rights
reserved. Licensed under the Apache Software License, Version 2.0"

But as said before, I'm definitely not a lawyer, so that's just my view 
of the things :) AFAICR, this possibility was planned for the 2.0 
version of the ASF license.

cheers,
Erik


Rich Bowen wrote:
> On Thu, 27 Feb 2003, Noel J. Bergman wrote:
> 
> 
>>Just in case it would be of help to any other project(s), here is a link to
>>a message I posted earlier tonight to james-dev@.  The message mentions the
>>automated process by which I updated every Java file in James to have the
>>full ASF License instead of a short form of the license that had previously
>>referred to the full license contained in the package.
>>
>>The sed script attached to that message might be of some use, although it
>>would need minor text changes depending upon the target project.
> 
> 
> I have often thought it would be very very nice if the source files
> could reference the license, and tell you where to get it, rather than
> including the full text. This hugely increases the size of everything,
> and provides no real benefit. If each file could reference a file
> (included in the distribution) and a URL, surely that would be
> sufficient? What is the rationale for the full text in each and every
> file?
> 


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


Re: Updating source files to have full ASF license

Posted by Joerg Pietschmann <pi...@apache.org>.
Rich Bowen wrote:
> Just for the record, my quick unscientific poll shows that the license
> consumes approximately 6.7M in the httpd-2.0 distribution. But I suspect
> that compresses well! ;-)

It does compress lousy for ZIP files, somewhat better for .tar.gz,
especially if the files are short enough, and reasonably good
for a .tar.bz2 file, which has by default a 1MB window.

If your distribution has lots of relatively short files, consisting
to >20% of the license, sorting files by size in the tar should
produce a noticably smaller distro after gzip compression. Bzip2
will still be hard to beat.
Anybody interested in discussing compression methods for source
distributions? :-)

J.Pietschmann


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


Re: Updating source files to have full ASF license

Posted by Erik Abele <er...@apache.org>.
Rich Bowen wrote:
> On Mon, 3 Mar 2003, Erik Abele wrote:
 >>
 >>so we get 808,9kb for the source files plus the license
 >>(22998/1024=22,5kb) itself: ~ 831,4kb
>>
>>hehe, really cute compared to 6,7M :->
> 
> That's not nearly as fun!
> 

Anyway, 831kb are also way to much for just the license text, but 6,7mb 
would be totally *overkill* (the whole source tree (HEAD) is 16,4mb and 
the 2.0.44 release 22,5mb (uncompressed .tar.gz)).

Bah, a third! Just couldn't believe it :)

cheers,
Erik


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


Re: Updating source files to have full ASF license

Posted by Rich Bowen <rb...@rcbowen.com>.
On Mon, 3 Mar 2003, Erik Abele wrote:

> Huh, are you sure?
>
> wget apache.org/LICENSE
> 100%[====================================>] 2,827
>
> ll
> -rw-rw-r--    1 erik     erik         2827 Sep 22  2001 LICENSE
>
> 2827 bytes * 293 files = 828311 bytes / 1024 = 808,9kb !
>
> The 22kb LICENSE you mentioned is the full-blown text (located at
> httpd-2.0/LICENSE) which includes all subcomponents' licenses but the
> source files only include the *Apache Software License* not that of the
> other comps...
>
> so we get 808,9kb for the source files plus the license
> (22998/1024=22,5kb) itself: ~ 831,4kb
>
> hehe, really cute compared to 6,7M :->

That's not nearly as fun!

-- 
Rich Bowen - rbowen@rcbowen.com
ReefKnot - http://www.reefknot.org

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


Re: Updating source files to have full ASF license

Posted by Erik Abele <er...@apache.org>.
Rich Bowen wrote:
> On Sun, 2 Mar 2003, Rich Bowen wrote:
> 
>>I have often thought it would be very very nice if the source files
>>could reference the license, and tell you where to get it, rather than
>>including the full text. This hugely increases the size of everything,
>>and provides no real benefit. If each file could reference a file
>>(included in the distribution) and a URL, surely that would be
>>sufficient? What is the rationale for the full text in each and every
>>file?
> 
> Just for the record, my quick unscientific poll shows that the license
> consumes approximately 6.7M in the httpd-2.0 distribution. But I suspect
> that compresses well! ;-)
> 
> Scientific method: LICENSE is 22998 bytes. The text of the license
> appears in 293 files, including the LICENSE file itself.
> 

Huh, are you sure?

wget apache.org/LICENSE
100%[====================================>] 2,827

ll
-rw-rw-r--    1 erik     erik         2827 Sep 22  2001 LICENSE

2827 bytes * 293 files = 828311 bytes / 1024 = 808,9kb !

The 22kb LICENSE you mentioned is the full-blown text (located at 
httpd-2.0/LICENSE) which includes all subcomponents' licenses but the 
source files only include the *Apache Software License* not that of the 
other comps...

so we get 808,9kb for the source files plus the license 
(22998/1024=22,5kb) itself: ~ 831,4kb

hehe, really cute compared to 6,7M :->

cheers,
Erik


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


Re: Updating source files to have full ASF license

Posted by Dirk-Willem van Gulik <di...@webweaving.org>.

> Just for the record, my quick unscientific poll shows that the license
> consumes approximately 6.7M in the httpd-2.0 distribution. But I suspect
> that compresses well! ;-)

Try - last time I did this it accounted for a 0.8% increase in file size
of the distribution (I think that was xerces-c++).

Dw.


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


Re: Updating source files to have full ASF license

Posted by Rich Bowen <rb...@rcbowen.com>.
On Sun, 2 Mar 2003, Rich Bowen wrote:

> I have often thought it would be very very nice if the source files
> could reference the license, and tell you where to get it, rather than
> including the full text. This hugely increases the size of everything,
> and provides no real benefit. If each file could reference a file
> (included in the distribution) and a URL, surely that would be
> sufficient? What is the rationale for the full text in each and every
> file?

Just for the record, my quick unscientific poll shows that the license
consumes approximately 6.7M in the httpd-2.0 distribution. But I suspect
that compresses well! ;-)

Scientific method: LICENSE is 22998 bytes. The text of the license
appears in 293 files, including the LICENSE file itself.

-- 
Who can say where the road goes
Where the day flows
Only time
 --Pilgrim (Enya - A Day Without Rain)

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


Re: Updating source files to have full ASF license

Posted by Danny Angus <da...@apache.org>.
Ah, 
So if I'm right Roy's point is that if the current ASFL is not applicable by reference then the copyright in the refrence is the only relevant statement. It reserves all rights to the copyright holder (ASF), so code released like this may be argued to be not Open Source, and that only the ASF has the right to use it. Blimey, thats a turn up for the books then...

d.


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


RE: Updating source files to have full ASF license

Posted by "Noel J. Bergman" <no...@devtech.com>.
> i said that, and i was at least partly wrong.  see the attached
> message from roy.

Translation: I did the right thing for ASL v1.1, but only for policy
reasons?

	--- Noel


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


Re: Updating source files to have full ASF license

Posted by Rodent of Unusual Size <Ke...@Golux.Com>.
Noel J. Bergman wrote:
> Rich,
> 
>> What is the rationale for the full text in each and every file?
> 
> ASF Board directive, as it was told to me.  I wasn't privy to the decision
> making process, but I assume that a determination was made that:
> 
>  /* Copyright (C) The Apache Software Foundation. All rights reserved.
>   *
>   * This software is published under the terms of the Apache Software
>   * License version 1.1, a copy of which has been included with this
>   * distribution in the LICENSE file.
>   *
>   */
> 
> is not sufficient from a legal perspective.

i said that, and i was at least partly wrong.  see the attached
message from roy.
-- 
#ken	P-)}

Ken Coar, Sanagendamgagwedweinini  http://Golux.Com/coar/
Author, developer, opinionist      http://Apache-Server.Com/

"Millennium hand and shrimp!"

RE: Updating source files to have full ASF license

Posted by "Noel J. Bergman" <no...@devtech.com>.
Rich,

> What is the rationale for the full text in each and every file?

ASF Board directive, as it was told to me.  I wasn't privy to the decision
making process, but I assume that a determination was made that:

 /* Copyright (C) The Apache Software Foundation. All rights reserved.
  *
  * This software is published under the terms of the Apache Software
  * License version 1.1, a copy of which has been included with this
  * distribution in the LICENSE file.
  *
  */

is not sufficient from a legal perspective.

	--- Noel


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