Mentor Working Group Meeting - 24 April 2025

Mentoring Working Group Minutes 2025.04.24

In Attendance

• Matthew Radcliffe 'mradcliffe'
• Chris Darke 'ChrisDarke'

Action items from previous meeting minutes:

• Create issues for existing action items so we can refer to those issues in future meetings.
• Update new coordinator issue title and scope, move to core isuse queue, and create a merge request.
• Bylaws

New Coordinator Discussion

• Rachel moved the issue to the core issue queue.
• James created the merge request
• Issue is now RTBC
• Next step: invite James to Slack channel — done

Cleaning up Slack channel membership

• Post message/notification about Slack channel membership.

Mapping out and auditing all Mentoring pages on drupal.org, Google drive(s), OpenSocial contribution

• Rachel assigned herself to track/being assigned to this topic.
• This would be a great task for James to help out with.

• Need to create issue by 29th of April

• Member platform would be great if we could be a test / use case and we would not need to worry about implementation.

  • Contribution idea for new and first-time contributors to work on it.
    • Matt needs to triage issues for MidCamp's Member Platform and Event Platform contribution day.
  • No definitive action items for this yet.

Updating timeframe documents and converting to a spreadsheet including subtask files

• Chris is okay with tracking/being assigned to this topic.
• Chris started timelines spreadsheet document.
  • We need to get something together soon so we can send a draft to Kuoni.
  • Potentially there are exportable lists depending on different schedules from different event organizers and companies.
  • Complete first draft by 29th of April
• Need to create issue by 29th of April
• Need to define the Europe Coordinator lead - will send out a message on the leads channel.

Resolving the calendar for meetings and events

• Matthew is assigned to this topic.
• Need to create issue by 29th of April — Matthew
  • Automation job looks a bit more complex than an out-of-the-box solution.
• Rachel will ask Tim about whether we should have these on the Drupal Core Calendar.

Agreeing on the Document store — writing up the proposal

• Chris is assigned to this topic.
• Need to create issue by 29th of April to organize all further Mentoring documentation.
  • Reference information it GitLab pages.
  • Roles, Skills, and Tasks on drupal.org
  • YouTube videos
• Need to create issue by 29th of April to create a Bylaws document (can be empty) to be stored in GitLab pages.

DrupalForge / DrupalPod Update

• Technical working group around contribution tools / contribution kit still needs to be formed. 14th of May is next Mentoring meeting. So bringing this up as an agenda item at the next mentoring meeting.
• Issues credits:
  • It would be tricky to get people to remember to add the "for customer" in their comments.
  • Issue tag for people using DrupalForge?
  • Do they credit if not using DrupalForge?
• Need to create an issue for co-maintainership of DrupalPod — Matthew
• Once this is working we will need to update videos / assets - need to make an issue

Mentoring Working Group Meeting

• Should we still be doing weekly?
  • Weekly is still good.
• Should we change the time?
  • Thursday is fine at 17:00 UTC.

Action items

• Create issues for existing action items so we can refer to those issues in future meetings. (See notes above)
• Post the message to those in mentoring leads channel about channel cleanup.
• Reminder for all leads to create the agenda item for 14 May 2025 Meeting
  • Next meeting: talk about coordinating / schedule creating/running/closing meta meeting issues.
  • Next meeting: review documentation for monthly mentoring meetings on Slack - [#3479788] 📌 Create documentation for monthly mentoring team meetings on Slack Active .
• Create issue for the minutes.