[Meta] mentoring mentor meeting June 6 2015 UTC 20:30

We encourage users to post events happening in the community to the community events group on https://www.drupal.org.
YesCT's picture
Start: 
2015-06-06 20:30 - 22:00 America/Chicago
Organizers: 
Event type: 
User group meeting

Share what mentoring successes and challenges you have had. 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.

We need:
people who can help organize us,
developers to help us with d.o issues that will effect contributor or mentor experience,
planners to help with events,
... lots of different skills.

Mentor Meta meetings are once a month, usually on the first saturday of the month, at UTC 20:30. To find the meeting ping YesCT or another mentor in IRC or check the mentor google calendar for the google hangout link. See https://www.drupal.org/core-mentoring for the calendar.

Comments

IRC Mentoring is picking up, what do do?

cilefen's picture

We had 8+ active mentees today. We need more IRC mentors. https://goo.gl/gV1X7U And, #drupal is becoming so noisy during mentoring we may need a channel.

That's awesome! I'll try to

disasm's picture

That's awesome! I'll try to be available next week. Been busy playing catch-up from being gone for DrupalCon this past month. As for moving it from #drupal I'm against that. I've had a number of people start mentoring that aren't there for it and check it out because it's announced in the past (that being how I started out myself as well). I usually find it better to tell everyone with support questions to go to #drupal-support.

Yes, #drupal becomes more noissy

RavindraSingh's picture

Agreed on @cilefen, but it should be fine, found only new drupalers are communicating on this. If we use different channel might be New drupalers feel only few are coming here to contribute (May be demotivate).

Thoughts?

The pro for having a separate

alimac's picture

The pro for having a separate channel is cutting down on the noise. The con for having a separate channel is... cutting down on the noise.

One of the worries is that having a dedicated channel will make folks likely to stick to just that channel and more reluctant to join #drupal-contribute.

Another worry is that the channel would be lightly attended outside of mentoring hours. It's also good to expose casual #drupal IRC user to mentoring.

We integrated content from drupalmentoring.org to drupal.org and the idea is to make mentoring an integral part of contribution, rather than its own thing.

When it gets crowded, you can pair people up to work on the same issue, together.

Or, ask a repeat mentee to start mentoring: ", I think you could help us mentor today. Let's work together with on this issue." or something like that. Basically, propose it to them, show confidence, but also reassure them that you are going to work with them.

Will join this meeting definitely.

RavindraSingh's picture

Will join this meeting definitely.

MEETING NOTES

roderik's picture

Thanks to xjm and others for taking live meeting minutes (in Google doc) - this is a reformatted version.

Attendees

Cathy (YesCT)
Alina (alimac)
Kalpana (kgoel)
Valery (valthebald)
David Hernandez
Jess (xjm)
Lucas Hedding (heddn)
Chris (cilefen)
roderik

Drupalcon LA recap

1)
Results from the Mentor Feedback survey (thanks alina for compiling) were discussed.

2)
Many people doing issue reviews posted short comments in the form of "Tested. Looks good", which are less than helpful in getting issues resolved. The relatively high number of first-time mentors at the LA mentored sprint probably contributed to this. An issue has been opened to mitigate this by a.o. updating mentor documentation.

3)
We continue to have more and more new mentors at DrupalCons, with fewer experienced mentors. Ideas were discussed to improve everyone's experiences at sprints. Summarized:

  • We (and/or the DA) need to make sure there are return mentors. Discussion included many comments about whether/how trying to encourage experienced mentors to do multiple Cons per year is feasible. Investing in someone who we know can lead next year would be great, but it's hard to plan people's time in advance.
  • Have mentees say who their mentors are so we can:
    • give the novices feedback via the mentor when needed for a better experience
    • mentor the mentors as well
  • Adding additional recognition for mentors (documenting/crediting mentor on issue, profile, etc.): is being done now.
  • What works well: have new mentors show an experienced mentor the work with the contributors
    • to make it scalable: we need around 4 experienced mentors that are essentially doing the second-tier feedback
    • can come up to front and/or walking around room to mentors asking how things are going
  • What worked well in terms of mentoring mentors: reading mentor orientation from a document, taking turns -- this kept people interested; demonstrated that no one person held the knowledge
  • What didn't work well: mentors still didn't all attend
    • A mic / more announcements in the mentor room might have helped pull things back together
    • Most mentees -after attending mentor orientation- don't really get started until right before lunch, most work done after lunch. We try to do the live commit at around 3PM which leaves them only around 2 hours to do real work. It's not a big timeframe to get things done.
  • More discussion about how/whether to group sprint participants around experienced mentors that will lead each group, and different possibilities to group people (skill level, per issue (category), contribution experience...)

4)
Environment setup

  • Speaker notes for the Newbie orientation should be improved
  • To do at sprint: intentionally excuse anyone from the Newbie orientation who is not needing to have D8 installed (i.e. documentation only sprinting) so they don't waste time on that.
  • vagrant issue: https://www.drupal.org/node/2232049

