New GHOP task workflow

Events happening in the community are now at Drupal community events on www.drupal.org.
webchick's picture

The first week of this contest was a bit hectic, because two of the primary organizers were on business trips, and we were starting to get used to the tools available to us. This weekend, a few of us did some brainstorming about how to better streamline things and get the community involved more.

aclight came up with the following solution:

  1. Due to limitations with the app (inability to edit, off-site resource not looked at by the vast majority of the community, etc.) we'll only use the Google tracker for basically status changes: Open -> Claimed, Claimed -> Open, Student uploads final work -> Closed, and that sort of thing. Please keep an eye on the Google task updates so we can shuffle these tasks/students around quickly.
  2. Each new task in the Google tracker needs to link to a corresponding drupal.org issue, where the student will do their work. Issues need the following:
    • Put them in the queue where they're most appropriate (a module if it's for a module, Drupal if it's for core, or User Experience/Documentation if it's kind of fuzzy)
    • Title it: "GHOP #xx: Description of task" and in the body, copy/paste the text of the official task.
    • Expand the new "Categories" fieldset and select the "GHOP" term, which will let it show up in a global GHOP task view (Yes! VIEW!! Warning: still buggy).

    Issue statuses should be synched with the Google task:

    • Active = Open
    • Active (needs more info) = Claimed, but nothing yet
    • Patch (code needs review) = student has submitted work that needs review Please get on these ASAP!!
    • Patch (code needs work) = student's work needs some revisions
    • Fixed/RTBC (depending on issue) = Closed

    Yep, manually syncing is going to be a pain, but it has a distinct advantage: it pushes GHOP info out to the people who know the most about the code/documentation/etc. (and also hopefully result in some more task ideas and reviews, which we desperately need.)

  3. We had talked about ditching this group, since it creates yet another place to have to look for information, but I think it's important to have a way to get announcements out and also hopefully for the students to kind of socialize with one another and introduce themselves. So we'll keep it for now and see how it goes.

Any questions/comments/suggestions welcome.

Google Highly Open Participation Contest (GHOP)

Group organizers

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds:

Hot content this week