The CREDITS etiquette for php extensions isn't quite what you describe here.
The accepted practice (there are no rules) is this:

If you have the karma and have made some contribution(s), and you feel
that it was worthwhile, you simply add yourself to the CREDITS file
for the relevant extension.
If you're unsure, you will usually ask someone else that is listed
there if it would be okay to be added.

If other people disagree, an argument^H^H^H^H^H^Hdiscussion will ensue
to resolve the matter.  (this has not ever happened, AFAIK)

IMO, it would be nice to extend this idea to phpdoc and have some kind
of author tags per file in the doc tree and allow the
authors/translators to use them to credit themselves.

--Wez.


On Wed, 21 Jul 2004 12:45:37 +0000, Gabor Hojtsy <[EMAIL PROTECTED]> wrote:
> PHP itself. See your phpcredits() page, I use the
> php.net/credits page for reference. I have picked the
> MySQL extension as the prime example. Look at the table:
> 
>    MySQL : Zeev Suraski, Zak Greant, Georg Richter
> 
> Is this to beleive? I guess noone doubts that this is
> far from a complete list of the MySQL extension contributors
> and authors.

> If you watch closely, you see two distinct approaches here. One is to
> credit *only the first* defining people behind some entity (PHP itself
> and smarty are examples for this approach). The PEAR, PECL and PHP
> website approach seems to be to credit *only the active* people behind
> the projects (thus the concept of maintainer comes to existance). The
> PHP source code approach (Andi and Zeev are the authors and maintainers
> of PHP, Alexander Aulbach, et.al. are the authors of the manual and
> stuff) is under attack by some people.

Reply via email to