On Sunday, August 17, 2003, at 08:56 AM, Mehdi Achour wrote:
1) Who is allowed to manage users notes ?
I've been asked a lot of time by new commers to the PHP team : "can we help you managing the notes ?"
I've always answered that I wasn't the person to ask but that any help would be appreciated.
Maybe we can add this to the howto ?
IMHO, everyone (from the PHP team) should have the right to moderate the notes. No need to provide
access to other people. A team of 5 or 6 persons is moderating the whole stuff since two month, the
amount of notes in the database is decreasing every week. no need to external help.
It tends to vary over time. When people are very active, the notes are well maintained. Sometimes people become less active. From what I can see, I think the manual is still totally flooded with confusing, contradictory, and poorly written notes.
As far as "who is allowed to manage a given page of notes", I think the bare minimum should be
1. Those who know PHP, and the note subject, well.
2. Those who have experience with writing PHP's documentation (preferably). If notes editors are also writing documentation, *most* of the good notes can be deleted as they are integrated.
And what about an abusive note ? Do we need to know how work the domxml extension to delete some non-related note ?
I wasn't talking about the skills needed to moderate the notes, but this can also be discussed. I was objecting for allowing other ppl (not memebers of the PHP team) to moderate the notes as I've seen that it was dicussed.
2) Reasons for suppression :
As approached in my first mail, we see from time to time abuses in the moderation,
Rather than adding to the workload for each note, how about correcting the actions of the abuser themselves?
You mean posting the note again if it was deleted ? Who will take care ?
Would that be a more effective solution than adding a greater workload to a simple system?A smart note, which maybe deserve to be integrated to the manual lost, without any
understable reason :
"note xxxx was deleted from yyyy by [EMAIL PROTECTED]"
Why ? did "zzzz" read it all ? does he just want to show that he's "taking care" ?
There are a lot of valid reasons for deleting notes... ;-) If one cannot *trust* in someone else's competency to manage the notes, adding a bunch of categories that they "check off" will not fix that problem. Rather than "abusing" without a reason, they can simply "abuse" *with* a reason, valid or otherwise.
Abusing with an invalid reason is more critical then abusing with no reason at all. Having the need to supply a reason will *maybe* make the abuser think twice before deleting the note.
One more occasion to fit our readers needs is lost here.
some notes disserve to be on the users notes, without being deleted nor integrated.
Can you provide some examples? I perceive the optimal manual as a manual without *any* notes. If the manual is good enough, no additional notes and explanations would ever be needed. So, if a page *has* notes, that is a sign that more effort should be applied to improving the documentation... to a point where PHP no longer requires "external help".
For example, a trick on the mysql_num_rows page showing the use of COUNT() (mysql function) to get the number of records in a table instead of doing mysql_num_rows(mysql_query('select * from foo'));
This can not be integrated to the manual (or we'll have to introduce all the optimization stuff) but is really usefull for newbies (when I've started PHP/MySQL I was using the bad way =D)
there's a lot of examples of this kind.
A new note is posted :
- if the note should be deleted (deleted, not rejected as described by the current howto) we do
[snip]
This is missing a large number of "other" reasons for deleting/rejecting notes, here are some reasons from poking around notes tonight:
12. Coding-101-notes: Notes that mention that things like "closing quotes" matter. (Uhm...)
(etc.)
nice shot :)
I'm sure we could create labels for all of these (or apply existing ones), but to what end? If the end product is a good manual, annotated and then improved as needed, how will it help reach that goal if each note submission/rejection/deletion/integration requires more work? Especially since the manual is still filled with notes that need to be integrated, or removed?
Goba answered well this question ;)
It will also introduce the "to_be_integrated" concept that can be really usefull IMHO to have a better manual.
Btw, choosing the good link to click is not hard and only require to concentrate a little :)
Regards
didou
-- PHP Documentation Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
