Difference between revisions of "Team:Cambridge-JIC/Practices"
KaterinaMN (Talk | contribs) |
KaterinaMN (Talk | contribs) |
||
Line 277: | Line 277: | ||
<div style="width: 80%; margin: 30px 50px;color:#000;min-height:0px"> | <div style="width: 80%; margin: 30px 50px;color:#000;min-height:0px"> | ||
<h2> Permissive Licenses </h2> | <h2> Permissive Licenses </h2> | ||
+ | <p>Features of Permissive licenses:</p> | ||
+ | <ul> | ||
+ | <li><p>There are no reciprocity requirements when using a Permissive license. Redistributors can restrict access to derivative products and make them proprietary [17]</p></li> | ||
+ | <li><p>Hence they make it more likely that a given product will be repackaged and commercialised [15]</p></li> | ||
+ | <li><p>This is seen by some as a driving force for innovation and an additional freedom compared to Copyleft licenses [13]</p></li> | ||
+ | <li><p>They are designed to be legally simple and compatible with a greater variety of downstream licenses than Copyleft licenses (see compatibility charts)</p></li> | ||
+ | <li><p>It is important to recognise that any improvements on the product that are made proprietary will not be available to the community. This is not a problem with Copyleft licenses.</p></li> | ||
+ | </ul> | ||
+ | <p>A variety of Permissive licenses are available (Fig. 5, Fig. 6), and recently it has been proposed to develop a new one based on the Apache 2.0 software license as this is already well established [14].</p> | ||
</div></div></section> | </div></div></section> | ||
Revision as of 14:04, 9 September 2015