Help needed: Review a new contributor's work
Three weeks ago at DrupalCon Munich, we held the seventh Get Involved with Core sprint. Sixteen mentors and trainers helped over 150 sprint participants contribute to Drupal core for the first time. The work's not done, though -- we still need to follow up and give participants feedback. Currently, eighty-four tasks from the sprint still need to be reviewed.
The idea behind core mentoring is that each Drupal.org issue can be broken down into bite-sized tasks, like reviewing a patch, finding steps to reproduce an issue, or writing an issue summary. Novice contributors attempt these tasks during office hours and sprints. What we need now is experienced contributors to review their work! Help us out by trying your hand at doing a mentor review, even for just one participant's task, to confirm the task was done correctly. Here's how:
Contact xjm (or ping her on IRC) so that she can grant your account permissions to review tasks.
Click the task name for a full page of information about the task. (The Drupal.org node ID links to the issue itself).
Confirm that the participant attempted that particular task on the issue, and that they left a comment on the issue on Drupal.org. (If they didn't, or they did something else instead of that task, contact xjm with a link to the task and she'll sort it out.)
Review the participant's work (not the Drupal.org issue itself) and give the participant feedback. E.g., if the task was to triage an issue, verify that the issue was triaged correctly. (See the "Notes for reviewers" in the task sidebar.)
Edit the task node and update its Followup field.
- If the task is complete (even if the Drupal.org issue itself is not), set the followup field to Completed.
- If the particular task is not done or needs more work, set the followup to Awaiting followup. This makes the task available for someone else.
Let us know if you have any questions or suggestions! (For a tour of drupalofficehours.org, see this blog post about the site.)