Contrib.social

Mentor Working Group Meeting − 17 April 2025

Open on Drupal.org →
Created on 18 April 2025, 3 months ago

Mentoring Working Group Minutes 2025.04.17

In Attendance

Matthew Radcliffe 'mradcliffe'
Rachel Lawson ‘rachel_norfolk’

Action Items from previous meeting minutes:

  • Mapping out and auditing all Mentoring pages on Drupal.org
  • Updating timeframe documents and converting to a spreadsheet including subtask files
  • Resolving the calendar for meetings and events
  • Agreeing on the Document Store - writing up the proposal

New Coordinator Discussion

  • James Shield 'lostcarpark' coordinator application - https://www.drupal.org/project/mentoring/issues/3516253 📌 Add new defacto Mentoring Coordinators to MAINTAINERS.txt Active
    • AmyJune, Chris, Rachel provided feedback.
    • Waiting on additional approvals, but deadline has been reached.
    • Feedback is good, we have given it time.
    • Next step: move to core issue and make a merge request — assigned Matthew

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

  • Next steps — assigned Rachel
    • Create an issue with an issue summary
    • Create a spreadsheet that's public.
    • Probably as good a way as we can do.
    • Audit page and categorize as whether it needs to be GitLab pages (reference information), Roles, Skills, Tasks.
  • Rachel and Matthew to put some further thought into the Drupal Contribution site of awesomeness and whether the member platform proposal could be interesting.

Updating timeframe documents and converting to a spreadsheet including subtask files

"t - 100" timing document, but we need to remember DrupalCon tends to have longer requirements than a camp − build for DrupalCon and camps can adjust. Other camp organizations like MidCamp may have a longer timeline.

  • Next steps: — assigned Chris
    • Create an issue with an issue summary
    • Create a spreadsheet in the Mentoring google drive for now?
    • Would this end up in GitLab pages?
    • There are useful things that spreadsheet provides.
    • We don't know yet, and need to find out.
  • We need to prioritize this item because DrupalCon Vienna 2025 planning starts soon.

Resolving the calendar for meetings and events

  • Automating and creating ICS/Shared Calendar file so we can import into our own calendars.
  • Matthew started playing around locally with a GitLab CI job and node.js command-line to create ICS files.
  • Drupal Core Calendar does still exist - at drupalcorecalendar@association.drupal.org
    • Theoretically a job could post to the calendar -or- retrieve a ICS file from that calendar with UTC as the date.
    • We could manage our own meetings with a merge request.
    • Rachel will ask Tim about whether we should have these on that calendar or not. — assigned Rachel
  • Create an issue with an issue summary to track this item — assigned Matthew

Agreeing on the Document Store − writing up the proposal

  • Does this depend on the auditing item?
    • Yes, it requires that.
    • We did decide that we would use GitLab pages for the document store of reference information. We have not documented as a proposal.
    • Create an issue with an issue summary to propose organizing all further Mentoring documentation — assigned Chris
      • Reference information in GitLab pages.
      • Roles, Skills, and Tasks on drupal.org content types.
      • YouTube videos
    • The Drupal Contribution site should not store documentation / reference information anymore.

DrupalForge / DrupalPod Update

  • Matthew has a every other week meeting with Salim at DrupalForge to discuss things.
    • Salim was looking at creating a contribution kit for people who want to lead contributions.
      • Software
      • Support
      • The idea is to create a baseline to create this contribution kit.
  • 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.
    • Consensus to we reach out to Brian to see if he's interested in working and discussing it as well?
    • Also Randy.
  • DrupalForge wants to be aware of when things happen so that they can scale.
  • How best to credit DrupalForge for their efforts.
    • Issues credits per user using DrupalForge?
    • Maybe using attributes customer (existing functionality on issues)? Could be a misuse of the system that could work.
    • Like an employer, but they're supporting the contribution.
    • DrupalForge also wants to sponsor contribution events possibly as an in-kind sponsor to the event.
  • https://drupalforge.org/drupalpod (for testing).
  • Still need to create an issue for co-maintainership of DrupalPod — assigned Matthew
  • We need to update the Mentoring vscode extension (open vscode).

Action items

  • 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 issue queue, and create a merge request.
  • Bylaws
📌 Task
Status

Needs review

Component

Meeting

Created by

🇺🇸United States mradcliffe USA

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024