<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi<div class=""><br class=""></div><div class="">I am -0 on it. Its probably OK legally but looks a bit confusing to me to mix and match FOSS and proprietary software in the same installer. So if the question is "am I allowed to do it" then yes based on Nathan's research, if the question is "how do I feel about it" my response would be "why not just ship two installers?".</div><div class=""><br class=""></div><div class="">Regards</div><div class=""><br class=""></div><div class="">Tim<br class=""><div><blockquote type="cite" class=""><div class="">On 09 Jan 2017, at 4:52 PM, Neumann, Andreas <<a href="mailto:a.neumann@carto.net" class="">a.neumann@carto.net</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" class=""><div style="font-size: 10pt; font-family: Verdana,Geneva,sans-serif" class=""><p class="">Hi Nathan,</p><p class="">Thanks for your reply and the pointer to the discussion. I wasn't sure about it.</p><p class="">So as long as the GPL and NON-GPL software doesn't link each others libraries, it should be fine to bundle the two in one single installer?</p><p class="">I'll wait for other comments before I reply with a definite answer.</p><p class="">Andreas</p><p class="">On 2017-01-09 10:36, Nathan Woodrow wrote:</p>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0" class=""><!-- html ignored --><!-- head ignored --><!-- meta ignored --><p dir="ltr" class="">Hey,</p><p dir="ltr" class="">This is fine. There is nothing wrong with making your own installer that bundles other software together with QGiS. QGIS is still GPL that doesn't change but creating your own installer is your own work.</p><p dir="ltr" class="">I don't think we should consider installers etc derived work. </p><p dir="ltr" class="">Nathan.</p>
<br class="">
<div class="gmail_quote">
<div dir="ltr" class="">On Mon, 9 Jan 2017 7:30 pm Neumann, Andreas <<a href="mailto:a.neumann@carto.net" class="">a.neumann@carto.net</a>> wrote:</div>
<blockquote class="gmail_quote" style="margin: 0 0 0 .8ex; border-left: 1px #ccc solid; padding-left: 1ex;">
<div class="gmail_msg" style="font-size: 10pt; font-family: Verdana,Geneva,sans-serif;"><p class="gmail_msg">Hi,</p><p class="gmail_msg">One of our recent QGIS bronze sponsors (<a class="gmail_msg" href="http://www.geos-hellinge.de/">http://www.geos-hellinge.de/</a>) asks me if he is allowed to bundle the QGIS installer with his own proprietary geodetic software, to allow a good integration of the two systems.</p><p class="gmail_msg">I said that most likely, that this is not possible, but that I will ask the QGIS PSC.</p><p class="gmail_msg">Am I right, that a combined installer of GPL with proprietary software is not possible? But if he provides something like a batch file that first installs the proprietary software and then runs QGIS 2.14 LTR as a separate independent installer, this may be allowed - is this correct?</p><p class="gmail_msg">Here is the original question in german language: "Ich habe noch eine Frage zur Installation von QGIS: Ich würde gerne eine QGIS-Installation zusammen mit unserem vermessungstechnischen Programmsystem KAVDI in einem Setup für unsere Kunden bereitstellen. Das hätte den Vorteil, dass das Zusammenspiel zwischen KAVDI und QGIS "Out of the box" funktioniert.<br class="gmail_msg"> Ist das lizenztechnisch erlaubt ?"</p><p class="gmail_msg">Thanks for a clarification,</p><p class="gmail_msg">Andreas</p>
<div class="gmail_msg"> </div>
</div>
_______________________________________________<br class="gmail_msg"> Qgis-psc mailing list<br class="gmail_msg"><a class="gmail_msg" href="mailto:Qgis-psc@lists.osgeo.org">Qgis-psc@lists.osgeo.org</a><br class="gmail_msg"><a class="gmail_msg" href="http://lists.osgeo.org/mailman/listinfo/qgis-psc">http://lists.osgeo.org/mailman/listinfo/qgis-psc</a></blockquote>
</div>
</blockquote><div class=""> <br class="webkit-block-placeholder"></div>
<div class=""> </div>
</div>
_______________________________________________<br class="">Qgis-psc mailing list<br class=""><a href="mailto:Qgis-psc@lists.osgeo.org" class="">Qgis-psc@lists.osgeo.org</a><br class="">http://lists.osgeo.org/mailman/listinfo/qgis-psc</div></blockquote></div><br class=""><div class="">
<span><img apple-inline="yes" id="2E3C18CD-F84D-4847-B371-EB58893CC78D" src="cid:879A6E78-CA46-47B2-AA0E-1810BD833229" class=""></span><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; line-height: normal; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="font-weight: normal;" class=""><br class="Apple-interchange-newline"><br class="Apple-interchange-newline">---</div><div style="font-weight: normal;" class=""><br class=""></div><div class=""><b class="">Tim Sutton</b></div><div style="font-weight: normal;" class="">QGIS Project Steering Committee Chair</div><div style="font-weight: normal;" class=""><a href="mailto:tim@qgis.org" class="">tim@qgis.org</a></div><div style="font-weight: normal;" class=""><br class=""></div></div><br class="Apple-interchange-newline" style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; line-height: normal;"><br class="Apple-interchange-newline" style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
</div>
<br class=""></div></body></html>