5)
What to do differently:

  • There needs to be a microphone in the mentoring room; need to have more announcements like:
    • attendees, please update your profile
    • add mentors to your profile
  • emphasize more that mentors should refer to contributor task documents with mentees
  • Idea: short survey with questions to help people sort by skillsets? Or: ask people to move themselves (and be insistent about it)
  • reiterate to DA that attendance should be taken 2-3 times (once in the morning during the workshop, one before lunch, once after lunch)
  • @alimac has ideas about doing the workshop, will take this up with Brian
  • have someone (other than Cathy) who makes sure DA, all mentors do their jobs

Drupalcon Barcelona

See 5) above.

Also, ideas/proposals for talks were discussed.

IRC checkin

Attendance:

  • very obvious increase in attendance since LA
  • fewer new people coming, more returning people coming
  • last Wednesday was very busy -- keeping a spreadsheet at https://goo.gl/gV1X7U
  • but also seen: lot of excitement before hour starts and when it does, people are not there
  • people demanding mentoring at random times -- joining mentoring channel
    lack of the second slot also makes things worse
  • @todo: revisit when another timeslot could be

Issue finding:

  • harder and harder to find good starter issues, fewer novice issues (due to the release phase)
  • still having the issue where mentees use mentors as issue-finders, mixed
  • results getting them to move on to their own work
  • some mentors gently giving harder issues works well

Novice issues triage

Finding novice issues is hard. Additionally, many categories of novice issues are out of scope for the beta release -- this point was not discussed extensively.

Major issues triage

  • The structure of previous triage/sprint(s) worked well
  • need to repeat more this summer
    • have major triage IRC meetings
    • reach out to local sprints/camps
      • target an area/component
      • physical (better) or online presense of area/component maintainer helps a lot
    • directly email component maintainers, so that they at least know the contributor task doc exists and they have read it
  • get feedback from chris and kgoel
  • People who did the triaging wanted to then work on the issue. It was hard for triage leaders to tell people "No, please don't work on things but do more triage".
  • not a case for d8 accelerate money

newly joining in

Tamara Parris's picture

Hi I am Tamara and just joining in to the discussion

Can you share how this works? I am interested in a mentor. Thanks :)

Hi Tamara, Are you interested

cilefen's picture

Hi Tamara,

Are you interested in being a mentor or in being mentored?

mentor or mentee

Tamara Parris's picture

I am interested in both. I am a newer CM, that could mentor a starter. I could help with the basics.

I would like to be mentored by someone more seasoned, and has 3 or 4 years more of experience.

My current group is called EHS Professionals on LinkedIn. I would like to take it to the next level.

Please go through

RavindraSingh's picture

Please go through https://www.drupal.org/core-mentoring and join the IRC as scheduled for Wednesday.

do not really understand

Tamara Parris's picture

I am not clear; what you want me to do on that page? Join what? Where do I join and what am I joining?

Follow @drupalmentoring on

cilefen's picture

Follow @drupalmentoring on Twitter. Online mentoring is handled in IRC (see https://www.drupal.org/irc). The IRC channels used for mentoring are #drupal and #drupal-mentoring. The former is for mentoring itself at scheduled times, and the latter is for mentors discussing mentoring.

It will be difficult to participate online without being on IRC. The instructions should get you started. Say hello in #drupal-mentoring and we will find what you need.

never mind - thanks

Tamara Parris's picture

I am sorry - this is too complex and confusing. I think I will look somewhere else.

I just wanted to mentor and be mentored, in a very simple platform.

I am on twitter, I do not find it at all valuable for real conversations of any depth. It is certainly not a places I would want to use to be mentored, or be mentoring someone. That is way to public a place to share things.

thanks anyways.

Tamara- I regret that you

cilefen's picture

Tamara-

I regret that you find this confusing. There are other ways to get involved with the project (https://www.drupal.org/contribute and https://assoc.drupal.org/).

By the way, Drupal core contribution mentoring is on IRC chat, not in Twitter. Twitter is for announcements about mentoring events. There are in-person mentoring events at national and regional events.

IRC Chat

Tamara Parris's picture

I tried that IRC Chat; I get an error message because our security does not allow it.

other options for IRC

decibel.places's picture

Tamara, I assume you mean your firewall at work blocks IRC. That is not uncommon. You could contact helpdesk and ask if there is a way to use IRC. Most likely they will say no.

You could join IRC from home, a WIFI cafe, or somewhere else.

There are IRC client apps for smartphones and tablets. If you must connect to your company VPN at work on a smartphone, you will probably encounter the same blockage.

Don't give up - there are solutions that can work for you!

I'm busy, but not dropping out of mentoring

decibel.places's picture

I'm very busy for the next couple of months. I'm still interested in mentoring, and I'll contact you when I have more time.

I had a job interview yesterday and I thrilled them when I said, "I mentor junior team members." :D

Tamara Parris's picture

thank you, I will try getting on at home then.

It would be great to connect -thank you

Good luck, I hope you land the new job.

You can try web-based IRC

alimac's picture

You can try web-based IRC clients: https://webchat.freenode.net/ or http://irccloud.com.

Mentoring

Group organizers

Group notifications

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

Hot content this week