Page 1 of 1
Q about making software by php
Posted: Tue Nov 17, 2009 11:46 am
by searcher_searcher
One of my friends said to me:
"If somebody want to produce a software for example a Portal by PHP code by order of license of PHP ; encrypting of all code is forbidden and it is legal to encrypting only some portion of software and not all software!"
is it true?
and 2 other question:
1) is Redhat Linux Open Source?
2) is Vbulletin Open Source?(it has visible source code)
thanks
Re: Q about making software by php
Posted: Tue Nov 17, 2009 2:56 pm
by requinix
I can't understand the question. A "portal" as in a web portal, or "Portal" as in the game? "by order of license of PHP" means what?
1) Last I knew RHL was closed-source but I'm not sure.
2) Yes, but it has a license.
Re: Q about making software by php
Posted: Tue Nov 17, 2009 4:22 pm
by Mark Baker
Your friend is talking out of his a***.
Programs written in PHP can be distributed using whatever license you want, as long as PHP itself is not part of your distribution. You can encrypt your script, charge for your script, issue it under a proprietary license, whatever; and all that is perfectly legal.
It's only if you distribute both PHP itself and your scripts, that you are constrained by the terms of the PHP license for the distribution of PHP.
Re: Q about making software by php
Posted: Tue Nov 17, 2009 4:59 pm
by requinix
Mark Baker wrote:Your friend is talking out of his a***.
Programs written in PHP can be distributed using whatever license you want, as long as PHP itself is not part of your distribution. You can encrypt your script, charge for your script, issue it under a proprietary license, whatever; and all that is perfectly legal.
Well, there is the issue of using somebody else's code. If they have a license on its use then you have to follow it.
Re: Q about making software by php
Posted: Tue Nov 17, 2009 5:47 pm
by Mark Baker
tasairis wrote:Well, there is the issue of using somebody else's code. If they have a license on its use then you have to follow it.
What I said applies, as long as the script that's being distributed is your script.... if you use additional libraries as part of your distribution, they'll have their own license terms.... but as long as all your distribution comprises code that you've written yourself, you're not constrained by the PHP license... at least, that's what I was trying to say. License restrictions only apply when you're including somebody else's code in your distribution.