This is an old revision of the document!
Revamping user comments at php.net
Possible mentor: Philip Olson
This task involves rethinking how we handle user comments at php.net. This is mainly (only, currently) done within the PHP manual but it could leak into other areas like at pecl.php.net.
The first task involves defining what a user note is (or should be). Is an example that happens to use strlen() a fine user note for the strlen() documentation? Are examples even appropriate user notes? Is the current moderation system working? Many other questions will arise.
There has been some discussion.
Baby steps: step A, moderation flags
This involves a simple user notes moderation flag option. Users can flag notes as “bad”, which prompts a moderator to look into it. Users do not need to login, but if not logged in, must answer a recaptcha or similar.
How it will probably work
- User clicks on “flag”
- Popup is created
- Checks if logged in
- If not logged in, prompts reCaptcha
- Popup now has several options, including:
- A button to submit the flag, with no details
- Or optionally allow entering details such as name, email, textarea reason for flag, select box reason for flag
- Flagged notes generate email to a list, and also find themselves listed in a web admin panel.
- People can subscribe to receive these emails?
- Moderator takes action, which includes current options (delete/reject/modify) as well as others like unflag.
- If note flag is accepted (e.g., deleted), should we notify the user via email? Or list via email?
Notes about the current system
The current system was written in the 90's, and contains files spread out in several places throughout the PHP project. Also, various note moderation statistics are listed here.
- http://svn.php.net/viewvc/web/php-master/trunk/manage/notes-alert.php (not implemented)
- http://svn.php.net/viewvc/web/php-master/trunk/include/alert_lib.inc (not implemented)
- PHP Web:
- Note archive (note actions are emailed here):