Difference between revisions of "Team:Cambridge-JIC/Practices"
Maoenglish (Talk | contribs) |
Maoenglish (Talk | contribs) |
||
Line 317: | Line 317: | ||
</div></div></section> | </div></div></section> | ||
− | <section style="background-color:white" id=" | + | <section style="background-color:white" id="viral"> |
<div class="slide"> | <div class="slide"> | ||
<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> | + | <h2>Copyleft or Viral Licenses</h2> |
− | <div style="float: | + | <div style="float:left;width:160px"><center><img src="//2015.igem.org/wiki/images/a/a3/CamJIC-Practices-CopyLeft.png" style="width:150px;margin-bottom:5px;margin-right:10px"><p style="font-size:80%;line-height:100%"><i>The Copyleft logo. The term was coined by Richard Stallman.</i></p></center></div> |
− | <p>The Creative Commons ‘No Rights Reserved license’ (known as the CC0 license) essentially waives all copyrights you have over you work. This means there is no legal protection against you works being used, modified, redistributed or made proprietary | + | <p>The Creative Commons ‘No Rights Reserved license’ (known as the CC0 license) essentially waives all copyrights you have over you work. This means there is no legal protection against you works being used, modified, redistributed or made proprietary.</p> |
− | <p> | + | <p>The phenomenon of OSH is in its infancy, and as a result there are only a handful of potential options when choosing an appropriate license. Many of these are Copyleft or ‘viral’ licenses.</p> |
− | + | <div style="float:right;width:220px;margin-left:10px;margin-bottom:5px"><center><img src="//2015.igem.org/wiki/images/2/22/CamJIC-Practices-CreativeCommons.png" style="width:220px;margin-bottom:5px"><p style="font-size:80%;line-height:100%"><i>An example of the human-readable version of the most recent Creative Commons Attribution-ShareAlike license (CC BY-SA).</i></p></center></div> | |
− | < | + | <p>Features of viral licenses:</p> |
− | <center | + | |
− | <p style="font-size:80%"> | + | |
− | </ | + | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | <p>Features of | + | |
<ul> | <ul> | ||
− | <li><p> | + | <li><p>Any derivatives must be licensed under the same conditions as the original</p></li> |
− | <li><p> | + | <li><p>Once licensed, all derivatives will be fully accessible forever</p></li> |
− | <li><p> | + | <li><p>Reduced likelihood of any derivatives being commercialised compared to Permissive licenses, and no chance of them being made proprietary</p></li> |
− | <li><p> | + | <li><p>Increased issues of license compatibility compared to Permissive licenses. This could be a problem if a new license is released later in time that may be more appropriate</p></li> |
− | + | ||
</ul> | </ul> | ||
− | < | + | <p>One of the most widespread is the Creative Commons* Attribution-ShareAlike license. This is however not specifically designed for OSH, and was instead developed for works of art such as music and designs, as well as software [1]. More comprehensive and hardware-specific licenses have been created, and here the authors will focus on two of them: the CERN OHL and the TAPR OHL.</p> |
− | + | <p style="font-size:80%">* A global non-profit organization that enables sharing and reuse of creativity and knowledge through the provision of free legal tools (<a href="wiki.creativecommons.org" class="blue">Creative Commons webpage</a>).<br>[1] Opensource.com, (2015). What is open hardware? | Opensource.com. <a href="http://opensource.com/resources/what-open-hardware" class="blue">[online]</a>[Accessed 23 Aug. 2015].</p></div></div></section> | |
− | + | ||
− | + | ||
− | <p style="font-size:80%"> | + | |
− | </div></div></section> | + | |
<section style="background-color:white" id="CERN"> | <section style="background-color:white" id="CERN"> | ||
Line 387: | Line 373: | ||
<p>This is a brief summary. For more detailed information, see the online text of the <a href="http://www.ohwr.org/documents/294" class="blue">CERN OHL license v1.2</a>.</p> | <p>This is a brief summary. For more detailed information, see the online text of the <a href="http://www.ohwr.org/documents/294" class="blue">CERN OHL license v1.2</a>.</p> | ||
</div></div></section> | </div></div></section> | ||
− | |||
− | |||
<section style="background-color:white" id="TAPR"> | <section style="background-color:white" id="TAPR"> | ||
Line 436: | Line 420: | ||
<p style="font-size:80%">* A reminder: copyright covers creative works such as designs, diagrams, software and other documentation. Patents are applicable to inventions and useful works as physical entities (the finished product). <br>[1] Keimform.de, (2009). The Tricky Business of "Copylefting" Hardware. <a href="http://keimform.de/2009/the-tricky-business-of-copylefting-hardware/" class="blue">[online]</a> [Accessed 10 Sep. 2015]</p> | <p style="font-size:80%">* A reminder: copyright covers creative works such as designs, diagrams, software and other documentation. Patents are applicable to inventions and useful works as physical entities (the finished product). <br>[1] Keimform.de, (2009). The Tricky Business of "Copylefting" Hardware. <a href="http://keimform.de/2009/the-tricky-business-of-copylefting-hardware/" class="blue">[online]</a> [Accessed 10 Sep. 2015]</p> | ||
+ | </div></div></section> | ||
+ | |||
+ | <section style="background-color:#ebe5dc" id="permissive"> | ||
+ | <div class="slide"> | ||
+ | <div style="width: 80%; margin: 30px 50px;color:#000;min-height:0px"> | ||
+ | <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 [1]</p></li> | ||
+ | <li><p>Hence they make it more likely that a given product will be repackaged and commercialised [2]</p></li> | ||
+ | <li><p>This is seen by some as a driving force for innovation and an additional freedom compared to Copyleft licenses [3]</p></li> | ||
+ | <li><p>They are designed to be legally simple and compatible with a greater variety of downstream licenses than Copyleft licenses <a href="#comp" class="blue">(see compatibility charts)</a></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> | ||
+ | <div style="float:right;width:300px"><center><img src="//2015.igem.org/wiki/images/7/76/BSD_MIT.png" style="width:300px;margin-bottom:5px;margin-left:10px"><p style="font-size:80%;line-height:100%"><i>The BSD and MIT license logos. These are widely used and well-established permissive licenses.</i></p></center></div> | ||
+ | <p>A variety of Permissive licenses are available, 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 [4].</p><br> | ||
+ | <p> A summary of the licenses available for open source projects:</p> | ||
+ | <center><img src="//2015.igem.org/wiki/images/1/1d/CamJIC-Practices-Licenses.png" style="width:85%"></center> | ||
+ | <p style="font-size:80%">[1] Opensource.org, (2015). Frequently Answered Questions | Open-source Initiative. <a href="http://opensource.org/faq#permissive" class="blue">[online]</a> [Accessed 6 Sep. 2015].<br>[2] Gnu.org, (2015). Categories of Free and Nonfree Software - GNU Project - Free Software Foundation. <a href="https://www.gnu.org/philosophy/categories.html" class="blue">[online]</a> [Accessed 6 Sep. 2015].<br>[3] Opensource.com, (2015). How to choose a license for your open-source project | Opensource.com. <a href="http://opensource.com/business/14/1/what-license-should-i-use-open-source-project" class="blue">[online]</a> [Accessed 6 Sep. 2015].<br>[4] Katz, A. (2012). Towards a Functional Licence for Open Hardware. IFOSS L. Rev., pp.41-62.</p> | ||
+ | </div></div></section> | ||
+ | |||
+ | <section style="background-color:white" id="CC0"> | ||
+ | <div class="slide"> | ||
+ | <div style="width: 80%; margin: 30px 50px;color:#000;min-height:0px"> | ||
+ | <h2>CC0 and Unlicensed Work</h2> | ||
+ | <div style="float:right;width:300px"><center><img src="//2015.igem.org/wiki/images/d/d4/CamJIC-Practices-CC0.png" style="width:300px;margin-bottom:5px"><p style="font-size:80%;line-height:100%"><i>The marks for the CC0 license (left) and Public Domain Mark (right) to be displayed on works under these agreements.</i></p></center></div> | ||
+ | <p>The Creative Commons ‘No Rights Reserved license’ (known as the CC0 license) essentially waives all copyrights you have over you work. This means there is no legal protection against you works being used, modified, redistributed or made proprietary. However, your work is now as free to use as it could possibly be. It is often used to release teaching material online, such that as many people as possible can benefit from it.</p> | ||
+ | <p>Under the CC0 anyone can access your work, and use it in any way they want. However, you cannot license the work of other people under the CC0 unless you have express permission to do so or they have also used the CC0 license. This is an example of license compatibility issues <a href="#comp" class="blue">(see compatibility tables)</a>.</p> | ||
+ | <p>Unlicensed work released into the public domain can be used by anyone in any way, again meaning that continued access cannot be ensured. Creative Commons recommends using the ‘Public Domain Mark’ for this work. This is intended for old works that are already in the public domain without copyright in order to provide information about them [1].</p> | ||
+ | <p>A brief summary to getting a CC license for your designs, software and literature:</p> | ||
+ | <center><a href="http://creativecommons.org/choose/"><img src="//2015.igem.org/wiki/images/7/71/CamJIC-Practices-CC0license.png"></a></center> | ||
+ | <p style="font-size:80%">[1] Wiki.creativecommons.org, (2015).Frequently Asked Questions - Creative Commons. <a href="https://wiki.creativecommons.org/wiki/Frequently_Asked_Questions#Can_I_combin-e_works_that_use_different_Creative_Commons_licenses_into_my_work.3F" class="blue">[online]</a> [Accessed 5 Sep. 2015].</p> | ||
</div></div></section> | </div></div></section> | ||
Line 448: | Line 464: | ||
<p>For more information about the GNU GPL, visit the <a href="http://www.gnu.org/" class="blue">GNU webpage</a>.</p> | <p>For more information about the GNU GPL, visit the <a href="http://www.gnu.org/" class="blue">GNU webpage</a>.</p> | ||
</div></div></section> | </div></div></section> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
Revision as of 09:01, 14 September 2015