<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">This is weird, since what they are suggesting is actually what the purpose was of their open source exemption.<div class=""><br class=""></div><div class="">Why not keep BSD then, like we have already in older versions?<br class=""><div class=""><div class=""><div class=""><div class=""><br class=""></div><div class="">Best regards,</div><div class="">Bart</div><div class=""><br class=""></div><div class=""><div><blockquote type="cite" class=""><div class="">On 06 Apr 2016, at 10:51, Marc Jansen <<a href="mailto:jansen@terrestris.de" class="">jansen@terrestris.de</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="content-type" content="text/html; charset=utf-8" class="">
<div text="#000000" bgcolor="#FFFFFF" class="">
Hi PSC-members,<br class="">
<br class="">
As I have discussed with you
(<a class="moz-txt-link-freetext" href="http://www.geoext.org/pipermail/psc/2016-January/000194.html">http://www.geoext.org/pipermail/psc/2016-January/000194.html</a>), I
went on to negotiate our licensing options with the Sencha people.<br class="">
<br class="">
Here is a short recap of the current situation:<br class="">
<ul class="">
<li class="">Since the Exception for OSS is no longer existing, GeoExt
switched to be licensed as GPL software
(<a class="moz-txt-link-freetext" href="https://github.com/geoext/geoext3/pull/16">https://github.com/geoext/geoext3/pull/16</a>)<br class="">
</li>
<li class="">This might be problematic when people want to use GeoExt code
with their correctly bought licensed software</li>
</ul><p class="">After some back and forth a Sencha official proposed the
following:<br class="">
</p>
<blockquote class=""><p class="">> So if geoExt does not include our code, you could dual
license it GPLv3 and Apache - the GPLv3 version to go with Ext
JS GPLv3 and the Apache version to go with Ext JS commercial for
closed source uses. You'd probably want to make this clear to
your users so they get the right version and don't wind up with
GPL issues. Apache could be Apache, MIT, BSD, free commercial,
or anything that allows you to combine it with other work and go
closed source (technically, going closed source is
redistributing under a commercial license). <br class="">
</p>
</blockquote><p class="">Effectively this would mean that we would dual license GeoExt,
and the license of the actually used ExtJS determines which
license from GeoExt actually applies to your code.<br class="">
</p><p class="">I personally feel this is a wonderful option we get back from
Sencha here and I am very grateful that they offer us this in my
communication with them.<br class="">
</p><p class="">Here is a rough outline what we could do starting from now:<br class="">
</p>
<ul class="">
<li class="">Decide on whether we want to be dual licensed as outlined
above (A simple +1, 0, -1 vote of the PSC in response to this
mail would be enough, I guess)</li>
<li class="">Decide which other license suits our need. Since Apache was
brought up by Sencha, I'd be willing to take that one</li>
<li class="">Discuss the wording of how we document the licensing
everywhere (Sencha and I have talked this through but in the end
we decide and simply make it totally cklear to our users)<br class="">
</li>
<li class="">Provide PR that actually does the change</li>
<ul class="">
<li class="">We should make it absolutely clear what the options are (see
above)<br class="">
</li>
<li class="">We should document this at several places</li>
<ul class="">
<li class="">LICENSE.md at the repository root<br class="">
</li>
<li class="">LICENSE-FAQ.md at the repository root<br class="">
</li>
<li class="">every source-file header</li>
<li class="">on the homepage</li>
<li class="">some other place?<br class="">
</li>
</ul>
</ul>
<li class="">Do we need to get the appreciation of all actual committers
again?</li>
</ul><p class="">What are your thoughts?<br class="">
</p><p class="">Best,<br class="">
Marc<br class="">
<br class="">
</p><p class="">PS: Once this is settled, I really want to have a v3.0.0
released. And then switch to a release often-strategy. But thats
stuff for another day.<br class="">
</p><p class=""><br class="">
</p>
</div>
_______________________________________________<br class="">Psc mailing list<br class=""><a href="mailto:Psc@geoext.org" class="">Psc@geoext.org</a><br class="">http://www.geoext.org/cgi-bin/mailman/listinfo/psc<br class=""></div></blockquote></div><br class=""></div></div></div></div></div></body></html>