Difference between revisions of "Team:Cambridge-JIC/Practices"
KaterinaMN (Talk | contribs) (Undo revision 212323 by KaterinaMN (talk)) |
KaterinaMN (Talk | contribs) (Undo revision 212284 by KaterinaMN (talk)) |
||
Line 356: | Line 356: | ||
<p>For more information on CERN licensing procedures, see <a href="#CERNextra" class="blue">here.</a></p> | <p>For more information on CERN licensing procedures, see <a href="#CERNextra" class="blue">here.</a></p> | ||
<p style="font-size:80%">* See <a href="http://www.ohwr.org/documents/294" class="blue">OHWR webpage</a> for more information.<br>[1] Ayass, M. (2015). CERN Open Hardware Licence. <a href="http://-www.ohwr.org/projects/cernohl/wiki" class="blue">[online]</a> [Accessed 7 Sep. 2015].<br>[2] Wiki.citoyenscapteurs.net, (2015). Le Wiki des Citoyens Capteurs. <a href="http://wiki.citoyenscapteurs.net/doku.php" class="blue">[online]</a> [Accessed 12 Aug. 2015].</p> | <p style="font-size:80%">* See <a href="http://www.ohwr.org/documents/294" class="blue">OHWR webpage</a> for more information.<br>[1] Ayass, M. (2015). CERN Open Hardware Licence. <a href="http://-www.ohwr.org/projects/cernohl/wiki" class="blue">[online]</a> [Accessed 7 Sep. 2015].<br>[2] Wiki.citoyenscapteurs.net, (2015). Le Wiki des Citoyens Capteurs. <a href="http://wiki.citoyenscapteurs.net/doku.php" class="blue">[online]</a> [Accessed 12 Aug. 2015].</p> | ||
+ | </div></div></section> | ||
+ | |||
+ | <section style="background-color:#ebe5dc" id="CERNextra"> | ||
+ | <div class="slide"> | ||
+ | <div style="width: 80%; margin: 30px 50px;color:#000;min-height:0px"> | ||
+ | <h2>CERN OHL additional info: CERN documentation requirements</h2> | ||
+ | <p>If you create a design that you want to license under the CERN OHL:</p> | ||
+ | <ol type="i"> | ||
+ | <li><p>Modified Documentation must carry prominent notices stating that the Licensee has modified the Documentation, with the date and description of the modifications</p></li> | ||
+ | <li><p>Documentation must carry a new Documentation Location notice if the original Documentation provided for one</p></li> | ||
+ | <li><p>Modified Documentation must be available at the same level of abstraction as that of the Documentation, in the preferred format for making modifications to it (e.g. the native format of the CAD tool as applicable), and in the event that format is proprietary, in a format viewable with a tool licensed under an OSI-approved license if the proprietary tool can create it</p></li> | ||
+ | <li><p>The modified Documentation must be released under the terms and conditions of this Licence or, where applicable, a later version of this Licence as may be issued by CERN</p></li> | ||
+ | </ol> | ||
+ | <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> | ||
+ | |||
+ | |||
+ | |||
+ | <section style="background-color:white" id="TAPR"> | ||
+ | <div class="slide"> | ||
+ | <div style="width: 80%; margin: 30px 50px;color:#000;min-height:0px"> | ||
+ | <h2>TAPR OHL</h2> | ||
+ | <p>The TAPR OHL was developed by Tucson Amateur Packet Radio, and like the CERN OHL was created to extend the success of OSS licenses*. It is available for anyone to use, and can be downloaded directly from their website [1]. Just like the CERN OHL it is a Copyleft or ‘viral’ license: the terms applied to one product are propagated to all downstream products. In short, this means that once a product is made open-source, it and all it’s modifications remain accessible to the community.</p> | ||
+ | <p>The key premises of the TAPR OHL are outlined below, as described by the official website [1]:</p> | ||
+ | <ol type="i"> | ||
+ | <li><p>Products can be used for any legal purpose</p></li> | ||
+ | <li><p>Unmodified documentation can be released, but it must be in the form of the entire package</p></li> | ||
+ | <li><p>Products can be commercially released as long as the documentation is also freely released, or is available for free for up to 3 years</p></li> | ||
+ | <li><p>All modifications must be released under the OHL</p></li> | ||
+ | <li><p>All modifications must be well documented, and attempts made to notify the designers of the original product</p></li> | ||
+ | </ol> | ||
+ | <p>Overall, the above requirements ensure that nobody is denied the rights to access the product and its documentation, including all downstream versions.</p> | ||
+ | <p>For more information on TAPR licensing procedures, see <a href="#TAPRextra" class="blue">here.</a></p> | ||
+ | <p style="font-size:80%">* It is worth mentioning that these licenses were created by volunteers with expertise in legal matters. They did this for the benefit of the community itself, despite it being a complex and time-consuming process.<br>[1] Tapr.org, (2015). The TAPR Open Hardware License. <a href="https://www.tapr.org/ohl.html" class="blue">[online]</a> [Accessed 23 Aug. 2015].</p> | ||
+ | </div></div></section> | ||
+ | |||
+ | <section style="background-color:#ebe5dc" id="TAPRextra"> | ||
+ | <div class="slide"> | ||
+ | <div style="width: 80%; margin: 30px 50px;color:#000;min-height:0px"> | ||
+ | <h2>TAPR OHL additional info: TAPR documentation requirements</h2> | ||
+ | <p>If you create a design that you want to license under the OHL, you should [1]:</p> | ||
+ | <ol type="i"> | ||
+ | <li><p>Include the OHL document in a file named LICENSE.TXT (or LICENSE.PDF) that is included in the documentation package.</p></li> | ||
+ | <li><p>If the file format allows, include a notice like "Licensed under the TAPR Open Hardware License (www.tapr.org/OHL)" in each documentation file. While not required, you should also include this notice on printed circuit board artwork and the product itself; if space is limited the notice can be shortened or abbreviated.</p></li> | ||
+ | <li><p>Include a copyright notice in each file and on printed circuit board artwork.</p></li> | ||
+ | <li><p>If you wish to be notified of modifications that others may make, include your email address in a file named "CONTRIB.TXT" or something similar.</p></li> | ||
+ | <li><p>Any time the OHL requires you to make documentation available to others, you must include all the materials you received from the upstream licensors. In addition, if you have modified the documentation:</p></li> | ||
+ | <li><p>You must identify the modifications in a text file (preferably named "CHANGES.TXT") that you include with the documentation. That file must also include a statement like "These modifications are licensed under the TAPR Open Hardware License."</p></li> | ||
+ | <li><p>You must include any new files you created, including any manufacturing files (such as Gerber files) you create in the course of making products.</p></li> | ||
+ | <li><p>You must include both "before" and "after" versions of all files you modified*.</p></li> | ||
+ | <li><p>You may include files in proprietary formats, but you must also include open format versions (such as Gerber, ASCII, Postscript, or PDF) if your tools can create them.</p></li> | ||
+ | <p style="font-size:80%">* Here it could be easier to link to the original version. Github allows you to do this by “forking” existing repositories to a new one. If you want to contribute back, you can send your changes back by sending a so-called "pull request" back to the original repository as a request to pull your new code into the original repo.<br>[1] Tapr.org, (2015). The TAPR Open Hardware License. <a href="http://-www.tapr.org/ohl.html" class="blue">[online]</a> [Accessed 23 Aug. 2015].</p> | ||
+ | </div></div></section> | ||
+ | |||
+ | <section style="background-color:white" id="CERNTAPR"> | ||
+ | <div class="slide"> | ||
+ | <div style="width: 80%; margin: 30px 50px;color:#000;min-height:0px"> | ||
+ | <h2>Choosing a hardware-specific Copyleft license: CERN or TAPR</h2> | ||
+ | <p>Overall, the Copyleft requirements ensure that nobody is denied the rights to access the product and its documentation, including all downstream versions. In this sense the two hardware licenses (CERN and TAPR) are similar. The most significant difference between the TAPR OHL and the CERN OHL is that the TAPR OHL attempts to deal directly with the patent aspect of hardware licensing, and currently is the only license to do so [1]. As mentioned previously, the aspects of hardware such as manufacture and use mean that it is not covered by copyright, and instead must be regulated under patent law*.</p> | ||
+ | <p>This makes the license extremely powerful if the original creator of the hardware patented their creation: they can waive their right to IP rights and provide full access to all downstream licenses. However, a problem arises when the Licensor does not have patent rights over the creation [1]. The cost and complexity of obtaining a license a significant obstacle that the creator must attempt to overcome if they want to patent their creation. If anyone else asserts IP rights over the creation under license, then access to the creation is no longer universal under the TAPR OHL.</p> | ||
+ | <p>Ultimately the choice is yours: the TAPR OHL is particularly effective if the patent rights for the original work belong to the licensor, but it also has its drawbacks. As a license TAPR is older, but the CERN OHL has the backing of a strong community of physicists and does not deal as directly with patent rights.</p> | ||
+ | <p>For more information on TAPR, see <a href="#TAPR" class="blue">here</a>.</p> | ||
+ | <p>For more information on CERN OHL, see <a href="#CERN" class="blue">here</a>.</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> | </div></div></section> | ||
Revision as of 14:31, 12 September 2015