On 16.04.2007, at 14:25, Chris Miner wrote:
Hey All,
If a person were to contribute a module or collection of classes to
the
Magnolia opensource project, under what license should they be
contributed?
Hey Chris,
the way it works is that you sign a Contribution agreement that
allows Magnolia International the copyright (so you have it and we
have it). This in effect makes it possible for us to release your
contribution under any license we like, which currently means we
release it under LGPL for the Community Edition and MVSL for the
Enterprise Edition. In other words: you don't need to care, you can
release your code under any license you like. Its dual (or more)
licensing at play here.
I see LGPL mentioned in many headers, on the other hand there is a
message on
the dev list discouraging the use of GPL and LGPL.
that thread (where it was on the subject ;-)) was talking about using
third party libs. If we use a third party lib that is GPL, in effect
we would need to release all of Magnolia as GPL. If we use a third
party lib that is LGPL, that is no problem. Things should even be ok
with respect to our ability to change the license of Magnolia CE
(after all, the point of LGPL is that one can use GPL'd code without
having to be a GPL project)
If you contribute, thats part of Magnolia, not a third party lib. Of
course, you can also do the latter and create your own library, which
then is no contribution to the project, and you can define your own
license terms. If it were GPL, we would not use it.
Cheers
- Boris
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/developer.html
----------------------------------------------------------------
