<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hey Chris,<br>
<br>
sorry for the late response. Find comments inline.<br>
<br>
On 30/10/15 10:39, Christian Mayer wrote:<br>
</div>
<blockquote cite="mid:56333AB4.7090706@meggsimum.de" type="cite">
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
Hi everyone,<br>
<br>
as you all know we had to switch the license of GeoExt 3 from BSD
to GPLv3 because Sencha removed the FLOSS exception for ExtJS 6
which allowed us to use BSD although we build GeoExt upon a GPL
product. GPL is maybe not the best solution for GeoExt and thus we
(mainly Bart) had mail contact to Sencha if there is a possibility
to run GeoExt under BSD without any success. The topic has salso
been discussed on the dev-list [1]. <br>
Meanwhile the CEO of the German Sencha partner company
"eyeworkers", which I know more or less well, had the possibility
to talk to the CEO of Sencha and explained him the situation. This
is what Sencha offers the GeoExt community:<br>
<br>
>><br>
<span lang="EN-US"><span style="mso-list:Ignore">1.<span
style="font:7.0pt "Times New Roman""> </span></span></span><u><span
lang="EN-US">The GeoExt Solution: </span> </u><span
lang="EN-US">If GeoExt buys our Pro Edition (5-pack) and stay
current on maintenance/support we will provide the following
conditions/restrictions:<o:p></o:p></span>
<p class="MsoListParagraph" style="margin-left:72.0pt"><span
lang="EN-US">Up to 25 GeoExt developers can use the license to
develop a commercial version of the mapping product. They
cannot provide the licenses to anyone outside of their
organization.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:72.0pt"><span
lang="EN-US">The license is restricted to just this mapping
application. If they want to provide another commercial
application they need to buy another license of this type.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:72.0pt"><span
lang="EN-US">We need to have a call with GeoExt on this
licensing so everyone understands the benefits and obligations
and to also make sure we establish a line of communications to
help them<o:p></o:p></span></p>
<span lang="EN-US">Eyeworkers can then provide the commercial
version of the mapping application as part of your overall Ext
JS application/service for your customers.<br>
<<<br>
<br>
My personal opinion is that this is not a suitable option for
GeoExt to build upon a commercial license or even make a closed
source pendant of GeoExt, which can be used in commercial
projects.<br>
</span></blockquote>
<br>
I share your thoughts, Chris. I'd happily provide a commercial
compliant (but still OSS) version of Geoext3, but I really doubt
that we get the money needed for this. We should probably simply do
the following:<br>
<br>
Create a sticky issue on github, so the offer gets visibility. If
some company decides it cannot live with the GPL, we may point them
to the issue and say, hey if yo'd spend that amount of money on the
Sencha livcenses, we'll build a compliant version.<br>
<br>
How does that sound?<br>
<br>
Best,<br>
Marc<br>
<br>
<blockquote cite="mid:56333AB4.7090706@meggsimum.de" type="cite"><span
lang="EN-US"> <br>
But maybe you have other opinions and thus I do not want to deny
you this information.<br>
<br>
Regards,<br>
Chris<br>
</span><br>
[1] <a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://www.geoext.org/pipermail/dev/2015-June/001286.html">http://www.geoext.org/pipermail/dev/2015-June/001286.html</a><br>
<pre class="moz-signature" cols="72">
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Psc mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Psc@geoext.org">Psc@geoext.org</a>
<a class="moz-txt-link-freetext" href="http://www.geoext.org/cgi-bin/mailman/listinfo/psc">http://www.geoext.org/cgi-bin/mailman/listinfo/psc</a>
</pre>
</blockquote>
<br>
</body>
</html>