You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by Ross Gardler <rg...@apache.org> on 2004/11/24 18:57:29 UTC
License question
I am preparing the htmlArea plugin for committing to SVN (can be used to
edit the new WD Forrest 1.0 document :-))
I have a question about legal stuff:
It uses htmlArea, which is available under a BSD style license (fill
license text below). I assume that I cannot commit the source code to
SVN, so what I have done is zipped it up and created a build target for
use when installing plugins. In this case the target unzips the zip when
installing.
Note, I also have the license stored as a text file alongside the zip.
Is this sufficient to fulfill the legal needs of the ASF?
=== full text of license ===
htmlArea License (based on BSD license)
Copyright (c) 2002-2004, interactivetools.com, inc.
Copyright (c) 2003-2004 dynarch.com
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
1) Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.
2) Redistributions in binary form must reproduce the above copyright notice,
this list of conditions and the following disclaimer in the
documentation
and/or other materials provided with the distribution.
3) Neither the name of interactivetools.com, inc. nor the names of its
contributors may be used to endorse or promote products derived from
this
software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
Re: License question
Posted by David Crossley <cr...@apache.org>.
Ross Gardler wrote:
> David Crossley wrote:
>> Nicola Ken Barozzi wrote:
>>> David Crossley wrote:
>>>> Dave Brondsema wrote:
>>> ...
>>>
>>>>> * this ownership needs to be recognized in a NOTICE file
>>>>> * the license they use should accompany the .jar file in our
>>>>> repository
>>>>
>>>> My understanding is that an entry goes in the
>>>> NOTICE.txt only if their license specifically
>>>> resuests that such notice be made.
>>>
>>> IANAL, but I would put a thanks anyway, be it in CREDITS or NOTICE.
>>
>> However, their license specifically says that we
>> are not allowed to use their name without their
>> written permission.
>>
>> One sees other licenses where the licensor specifically
>> says that we *must* display the name in a prominent
>> location. Those are the only occasions that i have
>> added them to the NOTICE.txt file.
>
> I read that to mean we can't use it in a marketing sense. I have added
> them to the NOTICE.txt file should I remove it?
Why risk it? Some might look upon the NOTICE.txt file
as a place to advertise. My approach when i did the
massive license tidy-up and move to AL2, was to only
put entries in there when it was one of their license
conditions. If we change that approach, then we are
going to need to revisit all of the licenses.
If we change tack, then how are we going to distinguish
between a licensor that *demands* a notice and those
that demand *no use* of their name. Not worth the confusion,
i reckon.
One thing that we definitely need is some words of
clarification in the top of the NOTICE.txt file.
(P.S. Sorry about the time problem with my email
I am trying hard to fix the one-hour delay.)
--David
Re: License question
Posted by Ross Gardler <rg...@apache.org>.
David Crossley wrote:
> Nicola Ken Barozzi wrote:
>
>> David Crossley wrote:
>>
>>> Dave Brondsema wrote:
>>
>>
>> ...
>>
>>>> * this ownership needs to be recognized in a NOTICE file
>>>> * the license they use should accompany the .jar file in our repository
>>>
>>>
>>>
>>> My understanding is that an entry goes in the
>>> NOTICE.txt only if their license specifically
>>> resuests that such notice be made.
>>
>>
>> IANAL, but I would put a thanks anyway, be it in CREDITS or NOTICE.
>
>
> However, their license specifically says that we
> are not allowed to use their name without their
> written permission.
>
> One sees other licenses where the licensor specifically
> says that we *must* display the name in a prominent
> location. Those are the only occasions that i have
> added them to the NOTICE.txt file.
>
I read that to mean we can't use it in a marketing sense. I have added
them to the NOTICE.txt file should I remove it?
Ross
Re: License question
Posted by David Crossley <cr...@apache.org>.
Nicola Ken Barozzi wrote:
> David Crossley wrote:
>
>> Dave Brondsema wrote:
>
> ...
>
>>> * this ownership needs to be recognized in a NOTICE file
>>> * the license they use should accompany the .jar file in our repository
>>
>>
>> My understanding is that an entry goes in the
>> NOTICE.txt only if their license specifically
>> resuests that such notice be made.
>
> IANAL, but I would put a thanks anyway, be it in CREDITS or NOTICE.
However, their license specifically says that we
are not allowed to use their name without their
written permission.
One sees other licenses where the licensor specifically
says that we *must* display the name in a prominent
location. Those are the only occasions that i have
added them to the NOTICE.txt file.
--David
Re: License question
Posted by Nicola Ken Barozzi <ni...@apache.org>.
David Crossley wrote:
> Dave Brondsema wrote:
...
>> * this ownership needs to be recognized in a NOTICE file
>> * the license they use should accompany the .jar file in our repository
>
> My understanding is that an entry goes in the
> NOTICE.txt only if their license specifically
> resuests that such notice be made.
IANAL, but I would put a thanks anyway, be it in CREDITS or NOTICE.
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: License question
Posted by David Crossley <cr...@apache.org>.
Dave Brondsema wrote:
> Ross Gardler wrote:
>
>> I am preparing the htmlArea plugin for committing to SVN (can be used
>> to edit the new WD Forrest 1.0 document :-))
>>
>> I have a question about legal stuff:
>>
>> It uses htmlArea, which is available under a BSD style license (fill
>> license text below). I assume that I cannot commit the source code to
>> SVN, so what I have done is zipped it up and created a build target
>> for use when installing plugins. In this case the target unzips the
>> zip when installing.
>>
>> Note, I also have the license stored as a text file alongside the zip.
>>
>> Is this sufficient to fulfill the legal needs of the ASF?
>>
>
> The policy (AFAIK) with respect to using organization's Jar files is as
> follows:
>
> * we don't want to distribute anything that is not "compatible" with
> AL2. So we can include jar files that are owned by other people and
> under the AL2, BSD and MIT family, or public domain. LGPL does not
> qualify.
Yes. The key is that the license cannot impose
restrictions that go beyond the Apache License AL2.
BSD is fine.
> * this ownership needs to be recognized in a NOTICE file
> * the license they use should accompany the .jar file in our repository
My understanding is that an entry goes in the
NOTICE.txt only if their license specifically
resuests that such notice be made.
> I do not know how this applies to source code. Generally we only
> include source that has been explicitly contributed to the ASF.
We can ship it as source code if we want, as long as
we adhere to their license conditions.
On the first 'svn commit' please be very specific
which version of their library was used.
Apache Cocoon contains the source code of "htmlarea"
http://svn.apache.org/repos/asf/cocoon/trunk/src/blocks/forms/samples/resources/htmlarea/
They have the license.txt beside the htmlarea source code.
They also have a copy in the "legal" directory. There is
no entry in their NOTICE.txt or CREDITS.txt files.
> more help can be gotten from http://apache.org/dev/apply-license.html
> and licensing@a.o
It is good to ask specific questions there.
That will help to clarify the situations for everyone.
However, the primary responsibility is with our PMC
and we should be able to determine most cases.
If there is any doubt then ask licensing@a.o
--David
Re: License question
Posted by Dave Brondsema <da...@brondsema.net>.
Ross Gardler wrote:
> I am preparing the htmlArea plugin for committing to SVN (can be used to
> edit the new WD Forrest 1.0 document :-))
>
> I have a question about legal stuff:
>
> It uses htmlArea, which is available under a BSD style license (fill
> license text below). I assume that I cannot commit the source code to
> SVN, so what I have done is zipped it up and created a build target for
> use when installing plugins. In this case the target unzips the zip when
> installing.
>
> Note, I also have the license stored as a text file alongside the zip.
>
> Is this sufficient to fulfill the legal needs of the ASF?
>
The policy (AFAIK) with respect to using organization's Jar files is as
follows:
* we don't want to distribute anything that is not "compatible" with
AL2. So we can include jar files that are owned by other people and
under the AL2, BSD and MIT family, or public domain. LGPL does not qualify.
* this ownership needs to be recognized in a NOTICE file
* the license they use should accompany the .jar file in our repository
I do not know how this applies to source code. Generally we only
include source that has been explicitly contributed to the ASF.
more help can be gotten from http://apache.org/dev/apply-license.html
and licensing@a.o
--
Dave Brondsema : dave@brondsema.net
http://www.splike.com : programming
http://csx.calvin.edu : student org
http://www.brondsema.net : personal