Mentor Meeting - Saturday, 5 March 2016 UTC 20:30

alimac's picture
2016-03-05 20:30 - 22:00 UTC
Event type: 
Online meeting (eg. IRC meeting)

[Meta] Mentor Meeting - Saturday, 5 March, 2016 at UTC 20:30 in Google Hangout.

To find the meeting ping YesCT or another mentor in #drupal-mentoring channel in IRC. See for the calendar.

Mentor Meta meetings are once a month, usually on the first Saturday of the month, at UTC 20:30. These are mentor meetings about mentoring (hence the "meta"), about upcoming events and ongoing Drupal core mentoring efforts.

Do you want to get involved doing mentoring but not sure what to do? Want to help Drupal mentoring be successful? Join us. All help is welcome:

  • people who can help organize us
  • developers to help us with issues that will effect contributor or mentor experience
  • planners to help with events
  • people with different skills who are interested

Share what mentoring successes and challenges you have had.


Mentoring meeting notes

davidhernandez's picture


  • cilefen (Chris)
  • heddn (Lucas Hedding)
  • xjm
  • YesCT (Cathy)
  • David Hernandez (davidhernandez)

DrupalCon Asia

  • 18-21 February. Sprint day was Sunday, 21 February.
  • Amazing level of participation
  • All-time record for first-time sprinter workshop attendance (188 people)
  • Second highest total of mentored sprint participation ever, after only Portland
  • Over 1/3 of conference attendees also attended the sprint -- comparable to the % sprint attendance at Bogotá
  • How did they do it? Combination of weekend con, closing session AFTER sprints, and really effective community organizing -- we should braindump with the con and sprint planners to learn more about what strategies they used.
  • Mentoring orientation was also very well attended (20 people), thanks in part to efforts from Ravindra tracking people down and getting them to come (pulling them away from company booths etc.)
  • About 10 participants in novice issue triage. (We weren't able to actually triage many issues during the time due to a d.o outage, but we were able to talk about what makes a good novice task.) (discuss more under novice triage item below)
  • @todo Should have had sticky nametags for sprint mentors and sprinters in addition to conference name badges, especially because of cross-cultural names. DrupalCon name badges remain too hard to read and facing the right way only 50% of the time.
  • Mentored major triage (discuss under major triage item below)
  • @todo Need to do a retrospective with con sprint team

DrupalCon New Orleans

  • May 9-13 2016
  • (invite needed)
  • Resources timeline:
  • Sprint leads:
  • Mentors attending:
    • Yes: xjm (but can't actually mentor....), heddn, Deciphered, alimac, yesct, joel, davidhernandez, valthebald
    • Maybe: cilefen
    • No: realityloop
  • Update from Cathy about looking for a new Sprint and Mentoring Lead
  • @realityloop/@Deciphered would like to trial at the event with a handful of people to get data about the issue that may arise, including trial before the event using different OS-es.
  • @heddn brought up the notion of using the PHP built-in server and sqlite, will update the group later.
  • @todo is it possible to have a web server on the conference venue network for distributing the workshop tools? (realityloop happy to follow this up if told who to contact at the DA. Can it be a regular laptop?) Mac Ethernet adapters needed, etc.
  • Distributing tools:
  • Have usb drives at booth with tools, and whenever someone approaches about sprinting, say, "here copy onto your desktop" with an elevator pitch of what it is
  • Direct people to link to download tools from a web server
  • during coffee breaks
  • Announce on social media
  • Have DA announce it in pre-keynote muckety muck (or have them have us do so)
  • Signs throughout the conference saying "Want to sprint Friday? If you don't have your dev environment set up, download this!"
  • New business:
  • @todo YesCT, heddn, alimac, meeting with DA late in the week of March 21.
  • @todo cilefen Organize a meeting after the DA meeting with sprint leads.

Documentation check-in

  • Old business:
  • @todo need a summary of points from Mentoring at events (append to the bottom of the doc)
  • @todo val (still relevant) - d.o. create or update a page with quality programming resources. (Drupal 8 developing guide, api.d.o D8 front page, phptherightway,, etc). Add an IRC factoid (programming?)

IRC mentoring check-in

  • Can we share some of the structure used for the contrib mentoring hours to give people the choice? Always a concern with specific maintainers, though. Core maintainers at least are a known quantity.
  • @todo It would also be good to see if there is something we can do reinvigorate interest in working on core

Novice issue triage

  • xjm ran a novice issue triage session at Mumbai with 10ish mentors. Talked through the novice issue guidelines, demoed triaging one issue while talking aloud through all my reasoning, then had several contributors also try doing a triage in front of the group. Triaged some small part of the queue; hindered by d.o being down.
  • Also removed the novice tag from fixed, closed, and postponed issues, since it is important for novices to be able to re-find the queue without relying on a link and not be confused when it contains issues that are not actionable.
  • is that in the doc?
  • Also
  • Some triagers did not link the novice tasks reference in their comments, which resulted in some confusion from a contributor (naveen) who went and put the tag back on, thinking it was for metrics rather than a status. Explained that the novice tag creates a queue and individual sprint tags should be used for metrics, and that this was a limitation of the d.o issue tag field in general (where some tags are a state but others are metadata).
  • @someone add timeline for novice issue triage (separeate page? link from organizer timeline page and novice task page?)
  • @xjm to write promotional words that make people want to participate "your chance to sit with X"

Major issue triage

  • Ran a "current state" triage as part of Mumbai
  • 8 active participants looked at 15-ish issues (there were other more "passive" participants)
  • Participants were reluctant to work in pairs as requested (cultural/language thing? Or just the typical reluctance)
  • One technical project manager came and grokked the goals very quickly, working efficiently; delegated him to go around the room and make sure everyone else was doing well and understood what was going on since they seemed shy to talk to me
  • @todo Flowchart needs update for updated instructions and current release cycle phase.
  • Identified 7 issues for "Current state" triage that committers will assess soon as part of major triage process
  • tag: triaged for d8 major current state

Contrib mentoring

  • heddn checked in with tim plunkett
  • participants seem to be bringing their own pet projects
  • sometimes long time experienced contributors "taking advantage" of tim
  • 1-3 issues in core blocking people, need patches, getting people into core
  • possible follow up for tim: are there issues when appropriate (in the contrib issue queue)