<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Thanks to Raymond, Evan and Andreas for the fast answers..</p>
<ul>
<li>A QGIS project is<b> content </b>and not code, therefore it
is not under the GPL regime and can be copyrighted/licensed
differently from GPL.<br>
<br>
</li>
<li>As an open source developer and a user of PostgreSQL/PostGIS
for many years, I'm 100% aware how GPL works regarding content
and code: created content using a GPL program is <b>not</b>
under GPL, derivative works of code is. (So Andreas, don't
worry, be happy ;-).</li>
</ul>
<p> It was simply how to regard QGIS projects: It is content or is
it code ? <br>
</p>
<p>A very small nibble: What about python code embedded in the
project ? <br>
</p>
<p> </p>
<pre class="moz-signature" cols="72">--
Med venlig hilsen / Kind regards
Bo Victor Thomsen</pre>
<p><br>
</p>
<p><br>
</p>
<div class="moz-cite-prefix">Den 30-10-2019 kl. 13:00 skrev Raymond
Nijssen:<br>
</div>
<blockquote type="cite"
cite="mid:beab2ffd-c8f4-d14a-1b13-c408320fe275@terglobo.nl">S
project (file) is <b class="moz-txt-star"><span
class="moz-txt-tag">*</span>content<span class="moz-txt-tag">*</span></b>
you create with QGIS and not code. And therefore not GPL licensed.
<br>
<br>
You can also write a top secret letter using LibreOffice, right?
<br>
<br>
Just my thoughts, didn't look this up in the license text.
<br>
<br>
Raymond
</blockquote>
<pre class="moz-signature" cols="72">
</pre>
</body>
</html>