In attendance: @adityakane, @coachbirgit, @gusa, @harishanker, @kafleg, @leogopal, @matteoenna, @mayukojpn, @kirasong, @nao, @ninianepress, @oglekler, @onealtr, @patricia70, @sereedmedia, @tobifjellner, @topher1kenobe, @webtechpooja, @yoga1103
Notes: @nao
Agenda: https://make.wordpress.org/community/2023/09/19/contributor-working-group-mentorship-chat-agenda-september-21st-0700-utc-apac-emea-and-1600-utc-amer/
Meeting Start
APAC/EMEA: https://wordpress.slack.com/archives/C037W5S7X/p1695279617297589
AMER: https://wordpress.slack.com/archives/C037W5S7X/p1695312003171489
Summary
Based on the conversation, here are some takeaways from the meetings:
- We should try doing the next cohort alongside 6.5
- The next cohort size should be bigger
- We should put out a call for mentors along with mentees
- We should try to include more Make/Teams in the process
- We should revisit the process of mentorship, add more documentation, and processes
- Our project management tool will be our GitHub Project
Pending Tasks from our Past Cohort
These pending tasks were discussed, and additional feedback was provided.
- Share a post-event survey for mentees and mentors: @ninianepress and @leogopal will work on the email message to send out the survey.
- Create a draft contribution plan document (template) to encourage mentees to continue ongoing contributions: volunteer(s) wanted.
- Create and assign badges to mentors, mentees, and facilitators’ WordPress.org profiles: We are waiting for the #meta team’s help.
- 3-month mark check-in with mentees: Follow up with our mentees after three months to check how they are doing by November. @ninianepress and @leogopal raised their hands to help here.
Training Team’s Onboarding Process & Guide Program
@leogopal brought up the Training Team’s Learning Pathway project and suggested that we work on creating different pathways for contributors to meet their interested roles.
@gusa shared @piyopiyofox’s comment in the Refreshing the contributor pipeline discussion, where she said the Training Team onboarding program is highly successful and can be adapted to other Make Teams, process-wise.
Planning the Next Mentorship Cohort
Timing
Many shared their preference for the next cohort tining to be after some break, possibly alongside of 6.5 release. “As soon as possible” was also mentioned.
Cohort Size
@nao @harishanker @adityakane @tobifjellner said the cohort size could be larger next time. No mention in the exact number, except @adityakane said doubling the size (= 26 mentees).
@tobifjellner suggested multiple mentees per mentor could also be possible.
Centralize project management
Everyone agreed that we need a better project management tool, and using the GitHub Project for the working group that @leogopal had set up earlier is a good idea.
@coachbirgit shared that the discussion feature on GitHub Project can be useful for the group, so @nao enabled it: https://github.com/WordPress/wp-contributor-working-group-tracker/discussions
Working alongside a release
@nao @harishanker @coachbirgit @tobifjellner @kirasong @sereedmedia said running the next cohort along the 6.5 release would give enough preparation time for the working group.
@sereedmedia: “I like that the cohort could get exposure to the release process, regardless of what team they are on. it touches all the teams in some way, and the releases are why we are all here at the end of the day.”
@adityakane said intentionally decoupling the timing from release could help new contributors see non-core development parts of the project.
@ninianepres: “having a cohort alongside one release it super great and less overwhelming. But also, it’s worth taking a look at when these releases are scheduled just so we don’t feel we’re rushed like the last cohort”
Duration/Timeframe
Some suggestions were brought up about the duration and timeframe: increasing the 4-week period, separating out the general onboarding parts, and spending four weeks on the specific team onboarding.
@sereedmedia made a point about reviewing survey feedback before making a concrete decision.
Things to change for the next cohort
- Clear milestones/blueprint & tracker (@coachbirgit @yoga1103)
- Clear communication of key dates (@coachbirgit, @nao)
- Centralized & clear documentation (@harishanker, @nao, @adityakane)
- More widely promoting an open mentee call (@kafleg, @harishanker, @yoga1103, @ninianepress)
- Project-based tasks/hackathon/co-working (@oglekler, @nao, @harishanker)
Additional comments:
@kafleg: “Strictly monitoring and reporting the updates, and Mentee rating from Mentor and monitor”
@coachbirgit: “Template for a 90-day plan as follow-up for the mentees after the cohorts end.”
@sereedmedia: “Bug scrub & contributor day as a sprint, developing actionable contribution goals for each team that would be suitable for a “first issue”
@oglekler: “I can make a bug scrub meetup or something”
@ninianepress: “Consider having facilitators initiate the onboarding process, followed by mentors taking over/have different levels where junior & senior mentors or facilitators come in at different times; create checklists and forms for mentors as well this time and not just mentees; more clarity around defining the roles”
@adityakane: “Clearer framework, Github to project manage.”
Open floor/FYI
- Open Source Summit Europe 2023 is happening in Bilbao, Spain. @jeffpaul shared a great resource for mentors and mentees: Overcoming Imposter Syndrome and Gaining Confidence as an Open Source Mentee. Video should be added to that page, but you can watch it here for now.
- Training Team’s Guide Program handbook pages are a great inspiration to our project.
- WP Tavern podcast from @OGlekler where she highlights contributions: #90 – Olga Gleckler on How Anyone Can Contribute to the WordPress Project
#wpcontributors, #contributor-mentorship, #contributor-working-group, #mentorship-programs, #mentorship-chat, #mentorship-chat-agenda #mentorship-chat-recap