Re: [Slashcode-general] licensing issues information?

[Wakko <una...@ho...>]

Actually... My understanding of the GPL is that you must release any bits of
code that incorporate GPL'ed bits of code.

So... if you write an app that only uses GPL'ed code for one module, you'd
only have to GPL the one module. Not the whole app.

The GPL only covers direct extensions/modifications/derivitives of GPL'ed
code.

But that's just my interpretation...  and I'm definitely not a lawyer.

---Wakko.

----- Original Message -----
From: "Chris Nandor" <pu...@po...>
To: <sla...@li...>
Cc: <sla...@li...>
Sent: Friday, August 24, 2001 5:50 AM
Subject: Re: [Slashcode-general] licensing issues information?


> At 08:49 -0400 2001.08.24, shane wrote:
> >Is there a website or other online resource that
> >explains all the different licenses available, and the
> >issues that come with each?
> >
> >I've got a number of plugins written, or atleast
> >being written. I plan to put them all out at no cost
> >because slash itself is free (atleast the calendar
> >and photo gallery plugins).
> >
> >But, I've got a wife, home, kids, and a small
> >side business. I don't want to endanger any of them
> >by using the "wrong" licensing to put some of these
> >out for use and have some idiot come after me
> >because he accidentally rm -f'd his drive while installing one
> >of my plugins.
> >
> >And I honestly don't know what license I would do
> >best by going with.
>
> Some would argue that you are required to put your publically available
> Slash plugin under the GPL.  I am not convinced this is true, but some
> would say that.  I think that it might be worthwhile to get the legal
> position of OSDN on that.  I'll try to find out.
>
> --
> Chris Nandor                      pu...@po...    http://pudge.net/
> Open Source Development Network    pu...@os...     http://osdn.com/
>
> _______________________________________________
> Slashcode-general mailing list
> Sla...@li...
> http://lists.sourceforge.net/lists/listinfo/slashcode-general