In attendance: @adityakane, @coachbirgit, @gusa, @harishanker, @kafleg, @leogopal, @matteoenna, @mayukojpn, @kirasong, @nao, @ninianepress, @oglekler, @onealtr, @patricia70, @sereedmedia, @tobifjellner, @topher1kenobe, @webtechpooja, @yoga1103
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 Event Supporter (formerly Mentor) is someone who has already organised a WordCamp and has time to meet with their assigned mentee every 2 weeks, they talk over where they should be in their timeline, help them to identify their issues, and also identify solutions for their issues. 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.
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
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.
@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 Event Supporter (formerly Mentor) is someone who has already organised a WordCamp and has time to meet with their assigned mentee every 2 weeks, they talk over where they should be in their timeline, help them to identify their issues, and also identify solutions for their issues. 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 GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ 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 Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 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”
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
@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 Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-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 Meetup groups are locally-organized groups that get together for face-to-face events on a regular basis (commonly once a month). Learn more about Meetups in our Meetup Organizer Handbook. 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.”
#wpcontributors, #contributor-mentorship, #contributor-working-group, #mentorship-programs, #mentorship-chat, #mentorship-chat-agenda #mentorship-chat-recap