From: Mike C. F. <mcf...@ro...> - 2003-07-01 23:42:22
|
Dear OSI board, As you are no doubt aware, the Python Software Foundation License is an aglomeration of various licensing restrictions from various sources, rather than a coherent attempt to outline a particularly desirable set of rights and/or responsibilities. The wording of the license is specific to the Python language, and has very little relevance to new software development. However, Python developers, seeing "Python License" are beginning to use the license as though it were a desirable license for new Open Source development simply because it is associated with Python (despite the 4 or 5 different licensors, and all the other rather ugly attributes of the Python Software Foundation License). Certainly SourceForge must take some of the responsibility for this given that they include the PSF license in the list of available Open Source licenses during project registration, but I'm wondering if the OSI could work to avoid this effect as well. Given that there are other licenses which embody the general terms of the Python license, I'm wondering if it would be reasonable to add notes to the Python Software Foundation License page on http://www.opensource.org/licenses/PythonSoftFoundation.php to the effect that the license is not particularly intended for reuse in other projects, possibly pointing the user to the BSD license, or even the Python CNRI license (as a subset of the PSF license). For example: The Python Software Foundation License represents the historical interplay of interests in the Python language implementation. It is not a license designed for reuse for other open source projects. If you are considering a license for use with a new open source project, you may want to consider the BSD <link> or MIT <link> licenses. With thanks for all your work, Mike Fletcher _______________________________________ Mike C. Fletcher Designer, VR Plumber, Coder http://members.rogers.com/mcfletch/ |