need some licencing advice

Christopher Browne cbbrowne-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org
Mon Jul 17 13:36:11 UTC 2006


On 7/17/06, bob <ican-rZHaEmXdJNJWk0Htik3J/w at public.gmane.org> wrote:
> I'm preparing to release some code which utilizes my LGPL'd SIMPL library.
>
> This code is intended to expose a framework consisting of a messaging API and
> several highly customizable SIMPL executables.
>
> In addition to a name (my problem) I need to chose a licence for this
> framework which require that derivative works be licenced under the same
> terms but can attract commericial entities who may connect their modules to
> the API.
>
> This is very similar to what the SugarCRM project does.   They use a modified
> MPL for their project.
>
> I'm guessing that the straight GPL might work in the same manner as it works
> for Linux.    Changes to the OS are considered derivative.    Apps written to
> the Linux API are not.
>
> I am not a lawyer nor am I able to understand much of the legalese in these
> licences.
>
> Any suggestions?

What do you WANT?  That's really the determining factor.

If you want the system as widely used as possible, then a BSD style
license restricts as little as possible.

If you want to tightly control how it is extended, then the GPL tends
to be preferable for that, as it means that anyone looking for any
"proprietary usage" will have to negotiate other arrangements with
you.

The LGPL falls somewhere in between.

There are other licenses out there; most aren't as well understood as
the three I mentioned.
-- 
http://www3.sympatico.ca/cbbrowne/linux.html
Oddly enough, this is completely standard behaviour for shells. This
is a roundabout way of saying `don't use combined chains of `&&'s and
`||'s unless you think Gödel's theorem is for sissies'.
--
The Toronto Linux Users Group.      Meetings: http://tlug.ss.org
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://tlug.ss.org/subscribe.shtml





More information about the Legacy mailing list