osw-users

[Osw-users] OSWPL and plugins

[smoerk <sm...@gm...>]

Does I understand it correctly that a plugin doesn't have to be under 
the OSWPL? I can use any Open Source license and also write commercial 
closed source plugins/transforms? I'm talking about plugins that work 
with a default OSW installation (and don't require any OSW modifications).

Mainly the question is: can I use GPL'ed code for writing a OSW transform?

Re: [Osw-users] OSWPL and plugins

[Amar <am...@pt...>]

Yes, you can use GPL'ed code in your own external transforms, and distribute
those transforms independently for the main OSW distributions.  Your
transform will probably carry both the GPL and the OSWPL, with the GPL's
provisions on open source probably taking precedence.

It's great to see interest in new transform development out there!  Let us
know if you have any further questions about the process.

   -Amar


----- Original Message -----
From: "smoerk" <sm...@gm...>
To: <osw...@li...>
Sent: Thursday, September 25, 2003 8:17 AM
Subject: [Osw-users] OSWPL and plugins


> Does I understand it correctly that a plugin doesn't have to be under
> the OSWPL? I can use any Open Source license and also write commercial
> closed source plugins/transforms? I'm talking about plugins that work
> with a default OSW installation (and don't require any OSW modifications).
>
> Mainly the question is: can I use GPL'ed code for writing a OSW transform?
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Osw-users mailing list
> Osw...@li...
> https://lists.sourceforge.net/lists/listinfo/osw-users

Re: [Osw-users] OSWPL and plugins

[Andy S. <an...@a2...>]

<quote who="Amar">
...
> those transforms independently for the main OSW distributions.  Your
> transform will probably carry both the GPL and the OSWPL, with the GPL's
> provisions on open source probably taking precedence.

OSWPL certainly does not prohibit interaction with any other license, but
I think that the GPL prohibits linking to a library under OSWPL.

Then again, interpretations of the GPL vary widely, e.g. Linux is GPL but
Linus says 'binary-only kernel modules are OK', but RMS thinks that two
programs merely existing on the same filesystem implies a 'link'.

Perhaps a dual license (OSWPL/GPL) as mentioned would work.  I don't know
how the 'precedence' thing would work, though.  I've only seen dual
licensing like GPL/Commercial where the selection of license is the user's
choice (choose free as in speech or pay money... you choose ;)

I think that GPL is okay if its your own code, but I would not integrate
or link someone elses GPL code into an OSW plugin without explicit
permission from the author.  Failing that, use LGPL.

---------------------------------------------------------------
 Andrew (Andy) W. Schmeder
 mailto:an...@a2...
 http://www.a2hd.com