Create documentation for monthly mentoring team meetings on Slack

Created on 9 October 2024, 8 months ago

Problem/Motivation

Mentoring team meetings take place at 20:00UTC on the second Wednesday each month.

We should document the process of planning and hosting the meetings.

Steps to reproduce

Proposed resolution

Create a document for meeting hosts to follow.

Remaining tasks

  • Create draft document
  • Mentors to review
  • Migrate to document page

User interface changes

API changes

Data model changes

📌 Task
Status

Active

Component

Documentation

Created by

🇮🇪Ireland lostcarpark

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

Comments & Activities

  • Issue created by @lostcarpark
  • 🇮🇪Ireland lostcarpark

    I would be happy to help lead mentoring meetings.

  • 🇺🇸United States mradcliffe USA

    My current process:

    I find it easiest for myself to create the new issue when I go to credit participation and close the previous month's meeting issue,

    1. Review Slack for participation in the roll call and other threads:
      1. Confirm the Credit & committing > By list and check the boxes
      2. For each person, confirm their drupal.org username if it was not provided by them, and type it in Credit & committing > Credit others, then type a comma
      3. Review the list to make sure I got everybody and did not use an old username from my memory rather than a current username.
    2. Change the Status to fixed and add a comment closing the issue with credits
    3. Follow the "clone issue" link (this might be dreditor)
    4. Update the title for the correct day, month and year of the next meeting.
    5. Update the dates in the issue summary
    6. Remove the URL to the previous month's meeting with a placeholder
    7. Remove any expired agenda items such as previous DrupalCon planning threads, previous event threads.
    8. Renumber thread emoji as needed
    9. Save
    10. Update placeholder from the step above with the new URL and save the issue again

    I think this should be done anywhere from 1 week after the previous meeting to account for continual discussion and 1 week prior to the next meeting to provide time for editing the agenda by any mentor.

    If I am running the meeting, then just before 20:00 UTC I do the following:

    1. Set the issue in my browser to Edit mode
    2. Ensure I am on Drupal Slack in the mentoring team coordination channel
    3. I copy the initial chunk of text until the first empty line and paste it into Slack
    4. I immediately paste the :zero: agenda item into Slack and start a thread introducing myself.
    5. I try to continually copy a group of agenda items, separately, so each can be its own thread in fairly rapid succession so that I can participate in the discussion too. I try to start each group of agenda items or the next agenda item after about 2-3 minutes so that there is time to bounce between threads for active discussion.
    6. Near the 45 minute mark or later, I paste the "That's it for now" message
  • 🇬🇧United Kingdom rachel_norfolk UK

    Following the notes for the meeting next week as testing...

  • 🇬🇧United Kingdom rachel_norfolk UK

    I tell you what, lostcarpark, let me run this meeting to test the script above, then you can test any changes we make next month?

  • 🇬🇧United Kingdom rachel_norfolk UK

    changes needed
    - add step to set status of new cloned issue to Active

  • 🇮🇪Ireland lostcarpark

    Sounds good, @rachel_norfolk!

  • 🇺🇸United States mradcliffe USA

    Thank you for running through what I had, rachel. Changing status to Needs work based on feedback.

Production build 0.71.5 2024