#meeting:fedoraproject.org: commops

Meeting started by @jflory7:fedora.im at 15:03:04 UTC

Meeting summary

  1. TOPIC:Agenda (@jflory7:fedora.im, 15:03:45)
    1. INFO: (1) Intros, welcomes, hellos (@jflory7:fedora.im, 15:03:49)
    2. INFO: (2) Team announcements & news (@jflory7:fedora.im, 15:03:52)
    3. INFO: (3) Initiative Co-Lead updates to the team (@jflory7:fedora.im, 15:04:03)
    4. INFO: (4) Follow-ups from last meeting (@jflory7:fedora.im, 15:04:06)
    5. INFO: (5) Ticket-driven discussion (@jflory7:fedora.im, 15:04:08)
    6. INFO: (6) Open floor (@jflory7:fedora.im, 15:04:10)
  2. TOPIC:Intros, welcomes, hellos (@jflory7:fedora.im, 15:04:16)
    1. INFO: Present: @moralcode @rwright @neil @jflory7 @jonathanspw (@jflory7:fedora.im, 15:06:59)
  3. TOPIC:Team announcements & news (@jflory7:fedora.im, 15:07:36)
    1. INFO: === The Fedora Linux 41 Global Watch Parties will take place on Friday, which is a new approach to how we produce and execute the virtual Release Parties. Registration is now open for the three major time zone regions of the world. === (@jflory7:fedora.im, 15:08:16)
    2. LINK: https://rsvp.fedoraproject.org/releases/f41-apac/ (@jflory7:fedora.im, 15:08:28)
    3. LINK: https://rsvp.fedoraproject.org/releases/f41-emea/ (@jflory7:fedora.im, 15:08:31)
    4. LINK: https://rsvp.fedoraproject.org/releases/f41-latam-na/ (@jflory7:fedora.im, 15:08:35)
    5. INFO: === "Looking back at Flock to Fedora 2024" === (@jflory7:fedora.im, 15:09:43)
    6. LINK: https://communityblog.fedoraproject.org/looking-back-at-flock-to-fedora-2024/ (@jflory7:fedora.im, 15:09:48)
    7. INFO: === "Proposed change to the Fedora Council policy for Edition promotion" === (@jflory7:fedora.im, 15:10:17)
    8. LINK: https://communityblog.fedoraproject.org/proposed-change-to-the-fedora-council-policy-for-edition-promotion/ (@jflory7:fedora.im, 15:10:22)
  4. TOPIC:Fedora CommOps Initiative Co-Lead updates to the team (@jflory7:fedora.im, 15:13:32)
    1. INFO: If you have the Message Bus data set from above in the Digital Ocean storage I shared, check out the user_parsed_2024 folder for a new dataset with parsed data. It contains a file per day of data that I've preparsed with data from the bus to extract FAS IDs. I will share the Python files on GitLab shortly, but I wanted to get the data up today. (@jflory7:fedora.im, 15:14:19)
    2. INFO: Example header: sent_at,id,topic,username 2024-07-29 23:59:48,014ee981-b122-4346-8be1-0b5af13685be,org.fedoraproject.prod.buildsys.untag,music (@jflory7:fedora.im, 15:14:33)
  5. TOPIC:Ticket-driven discussion (@jflory7:fedora.im, 15:16:32)
  6. TOPIC:Ticket #46: "Fedora Linux 41 Release Party - main tracker ticket" (@jflory7:fedora.im, 15:19:30)
    1. LINK: https://gitlab.com/fedora/commops/home/-/issues/46 (@jflory7:fedora.im, 15:19:31)
    2. ACTION: @jflory7 Add Adrian to the shared folder with video recordings (@jflory7:fedora.im, 15:31:04)
    3. ACTION: @jflory7 Add today's recordings to the shared folder (@jflory7:fedora.im, 15:31:26)
    4. ACTION: @rwright Create a CommBlog draft to announce the F41 Global Watch Parties and share for review with editors today (@jflory7:fedora.im, 15:41:06)
  7. TOPIC:Open floor (@jflory7:fedora.im, 15:53:09)


Meeting ended at 15:56:41 UTC

Action items

  1. @jflory7 Add Adrian to the shared folder with video recordings
  2. @jflory7 Add today's recordings to the shared folder
  3. @rwright Create a CommBlog draft to announce the F41 Global Watch Parties and share for review with editors today


People present (lines said)

  1. @jflory7:fedora.im (186)
  2. @irradiated_lemming:matrix.org (45)
  3. @rwright:fedora.im (23)
  4. @nhanlon:beeper.com (13)
  5. @zodbot:fedora.im (11)
  6. @jonathanspw:fedora.im (6)
  7. @meetbot:fedora.im (3)