You are viewing a plain text version of this content. The canonical link for it is here.
Posted to legal-discuss@apache.org by Martin Cooper <ma...@apache.org> on 2005/12/07 01:32:54 UTC
Re: AFL code in an ASF project
Anyone have any thoughts on this? Alternatively, if there isn't an easy
answer on the Academic Free License 2.1, is there an easy answer for
Modified BSD License? (The package in question has just dual-licensed under
AFL 2.1 & Modified BSD, since the latter is agreeable to the FSF.)
This subject is likely to come up in discussion at ApacheCon next week, so
it would be nice if we could know where we stand, ahead of time.
Thanks!
--
Martin Cooper
On 11/22/05, Martin Cooper <ma...@apache.org> wrote:
>
>
>
> On Tue, 22 Nov 2005, Lawrence Rosen wrote:
>
> > Do you mean "Academic Free License"? Which version?
>
> Whoops! Yes, I meant the Academic Free License. Sorry. Version 2.1.
>
> --
> Martin Cooper
>
>
> > /Larry
> >
> >
> >> -----Original Message-----
> >> From: Martin Cooper [mailto:martinc@apache.org]
> >> Sent: Tuesday, November 22, 2005 12:10 PM
> >> To: legal-discuss@apache.org
> >> Subject: AFL code in an ASF project
> >>
> >> A question came up about whether or not it would be OK to
> >> include a non-ASF project released under the Artistic Free
> >> License (AFL) as part of an ASF release. One of the
> >> differences I'm aware of between the two licenses is that the
> >> AFL provides a guarantee of provenance while the AL does not.
> >> What I don't understand is what effect this would have when
> >> an AFL project is embedded in an AL project.
> >>
> >> So, bottom line: Is it OK to include an AFL project as part
> >> of an ASF distributable (i.e. release)?
> >>
> >> TIA.
> >>
> >> --
> >> Martin Cooper
> >>
> >>
> >> ---------------------------------------------------------------------
> >> DISCLAIMER: Discussions on this list are informational and
> >> educational only. Statements made on this list are not
> >> privileged, do not constitute legal advice, and do not
> >> necessarily reflect the opinions and policies of the ASF.
> >> See <http://www.apache.org/licenses/> for official ASF
> >> policies and documents.
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
> >> For additional commands, e-mail: legal-discuss-help@apache.org
> >
> >
> > ---------------------------------------------------------------------
> > DISCLAIMER: Discussions on this list are informational and educational
> > only. Statements made on this list are not privileged, do not
> > constitute legal advice, and do not necessarily reflect the opinions
> > and policies of the ASF. See <http://www.apache.org/licenses/> for
> > official ASF policies and documents.
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
> > For additional commands, e-mail: legal-discuss-help@apache.org
> >
> >
>
> ---------------------------------------------------------------------
> DISCLAIMER: Discussions on this list are informational and educational
> only. Statements made on this list are not privileged, do not
> constitute legal advice, and do not necessarily reflect the opinions
> and policies of the ASF. See <http://www.apache.org/licenses/> for
> official ASF policies and documents.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
> For additional commands, e-mail: legal-discuss-help@apache.org
>
>
Re: AFL code in an ASF project
Posted by Henri Yandell <ba...@generationjava.com>.
Modified BSD License appears to be a name for BSD without the advertising
clause; ie) the BSD license that is commonly used by many projects. So no
problems with BSD licenses.
Can't say I understand dual licensing though :) Especially in the case of
a distributable. If Apache XXX depends on Dualie the Dual Licensed
Project, does Apache XXX's usage flatten the dual-license waveform into a
single license, ie) the one we can use, and mean that any user of Apache
XXX has to use Dualie as a BSD license and not as an AFL license. Or is it
something else :)
Going by hearsay, I thought AFL was okay if it was the right version, but
I'm not sure how you determine the right version.
Hen
On Tue, 6 Dec 2005, Martin Cooper wrote:
> Anyone have any thoughts on this? Alternatively, if there isn't an easy
> answer on the Academic Free License 2.1, is there an easy answer for
> Modified BSD License? (The package in question has just dual-licensed under
> AFL 2.1 & Modified BSD, since the latter is agreeable to the FSF.)
>
> This subject is likely to come up in discussion at ApacheCon next week, so
> it would be nice if we could know where we stand, ahead of time.
>
> Thanks!
>
> --
> Martin Cooper
>
>
> On 11/22/05, Martin Cooper <ma...@apache.org> wrote:
>>
>>
>>
>> On Tue, 22 Nov 2005, Lawrence Rosen wrote:
>>
>>> Do you mean "Academic Free License"? Which version?
>>
>> Whoops! Yes, I meant the Academic Free License. Sorry. Version 2.1.
>>
>> --
>> Martin Cooper
>>
>>
>>> /Larry
>>>
>>>
>>>> -----Original Message-----
>>>> From: Martin Cooper [mailto:martinc@apache.org]
>>>> Sent: Tuesday, November 22, 2005 12:10 PM
>>>> To: legal-discuss@apache.org
>>>> Subject: AFL code in an ASF project
>>>>
>>>> A question came up about whether or not it would be OK to
>>>> include a non-ASF project released under the Artistic Free
>>>> License (AFL) as part of an ASF release. One of the
>>>> differences I'm aware of between the two licenses is that the
>>>> AFL provides a guarantee of provenance while the AL does not.
>>>> What I don't understand is what effect this would have when
>>>> an AFL project is embedded in an AL project.
>>>>
>>>> So, bottom line: Is it OK to include an AFL project as part
>>>> of an ASF distributable (i.e. release)?
>>>>
>>>> TIA.
>>>>
>>>> --
>>>> Martin Cooper
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> DISCLAIMER: Discussions on this list are informational and
>>>> educational only. Statements made on this list are not
>>>> privileged, do not constitute legal advice, and do not
>>>> necessarily reflect the opinions and policies of the ASF.
>>>> See <http://www.apache.org/licenses/> for official ASF
>>>> policies and documents.
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
>>>> For additional commands, e-mail: legal-discuss-help@apache.org
>>>
>>>
>>> ---------------------------------------------------------------------
>>> DISCLAIMER: Discussions on this list are informational and educational
>>> only. Statements made on this list are not privileged, do not
>>> constitute legal advice, and do not necessarily reflect the opinions
>>> and policies of the ASF. See <http://www.apache.org/licenses/> for
>>> official ASF policies and documents.
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
>>> For additional commands, e-mail: legal-discuss-help@apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> DISCLAIMER: Discussions on this list are informational and educational
>> only. Statements made on this list are not privileged, do not
>> constitute legal advice, and do not necessarily reflect the opinions
>> and policies of the ASF. See <http://www.apache.org/licenses/> for
>> official ASF policies and documents.
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
>> For additional commands, e-mail: legal-discuss-help@apache.org
>>
>>
>
---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only. Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF. See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org