[policy, no patch] Comaintainer practices and procedures

I'd like to see a few more people become active comaintainers, some with commit privileges. I'd like to see specific people take responsibility for specific modules.

First, please be aware that it doesn't take commit privileges to help maintain this suite. It just means taking time in the issue queue, committing patches, developing new modules, and supporting people.

For committers, here are some proposed practices:

1. Examples is a teaching project. The idea is to do the simplest possible thing that can explain a technique in the Drupal API (and make it easy for people to copy and paste to get started solving their own problem.)
   • Keep it simple!
   • Comment well.
   • Don't show off fancy PHP or programming techniques unless they help people understand best practices.
   • Try to use variable names and function names that make sense and disambiguate the usage.
2. Every example module should have three basic means of access:
   • Viewing and studying the code.
   • Experiencing the code (enabling the module and following the menus). Note that every module should have at least one menu entry at examples/module_name that at the very least gives people a clue what to do next.
   • api.drupal.org will be used to present and explain the code, and people use it directly, so make sure your doxygen is good.
3. All work should be done in the issue queue. In other words, don't just commit stuff without showing the activity and explaining it in the issue queue. If you're going to fix something or improve it, do it in the issue queue. Wait until the tests come back green before committing. (If you think someone will help out and comment on the issue, wait for them as well. In many cases that won't happen. However, if several of us are comaintaining, maybe it will happen more often).
4. All of this code ends up on api.drupal.org, so please make sure to use excellent and helpful doxygen comments.
5. All work that involves new features or solves specific problems should have related tests, just like we do in core. Let's take every opportunity to improve the test suite.
6. Use Drupal coding standards, and please run coder on your work.
7. Please read the project page to get a clear idea of the philosophy proposed there