which is exactly why we cannot bundle the STK with the CE ;-)
- Boris
On Dec 9, 2009, at 4:35 PM, Ruben Reusser wrote:
this would also mean that the stk would have to be GPL if
distributed with the magnolia GPL version, would it not?
Ruben
Rakesh Vidyadharan wrote:
On 09/12/2009 04:39, "Boris Kraft" <[email protected]>
wrote:
> But what about modules? If I built a Magnolia module that
would be
> distributed on its own, but needs Magnolia to run and uses /
links to
> Magnolia libraries / jars - could that be distributed under a
closed
> source license?
I believe you can write modules that have any license you want as
long
as they are not distributed with Magnolia, but this is not a
binding
legal agreement. The GPL is the only binding agreement. I
suggest you
talk to a lawyer that understands the implications of GPL.
I am no lawyer, but from what I understand of the GPL licence, if
you link to a GPL library/software, your code is automatically
under the GPL.
------------------------------------------------------------------------
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
