Re: Apache License Question

2002-02-18 Thread Forrest J. Cavalier III

> The new program files that are added would only have the new
> Apache
> license.
> I have had the impression the new software "Yazd" would be
> distributed
> under the new Apache license. Therefore, the new license would be
> the license of the software, and there is no need to mention the old
> one on the site.


You must comply with the old license if you are distributing anything
which is derived from that software.

I'd say at a minimum, the warranty disclaimer and copyrights of the old 
software must be propagated to the new downloaders.  That is one
purpose of the Apache 1.1 clause #2:

  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.

(And clause #1 generally preserves the notice in source forms.)


> The original software creators have complained that the license on the site
> should also have the old license too. I was wondering if this is true.

You must comply with the old license terms.  Depending on how you 
are distributing and what your phrase "license on the site" means,
you could be OK or not.


But I would point out that I dislike license surprises when I 
download.  I dislike reading a license before downloading, and then 
finding a different license after downloading.  







> If anyone could help me out with this I would very much appreciate it.
> Best Regards
> 
> Aflatoon Aflatooni
> Yasna Inc.
> http://www.yasna.com/
> 
> 
> --
> license-discuss archive is at http://crynwr.com/cgi-bin/ezmlm-cgi?3
> 
> 

--
license-discuss archive is at http://crynwr.com/cgi-bin/ezmlm-cgi?3



Network Appliance Common Public License

2002-02-18 Thread Topper, Anthony

[ Pleaes review this license.  Should be like shooting fish in a
barrel, but still.  -russ ]

Dear Open Source Initiative Member,

On behalf of Network Appliance, Inc. I would like to request that the attached license 
be discussed for approval by the OSI. It is identical to the Common Public License 
0.5, except that we have changed the stewardship to Network Appliance Inc, the 
governing law to the State of California, added one sentence to the introduction 
indicating that the license is derived from the Common Public License and added to the 
title that it is Network Appliance's adaptation. 

We are planning a series of open source projects and find the Common Public License 
fits our needs except for the few very minor changes indicated.

Thank you for your time and consideration in this matter. We look forward to your 
feedback.

This license may be discussed in public.


Anthony Topper email: [EMAIL PROTECTED]
Network Appliance, Inc.Phone: 781-768-5385 
375 Totten Pond Road  Fax: 781-895-1195
Waltham, MA 02451   http: www.netapp.com

"For 'tis the sport to have the engineer hoist by his own petard"
 -- Shakespeare (Hamlet III, iv)


Common Public License Version 0.5, Network Appliance Adaptation



THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS COMMON
PUBLIC LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION OF
THE PROGRAM CONSTITUTES RECIPIENT'S ACCEPTANCE OF THIS AGREEMENT. 

ADAPTATION OF THIS LICENSE IS DERIVED FROM THE COMMON PUBLIC
LICENSE VERSION 0.5

1. DEFINITIONS 

"Contribution" means: 

 

a) in the case of the initial Contributor, the initial
code and documentation distributed under this Agreement, and  
b) in the case of each subsequent Contributor:  i) changes to
the Program, and  ii) additions to the Program;

where such changes and/or additions to the Program originate from
and are distributed by that particular Contributor. A Contribution
'originates' from a Contributor if it was added to the Program by such
Contributor itself or anyone acting on such Contributor's
behalf. Contributions do not include additions to the Program which:
(i) are separate modules of software distributed in conjunction with
the Program under their own license agreement, and (ii) are not
derivative works of the Program.


"Contributor" means any person or entity that distributes the Program. 

"Licensed Patents " mean patent claims licensable by a Contributor
which are necessarily infringed by the use or sale of its Contribution
alone or when combined with the Program.

"Program" means the Contributions distributed in accordance with
this Agreement. 

"Recipient" means anyone who receives the Program under this
Agreement, including all Contributors. 

2. GRANT OF RIGHTS


a) Subject to the terms of this Agreement, each Contributor hereby
grants Recipient a non-exclusive, worldwide, royalty-free copyright
license to reproduce, prepare derivative works of, publicly display,
publicly perform, distribute and sublicense the Contribution of such
Contributor, if any, and such derivative works, in source code and
object code form.


b) Subject to the terms of this Agreement, each Contributor hereby
grants Recipient a non-exclusive, worldwide, royalty-free patent
license under Licensed Patents to make, use, sell, offer to sell,
import and otherwise transfer the Contribution of such Contributor, if
any, in source code and object code form. This patent license shall
apply to the combination of the Contribution and the Program if, at
the time the Contribution is added by the Contributor, such addition
of the Contribution causes such combination to be covered by the
Licensed Patents. The patent license shall not apply to any other
combinations which include the Contribution. No hardware per se is
licensed hereunder.

c) Recipient understands that although each Contributor grants the
licenses to its Contributions set forth herein, no assurances are
provided by any Contributor that the Program does not infringe the
patent or other intellectual property rights of any other entity. Each
Contributor disclaims any liability to Recipient for claims brought by
any other entity based on infringement of intellectual property rights
or otherwise. As a condition to exercising the rights and licenses
granted hereunder, each Recipient hereby assumes sole responsibility
to secure any other intellectual property rights needed, if any. For
example, if a third party patent license is required to allow
Recipient to distribute the Program, it is Recipient's responsibility
to acquire that license before distributing the Program.

d) Each Contributor represents that to its knowledge it has
sufficient copyright rights in its Contribution, if any, to grant the
copyright license set forth in this Agreement.

3. REQUIREMENTS 

A Contributor may choose to distribute the Program i

Apache License Question

2002-02-18 Thread Aflatoon Aflatooni

Hi,
I have a license question.
There was an open-source software under the Apache license that the
original creators decided to discontinue the open-source software and sell
it instead.
I, as a big fan of open-source, decided to take the last version of the
open-source software and continue to add functionality and maintaining the
software as open-source.
I decided to maintain the software under the Apache license.
So under the Apache license, I kept the original license (with the original
name of the software, and everything else) intact on the programs, and added
a second block of Apache license with the new name to the program files.
Under the site where the software is distributed (http://yazd.yasna.com)
the new license is only mentioned.
The original software creators have complained that the license on the site
should also have the old license too. I was wondering if this is true.
The new program files that are added would only have the new Apache
license.
I have had the impression the new software "Yazd" would be distributed
under the new Apache license. Therefore, the new license would be the
license of the software, and there is no need to mention the old one on the
site.
If anyone could help me out with this I would very much appreciate it.
Best Regards

Aflatoon Aflatooni
Yasna Inc.
http://www.yasna.com/


--
license-discuss archive is at http://crynwr.com/cgi-bin/ezmlm-cgi?3