>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3519977. --> Reported by: [mradcliffe](https://www.drupal.org/user/157079) >>> <h2>Mentoring Working Group Minutes 2025.04.17</h2> <h3>In Attendance</h3> <p>Matthew Radcliffe 'mradcliffe'<br> Rachel Lawson &lsquo;rachel_norfolk&rsquo;</p> <h3>Action Items from previous meeting minutes:</h3> <ul> <li>Mapping out and auditing all Mentoring pages on Drupal.org</li> <li>Updating timeframe documents and converting to a spreadsheet including subtask files</li> <li>Resolving the calendar for meetings and events</li> <li>Agreeing on the Document Store - writing up the proposal</li> </ul> <h3>New Coordinator Discussion</h3> <ul> <li>James Shield 'lostcarpark' coordinator application - <a href="https://www.drupal.org/project/mentoring/issues/3516253">https://www.drupal.org/project/mentoring/issues/3516253</a> <ul> <li>AmyJune, Chris, Rachel provided feedback.</li> <li>Waiting on additional approvals, but deadline has been reached.</li> <li>Feedback is good, we have given it time.</li> <li>Next step: move to core issue and make a merge request &mdash; assigned Matthew</li> </ul> </li> </ul> <h3>Mapping out and auditing all Mentoring pages on drupal.org, Google drive(s), OpenSocial contributions</h3> <ul> <li>Next steps &mdash; assigned Rachel <ul> <li>Create an issue with an issue summary</li> <li>Create a spreadsheet that's public.</li> <li>Probably as good a way as we can do.</li> <li>Audit page and categorize as whether it needs to be GitLab pages (reference information), Roles, Skills, Tasks.</li> </ul> </li> <li>Rachel and Matthew to put some further thought into the Drupal Contribution site of awesomeness and whether the member platform proposal could be interesting.</li> </ul> <h3>Updating timeframe documents and converting to a spreadsheet including subtask files</h3> <p>"t - 100" timing document, but we need to remember DrupalCon tends to have longer requirements than a camp &minus; build for DrupalCon and camps can adjust. Other camp organizations like MidCamp may have a longer timeline.</p> <ul> <li>Next steps: &mdash; assigned Chris <ul> <li>Create an issue with an issue summary</li> <li>Create a spreadsheet in the Mentoring google drive for now?</li> <li>Would this end up in GitLab pages?</li> <li>There are useful things that spreadsheet provides.</li> <li>We don't know yet, and need to find out.</li> </ul> </li> <li>We need to prioritize this item because DrupalCon Vienna 2025 planning starts soon.</li> </ul> <h3>Resolving the calendar for meetings and events</h3> <ul> <li>Automating and creating ICS/Shared Calendar file so we can import into our own calendars.</li> <li>Matthew started playing around locally with a GitLab CI job and node.js command-line to create ICS files.</li> <li>Drupal Core Calendar does still exist - at <a href="mailto:drupalcorecalendar@association.drupal.org">drupalcorecalendar@association.drupal.org</a> <ul> <li>Theoretically a job could post to the calendar -or- retrieve a ICS file from that calendar with UTC as the date.</li> <li>We could manage our own meetings with a merge request.</li> <li>Rachel will ask Tim about whether we should have these on that calendar or not. &mdash; assigned Rachel</li> </ul> </li> <li>Create an issue with an issue summary to track this item &mdash; assigned Matthew</li> </ul> <h3>Agreeing on the Document Store &minus; writing up the proposal</h3> <ul> <li>Does this depend on the auditing item? <ul> <li>Yes, it requires that.</li> <li>We did decide that we would use GitLab pages for the document store of reference information. We have not documented as a proposal.</li> <li>Create an issue with an issue summary to propose organizing all further Mentoring documentation &mdash; assigned <del>Chris</del> Rachel <ul> <li>Reference information in GitLab pages.</li> <li>Roles, Skills, and Tasks on drupal.org content types.</li> <li>YouTube videos</li> </ul> </li> <li>The Drupal Contribution site should not store documentation / reference information anymore.</li> </ul> </li> </ul> <h3>DrupalForge / DrupalPod Update</h3> <ul> <li>Matthew has a every other week meeting with Salim at DrupalForge to discuss things. <ul> <li>Salim was looking at creating a contribution kit for people who want to lead contributions. <ul> <li>Software</li> <li>Support</li> <li>The idea is to create a baseline to create this contribution kit.</li> </ul></li> </ul> </li><li>Salim wants to be involved in working group / decisions. Not the Mentoring Working Group, but a working group around this particular topic. Being involved in future discussions. <ul> <li>Consensus to we reach out to Brian to see if he's interested in working and discussing it as well?</li> <li>Also Randy. </li> </ul> </li> <li>DrupalForge wants to be aware of when things happen so that they can scale.</li> <li>How best to credit DrupalForge for their efforts. <ul> <li>Issues credits per user using DrupalForge?</li> <li>Maybe using attributes customer (existing functionality on issues)? Could be a misuse of the system that could work.</li> <li>Like an employer, but they're supporting the contribution.</li> <li>DrupalForge also wants to sponsor contribution events possibly as an in-kind sponsor to the event.</li> </ul> </li> <li><a href="https://drupalforge.org/drupalpod">https://drupalforge.org/drupalpod</a> (for testing).</li> <li>Still need to create an issue for co-maintainership of DrupalPod &mdash; assigned Matthew</li> <li>We need to update the Mentoring vscode extension (open vscode).</li> </ul> <h3>Action items</h3> <ul> <li>Create issues for existing action items so we can refer to those issues in future meetings.</li> <li>Update new coordinator issue title and scope, move to core issue queue, and create a merge request.</li> <li>Bylaws</li> </ul>