Last updated 2 July 2015.

Mentors are contributors who can occasionally commit a 1- or 2-hour block of time during core mentoring to assist participants. Some mentors participate in core mentoring regularly; others are experienced contributors who are willing to be "backup" when a mentoring session is particularly busy or one of the regular mentors is not available.

If you're interested in helping mentor office hours, join #drupal during office hours and say so, or ping one of the experienced mentors (YesCT, ZenDoodles, Cottser, valthebald, Deciphered, heddn, mdrummond, realityloop) in #drupal-contribute anytime to volunteer. Don't be shy! You don't need to be a super-multi-tasker or starmode core developer to help. You can start by mentoring one specific participant for the course of the session, and there will be a facilitator available to help you.

  1. Make sure you are familiar with the core mentoring task types.
  2. Follow @drupalmentoring.
  3. Keep an eye on #drupal. Many participants will not remember to ping you, so make sure to scan for anyone who says they're there for core mentoring.
  4. Join #drupal-mentoring (It is channel for mentors, not to do the mentoring in. Be sure to do mentoring of participants in public, in #drupal.)
  5. Ask the mentorbot schedule? to see what other mentors might have signed up to mentor during the same core office hours time.
  6. Immediately make note of all participants. Help participants one by one. Make sure to inform participants who are waiting that you'll help them soon.
  7. If there are more participants than you can manage, ping another mentor for help. If no mentors are around, ask for help in #drupal-contribute.
  8. Help the participant find a suitable task
    • If the participant is new to core mentoring, ask the participant about his/her skills, experience, and interests.
    • Ask what other issues the participant has worked on in the past.
    • Paste links, and talk out-loud as you look for an issue.
    • Consider reviewing an issue the participant has worked on in the past, and have them address your feedback.
    • Issues tagged Novice or tagged with one of the needs tags might be helpful in identifying something to work on.
    • If the participant is hesitant, vague, or unsure, try specific questions, like, "Do you have a local installation of Drupal that you can use for testing?" and "Have you applied a patch before?" (Start with basic things and work up. We don't want to scare people away by asking them if they've done things they've never heard of.)
    • Regardless of the participant's skill level, start with a simple, straightforward task. (E.g., no matter how experienced they are, don't assign them manual testing that involves mail sending, or an upgrade path test, or a patch review, etc.)
  9. If the participant has participated in core mentoring previously, check the participant's site profile to see what sorts of tasks the participant has done before (as well as any notes from other mentors), and use that as a starting point for picking a task.
    • If the participant has had difficulty with previous tasks, try simpler ones (e.g., simple manual testing instead of patch cleanup).
    • If the participant did well and is enthusiastic, try to challenge the participant with a new kind of task from the same level (A, B, or C) or higher.
    • Certain "regulars" and experienced contributors will be able to handle anything you throw at them. Give these participants the difficult and high-priority tasks.
  10. Before assigning a task to a participant, check the latest comments in the Drupal.org issue and make sure the task is still relevant. If an issue is tagged novice, but does no longer meet the criteria of a good novice task, remove the novice tag.
  11. Make sure instructions to applicable contributor task documents are in the issue summary in the remaining tasks section. (The dreditor "insert novice tasks" button can be helpful sometimes for putting tasks and instructions into the summary.)
  12. Ping the participant with the link to the issue. Mention that task instructions are available in the issue summary and suggest the participant start by reading those instructions first, and then reading the linked issue. Encourage the participant to ask you any questions he or she might have.
  13. Help the participant through each task, including (when necessary) help with setting up a development site, installing git, using git, etc. If you're unsure about one of the participant's questions or something about the task, don't hesitate to ping xjm or ask for advice in #drupal-contribute.
  14. As the end of the session nears:
    • Make sure the participant adds a comment to the Drupal.org issue documenting what they did, and help them improve this comment if it's unclear or unspecific.
    • Ask if the participant would like to work on another task.
  15. At the end of the session, check back in with each person you have mentored and thank them.