Last updated September 9, 2012.
The Community Documentation pages on Drupal.org are written and edited by the Drupal community as a whole, with the aid of a small team of people (the "Community Documentation Moderation Team"), who have the responsibility of overseeing and moderating the documentation.
Moderation team member responsibilities
- Monitoring the Documentation issue queue and responding to issues.
- Deleting comments when requested on an issue, or when inappropriate comments are found (e.g., comments rolled into the text a page, irrelevant, inaccurate, etc.).
- Making edits on the few pages we have on Drupal.org that are locked by being Full HTML input format, when requested on an issue.
- Locking pages that need to be locked, and unlocking pages that should not be locked, when requested on an issue.
- Publishing and unpublishing pages, when requested on an issue.
- Creating URL aliases as needed, and redirects when duplicate pages are deleted or aliases are changed.
- Generally doing what you would expect a "moderator" or "maintainer" to do: mediating content disputes, making decisions on major docs changes (including the appropriateness of tasks above), moving pages around to make the organization more appropriate, etc.
- Asking for help from the Documentation Team Leader if there is any question about any of this, and for final arbitration of decisions.
(There are other provisional members who will be added to this list soon -- see below if you'd like to join!)
Joining the Moderation Team
The Community Documentation Moderation Team is now forming. We are looking for about 20 people who are willing to take on this responsibility, who have demonstrated that they will not abuse the elevated permissions they will have on Drupal.org, and who have recently been active Documentation editors.
As a prerequisite to joining the formal team, you should do all or most of the following (elevated permissions on Drupal.org are only granted to people who have demonstrated they will use them appropriately):
- Join the #drupal-docs irc channel. Add it to "auto-join" in your IRC client, and turn on your IRC client regularly.
- Subscribe to the Documentation issue queue. To do that:
- Visit your user profile page on Drupal.org.
- Click on the "Notifications" tab
- Enter "Documentation" in the "enter a project title" box in the "Issue email notification" section, and choose "All issues", so that you will receive an email message whenever there is any activity on a Documentation project issue.
- You probably also want to make sure that your default for non-specified projects is "Issues you follow", so that you receive notifications for non-Documentation issues you have chosen to follow (you can always un-follow them later if you lose interest).
- Save your settings.
You might also want to make sure Drupal.org has your correct email address (on the Edit tab of your profile).
- As issues are reported, respond to them. There are instructions for what we want to have happen at http://drupal.org/node/1204344 and http://drupal.org/node/24565. If you have questions, respond as best you can (including your question), or ping me in the #drupal-docs IRC channel. Ideally, all issues in the Documentation project would be responded to within 24 hours... silverwing and I have been pretty much the only people responding to them regularly for quite a while now, so if the Moderation Team could take on this responsibility, that would be great! I'll delay responding myself for the time being, to give the new team a chance. :)
- Edit some documentation pages (we probably won't grant elevated editing permissions to people who don't normally edit pages). To get started with that, see http://drupal.org/node/1424558
- If you've done a few edits, try "rolling in comments" on a few page. This task is described at http://drupal.org/node/1426262 -- and it's really important for the Moderators team, since deleting rolled-in comments is one of the main tasks. For now, if you don't have permission to delete comments, just follow the steps on that page (culminating in filing a documentation issue), and someone else (likely me) will take care of the actual deletion.
Once you've been doing this for a while, file an issue in the Webmasters project and ask to be given documentation issue moderator privileges.