incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "J Aaron Farr" <>
Subject Re: Making a non ASF project, ASF friendly
Date Sun, 07 Jan 2007 00:27:20 GMT
On 1/7/07, Henri Yandell <> wrote:

> I don't agree. Any AL2 licensed work can be included in an ASF
> distribution, as a dependency. In terms of committing a piece of work
> that is not under our IP (and is not covered by a CLA), the Apache
> license doesn't make it a given. You would still need to submit a
> grant or be covered by a CLA, and you would have to be responsible for
> the IP of the work. (I think... :) ).

>From a purely licensing point of view (independent of the ASF) you can
take two AL2 works and combine them and get an AL2 licensable work as
a result without having to get anyone's permission.  We may not always
do this in the ASF but that's a result of policy not licensing.

If something is small enough to submit via JIRA and it's already AL2,
then I don't think it would be a problem.  Our JIRA process already
covers this anyway.

As a pure dependency, it's also not an issue.  Our third-party
licensing guidelines make this clear.

So is the only situation that I see as tricky is taking say a handful
of source code from and dropping it directly into the main
trunk of an ASF project.  This would be a fork but it wouldn't create
a licensing issue as long as the code were clearly identified and any
attached copyright statements maintained.

I can understand some could feel uneasy about the forked result, but
the only legal concern I can detect would be if someone doubted
whether the original work had been properly put under the AL2
in the first place.  If the original work were encumbered in some way,
then that could put the ASF fork in a bind.  So in the end it's a
question of if we trust the original work is what it says it is -- a
legally licensed AL2 work.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message