Contrib.social

Feedback on AI Slack meetings

Open on Drupal.org →
Created on 1 July 2025, 3 days ago

Problem/Motivation

I have gone through a number of meeting-related issues and have feedback to review. I've put these in Slack but it's easy to lose these so putting here:

  1. I'm confused... it looks like you are manually grabbing information for the Slack meetings... do you know there is a browser plugin that will pull info out for async Slack meetings? https://www.drupal.org/project/ai/issues/3508193 🌱 Drupal AI Contribution meetup 2025.4 Active
  2. Why are the meeting issues created but then marked outdated? Example: https://www.drupal.org/project/ai/issues/3510849 🌱 Drupal AI Contribution meetup 2025.5 Active
  3. People are not being credited for participation
  4. a small thing, but I notice you call the Slack meetings a "meetup" rather than a "meeting"... is there a reason for this? From my experience, usually a "meetup" implies synchronous attendance (whether virtual or in-person)... other initiatives all call these async Slack discussions "meetings"... I like to keep things consistent with other projects/initiatives if possible to avoid potential confusion
  5. I don't understand why (it seems) we are numbering the meetings (e.g. 2025.1, 2025.2, etc)... meeting issues normally have the actual date in them (UTC time zone) so it's easier to see when it happened

Steps to reproduce (required for bugs, but not feature requests)

Please provide information like AI modules enabled, which AI provider, browser, etc.

Proposed resolution

  1. Use "meetings" instead of "meetup" for terminology in issue title and summary
  2. Do not tag with "meetup"
  3. Use the date of the meeting in the issue title (UTC time zone) and optionally include the meeting time in UTC
  4. Use the Chrome browser extension to grab the meeting info to put into the issue
  5. Have one or two people in charge of updating the issues in a timely manner and adding credits
  6. If a meeting doesn't happen and the issue needs to be closed, add a comment that the meeting didn't happen
  7. Have a backup facilitator who can run the meeting in case Val cannot

Remaining tasks

Review with Val and decide which of these will be implemented and by who.

Optional: Other details as applicable (e.g., User interface changes, API changes, Data model changes

🌱 Plan
Status

Active

Version

2.0

Component

Meetings

Created by

🇺🇸United States Kristen Pol Santa Cruz, CA, 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