GPL License question.

[sijis]

I actually had some time to completely read the GPL License (http://www.gnu.org/licenses/gpl.txt). I understood alot of it but I still have a question.

I basically got that the license is designed for copying, distribution and modification of software. What about using the 'software' with other code?

This is my scenerio:

i use a GPL'ed DB abstraction layer (a single file DB class) on a non GPL project.
This DB abstration layer does not enhance the project and i don't modify it. It just make it easier to port the project. Does my project also become GPL'ed?

I do notice this is stated in the licensing:
"10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation;"

Now, what if i wrote the DB Abstract class myself? Does that affect my project?

Thanks.

Sijis

[piersk]

I've kinda been in the same boat. I wanted to use another OS project in one of mine, so I just emailed the author to get a thumbs up. I think it would be nice to give them credit for their work (maybe a link to their website on your homepage?).

If you'd written the abstraction yourself, then of course you wouldn't have to credit anyone.

[ahundiak]

If the abstraction layer is GPL then your project must become GPL as well. Plain and simple.

Note that there is also a LGPL license. You can use LGPL code without makeing your project GPL.

Finally, there's a gazillion DB abstraction layers out there. Switch to a non-GPL one if GPL is too restrictive.

[sijis]

ahundiak, thanks for the LGPL comment.

i want to this:

share the code
if code modified, make it public (and let me know)
if the code is used in a project, the project doesn't go GPL.

its sort of seemed like the LGPL that you mentioned. Or is there another license that is similar to my goal?

i have a similar question about GPL now. Using GPL software means i can't sell that software but can i charge for implementing that software to a project?

assume i'm creating a website for a client.
in order to create the site, i use a GPL 'login' code.
i know i can't charge for creating that code, but that i charge the client for implementing that 'login' code onto their website? Better yet, what can i charge for, if anything?

[ahundiak]

I am far from being an expert on these matters but have done some research over the past years. Have you read the FAQ?
http://www.gnu.org/licenses/gpl-faq.html#DoesTheGPLAllowMoney

While the L in LGPL stands for Lesser you can also think of it as standing for Library. Many libraries such as the libxml2 are release under LGPL which means that non-GPL code can use them.

Of course not all libraries are released under LGPL. In particular, the mysql c interface library is GPL which in turn means that the php group had to stop bundling it with php. It's going to make installation (of php5) more difficult for the unskilled person.

GPL has nothing to do with charging for your program. You can charge as much as you want (see the faq) or see the mysql license page http://www.mysql.com/products/licensing.html for an example of how to release something under GPL but still charge for it.

Keep in mind that the whole LGPL/GPL license has never been challenged in court. So nobody really knows what the license actually means. Some of the sentences just don't make sense at all.

You might also browse a bit on sourceforge.net. There's a whole bunch of different licenses you can use. The site does some comparision between them.

[Moonglobe]

This (opensource.org/licenses/) is a list of Open Source licenses

[thoand]

I think this article has some answers to your question:

http://www.sitepoint.com/article/415

regards Thomas

[sijis]

i know this is a bit old but i thought it would be useful for someone.

I found that the Creative Commons license is basically what i was searching for. The license can be 'customized' to some extent.
you can get more info here:
http://creativecommons.org/license/

[drawmack]

you do not have to open code that interacts with open code as long as they are kept in seperate files.

For example if you use a gpl dll, you do not need to open your exe code.