In his latest blog entry, Marco Tabini talks about how we, the community, have "failed the PHP brand" through its overuse (such as in application names of things written in the language).

This is, I believe, a major point of failure for the PHP community. As many have pointed out to me more than once (not that I had anything to do with it, or that I would be able to do anything about it), allowing PHP-related applications to contain the word "PHP" is a major mistake, because it dilutes the value of the brand itself by allowing the quality of PHP to be associated with the value of products that have nothing to do with PHP proper.

He mentions that searches for things like "php vulnerabilities" come up more with things for apps written in PHP and less with results about PHP itself. He even suggests that there isn't a really useful application type that has a PHP-written option that doesn't use the PHP "brand" in its title. He finishes it off with three simple rules that he suggests will help to dilute the PHP brand - don't use it in your application title, always reference that PHP is a trademark of the PHP group (and that there's no association between you), and use the PHP logo in only a descriptive way.

In his latest blog entry, Marco Tabini talks about how we, the community, have "failed the PHP brand" through its overuse (such as in application names of things written in the language).

This is, I believe, a major point of failure for the PHP community. As many have pointed out to me more than once (not that I had anything to do with it, or that I would be able to do anything about it), allowing PHP-related applications to contain the word "PHP" is a major mistake, because it dilutes the value of the brand itself by allowing the quality of PHP to be associated with the value of products that have nothing to do with PHP proper.

He mentions that searches for things like "php vulnerabilities" come up more with things for apps written in PHP and less with results about PHP itself. He even suggests that there isn't a really useful application type that has a PHP-written option that doesn't use the PHP "brand" in its title. He finishes it off with three simple rules that he suggests will help to dilute the PHP brand - don't use it in your application title, always reference that PHP is a trademark of the PHP group (and that there's no association between you), and use the PHP logo in only a descriptive way.