[pypy-svn] r3649 - in pypy/trunk/doc/funding: . negotiations

[hpk at codespeak.net]

Author: hpk
Date: Thu Apr  1 19:26:03 2004
New Revision: 3649

Modified:
   pypy/trunk/doc/funding/B3.impact.txt
   pypy/trunk/doc/funding/negotiations/responses_2nd_april.txt
Log:
- added licensing discussion to both B3.0 and the responses document, 
  took Jacob's and others fragments and reworked them a bit 

- added a better para in the response about "end-users" 

Please check!




Modified: pypy/trunk/doc/funding/B3.impact.txt
==============================================================================
--- pypy/trunk/doc/funding/B3.impact.txt	(original)
+++ pypy/trunk/doc/funding/B3.impact.txt	Thu Apr  1 19:26:03 2004
@@ -264,15 +264,16 @@
 ++++++++++++++++++++++++++++++
 
 This is an Open Source Project.  Thus complicated issues involving
-intellectual property simply do not arise.  The knowledge produced
+intellectual property do not arise.  The knowledge produced
 by this project, every deliverable, is listed at Dissemination Level
 Public.  We are utterly committed to transparency and open dissemination,
 and as such will have all of our code available for nightly downloads,
 our papers freely available on the PyPy websites, and freely available
 for other people to link to.  All Consortium members will have signed
-a consortium agreement, asserting that all code will be released 
-under the MIT Open Source License, approved by both the Open Source
-Initiative and the Free Software Foundation.   The MIT license is here.
+a consortium agreement, asserting that all code producing during the
+PyPy STREP will be released under the MIT Open Source License, approved
+by both the Open Source Initiative and the Free Software Foundation.
+The MIT license is here.
 
 ::
 
@@ -299,14 +300,34 @@
     FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER 
     DEALINGS IN THE SOFTWARE.
 
-This license is concise and clearly permits any person obtaining our product to
-use it without limitation. The open, clear language removes any chance of
-licensing controversy.
-
-Management of this intellectual property consists of a posting the license on
-the website or wherever source code is available, and periodically running
-a program, especially before software releases, attaching a copy of the license
-at the top of every file released.
+This license is concise and clearly permits any person obtaining our
+product to use it without limitation. The open, clear language removes
+any chance of a licensing controversy.  It allows commercial entities
+and the project partners in particular to incorporate code and results
+into commercial or non-commercial projects. 
+
+The consortium did consider using the GPL license for protection from a
+commercial takeover.  We regognise that there is some risk that the
+results of our project would be subject to an "embrace and extend"
+strategy or another form of hostile takeover, especially if the project
+is a great success.
+
+However, we will not reach the adoption necessary for such a scenario to
+be likely unless we manage to get widespread adoption both within and
+outside the present Python community. Before we can get any adoption
+outside the Python community, we have to win the hearts of people on the
+inside. These people - especially the portal figures - have a strong
+preference for MIT license models and lack enthusiasm for the GPL.
+
+Also, a takeover attempt is not necessarily successful and the Python
+world is probably more resilient to such tries than most other
+communities, since it is more strongly integrated and collaboratively
+focused than other comparable groups.
+
+Management of intellectual property consists of a posting the license on
+the website or wherever source code is available, and periodically
+running a program, especially before software releases, to check that
+the license is properly refered to from each file. 
 
 The only other intellectual property which we will produce are 
 scientific papers, talks, and the like.  They will all be freely

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	Thu Apr  1 19:26:03 2004
@@ -156,23 +156,31 @@
 
 **Action: The DoW will include a justification of the license chosen. Compatibility with the GPL will be addressed.**
 
-The chapter in B3.0 Impact chapter which mentioned licensing has been extended to
-cover a short discussion of choosing the MIT license over the GPL.  While
-all consortium partners commit to produce source code always under an MIT 
-license the project explicitely 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 may be
-some pressure to release this under the Python license.  If we develop
-under the MIT license, then we are most flexible in this regard.  Committing
-to a GPL license would drastically reduce our ability to become the basis
-of Python 3000, since the CPython developers have already rejected the
-GPL as the license for developing Python. 
+The chapter in B3.0 Impact chapter which mentioned licensing has been
+extended to cover a short discussion of choosing the MIT license over
+the GPL.  
+
+In summary, the risk of a complete "hostile takeover" from some
+commercial company is low considering the partners and the communities
+involved. However, our results and source code can be freely used from
+GPL licensed projects. 
+
+While all consortium partners commit to produce source code and results
+always under an MIT license the project explicitely 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 may be some pressure to release PyPy under
+the Python license.  If we develop under the MIT license, then we remain
+compatible to the bsd-like Python license.  In contrast, using a GPL
+license would drastically reduce our ability to become the basis of
+Python 3000, since the CPython developers have already rejected the GPL
+as the license for developing Python. 
 
 **Action: The DoW will be modified to avoid this [user] confusion.**
 
-The complete DoW has been clarified accordingly.  Mainly end-users 
-of the PyPy STREP will be language integrators and researchers.  
-Please note especially, that Users of Applications running on top of PyPy 
-are not refered to as "End users" but - if neccessary - as "application users". 
-The PyPy implementation is planned to be useful to end-users and all application
-users. 
+The complete DoW has been clarified accordingly.  End-users of the PyPy
+STREP are language integrators and researchers.  The line between beeing 
+an end-user and a contributor to the project is designed to be easy to cross 
+thus contributing to effective mobilization of resources.  Nevertheless, The PyPy 
+implementation is indirectly useful to all users running applications (especially
+novel ones)  on top of PyPy.