On Thu, 23 Sep 2010, Hannes Hirzel wrote:
Why can't we have stuff from Sophie back to Squeak/Pharo? - only the Sophie developers are familiar with the code and they are not motivated enough to extract it
Not necessarily their task..... :-)
That's right, but tell me who else is up to the task?
Writing libraries and reusable components is a different project.
- the license is BSD, so the code can't be included in Pharo/Squeak
I googled for BSD MIT license compatibility
and found some interesting information
see for example http://www.dwheeler.com/essays/floss-license-slide.html
the paragraph about BSD in http://producingoss.com/en/license-choosing.html
The license might be compatible depending on the "version" of the BSD license. And if not you could extract code and then ask the developers to release it as MIT.
MIT and BSD are very close (or the same depending on the version)
To summarize: The statement
"the license is BSD, so the code can't be included in Pharo/Squeak"
is too strong. There might be some problems including code, but they may be solved easily with by writing a few emails....
The license is the 3-clause BSD license, it contains the following non-endorsement clause: "Neither the name of the University of Southern California, Los Angeles nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission." I wonder what can be done about this. Levente
--Hannes
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project