Proposed Grail and JPython Licenses
Dear Debian Folks,
I'm writing to because some Debian folks have written me before about
some issues with the Grail and JPython licenses (go to www.python.org
and follow pointers to Grail or JPython in the left sidebar if you
want to see the current licenses). Gregor Hoffleit suggested that I
mail this here. I have no idea who reads this, so please bear with
I'm in the process of revising the licenses for Grail and JPython.
Before I commit to a particular license, I'd like to get feedback from
Debian on the draft license below. In particular, would software with
this license be acceptable for inclusion in the Debian distribution?
I believe I've addressed the comments on previous versions of the
I have to work with corporate management and lawyers here, who have
approved a draft very similar to this as a template for a license for
non-commercial use of other software to be released by CNRI. The
license I show here does not have the restriction on non-commercial
use -- but I'm not sure if the corporate lawyers might want to change
the rest of the license because of this. But if this version in't
good enough for Debian I'm not even going to propose this one to the
corporate lawyers before discussing this more with Debian.
A note on clause 4 (about OROmatcher, a regular expression package for
Java), which only applies to JPython. I expect that this may be a
show-stopper for Debian, since OROmatcher is only available in binary
form. I propose to have a developers release that does not include
OROmatcher or clause 4, which can be safely included in Debial
distributions, and an end-user release which has those (as well as
other goodies, like the standard Python library) which you may have to
avoid (actually, Gregor mentioned that it might still be available
from the Debian ftp site).
The Grail license will be the same, without clause 4, and with an (R)
sign attached to the Grail name, because it is a CNRI registered
trademark. This may happen for JPython as well.
Let me know if this license works for Debian, and if not, what
problems it has.
Remember: I can't promise that this will be the license -- but I'm
--Guido van Rossum (home page: http://www.python.org/~guido/)
CNRI LICENSE AGREEMENT
IMPORTANT: PLEASE READ THE FOLLOWING AGREEMENT CAREFULLY.
BY CLICKING ON THE SOFTWARE RELEASE BUTTON YOU ARE DEEMED TO
HAVE ACCEPTED THE TERMS AND CONDITIONS OF THIS AGREEMENT.
1. This CNRI LICENSE AGREEMENT (the "Agreement") by and between the
Corporation for National Research Initiatives, having an office at
1895 Preston White Drive, Reston, VA 20191 ("CNRI") and the Individual
or Organization ("Licensee") requesting release of JPython 1.0.x, for
any integer x, in binary and source form and its associated
documentation as provided herein ("Software"), is effective as of the
date of release to Licensee of the Software.
2. Except as otherwise provided herein, CNRI hereby grants Licensee a
non-exclusive, irrevocable, non-transferable, royalty-free, world-wide
license to reproduce, analyze, test, perform and/or display publicly,
prepare derivative works, distribute, and otherwise use the Software,
alone or in any derivative version, provided, however, that CNRI's
License Agreement and CNRI's notice of copyright, i.e., "Copyright ©
1997-1999 Corporation for National Research Initiatives; All
Rights Reserved" are both retained in the Software, alone or in any
derivative version prepared by Licensee. In the event Licensee
prepares a derivative work that is based on or incorporates the
Software or any part thereof, and wants to make the derivative work
available to the public, then Licensee hereby agrees to indicate in
any such work, in a prominently visible way, the nature of the
modifications made to CNRI's Software.
3. Licensee may not use CNRI trademarks or trade name, including
JPython or CNRI, in a trademark sense to endorse or promote products
or services of Licensee, or any third party. Licensee may use the mark
JPython in connection with Licensee's derivative versions that are
based on or incorporate the Software, but only in the form
"JPython-based ___________________," or equivalent.
4. The Software contains OROMatcher regular expression software from
ORO, Inc. Copyright 1997 by ORO, Inc. ("ORO software"). OROMatcher
(TM) is a trademark of Original Reusable Objects, Inc. Except as
permitted by applicable law and this Agreement, Licensee may not
decompile, reverse engineer, disassemble, or modify the ORO software
provided herein. Licensee acknowledges that redistribution of the ORO
software separate from JPython or direct use of the ORO software
interfaces requires a separate license from ORO,
5. CNRI is making the Software available to Licensee on an "AS IS"
basis. CNRI MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR
IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, CNRI MAKES NO AND
DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS
FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE WILL NOT
INFRINGE ANY THIRD PARTY RIGHTS.
6. CNRI SHALL NOT BE LIABLE TO LICENSEE OR OTHER USERS OF THE SOFTWARE
FOR ANY INCIDENTAL, SPECIAL OR CONSEQUENTIAL DAMAGES OR LOSS AS A
RESULT OF USING, MODIFYING OR DISTRIBUTING THE SOFTWARE, OR ANY
DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF. SOME
STATES DO NOT ALLOW THE LIMITATION OR EXCLUSION OF LIABILITY SO THE
ABOVE DISCLAIMER MAY NOT APPLY TO LICENSEE.
7. This Agreement may be terminated by CNRI (i) immediately upon
written notice from CNRI of any material breach by the Licensee, if
the nature of the breach is such that it cannot be promptly remedied;
or (ii) sixty (60) days following notice from CNRI to Licensee of a
material remediable breach, if Licensee has not remedied such breach
within that sixty-day period.
8. This Agreement shall be governed by and interpreted in all respects
by the law of the State of Virginia, excluding conflict of law
provisions. In the event any part of this Agreement is declared
invalid or otherwise unenforceable by a court of competent
jurisdiction, the remaining provisions shall remain in effect. Nothing
in this Agreement shall be deemed to create any relationship of
agency, partnership, or joint venture between CNRI and Licensee.