<div dir="ltr"><div>Commercial FOSS audit tools like Protecode and Blackduck will be able to recognize the SPDX tags, and the Copyright text.</div><div><br></div><div><br></div>In our file ntpsec/devel/hacking.txt :<div><br></div><div>
<p class="inbox-inbox-p1"><span class="inbox-inbox-s1">We use the SPDX convention for inclusion by reference.<span class="inbox-inbox-Apple-converted-space"> </span>You can read </span>about this at</p>
<p class="inbox-inbox-p1"><span class="inbox-inbox-s1"><span class="inbox-inbox-Apple-converted-space"> </span><a href="http://spdx.org/licenses">http://spdx.org/licenses</a></span></p>
<p class="inbox-inbox-p1"><span class="inbox-inbox-s1">When you create a new file, mark it as follows (updating the year) </span>as required:</p>
<p class="inbox-inbox-p1"><span class="inbox-inbox-s1">------------------------------------------------</span></p><p class="inbox-inbox-p1">/* Copyright 2017 by the NTPsec project contributors</p>
<p class="inbox-inbox-p1"><span class="inbox-inbox-s1"><span class="inbox-inbox-Apple-converted-space"> </span>* SPDX-License-Identifier: BSD-2-Clause</span></p>
<p class="inbox-inbox-p1"><span class="inbox-inbox-s1"><span class="inbox-inbox-Apple-converted-space"> </span>*/</span></p>
<p class="inbox-inbox-p1"><span class="inbox-inbox-s1">------------------------------------------------</span></p>
<p class="inbox-inbox-p2"><span class="inbox-inbox-s1"></span><br></p>
<p class="inbox-inbox-p1"><span class="inbox-inbox-s1">For documentation:</span></p>
<p class="inbox-inbox-p2"><span class="inbox-inbox-s1"></span><br></p>
<p class="inbox-inbox-p1"><span class="inbox-inbox-s1">------------------------------------------------</span></p>
<p class="inbox-inbox-p1"><span class="inbox-inbox-s1">// Copyright 2017 by the NTPsec project contributors</span></p>
<p class="inbox-inbox-p1"><span class="inbox-inbox-s1">// SPDX-License-Identifier: CC-BY-4.0</span></p>
<p class="inbox-inbox-p1"><span class="inbox-inbox-s1">------------------------------------------------</span></p><p class="inbox-inbox-p1"><span class="inbox-inbox-s1"><br></span></p><p class="inbox-inbox-p1"><span class="inbox-inbox-s1">Modify as needed for whatever comment syntax the language or markup uses. </span>Good places for these markings are at the end of an extended</p><p class="inbox-inbox-p1"><span class="inbox-inbox-s1">header comment, or at the very top of the file.</span></p><p class="inbox-inbox-p2"><span class="inbox-inbox-s1"></span><br></p><p class="inbox-inbox-p1"><span class="inbox-inbox-s1">When you modify a file, leave existing copyright markings in place - </span>especially all references to Dr. Dave Mills, to Mr. Harlan Stenn, and</p><p class="inbox-inbox-p1"><span class="inbox-inbox-s1">to the Network Time Foundation.</span></p><p class="inbox-inbox-p2"><span class="inbox-inbox-s1"></span><br></p><p class="inbox-inbox-p1"><span class="inbox-inbox-s1">You *may* add a project copyright and replace the inline license </span>with an SPDX tag. For example:</p><p class="inbox-inbox-p2"><span class="inbox-inbox-s1"></span><br></p><p class="inbox-inbox-p1"><span class="inbox-inbox-s1">------------------------------------------------</span></p><p class="inbox-inbox-p1"><span class="inbox-inbox-s1">/* Copyright 2017 by the NTPsec project contributors</span></p><p class="inbox-inbox-p1"><span class="inbox-inbox-s1"><span class="inbox-inbox-Apple-converted-space"> </span>* SPDX-License-Identifier: NTP</span></p><p class="inbox-inbox-p1"><span class="inbox-inbox-s1"><span class="inbox-inbox-Apple-converted-space"> </span>*/</span></p><p class="inbox-inbox-p1"><span class="inbox-inbox-s1">
</span></p><p class="inbox-inbox-p1"><span class="inbox-inbox-s1">------------------------------------------------</span></p><p class="inbox-inbox-p1"><span class="inbox-inbox-s1"><br></span></p></div></div><br><div class="gmail_quote"><div dir="ltr">On Mon, Jan 30, 2017 at 10:44 AM Daniel Poirot <<a href="mailto:dtpoirot@gmail.com">dtpoirot@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto" class="gmail_msg"><div class="gmail_msg"></div><div class="gmail_msg">Commercial FOSS audit tools like Protecode and BlackDuck will match a snippet and attribute to the FOSS project. </div></div><div dir="auto" class="gmail_msg"><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg"><br class="gmail_msg">On Jan 30, 2017, at 12:30 PM, Mark Atwood <<a href="mailto:fallenpegasus@gmail.com" class="gmail_msg" target="_blank">fallenpegasus@gmail.com</a>> wrote:<br class="gmail_msg"><br class="gmail_msg"></div><blockquote type="cite" class="gmail_msg"><div class="gmail_msg"><div dir="ltr" class="gmail_msg">That's... complicated.<div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg">We don't need to have a notice attached to every file, because there is a copyright notice attached to the project as a whole, and there is a notice attached to each repo. Individual files generally don't each need their own notice, since individual files generally no longer get "detached" from a project or tree.</div><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">But, if you were to copy in a substantial amount of text from another source, you should make sure that the copyright from that source is properly declared, right next to the text pulled in.</div><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">Also, however, documentation is a bit unusual in that it is much more likely to be detached and separately distributed from the rest of the project. We should make sure that if the documentation is ever printed out, or is separately displayed on sites like <a href="http://man7.org" class="gmail_msg" target="_blank">man7.org</a>, that a copyright notice should be readable.</div></div></div><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">..m</div></div><br class="gmail_msg"><div class="gmail_quote gmail_msg"><div dir="ltr" class="gmail_msg">On Mon, Jan 30, 2017 at 1:55 AM Hal Murray <<a href="mailto:hmurray@megapathdsl.net" class="gmail_msg" target="_blank">hmurray@megapathdsl.net</a>> wrote:<br class="gmail_msg"></div><blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br class="gmail_msg">
<a href="mailto:fallenpegasus@gmail.com" class="gmail_msg" target="_blank">fallenpegasus@gmail.com</a> said:<br class="gmail_msg">
> Right now our standard copyright text is "Copyright $YEAR_YOU_ARE_WRITING_THI<br class="gmail_msg">
> S by the NTP Project contributors"<br class="gmail_msg">
<br class="gmail_msg">
Should the documentation files have a copyright notice?<br class="gmail_msg">
<br class="gmail_msg">
<br class="gmail_msg">
--<br class="gmail_msg">
These are my opinions. I hate spam.<br class="gmail_msg">
<br class="gmail_msg">
<br class="gmail_msg">
<br class="gmail_msg">
</blockquote></div>
</div></blockquote></div><div dir="auto" class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg"><span class="gmail_msg">_______________________________________________</span><br class="gmail_msg"><span class="gmail_msg">devel mailing list</span><br class="gmail_msg"><span class="gmail_msg"><a href="mailto:devel@ntpsec.org" class="gmail_msg" target="_blank">devel@ntpsec.org</a></span><br class="gmail_msg"><span class="gmail_msg"><a href="http://lists.ntpsec.org/mailman/listinfo/devel" class="gmail_msg" target="_blank">http://lists.ntpsec.org/mailman/listinfo/devel</a></span></div></blockquote></div></blockquote></div>