Update of /cvsroot/crickscore/documents
In directory sc8-pr-cvs1:/tmp/cvs-serv12337
Added Files:
Licencing_Discussion.html
Log Message:
Initial Revision
--- NEW FILE: Licencing_Discussion.html ---
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type"
content="text/html; charset=ISO-8859-1">
<title>Licencing Discussion</title>
</head>
<body>
<h1>Licencing Discussion</h1>
<h2>Licencing Concerns</h2>
I would like to keep the option of using the crickscore engine in a
commercial product open. The system will be built in a modular
way, with the data access maintained by the open source core. To
maintain the activity of the project it may be nessicary for 3rd partys
to create commercial addons to the standard core to enable active
customisations for each installation. We need to find an open
source licence that enables the project to allow the core to be
utalised in a commercial fashion, without their source needing to be
released. I would not encourage this splintering of the code
base, but it is somthing that I don't want to completely outlaw.
If 3rd partys want to create custom front ends, or custom plugins for
the system, then they should be able to. I would hope that if any
commercial success comes from re-using the the crickscore core, then
they will contribute either time or resources back to the core to
enable it to be come stronger and in turn assist them more.<br>
<h2>Licencing Options</h2>
This is somthing that i'm not sure about. There are things like
the GPL, LGPL, Apache, etc... Source forge has a good list of
them.<br>
<h2>Licencing Comparison</h2>
I would like to fill this section in with discussions of each possible
open source licence. These may be 3rd party discussions, and if
so should be linked to the source and not copied into this
document. If someone actually reads the licence and offers their
own opinion on it then the content is most welcome in this document.<br>
<br>
</body>
</html>
|
