<@jflory7:fedora.im>
14:03:50
!startmeeting Community Ops Team Meeting - 2026-09-15
<@meetbot:fedora.im>
14:03:51
Meeting started at 2026-09-15 14:03:50 UTC
<@meetbot:fedora.im>
14:03:52
The Meeting name is 'Community Ops Team Meeting - 2026-09-15'
<@jflory7:fedora.im>
14:03:53
!meetingname commops
<@meetbot:fedora.im>
14:03:54
The Meeting Name is now commops
<@jflory7:fedora.im>
14:03:56
!topic Roll Call
<@jflory7:fedora.im>
14:04:21
!info Welcome! Type `!hi` for zodbot to introduce yourself. If it is your first time attending, please share a sentence or two of introduction.
<@jflory7:fedora.im>
14:04:22
!hi
<@zodbot:fedora.im>
14:04:23
Justin Wheeler: Justin Wheeler (jflory7) - he / him / his
<@jflory7:fedora.im>
14:04:33
I know shaunm is here 🙂
<@jflory7:fedora.im>
14:05:35
Neil Hanlon, Cornelius Emase, Michal Konečný, Michael Winters?
<@jflory7:fedora.im>
14:06:35
If we are missing quorum, we could just chat about the upcoming Release Party in #commops:fedoraproject.org. Or here, since this gets summarized.
<@shaunm:matrix.org>
14:06:40
!hi
<@zodbot:fedora.im>
14:06:43
shaunm: Shaun McCance (shaunm) - he / him / his
<@mwinters:fedora.im>
14:06:57
!hi
<@zodbot:fedora.im>
14:06:59
Michael Winters: Michael Winters (mwinters) - he / him / his
<@jflory7:fedora.im>
14:07:09
Hi folks!
<@jflory7:fedora.im>
14:07:57
I guess it might be a more quiet meeting today. That's alright. We can tailor the agenda to the topics we want to discuss.
<@jflory7:fedora.im>
14:08:06
!info Present: @jflory7, @shaunm, @mwinters
<@jflory7:fedora.im>
14:08:09
!topic Agenda triage
<@jflory7:fedora.im>
14:08:15
I can think of two tickets worth discussing
<@jflory7:fedora.im>
14:08:22
!link https://forge.fedoraproject.org/commops/tickets/issues/143
<@jflory7:fedora.im>
14:08:28
!link https://forge.fedoraproject.org/commops/tickets/issues/145
<@jflory7:fedora.im>
14:08:34
These two are top of mind for me
<@jflory7:fedora.im>
14:08:40
Anyone else want to nominate a ticket for discussion?
<@jflory7:fedora.im>
14:08:47
Or, even a non-ticket item 😛
<@jflory7:fedora.im>
14:10:00
Michael Winters: Any Data WG topics you want to bubble up?
<@shaunm:matrix.org>
14:10:01
Those are my top 2 as well
<@mwinters:fedora.im>
14:10:53
I have a minor update related to https://forge.fedoraproject.org/commops/tickets/issues/146
<@jflory7:fedora.im>
14:11:46
Ooh, interesting.
<@mwinters:fedora.im>
14:11:46
Through mattdm 's brontosaurus, I have a pretty good historical record at least for dates of things like releases. I'm planning to continue to flesh this out as essentially a timeline of all major Fedora events.
<@jflory7:fedora.im>
14:12:00
Then, let's hit these three tickets for today.
<@jflory7:fedora.im>
14:12:06
!link https://forge.fedoraproject.org/commops/tickets/issues/146
<@jflory7:fedora.im>
14:12:15
!info Three tickets triaged for today's meeting discussion.
<@mwinters:fedora.im>
14:12:19
It's really the only dataset that might have a lot of human-generated content. Haven't figured out how to handle that yet.
<@jflory7:fedora.im>
14:12:49
I think the best flow for discussion in #143, #146, then #145
<@jflory7:fedora.im>
14:13:10
!topic Ticket #143: Virtual F45 Release Party: Wrangler Planning Ticket
<@jflory7:fedora.im>
14:13:13
!link https://forge.fedoraproject.org/commops/tickets/issues/143
<@mwinters:fedora.im>
14:13:20
But having a list of dates allows us to annotate the graphs that we produce. e.g. we can see the number of downloads spike after a release (as opposed to "after some random date, who knows why")
<@jflory7:fedora.im>
14:13:25
Okay, first things first. Release Party. F45. October 30th.
<@jflory7:fedora.im>
14:13:34
That is 1.5 months away.
<@shaunm:matrix.org>
14:13:43
Feels like that date should be a costume party...
<@jflory7:fedora.im>
14:13:47
Michael Winters: Let's hit this in the next ticket discussion, definitely want to chat more about it!
<@jflory7:fedora.im>
14:13:53
shaunm: lolol. Who is to say it couldn't be?
<@jflory7:fedora.im>
14:14:00
I think we need to make a call to rally the forces, though
<@mwinters:fedora.im>
14:14:09
The gentleman yields the floor!
<@jflory7:fedora.im>
14:14:13
The ticket has been sitting for months but we haven't solicited or invited participation yet
<@jflory7:fedora.im>
14:14:22
The five roles are written out there in the ticket.
<@shaunm:matrix.org>
14:14:30
We have five roles identified in the ticket. Can we voluntell anybody on them?
<@jflory7:fedora.im>
14:14:34
I think it might help to figure out who this party's wrangler will be first
<@shaunm:matrix.org>
14:14:46
Or suggest people, and we can follow up with them after
<@jflory7:fedora.im>
14:15:02
Aoife Moloney often helps with speakers, Emma Kidney and Madeline Peck often help with design, and Neil Hanlon often helps with production & video
<@shaunm:matrix.org>
14:15:32
I like all those names on those roles
<@jflory7:fedora.im>
14:15:35
Robert Wright (he/him) was our wrangler last time I think.
<@jflory7:fedora.im>
14:15:41
But I don't think he is around now
<@shaunm:matrix.org>
14:16:21
I can take it, but I also enjoy you doing it if you have the bandwidth
<@jflory7:fedora.im>
14:16:23
Michael Winters: We could recruit you for a Data WG slot at the party, perhaps 😉
<@jflory7:fedora.im>
14:16:51
I could do either the Wrangler or Promotion & Content roles
<@jflory7:fedora.im>
14:17:05
One but not both like I did sort of last time 😅
<@shaunm:matrix.org>
14:17:27
yeah, fair
<@mwinters:fedora.im>
14:17:49
Oh man ... I thought I'd be ready 6 months ago. So I don't know whether I'll be ready by then. I can be tentative 🤞
<@jflory7:fedora.im>
14:18:03
I guess I could do the Wrangler role, and use these meetings as the primary vehicle for checking in and organizing the work
<@jflory7:fedora.im>
14:18:11
Michael Winters: Sure. Now is the time to start thinking about it!
<@jflory7:fedora.im>
14:18:19
There is a month and a half left to go 🙂
<@jflory7:fedora.im>
14:18:36
shaunm: Would you be up for being the Promo & Content lead?
<@shaunm:matrix.org>
14:18:40
then I'll take promotion
<@jflory7:fedora.im>
14:18:48
Super.
<@jflory7:fedora.im>
14:19:07
!agreed @jflory7 will take the role of F45 Party Wrangler, and @shaunm will take the role of Promotion & Content lead.
<@amoloney:fedora.im>
14:19:39
Im ok for speaker stuff agaon
<@jflory7:fedora.im>
14:19:42
!info The following people will be asked for the following roles: @amoloney for Speaker Management, @ekidney/@madelinepeck for Design, Production & Video for @neil.
<@amoloney:fedora.im>
14:19:44
*again
<@jflory7:fedora.im>
14:20:06
!agreed Slight revision to previous, @amoloney confirmed for F45 Party Speaker Management lead. 🙌
<@jflory7:fedora.im>
14:20:14
OK, cool. That is 3 of 5 roles filled.
<@jflory7:fedora.im>
14:20:41
I can help solicit the last two slots from our usual suspects.
<@jflory7:fedora.im>
14:20:56
shaunm: Would you be up for writing a super-short save-the-date for the Magazine?
<@jflory7:fedora.im>
14:21:09
Aoife Moloney: Is there anything we could do to help you kickstart speaker management, or do you have your own workflow for that?
<@jflory7:fedora.im>
14:21:39
!action @jflory7 Reach out to potential Design and Production & Video leads to confirm participation.
<@shaunm:matrix.org>
14:21:45
I can do that
<@jflory7:fedora.im>
14:22:11
!action @shaunm Draft a short Fedora Magazine save-the-date article to announce the October 30th F45 Release Party
<@jflory7:fedora.im>
14:22:28
!action @mwinters Consider submitting a Data WG 10-minute talk for the F45 Release Party 😉
<@jflory7:fedora.im>
14:22:53
!action Aoife Moloney Begin pulling together a list of contacts for F45 Release Party speaker sessions
<@mwinters:fedora.im>
14:22:57
How does one talk for 10 minutes? Your options: 10 seconds or 10 hours.
<@mwinters:fedora.im>
14:23:02
(jk)
<@jflory7:fedora.im>
14:23:07
As a reminder, the total amount of allocated time for the entire party is 3 hours.
<@jflory7:fedora.im>
14:23:12
😄
<@jflory7:fedora.im>
14:23:36
Since I am less spread thin, maybe I can look at the idea of running a social activity or a game during the party
<@jflory7:fedora.im>
14:23:43
I'll see how far I get from now until October
<@jflory7:fedora.im>
14:23:52
OK folks… anything else for the F45 Release Party?
<@jflory7:fedora.im>
14:24:03
This one was honestly more about rallying the call for action 🙂
<@jflory7:fedora.im>
14:24:25
shaunm: Maybe you could also point anyone interested in helping out with organizing to https://forge.fedoraproject.org/commops/tickets/issues/143, in case we can get some fresh faces that way too
<@jflory7:fedora.im>
14:24:53
Oh huh, helps to read my own comments. Carol Chen volunteered in June for Content & Promotion.
<@jflory7:fedora.im>
14:25:09
shaunm: Maybe you can also follow up with Carol to see if she still has capacity and if she can help out with any of that work.
<@jflory7:fedora.im>
14:25:31
!action @shaunm Reach out to @cybette to reconfirm her interest/capacity for helping out with Content & Promotion
<@shaunm:matrix.org>
14:25:38
:) I'll talk to Carol. We can probably share duties.
<@jflory7:fedora.im>
14:25:49
Sharing is caring!
<@jflory7:fedora.im>
14:26:11
root_dir had also volunteered for design work, but I am not sure if they are still around. I'll do some sleuthing.
<@jflory7:fedora.im>
14:26:20
Well, I think that is about everything F45 Party…
<@jflory7:fedora.im>
14:26:34
Last call, before switching over to Michael Winters for #146?
<@jflory7:fedora.im>
14:27:08
### Going once…
<@jflory7:fedora.im>
14:27:20
### Going twice…
<@jflory7:fedora.im>
14:27:30
### Going thrice…
<@jflory7:fedora.im>
14:27:47
!topic Ticket #146: Create an official account of Fedora's history for Fedora Docs
<@jflory7:fedora.im>
14:27:49
!link https://forge.fedoraproject.org/commops/tickets/issues/146
<@jflory7:fedora.im>
14:28:20
So, I opened this ticket a while back, from an old ticket I had opened in the Interns repo a long time ago, and from another repo before that one. So, this ticket has hopped through a few places until now.
<@jflory7:fedora.im>
14:28:25
Michael Winters: I'll pass the mic over to you!
<@mwinters:fedora.im>
14:30:19
I don't have anything to demo but briefly, I'll say that I needed a version of https://en.wikipedia.org/wiki/Fedora_Linux_release_history in a data file, so now I have one (in duckdb)
<@mwinters:fedora.im>
14:30:19
1. I could make it available for download if anyone wants it.
<@mwinters:fedora.im>
14:30:19
2. I could in theory make this something more wiki-style, where others can add dates to it.
<@mwinters:fedora.im>
14:30:19
3. I need to find a live data source to pull more of these things from. I want to gather essentially any relevant date, not just release dates (e.g. release parties! Flocks! etc.)
<@jflory7:fedora.im>
14:30:43
Oh, nice.
<@mwinters:fedora.im>
14:30:45
I imagine that would be useful for anyone tackling #146
<@jflory7:fedora.im>
14:31:02
What did you say you were using for milestones? Just the release date history, or something else too?
<@jflory7:fedora.im>
14:31:27
I'm not sure what live data source exists for events. That's a tricky one
<@mwinters:fedora.im>
14:31:58
This is maybe an announcement-ish? But my source was this: https://codeberg.org/mattdm/brontosaurusifier which I've now made available publicly here: https://superset.hatlas.mwinters.net/superset/dashboard/bronto-index/
<@mwinters:fedora.im>
14:32:16
See for example: https://superset.hatlas.mwinters.net/superset/dashboard/bronto-fedora-updates-systems/
<@jflory7:fedora.im>
14:34:22
Oh yeah, these 😄
<@jflory7:fedora.im>
14:34:42
They are super cool and might provide some structure for someone to do the storytelling of that history in a docs page
<@jflory7:fedora.im>
14:35:07
[@mwinters:fedora.im](https://matrix.to/#/@mwinters:fedora.im) Could I action you to add a ticket comment summarizing your datasets and the "geological ages" of Fedora in the ticket?
<@jflory7:fedora.im>
14:35:22
Doesn't need to be huge, but just some breadcrumbs to help people find their way through what you have in Hatlas.
<@mwinters:fedora.im>
14:35:44
This is the "countme" data, which has been thoroughly sanitized by Matt's project because the source data is quite insane.
<@mwinters:fedora.im>
14:36:13
Yep! That's all I have for this ticket.
<@jflory7:fedora.im>
14:36:21
Okay, cool.
<@jflory7:fedora.im>
14:37:27
!info Building on @mattdm's data projects, @mwinters took it to the next level and made a lot of that work more accessible in an explorable dashboard. This would be useful for any writer in the future to reference. In particular, a useful part of these datasets is the "geological ages" of Fedora, represented by IP address hits to Fedora RPM update repositories.
<@jflory7:fedora.im>
14:37:50
!action @mwinters Add a comment to Ticket #146 pointing to the Hatlas data for a future author to dig into and explore
<@jflory7:fedora.im>
14:37:55
I think that covers it.
<@jflory7:fedora.im>
14:37:59
Did I get anything wrong?
<@mwinters:fedora.im>
14:38:18
Close enough 😉
<@jflory7:fedora.im>
14:38:29
Hahah, alright.
<@jflory7:fedora.im>
14:38:47
!topic Ticket #145: New CommOps representative needed on the Mindshare committee
<@jflory7:fedora.im>
14:38:52
!link https://forge.fedoraproject.org/commops/tickets/issues/145
<@jflory7:fedora.im>
14:38:58
OK, this one ties into some governance woes.
<@jflory7:fedora.im>
14:39:14
Ever since Gwmngilfen vacated the seat, we have not been able to identify a successor to the Mindshare Committee.
<@jflory7:fedora.im>
14:39:46
This leaves our team's representation out of the picture. The biggest thing I think we have to offer to Mindshare Committee is the Community Social Analysis part of our team charter.
<@jflory7:fedora.im>
14:39:57
Having useful data available for events and deciding spending impact is key
<@jflory7:fedora.im>
14:40:26
shaunm is already chairing the Mindshare Committee, and I have personally decided to stay out of Fedora governance for at least a while as part of my role transition
<@jflory7:fedora.im>
14:40:34
So, that brings us to where we are now…
<@jflory7:fedora.im>
14:40:40
I am wondering what makes the most sense to do here
<@jflory7:fedora.im>
14:40:57
We could make a wider call on Fedora Discussion, but I'd prefer if someone who has been in Fedora for a bit had a role like this
<@jflory7:fedora.im>
14:41:22
Another option is to deprecate the seat entirely, since three months is a long time and might speak to the level of engagement we have currently
<@jflory7:fedora.im>
14:41:24
I'm open to ideas
<@jflory7:fedora.im>
14:41:26
Thoughts?
<@shaunm:matrix.org>
14:42:28
I would suggest Akashdeep Dhar / আকাশদীপ ধর if he weren't already elected there.
<@jflory7:fedora.im>
14:42:58
Hahah, true.
<@jflory7:fedora.im>
14:44:14
Hmmm
<@jflory7:fedora.im>
14:44:19
Well, we do have the Matrix WG folks
<@jflory7:fedora.im>
14:44:36
Like [@farchord:fedora.im](https://matrix.to/#/@farchord:fedora.im) and [@sfaulken:fedora.im](https://matrix.to/#/@sfaulken:fedora.im). Not sure if this is something they'd want to consider.
<@shaunm:matrix.org>
14:45:13
Keep tagging people until somebody's ears perk up?
<@jflory7:fedora.im>
14:45:32
Heheh
<@mwinters:fedora.im>
14:45:33
You have my attention. I've been heads-down focused on building analysis capabilities, but I haven't been in any discussions about how we gather data / what data we gather. The closest has been my requests on the Council board for our historical data from community polls and surveys.
<@sfaulken:fedora.im>
14:46:00
wat?
<@shaunm:matrix.org>
14:46:00
I think it's good to have somebody, but I want to point out that there is a real time commitment.
<@sfaulken:fedora.im>
14:46:13
sorry, just got on the computer for about the first time in a week.
<@jflory7:fedora.im>
14:46:31
Are you very familiar with the Mindshare Committee charter? In terms of getting your data into a useful place, this is a great place to advocate. The representative role is not inherently technical, but being able to speak to trends in data is interesting and useful.
<@jflory7:fedora.im>
14:46:50
Ah, no worries. We are discussing what to do about this CommOps ticket. https://forge.fedoraproject.org/commops/tickets/issues/145
<@mwinters:fedora.im>
14:47:15
Yeah, I only hesitate because I'm not certain I can make that commitment now. I'd rather leave the chair open for a stronger representative if there is one, but I'm happy to float in where I can.
<@jflory7:fedora.im>
14:47:48
Would you be interested in interim rep until F45 in October, by at which point, we hope to have identified a long-term replacement?
<@jflory7:fedora.im>
14:48:04
That might be a way to get a bite-sized experience without a major, huge commitment
<@mwinters:fedora.im>
14:48:46
Sure. I know that I have the time now, I'm just also expecting that to change if/when I find employment.
<@jflory7:fedora.im>
14:48:49
Work is divided across major time zone split, so a lot of the work is a sync and a small portion is done in meetings
<@jflory7:fedora.im>
14:49:15
If there was a major life commitment change, you can always step back. Ask me how I know 😛
<@jflory7:fedora.im>
14:49:33
https://jwheel.org/blog/2017/10/resigning-fedora-council/
<@jflory7:fedora.im>
14:50:59
Anyways, something to think about.
<@jflory7:fedora.im>
14:51:08
I do think we should time-box this to F45 release though
<@mwinters:fedora.im>
14:51:10
I'll need someone to help me onboard to that role.
<@jflory7:fedora.im>
14:51:30
If we cannot find someone to fill the seat post-F45, we should maybe consider if there is a more impactful part of the project which could steward this seat
<@mwinters:fedora.im>
14:51:34
I'm familiar with MindShare from a distance but not the machinery thereof.
<@jflory7:fedora.im>
14:51:53
I think you will have good success in this part.
<@sfaulken:fedora.im>
14:52:06
I'm not opposed to doing the thing, I'm just in the midst of a few things that have my attention for the next couple months.
<@jflory7:fedora.im>
14:52:21
Sure. Since this coming up for the first time for a lot of folks, let's not rush it.
<@jflory7:fedora.im>
14:52:44
Let's delay a follow-up to our next meeting in two weeks, with a deadline to revisit and attempt to find a F44 interim rep to Mindshare Committee.
<@jflory7:fedora.im>
14:53:34
!info More time is needed to find a new CommOps representative to the Fedora Mindshare Committee. CommOps is allocated one appointed seat to the Mindshare Committee, ideally in 12-month/two-release terms to match the elected Mindshare Committee roles.
<@jflory7:fedora.im>
14:54:42
!agreed Revisit in next meeting to discuss possible nominees from CommOps for the role, with the intent to decide in the short-term for a F44 interim rep, and then a F45 to F46 appointed rep for at least one full release cycle.
<@jflory7:fedora.im>
14:54:57
!topic Open Floor
<@jflory7:fedora.im>
14:55:08
Alright, we made it to the last five minutes of today's meeting.
<@jflory7:fedora.im>
14:55:26
Anyone have anything else they want to bring up?
<@jflory7:fedora.im>
14:55:42
!action @jflory7 Post a meeting summary topic on Fedora Discussion
<@sfaulken:fedora.im>
14:56:02
Nah, I got nothing.
<@jflory7:fedora.im>
14:56:03
!action @jflory7 Post ticket-specific meeting outcomes as new comments in each ticket
<@jflory7:fedora.im>
14:56:54
I think folks might have also switched focus too. Let's call it here and take a few minutes back.
<@jflory7:fedora.im>
14:57:03
Thanks everyone for being here and showing up!
<@jflory7:fedora.im>
14:57:07
See you next time 👋
<@jflory7:fedora.im>
14:57:09
!endmeeting