Difference between revisions of "Team:Cambridge-JIC/Practices"
KaterinaMN (Talk | contribs) |
KaterinaMN (Talk | contribs) |
||
Line 331: | Line 331: | ||
<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>TAPR OHL Extra Info: TAPR documentation requirements</h2> | <h2>TAPR OHL Extra Info: TAPR documentation requirements</h2> | ||
− | <p>If you create a design that you want to license under the OHL, you should [ | + | <p>If you create a design that you want to license under the OHL, you should [1]:</p> |
<ol type="i"> | <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>Include the OHL document in a file named LICENSE.TXT (or LICENSE.PDF) that is included in the documentation package.</p></li> | ||
Line 340: | Line 340: | ||
<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 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 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 | + | <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> | <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> | </div></div></section> | ||
Revision as of 15:11, 9 September 2015