commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Simon Kitching <si...@ecnetwork.co.nz>
Subject Re: cvs commit: jakarta-commons/jelly NOTICE.txt
Date Mon, 01 Mar 2004 05:39:31 GMT
On Mon, 2004-03-01 at 18:35, dion@multitask.com.au wrote:
> yoavs@apache.org wrote on 29/02/2004 12:44:05 AM:
> 
> > yoavs       2004/02/28 05:44:05
> > 
> >   Added:       jelly    NOTICE.txt
> >   Log:
> >   Added NOTICE.txt per ASF directive,
> >   http://www.apache.org/dev/apply-license.html.
> > 
> >   Revision  Changes    Path
> >   1.1                  jakarta-commons/jelly/NOTICE.txt
> > 
> >   Index: NOTICE.txt
> >   ===================================================================
> >   This product includes software developed by
> >   The Apache Software Foundation (http://www.apache.org/).
> 
> I'm not sure that for ASF software this makes any sense. 
> 
> Of course our software includes software developed by us.
> 
> Can someone please explain why this is needed?

Because the new 2.0 license explicitly avoids mentioning which party is
granting the license. It's a totally generic open-source license, usable
by any project without changing a single word. The "apache" references
within the license just mean that the license was written by the Apache
legal team, and implies nothing about the license *being issued*.

Instead, the wording of the license refers to an associated "Notice"
file for details of who exactly the license is being issued by, and who
needs to be given credit, etc.


At least that's my understanding. IANAL and all that.

The apache licensing web pages are very explicit about a NOTICE file
having to be included with exactly the wording of Yoav's commit.

Regards,

Simon


---------------------------------------------------------------------
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