Re: Re: License for documentation (here: Supporting the translation team)

Friedhelm Betz wrote:

Furthermore: If you look at the huge list of "translators" and then realize that only 20%-30% of them really do the work:

I don't expect any changes, because once listed for ever listed due to the policy to list people who contributed. (?) Hm. The contributors list is also a point, and there would be possibilities (like "regular contributors", etc.), this is a special thing, which we should discuss separately (or simply follow the "future" policy of the en-manual).

But what I meant is the endlessly long list in revcheck I have to scroll over (over and over again ;).

I would make it even harder, like in the dev-group: FIRST contribute to the list, THEN get a cvs-account. Otherwise you create an endless number of accounts for PHP-beginners which just think they might help, and then they realize that it's work...

One possible way to go I personally would agree. But this implies, someone must be williing to commit contributions ASAP. To go this way, we should have to provide a mechanism people can rely on like which amount first, positive votes (how much) from whome? I've also started with contributing to the list, and if there are contribs, I'm shure that one of us will take care of it.

Note that I'm just talking about cvs-accounts here, not the contrib-list: I don't think that we need special rules, it's just to get the feeling that this person will work actively (and probably has already done the "work" of learning xml, docbook, ...) Even it's not the ideal wording for php-doc, I like the part "...team can get to know you and what you'll be contributing." out of the following paragraph at http://www.php.net/cvs-php.php: "Submitting patches and participating in the discussion on the 'internals' list before requesting full CVS access is strongly suggested, so the PHP development team can get to know you and what you'll be contributing. It is suggested that all PHP developers (people developing PHP itself, not people developing in PHP) subscribe to this list. (Similarly, if you plan on contributing documentation, you should subscribe to the documentation mailing list by sending a blank mail to phpdoc-subscribe@lists.php.net)."

This is sort a thing like the listing of contributors to the en manual on phpdoc@ ;-) Yep,

Thomas