Open Source Software - Licence clarification

Author

Licence clarification

Ged Robinson

2005-09-23, 7:01 pm

Hello,

I'm s

ing some plain-language (as opposed to legalese) explanations of
what the various licencing of open source products *actually means* in
practice.

To set the scene, I'm going to be engaged with my employer in developing
some solutions using common open source products. Specifically, a Linux
(Mandrake linux), Apache, MySQL, PHP platform. Potentially, depending on the
requirements, some other open source components too.

Would somebody be willing to spend the time to explain to me what the LGPL,
GPL (and other common licencing schemes) actually mean when deploying a
commercial solution. For example, Mandrake Linux & MySQL ..... am I free to
use these products in a solution actually free-of-charge, or do I need to
purchase a licence if I'm going to include it in something I sell??
(This is really the fundamental question).

Any feedback is appreciated.

Thanks,

Ged

Pasi Parviainen

2005-09-26, 7:02 pm

Ged Robinson wrote:
> Hello,
>
> I'm s

ing some plain-language (as opposed to legalese) explanations of
> what the various licencing of open source products *actually means* in
> practice.
>
> To set the scene, I'm going to be engaged with my employer in developing
> some solutions using common open source products. Specifically, a Linux
> (Mandrake linux), Apache, MySQL, PHP platform. Potentially, depending on the
> requirements, some other open source components too.
>
> Would somebody be willing to spend the time to explain to me what the LGPL,
> GPL (and other common licencing schemes) actually mean when deploying a
> commercial solution. For example, Mandrake Linux & MySQL
http://www.mysql.com/company/legal/licensing/faq.html

>..... am I free to
> use these products in a solution actually free-of-charge, or do I need to
> purchase a licence if I'm going to include it in something I sell??
> (This is really the fundamental question).
How do I know which license to use?

The overall guiding business principle of MySQL's dual licensing is one
of fair exchange or "Quid pro Quo" which means "something for something."

So if you use MySQL with GPL-licensed software (or a license that is
GPL-compatible) we encourage you to use the GPL license. For all other
users of MySQL, we recommend that you purchase a MySQL commercial license.

>
> Any feedback is appreciated.
>
> Thanks,
>
> Ged
>
>

--
Pasi Parviainen, Chairperson
Open Source Finland - OSF ry
http://www.opensourcefinland.org
==
When you do work, you use OS X. When you need the computer to do work
for you, you use Linux.

Jasen Betts

2005-09-28, 8:07 am

> Would somebody be willing to spend the time to explain to me what the LGPL,
> GPL (and other common licencing schemes) actually mean when deploying a
> commercial solution.

read them again if it's critical don't believe some yobbo on usenet, get a
lawyer.

here's my take on the two.

With GPL if you make something from it and make it available. the source
must be freely available to anone who gets the bibary, the recipient must be
free to distribute copies.

You can charge for a GPL product but you can't stop othewr from making
copies (or modified versions) and distributing them for free. you can't
restrict the source from those who you give the binary to. (this would
include demo versions etc....)

With LGPL if you use a LGPL product unmodified it must be dynamically
linked (so those who get your application can upgrade to a new library
version...) or otherwse you must provide compiled object (or provide
source)

> For example, Mandrake Linux & MySQL ..... am I free to
> use these products in a solution actually free-of-charge, or do I need to
> purchase a licence if I'm going to include it in something I sell??

If you include mandrake linux you are distributing a copy, what's
mandrake's policy on distributing copies of mandrake and charging
for them?

Bye.
Jasen

--

Opinions expressed herein are GPL :)

Sponsored Links