Re: cvs: php4 / LICENSE
| From: | Yasuo Ohgaki | Date: | Mon, 22 Jul 2002 06:28:35 +0000 |
| Subject: | Re: cvs: php4 / LICENSE | ||
| References: | 1 2 3 | Groups: | php.cvs |
| Request: | Send a blank email to php-cvs+get-12930@lists.php.net to get a copy of this message | ||
Andi Gutmans wrote:
At 11:25 AM 7/22/2002 +0900, Yasuo Ohgaki wrote:Hmm. Then, PhpEzmlm nor EzmlmPhp is _not_ ok w/o permission for example. I guess Derick is asking the same thing about naming. "PhpSomthing" is like "XSomething" for X applications, "GnoSomething" for Gnome, "KdeSomething" for KDE, etc, etc. Is't this a common sense to us? Why bother? What's wrong with it? It's great thing to promote PHP to have applications named "PhpSomething". IMHO. I'm sure there are people who will be suprised by this ;) -- Yasuo Ohgakiderick@php.net wrote:Yes you do. You also did previously but it wasn't clear enough. Apache does the same thing. This clause makes sure that the PHP name isn't used in ways where it isn't clear that the product isn't PHP itself nor endorsed by the official PHP community. Good products should be able to be successful without having to use PHP as part of the name.On Sun, 21 Jul 2002, Stig Bakken wrote:I think older statement is better... "ezmlm for PHP" sounds strange. Do I need approval for "PHP ezmlm"?+ 4. Products derived from this software may not be called "PHP", norAre phpMyAdmin and PHP OpenTracker forms of derived software? Derick+ may "PHP" appear in their name, without prior written permission + from group@php.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"