BTW Goba, can we make things move for the notes maintenance ? Two things : 2 - The notes system
From the same URL, topic "3. User note handling"
When deleting :
- outdated : for example, a note helping to configure some library with PHP 3.X, a note using a function that is no more part of PHP.
- replying : the note is a reply to another note asking for help. The original note should be hunted down and rejected (as stated in the HOWTO)
So should the reply, IMNSHO.
IMHO, the reply should be deleted. No need to send a mail to a helper.
- bogus : for example, a note giving an example for a mysql_* function on a mssql_* function page.
- trash : spam, bad words, an _old_ (more than 6 months is a good limit) note asking for help, a non-english note, a note that should be rejected but have a wrong email address ..
- duplicated : there's already a note saying the same thing, differently. If there's a lot of duplicated entries stating the same thing, we should think about integrating the note in the manual
- added : the note content was added to the manual. We can even send a mail to the note submitter, giving him a link to the updated CVS file and thanking him for his add-on.
When rejecting : - support : a note asking for help
Uhm, see above?
What do you mean ? There's to kind of notes related to support : - asking : reject - answering : delete
That doesn't sounds good to you ? What do you propose ?
Here's how I think of the notes: Unless it helps *me* somehow, someday, it doesn't belong.
You've got to keep in mind that the documentation is also readed by "newbies" so what can seem irrelevant for you can be the a field of gold for someone else. That's the hardest part of moderation : relevance.
didou
-- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
