Talk:CSL: Difference between revisions
m (→Proposal: CSL SDK license: wording) |
|||
Line 18: | Line 18: | ||
A CSL SDK license could be a license to develop commercial plugins for a CSL-licensed program. This could be seen as a middle ground between trying to prohibit commercial plugins and allowing commercial plugins without restrictions. A CSL SDK license should have an annual licensing fee, possibly in percent of the generated revenue. A commercial vendor would always be free to make his plugins usable in a different container program but might lose the community around the CSL-licensed program. |
A CSL SDK license could be a license to develop commercial plugins for a CSL-licensed program. This could be seen as a middle ground between trying to prohibit commercial plugins and allowing commercial plugins without restrictions. A CSL SDK license should have an annual licensing fee, possibly in percent of the generated revenue. A commercial vendor would always be free to make his plugins usable in a different container program but might lose the community around the CSL-licensed program. |
||
An interesting consideration here may be: "If you accept a moral obligation to educate others, how much motivation are you willing to provide?" |
An interesting consideration here may be: "If you accept a moral obligation to educate/motivate others, how much motivation are you willing to provide?" |
||
One could, for instance, make payment of the full license fee voluntary but revoke the license below a minimum threshold. |
One could, for instance, make payment of the full license fee voluntary but revoke the license below a minimum threshold. |
||
Revision as of 22:19, 9 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 (e.g. 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.
Proposal: CSL SDK license
A CSL SDK license could be a license to develop commercial plugins for a CSL-licensed program. This could be seen as a middle ground between trying to prohibit commercial plugins and allowing commercial plugins without restrictions. A CSL SDK license should have an annual licensing fee, possibly in percent of the generated revenue. A commercial vendor would always be free to make his plugins usable in a different container program but might lose the community around the CSL-licensed program.
An interesting consideration here may be: "If you accept a moral obligation to educate/motivate others, how much motivation are you willing to provide?" One could, for instance, make payment of the full license fee voluntary but revoke the license below a minimum threshold.
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.
- Examples:
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++
A language that combines C++, XML and Java with a simplified syntax. Releasing X++ (working title) under CSL could have the psychological effects of increasing awareness for CSL and making CSL licensing a more natural choice. --fasten 12:30, 30 January 2009 (UTC)
- Features:
- The C++ object hierarchy is replaced with that of Java. All C++ methods are part of Java objects. C structs can be used and are accessible from Java (as in javolution)
- All objects are partitioned into aspects. This isn't exactly aspect orientation but makes large objects more easily understandable. Refactoring on aspect level will be possible.
- typedef for Java basic types.
- free IDE under GPL+CSL.
- IDE is designed with respect to psychological effects.
- Wiki syntax for code documentation; alternative XML output for templates; Java code embedded in templates can be used to generate custom template output