===================================== # #meeting:fedoraproject.org: commops ===================================== Meeting started by @jflory7:fedora.im at 2025-10-14 13:59:49 Meeting summary --------------- * INFO: 2. Team announcements & news (@jflory7:fedora.im, 14:01:21) * TOPIC: Agenda (@jflory7:fedora.im, 14:01:21) * INFO: 1. Intros, welcomes, hellos (@jflory7:fedora.im, 14:01:21) * INFO: 3. Ticket discussions (@jflory7:fedora.im, 14:01:21) * INFO: 4. Open floor / Questions (@jflory7:fedora.im, 14:01:21) * TOPIC: Intros, welcomes, hellos (@jflory7:fedora.im, 14:01:43) * INFO: Name, FAS ID, time zone, morning bird or night owl? (@jflory7:fedora.im, 14:02:53) * INFO: Justin, `jflory7`, US Eastern, morning bird usually but night owl occasionally (@jflory7:fedora.im, 14:03:16) * INFO: Michael, `mwinters`, US Central, Whenever my toddlers let me! (@mwinters:fedora.im, 14:04:35) * INFO: Nancy, nancywrites, WAT, It really all depends on my mood. I can be both a morning bird or a night owl. (@nancywrites:matrix.org, 14:05:13) * INFO: Jona, jonatoni, CEST, night owl 😄 (@jonatoni:fedora.im, 14:05:36) * TOPIC: Team announcements & news (@jflory7:fedora.im, 14:08:03) * LINK: https://pagure.io/Fedora-Council/tickets/issue/542#comment-989257 (@jflory7:fedora.im, 14:12:30) * LINK: https://discussion.fedoraproject.org/t/council-policy-proposal-policy-on-ai-assisted-contributions/165092/233 (@jflory7:fedora.im, 14:12:30) * INFO: Discussion is ongoing on adopting an AI-assisted contributions policy for Fedora. A final draft is proposed and is under review by the Council. A vote is anticipated within the next week. A callout was shared on the devel-announce mailing list about the policy draft. (@jflory7:fedora.im, 14:12:30) * INFO: nancywrites is working on a draft on how to create a new Fedora SIG. This is a candidate for a new CommOps docs page. Review is welcome. The next step is to get it into a Merge Request on the CommOps docs. (@jflory7:fedora.im, 14:13:20) * LINK: https://docs.google.com/document/d/1EfdB5YRSjQ411WgI9HRHhft6VQpSWcrQ5d0upfQBB3g/edit?usp=sharing (@jflory7:fedora.im, 14:13:20) * INFO: There are a few docs-related Merge Requests ready for review. Team members are encouraged to add their review to the MRs as your time allows. (@jflory7:fedora.im, 14:14:10) * LINK: https://gitlab.com/fedora/commops/home/-/merge_requests (@jflory7:fedora.im, 14:14:10) * LINK: https://fedoraproject.org/wiki/Initiatives/Fedora_Docs_2025 (@jflory7:fedora.im, 14:15:30) * INFO: A new Fedora Community Initiative was recently proposed about the Fedora Docs team. A full proposal is available on the Wiki and a Fedora Discussion topic is open to invite feedback from the community, ahead of an official vote on the Council. Have thoughts on Fedora Docs? Check out the proposal and leave your feedback. (@jflory7:fedora.im, 14:15:30) * LINK: https://discussion.fedoraproject.org/t/fedora-council-tickets-ticket-543-new-initiative-fedora-docs-2025/167686 (@jflory7:fedora.im, 14:15:30) * TOPIC: Ticket discussions (@jflory7:fedora.im, 14:19:21) * INFO: I'm a relatively new community member who is working towards community health metrics. Fedora has a lot of data to analyze, and projects like CHAOSS (which I'm just getting up to speed on) will not be able to read all of it because some of it is very unique to us and our history. As such, I decided two things: 1) We need a data lakehouse where we can house all of our unique data and blend it into insights, and ideally integrate this into the CHAOSS tools. Status: I've got a POC which I will make public soon, hopefully later this week. 2) The first dataset that should probably go in there is datanommer/datagrepper. I've been working hard on tooling that will allow us to reliably and easily refine all of that historical semi-structured data into structured data, so that we can make it publicly available in the lakehouse. This is a large effort that could use extra hands, and most of my tooling is around making that work easier to contribute to. Please reach out if interested! (@mwinters:fedora.im, 14:19:29) * INFO: Topic 2: Fedora Data Working Group (@jflory7:fedora.im, 14:24:23) * INFO: Topic 1: Release Party check-in (@jflory7:fedora.im, 14:24:23) * INFO: Topic 3: Community Blog to Fedora Discussion (@jflory7:fedora.im, 14:26:46) * TOPIC: Release Party check-in (@jflory7:fedora.im, 14:26:53) * LINK: https://gitlab.com/groups/fedora/design/team/-/epics/11 (@jflory7:fedora.im, 14:29:46) * INFO: Design update: The Fedora Design Team is working on thumbnail artwork and social media graphics to help promote the virtual event. We are also experimenting with some design customization of Pretix to add release wallpaper theming to the registration. (@jflory7:fedora.im, 14:29:46) * LINK: https://gitlab.com/fedora/commops/home/-/issues/75 (@jflory7:fedora.im, 14:31:30) * ACTION: @shaunm Follow up with @amoloney and @jspaleta on planning Fedora 43 Release Party speakers and content; check in on the Wiki page for the schedule (@jflory7:fedora.im, 14:33:40) * ACTION: @neil Follow up with @rwright on confirming the deadline for speakers to share pre-recorded videos for processing and upload to Fedora YouTube account (@jflory7:fedora.im, 14:34:38) * TOPIC: Topic 2: Fedora Data Working Group (@jflory7:fedora.im, 14:35:43) * INFO: Quick summary: There is a long conversation about making a more clear, visible home for "data science" / "metrics" / "fedora-messaging bus" type of work. Over the last week or two, we have discussed branching out a new Working Group underneath CommOps as a "Data Working Group", to provide a more clear home for this sort of work and invite others to collaborate, without having to follow all of the CommOps topics. (@jflory7:fedora.im, 14:36:39) * ACTION: @mwinters File a new CommOps issue on GitLab to formally pitch the idea of a Data WG under CommOps, to help give a better home for data-related conversations across the three groups (data engineering / analysis conversations, data sources, "wider data community" folks) (@jflory7:fedora.im, 14:44:01) * ACTION: @jflory7 Create a new Matrix room for Fedora Data WG, invite some CommOps folks and share in #commops:fedoraproject.org when ready (@jflory7:fedora.im, 14:44:25) * TOPIC: Topic 3: Community Blog to Fedora Discussion (@jflory7:fedora.im, 14:47:43) * INFO: Summary: We were discussing retiring the Community Blog in favor of a Discourse-native workflow. We had an extensive conversation about it many, many months ago, but things trailed off and we didn't follow up. We should revisit on a possible timeline for this, and how new editors could come on board to help us with this. (@jflory7:fedora.im, 14:48:38) * LINK: https://communityblog.fedoraproject.org/proposal-to-move-community-blog-to-fedora-discussion/ (@jflory7:fedora.im, 14:51:15) * LINK: https://discussion.fedoraproject.org/t/proposal-to-move-community-blog-to-fedora-discussion/146656 (@jflory7:fedora.im, 14:51:35) * ACTION: @mwinters Reply on Fedora Discussion topic, RE: move CommBlog to Fedora Discussion, about tactics and tools we could use to publish across different platforms, with Discourse as the origin point for new content (@jflory7:fedora.im, 14:59:25) * ACTION: @nancywrites Reply on Fedora Discussion topic, RE: move CommBlog to Fedora Discussion, raising your hand as an interested person for editing (@jflory7:fedora.im, 14:59:43) * ACTION: @jflory7 Reply on Fedora Discussion topic, RE: move CommBlog to Fedora Discussion, about proposing a possible timeline for when/how this work should happen (@jflory7:fedora.im, 15:00:01) * TOPIC: Open floor (@jflory7:fedora.im, 15:00:09) Meeting ended at 2025-10-14 15:01:36 Action items ------------ * @shaunm Follow up with @amoloney and @jspaleta on planning Fedora 43 Release Party speakers and content; check in on the Wiki page for the schedule * @neil Follow up with @rwright on confirming the deadline for speakers to share pre-recorded videos for processing and upload to Fedora YouTube account * @mwinters File a new CommOps issue on GitLab to formally pitch the idea of a Data WG under CommOps, to help give a better home for data-related conversations across the three groups (data engineering / analysis conversations, data sources, "wider data community" folks) * @jflory7 Create a new Matrix room for Fedora Data WG, invite some CommOps folks and share in #commops:fedoraproject.org when ready * @mwinters Reply on Fedora Discussion topic, RE: move CommBlog to Fedora Discussion, about tactics and tools we could use to publish across different platforms, with Discourse as the origin point for new content * @nancywrites Reply on Fedora Discussion topic, RE: move CommBlog to Fedora Discussion, raising your hand as an interested person for editing * @jflory7 Reply on Fedora Discussion topic, RE: move CommBlog to Fedora Discussion, about proposing a possible timeline for when/how this work should happen People Present (lines said) --------------------------- * @jflory7:fedora.im (162) * @mwinters:fedora.im (28) * @shaunm:matrix.org (9) * @nancywrites:matrix.org (8) * @moralcode:fedora.im (6) * @nhanlon:beeper.com (5) * @zodbot:fedora.im (4) * @meetbot:fedora.im (3) * @nirik:matrix.scrye.com (3) * @jonatoni:fedora.im (1) * @kashyapc:fedora.im (1)