Talk:CSL: Difference between revisions

From OLPC
Jump to navigation Jump to search
Line 12: Line 12:
== Proposal: Modular design ==
== Proposal: Modular design ==


This is not a license issue but a design recommendation. CSL programs can build on a freely available core but allow plugins (similar to Firefox or Eclipse plugins) under the CSL license. One would probably want an option in the CSL license to either allow or disallow commercial plugins under different licenses.
This is not a license issue but a design recommendation. CSL programs can build on a freely available core but allow plugins, extensions or related programs (similar to Firefox or Eclipse plugins) under the CSL license. One would probably want an option in the CSL license to either allow or disallow commercial plugins under different licenses.


= Projects =
= Projects =

Revision as of 00:03, 1 February 2009

Proposals

Proposal: CSL Membership License

At a fixed annual cost access to all software under CSL Membership License could be made available. CSL-EDU could be a special case for education providers. This license would allow a community of users and programmers with open access, similar to the open source community.

Proposal: CSL-EDU

The CSL-EDU license would be a special license for education providers. At a fixed cost the education provider can license all software that is made available under the CSL-EDU license. Licensor and education provider can negotiate the cost according to published policies of the Licensor. The Licensor is responsible to provide a license management system that allows to distribute and revoke licenses for students conveniently and to make software released under the CSL-EDU compatible with the licensing scheme. Licensors who do not meet that criterion cannot sell site licenses for education providers.

Proposal: Modular design

This is not a license issue but a design recommendation. CSL programs can build on a freely available core but allow plugins, extensions or related programs (similar to Firefox or Eclipse plugins) under the CSL license. One would probably want an option in the CSL license to either allow or disallow commercial plugins under different licenses.

Projects

Project proposal: Eclipse under CSL?

The EPL states "A Contributor may choose to distribute the Program in object code form under its own license agreement", which could be the CSL. An Eclipse-Jemacs hybrid might be a good idea (for instance). --fasten 19:02, 17 January 2009 (UTC)

Project proposal: Software that is useful for OLPC

  • QNX, Sugar and Java/X++ as a CSL-licensed commercial distribution? (For instance with application monitoring written in Java) The distribution would, of course, not be attached to the XO hardware. --fasten 02:16, 31 January 2009 (UTC)

Project: X++ (working title)

A language that combines C++, XML and Java with a simplified syntax. Releasing X++ under CSL could have the psychological effects of increasing awareness for CSL and making CSL licensing a more natural choice. (Under development) --fasten 12:30, 30 January 2009 (UTC)

The name "X++" is already used by Microsoft for a language that has similarities with C# and C++ but includes SQL syntax. [1] --fasten 12:37, 30 January 2009 (UTC)
If the X++ compiler frontend was licensed under CSL only the compilation process would apparently not be an Eligible Compilation Process according to the GCC Runtime Library Exception for GPLv3, which would mean the resulting binaries would be under GPL license. One could follow the modular design proposal and license the compiler frontend under GPL+CSL, which seems to be a sensible strategy anyway. --fasten 23:57, 31 January 2009 (UTC)

Comments