[pypy-svn] r3850 - pypy/trunk/doc/funding/negotiations

[alastair at codespeak.net]

Author: alastair
Date: Tue Apr  6 18:34:32 2004
New Revision: 3850

Modified:
   pypy/trunk/doc/funding/negotiations/responses_2nd_april.txt
Log:
More diplomatic text on licensing

Modified: pypy/trunk/doc/funding/negotiations/responses_2nd_april.txt
==============================================================================
--- pypy/trunk/doc/funding/negotiations/responses_2nd_april.txt	(original)
+++ pypy/trunk/doc/funding/negotiations/responses_2nd_april.txt	Tue Apr  6 18:34:32 2004
@@ -250,14 +250,14 @@
 GPL licensed projects. 
 
 While all consortium partners commit to produce source code and results
-always under an MIT license the project explicitly reserves the right
-to *include* GPLed software.  In the latter case some versions of PyPy
-might have to be released under a GPL license.  If PyPy becomes the
-basis of Python 3000, there will be pressure to release PyPy under the
-Python license which is very similar to the MIT license.  In contrast,
-using a GPL license would drastically reduce our ability to become the
-basis of Python 3000, since the CPython developers reject the GPL as the
-license for developing Python. 
+always under an MIT license the project explicitly reserves the right to
+*include* GPLed software.  In the latter case some versions of PyPy might
+have to be released under a GPL license.  If PyPy becomes the basis of
+Python 3000, there will be pressure to release PyPy under the Python
+license which is very similar to the MIT license.  In contrast, using a GPL
+license would drastically reduce our ability to become the basis of Python
+3000, since the CPython developers have a clear preference for an MIT-style
+license for developing Python.
 
 **Action: The DoW will be modified to avoid this [user] confusion.**