[iks-community] Aloha license Re: IKS Semantic Editor hackathon in Helsinki on July 26-27

[Stéphane Croisier]

Hi Henri,

It really depends of the reciprocity schema you 
want to enforce for the Aloha project. But if 
Aloha is done from a very modular and extensible 
manner, the GPL could cause issues for commercial 
vendors (or dual-licensed vendors) which may want 
to add new modules (e.g. a custom selectors 
directly connected to their proprietary DAM or 
DMS). In such a case, we never really know if the 
viral effect of the GPL will apply or not. In 
case of doubt, vendors sometimes prefer to avoid 
taking any legal risk even if the project looks like being promising.

If you want to be friendly with anyone a 
dual-license BSD + GPL could be just fine ;-)

Cheers,
Stéphane

At 09:23 29.06.2010, Henri Bergius wrote:
>Hi,
>
>On 29 June 2010 10:01, Andreas Kuckartz <A.Kuckartz at ping.de> wrote:
> > One clarification: The GPL can be used and is used in "commercial"
> > projects (Linux is the most well-known example). But it can be a problem
> > for proprietary software / closed source projects.
>
>jQuery, the javascript framework used with Aloha is dual licensed
>under MIT and GPL.
>
>I know BSD is more familiar to the Apache people here. But as Aloha is
>something that runs entirely in the browser and only interfaces with
>your CMS through some REST APIs, will license compatibility really
>matter?
>
>As I wrote on the Semantic Editor page, the main deal with licensing
>for our editor is to fit in the licensing scheme of the javascript
>ecosystem it builds on, not particularly target some server-side
>conventions like ASF.
>
>http://wiki.iks-project.eu/index.php/Semantic_Editor#Requirements_for_the_editor
>
> > Andreas
>
>/Henri
>
>--
>Henri Bergius
>Nemein - Web Craftsmanship
>http://nemein.com
>_______________________________________________
>iks-community mailing list
>iks-community at iks-project.eu
>http://lists.iks-project.eu/cgi-bin/mailman/listinfo/iks-community