Re: php license [message #173804 is a reply to message #173785] |
Thu, 05 May 2011 16:10 |
Thomas 'PointedEars'
Messages: 701 Registered: October 2010
Karma:
|
Senior Member |
|
|
VanguardLH wrote:
> Aleks Kleyn wrote:
>> when I setup MSI file from http://us3.php.net/downloads.php web site, it
>> shows license agreement which includes following text
>>
>> 3. The name "PHP" must not be used to endorse or promote products
>> derived from this software without prior written permission. For
>> written permission, please contact group(at)php(dot)net.
>
> You cannot use PHP to build yet another programming language. That is,
> PHP cannot be the base for your new language without first getting
> permission.
Wrong. This is about endorsement and promotion, and it is about name, not
foundation. Suppose you do a new language that is based on PHP that does
not have "PHP" in its name, then you do not need that written permission in
order to endorse or promote it; otherwise you do.
> If you want to build something atop of PHP, like PHP-Plus,
> then you have to ask because the founders of PHP probably don't want the
> quality of their product polluted with bad projects that build up from
> PHP as their base.
That is correct for this particular example only because it includes "PHP"
in the name of the new language.
> If you want to use their codebase for their PHP product in your
> derivative product then you need permission.
No. *That* permission is explicitly granted by the license.
> Writing scripts that rely on their interpreter to execute is NOT stealing
> the code of that interpreter.
Nor would be using it as basis. PHP is Open Source, after all. Again, this
is only about names.
>> 4. Products derived from this software may not be called "PHP", nor
>> may "PHP" appear in their name, without prior written permission
>> from group(at)php(dot)net. You may indicate that your software works in
>> conjunction with PHP by saying "Foo for PHP" instead of calling
>> it "PHP Foo" or "phpfoo"
>
> You cannot use "PHP" in the product's title. Something like
> "PHPfantastic" is a no-no. Just because you use PHP to code your
> product doesn't grant you permission to use "PHP" (as a distinct
> reference) in your product name. "SLOPHP" for something related to HP
> would be okay, however.
Nonsense. "SLOPHP" would make no difference (as it is a variant of
"phpfoo", and you can use "PHP" in the product's _name_ if you have
requested and gotten written permission.
Why are you reinterpreting and misinterpreting what is written there?
It could not be more clear.
PointedEars (IANAL)
--
Danny Goodman's books are out of date and teach practices that are
positively harmful for cross-browser scripting.
-- Richard Cornford, cljs, <cife6q$253$1$8300dec7(at)news(dot)demon(dot)co(dot)uk> (2004)
|
|
|