[Psc] Sencha offer to solve GPL issue for GeoExt 3

[Christian Mayer]

Hi Marc,

thanks for your comments. I am not sure how all this can work. In case someone will pay the licenses will there be two versions of GeoExt or will the current code be relicensed? Then how external contributions are handled since not everybody has the license? Questions over questions...
Maybe you are right and we create an issue describing the situation and we will see what happens. Can you create such an issue?

Cheers,
Chris

Am 9. November 2015 09:11:20 MEZ, schrieb Marc Jansen <jansen at terrestris.de>:
>Hey Chris,
>
>sorry for the late response. Find comments inline.
>
>On 30/10/15 10:39, Christian Mayer wrote:
>> Hi everyone,
>>
>> 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].
>> 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:
>>
>> >>
>> 1._The GeoExt Solution: _If GeoExt buys our Pro Edition (5-pack) and 
>> stay current on maintenance/support we will provide the following 
>> conditions/restrictions:
>>
>> 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.
>>
>> 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.
>>
>> 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
>>
>> Eyeworkers can then provide the commercial version of the mapping 
>> application as part of your overall Ext JS application/service for 
>> your customers.
>> <<
>>
>> 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.
>
>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:
>
>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.
>
>How does that sound?
>
>Best,
>Marc
>
>>
>> But maybe you have other opinions and thus I do not want to deny you 
>> this information.
>>
>> Regards,
>> Chris
>>
>> [1] http://www.geoext.org/pipermail/dev/2015-June/001286.html
>>
>>
>>
>>
>> _______________________________________________
>> Psc mailing list
>> Psc at geoext.org
>> http://www.geoext.org/cgi-bin/mailman/listinfo/psc
>
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Psc mailing list
>Psc at geoext.org
>http://www.geoext.org/cgi-bin/mailman/listinfo/psc