Hi Everyone

I wanted to quickly follow up with an additional link to the "I'd like to help with the administration of the GHOP program! How do I start?" page that webchick created at http://groups.drupal.org/node/7360

Before creating a task on the Google issue tracker, *please* read section 2 of this page ( http://groups.drupal.org/node/7360#tasks).  The Google issue tracker is--how should I say it--limited in it's feature set.  For example, it's not possible for anyone (even the project owners) to edit tasks once they are created.

As Angie said, these students for the most part do a really great job on the tasks.  The more focused and detailed the task description is, the more likely you are to get the results you're hoping for.  So please be very explicit in your task description as to what you expect, how you expect it (ie. file format for non code/documentation tasks, what version of Drupal the code should be written for if it's not a porting task, etc.), and who the student can contact if they have questions (it would be great if you could include your d.o username and/or IRC nick).

Finally, because most d.o users aren't following the Google issues closely, we've found that it's best if each GHOP task has a separate issue on drupal.org in the appropriate issue queue.  This helps the students to get as many people looking at their work as possible, and it also helps them to gain experience in how normal tasks and issues are handled in Drupal.  Please provide a link to your d.o issue in the Google issue, and also a link to the Google issue in your d.o issue.

I know this is a little extra work on the part of the person who creates the task, but ultimately you're more likely to get great results this way.