Using GPL'd software/scripts in WebDev business?

hi everybody,
I'm hoping somebody can give me some advice.

I'd like to know what the limitations of using GPL'd software and scripts are when you have a web design/development business?

I was thinking of creating my own php classes + templates for different things like (database control panel, newsscripts, newsletters etc.), to speed up production and focus on design/user customization.

Can I use gpl'd scripts, like the ones found on freshmeat.org, instead?
I know a lot of businesses have profited from using opensource tools like linux, apache, mysql, php, the gimp? But is it the same for scripts like phpnuke, dynapi etc?

And what are some of the legal, ethical concerns? Can I charge as much for a website using gpl'd scripts (like php-nuke?) or would I be better off creating my own PHP webscripts?

Thanks for any advice or experience

You can charge whatever you want for the changing/customization of a GPLed program and also whatever you want for distribution of the program so long as the GPLed stuff stays GPLed and the changes are available to the public in a form described by the GPL.

Otherwise the concept wouldn't work

edit: since I'm not a lawyer, you'd better read the GPL yourself and hire a lawyer if you are unsure about anything.

Here's the key:

If you want to use any GPL libraries, and code you write that uses the libraries must also be GPLed. This doesn't mean you can't charge for writing it, distributing it, or installing it, however. If you can find libraries that have been released under the LGPL, you are free to use these in applications without releasing the application source code, but any modifications to the libraries themselves still must be re-released.

The part about having to relicense the code doesn't apply for in-house projects, as I understand it. If you don't distribute the product at all, you don't have to release the source. I could be mistaken about the details of this bit though. Do read the licenses.

-wg <><

GPL section 2 b):

hi,
thanks for your replies. I've read the GPL but it's sometimes hard to understand and it seems to contradict itself Maybe I need more real world examples.

from GPL:


@realnowhereman:
I think there talking about the license only, right?

If for example I design/develop websites and the website is 80% original code/markup/graphics etc. And I use a gpl'd bbs like (phpbb) and/or somekind of gpl'd newsscript. As long as I keep the license intact, I can charge for the website as if I made 100%? Or do I charge 80%? Or is it somewhere in between because of a distribution fee?

(Most of the people I would be making this for would not know the difference between Linux and Mac let alone GPL and for cost scripts.)
That's why I thought of making various libraries on my own until I looked at what they had at freshmeat.org.

If you make a site using a LAMP server as opposed to some Win 2000, ASP, IIS, Oracle alternative most developers would still charge the same. Even though the opensource way will save you a bundle (and works better anyway). It's the same situation with webhosting. That's why I don't really understand how gpl'd software can be used for profit in some instances where in others you can't?

p.s. @nowhereman:
I grew up in Berlin

Hard to believe

No, they're talking about the code that you change/redistribute. That code must be available at GPL terms. It must be known that the code is available at GPL terms.

You can charge as much as you like - work with GPL software is not necessarily easy. However, you must keep whatever GPLed stuff you use GPLed. The same goes for anyone who buys your product. You also must make your changes in GPL code available for the public.

Hard decision ... it really depends.

In site development, of course. The amount of work is the same. Just make sure your boss knows about the implications of GPL code.

You can't make GPL code proprietary. So M$, for example, can't use Linux code in Windoze if they want to keep it under the current EULA. (They use BSD code, though.)

Alright thanks, I'm starting to see how it works.

ciao