<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>Hi all,</p>
    <p>thanks for this discussion. I'm also pretty sure getting a
      property transfer from all developers will be difficult if not
      impossible (quite a few devs even disappeared from the radar, not
      easy to find them again).</p>
    <p>A possible intermediate step would be to:</p>
    <p>* get the transfer of code property to QGIS.ORG only from those
      developers who are happy to do it</p>
    <p>* ask a more specific question to others (e.g. are you willing to
      move from GPL2 to GPL3?).</p>
    <p>I think this is more feasible, will help building trust, will
      help moving forward, and will make it easier (less people to
      contact) to do further changes in the future.</p>
    <p>All the best.</p>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 11/9/18 9:31 AM, Andreas Neumann
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:197d5b83-b510-b834-5d0f-6f47b00f33a7@carto.net">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <p>However, if we just talk about moving from GPL v2 to v3 - I
        think this would definitely be possible.</p>
      <p>A change to a more permissive license is a different thing.
        There you need really, really good arguments to convince the
        majority of the voting members, I think.</p>
      <p>Please don't see this as a PSC opinion - it is my own, personal
        opinion, and as I said, the PSC doesn't have an official
        "opinion" yet on this topic.</p>
      <p>Greetings,</p>
      <p>Andreas<br>
      </p>
      <div class="moz-cite-prefix">Am 09.11.18 um 09:21 schrieb Andreas
        Neumann:<br>
      </div>
      <blockquote type="cite"
        cite="mid:d62d92fb-c6eb-8431-17c4-195f285617fd@carto.net">
        <meta http-equiv="Content-Type" content="text/html;
          charset=UTF-8">
        <p>Hi,</p>
        <p>We talked about this very, very briefly on the PSC - and I
          can already say that the topic is quite controversial within
          the PSC.</p>
        <p>I really don't see consensus here at the moment. And even if
          the PSC wants to move in this direction, it is the voting
          members who need to agree to it - and I personally doubt that
          a majority of them would agree. The PSC (or any voting or
          community member) can suggest such changes, but it is the
          voting members who decide/vote on it.<br>
        </p>
        <p>@Nyall - if you want to raise such a voting, you are welcome
          to do so. But it needs a proper listing of pros and cons of
          such a move - and need to be prepared to give both sides (the
          proponents and the opponents of such a change) a fair chance
          to raise their arguments.</p>
        <p>There are other open source projects that did such changes -
          so it seems to be possible. But there is a fair chance that it
          will create a lot of harm along the process (e.g. split the
          community into two parts).</p>
        <p>Andreas<br>
        </p>
        <br>
        <div class="moz-cite-prefix">Am 09.11.18 um 09:06 schrieb
          Alessandro Pasotti:<br>
        </div>
        <blockquote type="cite"
cite="mid:CAL5Q673rQPdC2qLDCHcHuX9eZo+bZQHiiZY81zReT810Rs9QnA@mail.gmail.com">
          <meta http-equiv="content-type" content="text/html;
            charset=UTF-8">
          <div dir="ltr">
            <div class="gmail_quote">
              <div dir="ltr">On Fri, Nov 9, 2018 at 8:52 AM Nyall Dawson
                <<a href="mailto:nyall.dawson@gmail.com"
                  moz-do-not-send="true">nyall.dawson@gmail.com</a>>
                wrote:<br>
              </div>
              <blockquote class="gmail_quote" style="margin:0 0
                0&#xA;&#xA; .8ex;border-left:1px #ccc
                solid;padding-left:1ex"><br>
                <br>
                Your concerns are very valid, but could we defer this to
                a different<br>
                discussion? I really want to avoid this becoming an
                us-vs-apple/debate<br>
                about the merit of specific licenses, and instead allow
                it to focus<br>
                solely on the question: "should the qgis org, with all
                the checks and<br>
                balances it has in place, have the power to relicense
                the QGIS<br>
                codebase (or not)"?.<br>
                <br>
                Nyall<br>
                <br>
              </blockquote>
            </div>
            <br>
            <div>I'm -1 on this proposal, it's not that I don't trust
              the PSC (that have always done an amazing job!),  but
              perhaps because I'm Italian, I never fully trust the
              "government", to me the GPL license is like the
              constitution and it's there to protect from the possible
              abuses from the "government".</div>
            <div><br>
            </div>
            <div>Also, I particularly didn't like the "(8. Replace
              existing code from any non-signing contributors)", it
              sounds like "you don't like that? We don't need you".</div>
            <div><br>
            </div>
            <div>-- </div>
            <div dir="ltr" class="gmail_signature"
              data-smartmail="gmail_signature">Alessandro Pasotti<br>
              w3:   <a href="http://www.itopen.it" target="_blank"
                moz-do-not-send="true">www.itopen.it</a></div>
          </div>
          <br>
          <fieldset class="mimeAttachmentHeader"></fieldset>
          <pre class="moz-quote-pre" wrap="">_______________________________________________
QGIS-Developer mailing list
<a class="moz-txt-link-abbreviated" href="mailto:QGIS-Developer@lists.osgeo.org" moz-do-not-send="true">QGIS-Developer@lists.osgeo.org</a>
List info: <a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a>
Unsubscribe: <a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a></pre>
        </blockquote>
        <br>
        <fieldset class="mimeAttachmentHeader"></fieldset>
        <pre class="moz-quote-pre" wrap="">_______________________________________________
QGIS-Developer mailing list
<a class="moz-txt-link-abbreviated" href="mailto:QGIS-Developer@lists.osgeo.org" moz-do-not-send="true">QGIS-Developer@lists.osgeo.org</a>
List info: <a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a>
Unsubscribe: <a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a></pre>
      </blockquote>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <pre class="moz-quote-pre" wrap="">_______________________________________________
QGIS-Developer mailing list
<a class="moz-txt-link-abbreviated" href="mailto:QGIS-Developer@lists.osgeo.org">QGIS-Developer@lists.osgeo.org</a>
List info: <a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/qgis-developer">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a>
Unsubscribe: <a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/qgis-developer">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a></pre>
    </blockquote>
    <pre class="moz-signature" cols="72">-- 
Paolo Cavallini - <a class="moz-txt-link-abbreviated" href="http://www.faunalia.eu">www.faunalia.eu</a>
QGIS.ORG Chair:
<a class="moz-txt-link-freetext" href="http://planet.qgis.org/planet/user/28/tag/qgis%20board/">http://planet.qgis.org/planet/user/28/tag/qgis%20board/</a></pre>
  </body>
</html>