<div dir="auto">Hi,<div dir="auto"><br></div><div dir="auto">Although I think you can safely use and replicate any part of the documentation, including code snippets, I think you spotted an important issue.</div><div dir="auto"><br></div><div dir="auto">I do believe we should add a licence to all our documentation. Maybe a creative commons license.</div><div dir="auto"><br></div><div dir="auto">I have included the PSC mailing list in this reply, maybe they already have a position about this subject.</div><div dir="auto"><br></div><div dir="auto">Alexandre Neto</div><div dir="auto"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">A sexta, 2/07/2021, 18:30, Malte Ziebarth <<a href="mailto:ziebarth@gfz-potsdam.de">ziebarth@gfz-potsdam.de</a>> escreveu:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<p>Dear all,</p>
<p>first off, thank you all for all the great work that went into
QGIS!</p>
<p>I am currently writing a Python plugin that I intend to make
publicly<br>
available in the plugin repository. I started developing the
plugin by<br>
adapting the examples from the PyQGIS Cookbook, specifically this
page:</p>
<p><a href="https://docs.qgis.org/3.16/en/docs/pyqgis_developer_cookbook/plugins/plugins.html#writing-a-plugin" target="_blank" rel="noreferrer">https://docs.qgis.org/3.16/en/docs/pyqgis_developer_cookbook/plugins/plugins.html#writing-a-plugin</a><br>
</p>
<p>Now the problem that I encountered with that is the license of
the skeleton<br>
code (i.e. __init__.py and mainPlugin.py). The code does not
actually contain<br>
a license header and the documentation page itself contains only
the<br>
very general copyright information</p>
<p>"© Copyright 2002-now, QGIS project. <span>
Last updated on Jul 02, 2021 09:02."<br>
</span></p>
<p><span>with no further licensing information.<br>
</span></p>
<p><span>I guess that the intention of this part
of documentation is for people to<br>
have an easy start developing plugins which can then be
contributed back<br>
to the community under GPL license. This is just what I am
planning to<br>
do. However, trying to put this into a correct license header is
currently<br>
giving me a bit of a headache.</span></p>
<p><span>Maybe someone here in this mailing list
has some advice about this issue,<br>
and maybe even the person/people who wrote this piece of code
can clarify?<br>
Any help would be greatly appreciated!</span></p>
<p><span>Kind regards<br>
Malte Ziebarth<br>
</span></p>
<pre cols="72">--
Malte J. Ziebarth
Section 2.6
Tel.: +49 (0)331/288-28634
E-Mail: <a href="mailto:ziebarth@gfz-potsdam.de" target="_blank" rel="noreferrer">ziebarth@gfz-potsdam.de</a>
___________________________________
Helmholtz-Zentrum Potsdam
Deutsches GeoForschungsZentrum GFZ
Stiftung des öff. Rechts Land Brandenburg
Telegrafenberg, 14473 Potsdam</pre>
</div>
_______________________________________________<br>
QGIS-Developer mailing list<br>
<a href="mailto:QGIS-Developer@lists.osgeo.org" target="_blank" rel="noreferrer">QGIS-Developer@lists.osgeo.org</a><br>
List info: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
Unsubscribe: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
</blockquote></div>