RainbowArray
commented
7 years ago I'd maybe just add another bullet point under number 3:
- If there's sufficient interest for a second cohort group that's more back-end based, maybe look at Media API updates in contrib? And/or working on updating tests in core?
sparklingrobots
1b. Meeting Overview: Goal of the project: To increase code-based contributions from individuals from under-represented groups to the Drupal project.
This channel right now is being used to organize a mentoring program. During this meeting I'd like to formalize the first group/cohort of mentors/mentees and develop a plan to support them as they work together.
Survey to find out: Names, Contact info, skills/connections you can offer, skills/connections you want to develop, what do you want to get out of participating in this project?
Form a team (or multiple teams) of 6-10 to work together for 2 months as the first cohort(s). --Which project to tackle first? ok_lyndsey's accessible NFP theme idea? something else? --Who is taking the lead on the cohort's project?
How will the cohort(s) work together? --Priority is to use standard community tools & practices (e.g. drupal.org), but what will we use to supplement? Is this slack channel enough? DDI repos? Drupal Dojo group? --More stable place for documentation of our process/resources/meeting notes?
When will we meet on an ongoing basis to support the mentoring program as a whole (as opposed to the specific work of a cohort)?
I don't think we will have time for these but they are on my mind:
How will we measure diversity of the cohort(s)?
How will we measure success of the cohort(s)?
If time remains, how do we want to work with other groups, like Drupal Dojo?