Licensing questions

[di...@multitask.com.au]

For each ASF jar file distributed, we need to distribute the 
license/copyright and conditions from the source of that jar.

e.g. for ant, we need ants LICENSE, for jelly Jelly's license.

Until ASL v2, when all the licenses become the same text, I understand 
that we need a license for each binary distribution of ASF code. Is this 
correct?
--
dIon Gillard, Multitask Consulting
Blog:      http://www.freeroller.net/page/dion/Weblog
Work:      http://www.multitask.com.au


Sam Ruby <ru...@apache.org> wrote on 06/02/2003 03:53:47 AM:

> Rodent of Unusual Size wrote:
> > 
> >>Roy T. Fielding wrote:
> >>
> >>>In short, the answer is no, and this applies to any software with
> >>>copyright of The Apache Software Foundation. 
> >>
> >>which brings up a very good point that may have been overlooked:
> >>this applies to anything on ibiblio or elsewhere that is copyright
> >>the asf.  it does not apply strictly to the repositories on the asf
> >>machines, but to the asf *code*.
> 
> This issue has come up before.  This time, let's flatten it.
> 
> In two weeks, there is a board meeting.  At that time, I would like to
> be able to report that the contents of the Maven repository conforms to
> the policies of the Apache Software Foundation.
> 
> Code under the ASF License is clearly OK.  As is the IBM Public License
> (the pre-Jakarta BSF, for example) and the MPL (Rhino).  The following
> public domain components are also approved: Antlr and Doug Lea's
> concurrency package.
> 
> Licenses clearly not conforming to the ASF's policies for distribution:
> LGPL, GPL, Sun's Binary Code License.
> 
> Please direct any questions or comments (including new licenses to be
> considered) to general@jakarta.apache.org.  Some we can resolve for
> ourselves (e.g., the specific public domain packages above).  Others
> I'll batch up and forward to the board and/or licensing folk.
> 
> By the board meeting after that (3rd week in March), I'd like to have
> the infrastructure issues resolved (where should this data should be
> hosted, mirrored, etc).
> 
> - Sam Ruby
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-maven-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: 
turbine-maven-dev-help@jakarta.apache.org
> 

> ForwardSourceID:NT000AD6BE 

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

Re: Licensing questions

[Sam Ruby <ru...@apache.org>]

dion@multitask.com.au wrote:
> For each ASF jar file distributed, we need to distribute the 
> license/copyright and conditions from the source of that jar.
> 
> e.g. for ant, we need ants LICENSE, for jelly Jelly's license.
> 
> Until ASL v2, when all the licenses become the same text, I understand 
> that we need a license for each binary distribution of ASF code. Is this 
> correct?

Let me generalize this a bit and then state a personal recommendation - 
i.e., not an official statement of ASF policy, but how I would apply 
common sense in this situation.

Independent of whether an artifact is source or binary, independent of 
whether such an artifact is ASF Licensed or not, we need to make it 
relatively easily apparent as to what license applies to everything.

This includes public domain, Mozilla Public License, Sun Public License 
jars, ... everything.

When things are organized like the maven repository on ibiblio is, I 
would recommend one license per directory.  Ant, for example, has 
multiple jars but it would be clear enough to me that each were covered 
under the ASF license.

Even before ASF Sofware License v2, in my mind it would simplify things 
if we were to consolidate and standardize our licenses.  However, for 
various reasons (impending v2, more serious license issues, desire to do 
some thing other than purely licensing related on occasion <grin>), this 
is not my personal top priority at this time.

-Sam Ruby


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