Licensing of Lisaac

[Mildred Ki'Lya]

On 08/26/2009 03:25 PM, Nicolas Boulay wrote:
> You can't reuse a code in GPL in a BSD project if the whole is a
> "combined form of work". That means if you project absolutrly need a
> GPL code (linked or thouth the network, like a MYSQL server), you need
> to follow GPL rules.
>
> Thats our main problem today. That's  the "vaccine" behavior of the
> GPL, that is too strong for us.
>   
What I'm saying is that you can use MIT code (my code) in a GPL project
(Lisaac)

The MIT licence allows you to do whatever you like with the code, even
re-license it to BSD, LGPL, GPL, whatever ... Of course, if the MIT code
is used in a GPL project, the project as a whole stays GPL. But you can
always take the MIT licensed parts apart and create a project not GPL
licensed.

And, I wanted to add. All the code I wrote on the Lisaac project (lib,
compiler, anywhere) is MIT licensed. It means that you can do whatever
you like with it. Ultimately it gives you the power to change the
license as you like, without having to ask me.

I wanted to say that because I feel that with more and more developers,
changing the licence can become difficult. Perhaps we should think about
giving all our right of the code we write to some sort of organization
that would have the power to change the license, without having to ask
all the developers.

-- 
Mildred Ki'Lya
╭───────── ｍｉｌｄｒｅｄ５９３＠ｏｎｌｉｎｅ．ｆｒ ──────────
│ Jabber, GoogleTalk: <mildred at jabber.fr>
│ Website: <http://ki.lya.online.fr>           GPG ID: 9A7D 2E2B
│ Fingerprint: 197C A7E6 645B 4299 6D37 684B 6F9D A8D6 9A7D 2E2B


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/lisaac-devel/attachments/20090826/13d69d5a/attachment.pgp>