<div dir="ltr"><div>No problem with your feedback Daniel - can you provide an alternate wording for the FAQ for the mailing list to consider?</div><div><br></div><div><br>While I am more comfortable with a copyright header ... I am old and recognize it is just what I am used to. You can see the policy geotools did after this clarification, filling in a (c) based on file creation date and then leaving it alone.</div><div><br></div><div>As for minimums, from the community projects table we have the following:</div><div><br></div><div>- LICENSE.txt <-- this covers open source. This is both a github convention and used for automated open source audits</div><div>- CONTRIBUTING.txt <-- this covers inclusive development (ie project has thought about having outside contribution). This is a github convention.</div><div>- README.txt <-- recommended :)</div><div><br></div><div><br></div><div><br></div><div><div><div><div class="gmail_extra"><div><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>--</div><div>Jody Garnett</div></div></div></div></div></div>
<br><div class="gmail_quote">On 28 September 2016 at 04:56, Daniel Morissette <span dir="ltr"><<a href="mailto:dmorissette@mapgears.com" target="_blank">dmorissette@mapgears.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Hi Jody,<br>
<br>
While the copyright header may not be a legal requirement, I think it is a best practice that we should strongly encourage to avoid any risk of ambiguity in the interpretation of code ownership and licensing.<br>
<br>
At the minimum, I would reword your text to say "A header that names the project, links to the project page, and references the licence is informative and is strongly recommended."<br>
<br>
Can we also agree on a minimal requirement to have a LICENSE.txt file as part of the source tree and make that an incubation requirement?<br>
<br>
Once again, while this may not be required legally, we need to make sure we reduce the chances of outsiders misinterpreting the copyright and license terms associated with a given piece of code.<br>
<br>
My 0.02$<br>
<br>
Daniel<span class="gmail-"><br>
<br>
<br>
<br>
On 2016-09-28 2:38 AM, Jody Garnett wrote:<br>
</span><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span class="gmail-">
Thanks! I think I can edit that ... oh wait it is a formal document with<br>
a version 1.0 so I need to make a motion.<br>
<br>
Here is an alternate wording - if you are happy with that I can make a<br>
motion to update to version 1.0.1.<br>
<br></span>
*Q: Do we need to ensure there is a copyright and licence headers in<br>
every file?*<br>
*<br>
*<span class="gmail-"><br>
No - copyright headers in source code files are not required to enforce<br>
copyright.<br>
<br>
A header that names the project, links to the project page, and<br>
references the licence is informative is recommended. While not legally<br>
binding this approach can help anyone who found your code via a web search.<br></span>
*<br>
*<span class="gmail-"><br>
This question arrises from the traditional practice of embedding a<br>
copyright and license header in every source file (.cpp and .h for<br>
instance) required in the United States prior to joining the Berne<br></span>
Convention <<a href="https://en.wikipedia.org/wiki/Berne_Convention" rel="noreferrer" target="_blank">https://en.wikipedia.org/wiki<wbr>/Berne_Convention</a>> in 1992. For<span class="gmail-"><br>
more information see GeoTools blog post<br></span>
<<a href="http://geotoolsnews.blogspot.ca/2016/07/copyright-headers-in-source-code-files.html" rel="noreferrer" target="_blank">http://geotoolsnews.blogspot.<wbr>ca/2016/07/copyright-headers-i<wbr>n-source-code-files.html</a>>.<span class="gmail-"><br>
<br>
<br>
--<br>
Jody Garnett<br>
<br>
On 27 September 2016 at 03:22, Tom Kralidis <<a href="mailto:tomkralidis@gmail.com" target="_blank">tomkralidis@gmail.com</a><br></span><span class="gmail-">
<mailto:<a href="mailto:tomkralidis@gmail.com" target="_blank">tomkralidis@gmail.com</a>><wbr>> wrote:<br>
<br>
<br>
Thanks for the clarification. As specified originally, in<br>
<a href="http://www.osgeo.org/incubator/process/codereview.html" rel="noreferrer" target="_blank">http://www.osgeo.org/incubator<wbr>/process/codereview.html</a><br></span>
<<a href="http://www.osgeo.org/incubator/process/codereview.html" rel="noreferrer" target="_blank">http://www.osgeo.org/incubato<wbr>r/process/codereview.html</a>>,<span class="gmail-"><br>
section "Frequently Asked Questions". Snippet:<br>
<br>
Do we need to ensure there is a copyright and licence headers in<br>
every file?<br>
<br>
Projects are expected to embed a copyright and license header in<br>
every source file (.cpp and .h for instance). Machine generated<br>
files (such as lex or yacc output for instance) does not require a<br>
header if it is inconvenient to embed one, but then an effort should<br>
be made to embed a header in the original source file (ie. .l or<br>
.y). There is no need to embed copyright and license headers in<br>
build files (ie. Makefiles, Visual Studio project files), nor in<br>
small documentation fragments (like READMEs). Copyright/license<br>
headers should be included in substantial bodies of documentation if<br>
it can be done in such a way that it doesn't interfere with the<br>
document.<br>
<br>
Thanks<br>
<br>
..Tom<br>
<br>
<br>
On Tue, 27 Sep 2016, Jody Garnett wrote:<br>
<br>
Date: Tue, 27 Sep 2016 02:44:48 -0700<br>
<br>
From: Jody Garnett <<a href="mailto:jody.garnett@gmail.com" target="_blank">jody.garnett@gmail.com</a><br></span>
<mailto:<a href="mailto:jody.garnett@gmail.com" target="_blank">jody.garnett@gmail.com</a><wbr>>><br>
To: Tom Kralidis <<a href="mailto:tomkralidis@gmail.com" target="_blank">tomkralidis@gmail.com</a><br>
<mailto:<a href="mailto:tomkralidis@gmail.com" target="_blank">tomkralidis@gmail.com</a>><wbr>><br>
Cc: "<a href="mailto:incubator@lists.osgeo.org" target="_blank">incubator@lists.osgeo.org</a><br>
<mailto:<a href="mailto:incubator@lists.osgeo.org" target="_blank">incubator@lists.osgeo.<wbr>org</a>>" <<a href="mailto:incubator@lists.osgeo.org" target="_blank">incubator@lists.osgeo.org</a><br>
<mailto:<a href="mailto:incubator@lists.osgeo.org" target="_blank">incubator@lists.osgeo.<wbr>org</a>>><span class="gmail-"><br>
Subject: Re: [Incubator] PyWPS copyright and license headers<br>
requirement<br>
<br>
I expect you were finding the incubation faq? do you have a link<br>
to any<br>
page that led you astray?<br>
<br>
Here was the blog post I was looking for:<br>
<br>
-<br>
<a href="http://geotoolsnews.blogspot.ca/2016/07/copyright-headers-in-source-code-files.html" rel="noreferrer" target="_blank">http://geotoolsnews.blogspot.c<wbr>a/2016/07/copyright-headers-in<wbr>-source-code-files.html</a><br>
<<a href="http://geotoolsnews.blogspot.ca/2016/07/copyright-headers-in-source-code-files.html" rel="noreferrer" target="_blank">http://geotoolsnews.blogspot.<wbr>ca/2016/07/copyright-headers-i<wbr>n-source-code-files.html</a>><br>
<br>
That should be super clear :)<br>
<br>
--<br>
Jody Garnett<br>
<br>
On 21 September 2016 at 08:21, Tom Kralidis<br></span><span class="gmail-">
<<a href="mailto:tomkralidis@gmail.com" target="_blank">tomkralidis@gmail.com</a> <mailto:<a href="mailto:tomkralidis@gmail.com" target="_blank">tomkralidis@gmail.com</a>><wbr>> wrote:<br>
<br>
<br>
Thanks for the clarification. I imagine the FAQ will be<br>
updated over time.<br>
<br>
Thanks<br>
<br>
..Tom<br>
<br>
On Wed, 21 Sep 2016, Jody Garnett wrote:<br>
<br>
Date: Wed, 21 Sep 2016 14:59:12 +0000<br>
<br>
From: Jody Garnett <<a href="mailto:jody.garnett@gmail.com" target="_blank">jody.garnett@gmail.com</a><br></span>
<mailto:<a href="mailto:jody.garnett@gmail.com" target="_blank">jody.garnett@gmail.com</a><wbr>>><br>
To: Tom Kralidis <<a href="mailto:tomkralidis@gmail.com" target="_blank">tomkralidis@gmail.com</a><br>
<mailto:<a href="mailto:tomkralidis@gmail.com" target="_blank">tomkralidis@gmail.com</a>><wbr>><br>
Cc: "<a href="mailto:incubator@lists.osgeo.org" target="_blank">incubator@lists.osgeo.org</a><br>
<mailto:<a href="mailto:incubator@lists.osgeo.org" target="_blank">incubator@lists.osgeo.<wbr>org</a>>"<br>
<<a href="mailto:incubator@lists.osgeo.org" target="_blank">incubator@lists.osgeo.org</a><br>
<mailto:<a href="mailto:incubator@lists.osgeo.org" target="_blank">incubator@lists.osgeo.<wbr>org</a>>><span class="gmail-"><br>
Subject: Re: [Incubator] PyWPS copyright and license<br>
headers requirement<br>
<br>
<br>
It is not a requirement at all. There is an advantage to<br>
listing the<br>
license at the top of each file.<br>
<br>
Can you read the links provided again and tell me what I<br>
can do to be more<br>
clear?<br>
On Tue, Sep 20, 2016 at 12:34 PM Tom Kralidis<br></span>
<<a href="mailto:tomkralidis@gmail.com" target="_blank">tomkralidis@gmail.com</a> <mailto:<a href="mailto:tomkralidis@gmail.com" target="_blank">tomkralidis@gmail.com</a>><wbr>><span class="gmail-"><br>
wrote:<br>
<br>
Jody: thanks for the info. So to clarify, having a<br>
copyright and<br>
<br>
license header in source code files is a hard<br>
requirement correct?<br>
<br>
On Mon, Sep 19, 2016 at 9:39 PM, Jody Garnett<br></span>
<<a href="mailto:jody.garnett@gmail.com" target="_blank">jody.garnett@gmail.com</a> <mailto:<a href="mailto:jody.garnett@gmail.com" target="_blank">jody.garnett@gmail.com</a><wbr>>><span class="gmail-"><br>
wrote:<br>
<br>
We had a clarifications via OSGeo legal in<br>
August. I shared it with the<br>
mailing list here and wrote a geotools blog post<br>
(which was the project<br>
seeking clarification). GeoServer, and I expect<br>
other OSGeo project will<br>
match this policy over time as is less work.<br>
<br>
<br>
<a href="http://geotoolsnews.blogspot.com.au/2016/06/geotools-header-" rel="noreferrer" target="_blank">http://geotoolsnews.blogspot.c<wbr>om.au/2016/06/geotools-header-</a><br>
<<a href="http://geotoolsnews.blogspot.com.au/2016/06/geotools-header-" rel="noreferrer" target="_blank">http://geotoolsnews.blogspot.<wbr>com.au/2016/06/geotools-header<wbr>-</a>><br>
<br>
policy-updated.html<br>
<br>
<br>
<br>
<a href="https://github.com/geotools/geotools/wiki/Updates-to-Copyrig" rel="noreferrer" target="_blank">https://github.com/geotools/ge<wbr>otools/wiki/Updates-to-Copyrig</a><br>
<<a href="https://github.com/geotools/geotools/wiki/Updates-to-Copyrig" rel="noreferrer" target="_blank">https://github.com/geotools/g<wbr>eotools/wiki/Updates-to-Copyri<wbr>g</a>><br>
<br>
ht-Header-Policy<br>
<br>
<br>
<a href="https://github.com/geoserver/geoserver/wiki/GSIP%20147" rel="noreferrer" target="_blank">https://github.com/geoserver/g<wbr>eoserver/wiki/GSIP%20147</a><br>
<<a href="https://github.com/geoserver/geoserver/wiki/GSIP%20147" rel="noreferrer" target="_blank">https://github.com/geoserver/<wbr>geoserver/wiki/GSIP%20147</a>><br>
<br>
Do you have any questions?<br>
On Tue, Sep 20, 2016 at 12:44 AM Tom Kralidis<br>
<<a href="mailto:tomkralidis@gmail.com" target="_blank">tomkralidis@gmail.com</a><br></span>
<mailto:<a href="mailto:tomkralidis@gmail.com" target="_blank">tomkralidis@gmail.com</a>><wbr>><span class="gmail-"><br>
<br>
wrote:<br>
<br>
<br>
Hi all: we are discussing the requirement of<br>
copyright/license headers<br>
as part of PyWPS incubation [1] and as a<br>
result looking for<br>
<br>
clarification.<br>
<br>
<br>
<br>
The FAQ in [2] says that we need this for<br>
every source file. While I<br>
fully agree with this practice there are<br>
questions and examples of<br>
other 'serious' (<- my word :) projects<br>
which do not adhere to this,<br>
<br>
like<br>
<br>
<br>
the Django project (e.g. in [3]).<br>
<br>
<br>
Thoughts? Am I (aside from my personal<br>
preference of always having<br>
<br>
these<br>
<br>
<br>
headers) interpreting this requirement<br>
incorrectly? If not, is there<br>
<br>
background/context which roots the requirement?<br>
<br>
Please advise.<br>
<br>
Thanks<br>
<br>
..Tom<br>
<br>
<br>
[1]<br></span>
<a href="https://github.com/geopython/pywps/issues/187" rel="noreferrer" target="_blank">https://github.com/geopython/p<wbr>ywps/issues/187</a> <<a href="https://github.com/geopython/pywps/issues/187" rel="noreferrer" target="_blank">https://github.com/geopython/<wbr>pywps/issues/187</a>><span class="gmail-"><br>
[2]<br>
<a href="http://www.osgeo.org/incubator/process/codereview.html" rel="noreferrer" target="_blank">http://www.osgeo.org/incubator<wbr>/process/codereview.html</a><br>
<<a href="http://www.osgeo.org/incubator/process/codereview.html" rel="noreferrer" target="_blank">http://www.osgeo.org/incubato<wbr>r/process/codereview.html</a>><br>
[3]<br>
<br>
<a href="https://github.com/django/django/blob/master/django/db/model" rel="noreferrer" target="_blank">https://github.com/django/djan<wbr>go/blob/master/django/db/model</a><br>
<<a href="https://github.com/django/django/blob/master/django/db/model" rel="noreferrer" target="_blank">https://github.com/django/dja<wbr>ngo/blob/master/django/db/mode<wbr>l</a>><br>
<br>
s/__init__.py<br>
<br>
______________________________<wbr>_________________<br>
<br>
Incubator mailing list<br>
<a href="mailto:Incubator@lists.osgeo.org" target="_blank">Incubator@lists.osgeo.org</a><br></span>
<mailto:<a href="mailto:Incubator@lists.osgeo.org" target="_blank">Incubator@lists.osgeo.<wbr>org</a>><br>
<a href="http://lists.osgeo.org/mailman/listinfo/incubator" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman<wbr>/listinfo/incubator</a><span class="gmail-"><br>
<<a href="http://lists.osgeo.org/mailman/listinfo/incubator" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailma<wbr>n/listinfo/incubator</a>><br>
<br>
<br>
--<br>
--<br>
Jody Garnett<br>
<br>
<br>
--<br>
<br>
--<br>
Jody Garnett<br>
<br>
<br>
<br>
<br>
<br>
<br>
______________________________<wbr>_________________<br>
Incubator mailing list<br>
<a href="mailto:Incubator@lists.osgeo.org" target="_blank">Incubator@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/incubator" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman<wbr>/listinfo/incubator</a><br>
<br>
</span></blockquote><span class="gmail-HOEnZb"><font color="#888888">
<br>
<br>
-- <br>
Daniel Morissette<br>
<a href="http://www.mapgears.com/" rel="noreferrer" target="_blank">http://www.mapgears.com/</a><br>
T: <a href="tel:%2B1%20418-696-5056%20%23201" value="+14186965056" target="_blank">+1 418-696-5056 #201</a><br>
<br>
<a href="http://evouala.com/" rel="noreferrer" target="_blank">http://evouala.com/</a> - Location Intelligence Made Easy</font></span><div class="gmail-HOEnZb"><div class="gmail-h5"><br>
______________________________<wbr>_________________<br>
Incubator mailing list<br>
<a href="mailto:Incubator@lists.osgeo.org" target="_blank">Incubator@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/incubator" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman<wbr>/listinfo/incubator</a></div></div></blockquote></div><br></div></div></div></div></div>