<@jflory7:fedora.im>
15:02:32
!startmeeting Fedora CommOps team meeting - 2025-01-07
<@meetbot:fedora.im>
15:02:35
Meeting started at 2025-01-07 15:02:32 UTC
<@jflory7:fedora.im>
15:02:35
!meetingname commops
<@meetbot:fedora.im>
15:02:35
The Meeting name is 'Fedora CommOps team meeting - 2025-01-07'
<@meetbot:fedora.im>
15:02:36
The Meeting Name is now commops
<@rwright:fedora.im>
15:02:40
!hi
<@zodbot:fedora.im>
15:02:42
Robert Wright (rwright) - he / him / his
<@thisisyaash:fedora.im>
15:02:44
!hi
<@zodbot:fedora.im>
15:02:45
Yashwanth Rathakrishnan (thisisyaash)
<@shaunm:matrix.org>
15:02:46
!hi
<@zodbot:fedora.im>
15:02:47
Shaun McCance (shaunm) - he / him / his
<@bt0dotninja:fedora.im>
15:03:11
!hi
<@zodbot:fedora.im>
15:03:12
Alberto Rodriguez Sanchez (bt0dotninja) - he / him / his
<@jflory7:fedora.im>
15:03:12
!topic Meeting agenda
<@jflory7:fedora.im>
15:03:46
!info Intros, welcomes, hellos (~5m)
<@jflory7:fedora.im>
15:03:50
!info Team announcements & news (~5-10m)
<@jflory7:fedora.im>
15:03:53
!info Follow-ups from last meeting (if any) (~5-10m)
<@jflory7:fedora.im>
15:03:56
!info Ticket discussions (remaining time)
<@jflory7:fedora.im>
15:03:59
!info Open floor (remaining 5-10 minutes)
<@jflory7:fedora.im>
15:04:07
!topic Intros, welcomes, hellos (~5m)
<@jflory7:fedora.im>
15:04:08
!hi
<@zodbot:fedora.im>
15:04:09
Justin W. Flory (jflory7) - he / him / his
<@nhanlon:beeper.com>
15:04:15
!hi
<@jflory7:fedora.im>
15:04:16
Oh, this is a nice quorum today :)
<@zodbot:fedora.im>
15:04:16
Neil Hanlon (neil) - he / him / his
<@jflory7:fedora.im>
15:04:17
Hi folks :)
<@jflory7:fedora.im>
15:04:19
Happy new year.
<@nhanlon:beeper.com>
15:04:36
G'day all
<@bt0dotninja:fedora.im>
15:04:54
Hi 👋
<@thisisyaash:fedora.im>
15:05:16
hello everyone!
<@jflory7:fedora.im>
15:05:17
I trust folks had a nice chance to disconnect and unwind over the year-end holidays :)
<@jflory7:fedora.im>
15:05:46
I am still waking up from what feels like hibernation :D But I am excited about the year ahead for Fedora and continuing to work with you folks on Freedom, Friends, Features, First.
<@jflory7:fedora.im>
15:06:27
Phewwwwww
<@jflory7:fedora.im>
15:06:33
I was just thinking to go for my second coffee :)
<@jflory7:fedora.im>
15:07:23
OK, so since we have a good quorum, let's hop to it. In #commops:fedoraproject.org, I would be curious to know how y'all all spent your holidays :)
<@jflory7:fedora.im>
15:07:31
!info Present: @jflory7 @rwright @thisisyaash @shaunm @bt0dotninja @neil
<@jflory7:fedora.im>
15:07:47
!topic Team announcements & news
<@jflory7:fedora.im>
15:07:51
What's good, y'all?
<@jflory7:fedora.im>
15:07:58
It is a new year. Any exciting news or announcements?
<@jflory7:fedora.im>
15:08:05
From Fedora-land or the wider FOSS/Linux spaces?
<@rwright:fedora.im>
15:08:06
I installed KDE as my DE for 2025. That's what is new with me.
<@jflory7:fedora.im>
15:08:28
Robert Wright (he/him): Oohhh. Funnily enough, I have been thinking about the same. I will be curious for your experience there
<@rwright:fedora.im>
15:08:37
Distro Hopping is so 2024, Desktop Environment Hopping is 2025.
<@jflory7:fedora.im>
15:09:09
There was an interesting article from Sumantro Mukherjee on the Magazine recently
<@jflory7:fedora.im>
15:09:12
!info === "Running Generative AI Models Locally with Ollama and Open WebUI" ===
<@jflory7:fedora.im>
15:09:17
!link https://fedoramagazine.org/running-generative-ai-models-locally-with-ollama-and-open-webui/
<@jflory7:fedora.im>
15:09:37
A cool tutorial made for Fedora :)
<@jflory7:fedora.im>
15:10:18
Oh, there is one that is not exactly new, but it was 24 December, so I am calling it fresh :)
<@jflory7:fedora.im>
15:10:22
!info === "Fedora Chooses Forgejo!" ====
<@jflory7:fedora.im>
15:10:27
!link https://communityblog.fedoraproject.org/fedora-chooses-forgejo/
<@jflory7:fedora.im>
15:10:33
_four years later_ :D
<@jflory7:fedora.im>
15:10:46
But this is a very big deal actually, and the work begins in 2025
<@rwright:fedora.im>
15:10:48
That's actually pretty cool - this would be something pretty interesting for new folks hopping into Linux for the first time that they could do something AI fast with Fedora.
<@jflory7:fedora.im>
15:10:55
So there will be more doing and less talking with git forges :P
<@rwright:fedora.im>
15:10:59
All the best things are worth waiting for.
<@jflory7:fedora.im>
15:11:18
Robert Wright (he/him): Exactly. I think this was Sumantro's goal for the Magazine article.
<@jflory7:fedora.im>
15:11:35
I, for one, welcome our new Forgejo overlord.
<@jflory7:fedora.im>
15:12:15
!info FOSDEM 2025 is around the corner, from 1-2 February 2025
<@jflory7:fedora.im>
15:12:26
!link https://fosdem.org/2025/
<@thisisyaash:fedora.im>
15:12:31
and it was really good running a local LLMs
<@thisisyaash:fedora.im>
15:12:31
<@thisisyaash:fedora.im>
15:12:31
also it's super fast, IMO
<@thisisyaash:fedora.im>
15:12:31
i have been using Ollama for 2 months
<@jflory7:fedora.im>
15:12:38
As I understand, the Fedora booth will be neighbors with AlmaLinux and Rocky Linux on different days :)
<@jflory7:fedora.im>
15:13:01
I want to check out RamaLama sometime soon 👀
<@nhanlon:beeper.com>
15:13:03
prank war?
<@nhanlon:beeper.com>
15:13:05
prank war.
<@nhanlon:beeper.com>
15:13:07
;)
<@rwright:fedora.im>
15:13:11
I have been meaning to do a offline LLM setup - I'll give this a try.
<@jflory7:fedora.im>
15:13:39
OK, so, any last news, announcements, updates?
<@jflory7:fedora.im>
15:14:00
Before we move to the tentative agenda proposed earlier by Robert
<@jflory7:fedora.im>
15:14:16
## News & announcements, going once…
<@rwright:fedora.im>
15:14:22
So bold of you.
<@thisisyaash:fedora.im>
15:14:31
"RamaLama" 👀
<@thisisyaash:fedora.im>
15:14:31
interesting...
<@thisisyaash:fedora.im>
15:14:31
<@thisisyaash:fedora.im>
15:14:31
ill give it a try
<@nhanlon:beeper.com>
15:14:33
by the way regarding forgejo, not sure if it'll be of interest, but we (I mean nalika) has been working on a Forgejo-to-mqtt bridge, which we're looking to package into Fedora (and hopefully have others use) https://git.resf.org/infrastructure/buzon
<@jflory7:fedora.im>
15:14:36
## News & announcements, going twice…
<@nhanlon:beeper.com>
15:14:42
not really commops related, but, you know
<@jflory7:fedora.im>
15:14:54
!info regarding forgejo, not sure if it'll be of interest, but we (I mean nalika) has been working on a Forgejo-to-mqtt bridge, which we're looking to package into Fedora (and hopefully have others use)
<@jflory7:fedora.im>
15:14:55
!link https://git.resf.org/infrastructure/buzon
<@rwright:fedora.im>
15:14:58
Very interesting to me - love some message bus.
<@jflory7:fedora.im>
15:15:04
## News and announcements, going thrice…
<@jflory7:fedora.im>
15:15:26
💥💥
<@jflory7:fedora.im>
15:15:56
!topic Ad-hoc agenda for today
<@jflory7:fedora.im>
15:16:11
!info Review of "what we want to do in 2025 as CommOps"
<@jflory7:fedora.im>
15:16:13
!info Review of Jupyter Style Data Analysis on ComminiShift
<@jflory7:fedora.im>
15:16:14
!info F42 Planning!
<@jflory7:fedora.im>
15:16:19
Any additions or objections?
<@jflory7:fedora.im>
15:16:39
Silence assumes consent for the topics :)
<@jflory7:fedora.im>
15:17:05
Or plus marks :)
<@jflory7:fedora.im>
15:17:31
So, let's start with the big one
<@jflory7:fedora.im>
15:17:32
!topic Review of "what we want to do in 2025 as CommOps"
<@jflory7:fedora.im>
15:17:39
So.
<@jflory7:fedora.im>
15:17:42
It is a new year.
<@jflory7:fedora.im>
15:17:48
And a new release cycle, almost.
<@jflory7:fedora.im>
15:18:21
This is a good chance for us to reflect on 2024, what we accomplished, and where we want to focus in 2025.
<@jflory7:fedora.im>
15:19:07
Some things worked well, and others were challenging.
<@jflory7:fedora.im>
15:19:25
I think our main success was restarting this team as an active presence. I think our greatest challenge was reorganizing and narrowing down our scope as a team.
<@jflory7:fedora.im>
15:19:39
The Initiative helped with that some, but I think we could do better, and really have some focused, targeted goals.
<@jflory7:fedora.im>
15:19:59
I could ramble and act like a LLM to offer ideas, but actually, I am curious to hear from you all
<@jflory7:fedora.im>
15:20:15
What you liked working on in 2024, what you didn't like working on, what you want to work with more, and things you want to learn about
<@jflory7:fedora.im>
15:20:46
I think data, events, and docs were some major 2024 themes
<@jflory7:fedora.im>
15:20:50
What do y'all think?
<@rwright:fedora.im>
15:21:22
Small Goals - I learned I had less time than I thought.
<@rwright:fedora.im>
15:21:37
I licked a lot of cookies, so I want to bake new ones using the original cookies.
<@rwright:fedora.im>
15:22:09
Andddddd. I would like to see metrics behind what we do. And for us to have a quarterly plan for the year at a high level and keep focus at a quarterly level.
<@rwright:fedora.im>
15:22:37
Proud of this analogy.
<@nhanlon:beeper.com>
15:22:46
Robert stole all my points.
<@nhanlon:beeper.com>
15:22:50
Theif!
<@rwright:fedora.im>
15:22:58
I type fast.
<@jflory7:fedora.im>
15:23:24
For the unaware about what "cookie licking" means: https://www.redhat.com/en/blog/stop-licking-cookie
<@rwright:fedora.im>
15:23:36
Ironic - it's about New Years as well
<@jflory7:fedora.im>
15:23:37
!link https://www.redhat.com/en/blog/stop-licking-cookie
<@jflory7:fedora.im>
15:23:44
Actually, yes
<@rwright:fedora.im>
15:23:50
For new years, I am gonna lick less cookies.
<@rwright:fedora.im>
15:23:56
That's it - I'm telling everyone that's my new resolution.
<@rwright:fedora.im>
15:24:08
Open source or not, I'm just saying that
<@jflory7:fedora.im>
15:24:30
I think this is a good area of focus – but I think we have to first figure out what we want to measure with metrics
<@jflory7:fedora.im>
15:24:39
We need to ask the questions we want to answer
<@jflory7:fedora.im>
15:24:50
And then figure out metrics/data once we have the question(s) we want answered
<@rwright:fedora.im>
15:24:56
I think my ask is if we decide to do something, it should be measurable with a result. Not a good or bad, but for us to reflect.
<@rwright:fedora.im>
15:25:28
Like - if we hold F42's release party:
<@rwright:fedora.im>
15:25:28
- How many people signed up to attend? What is the growth from F41?
<@rwright:fedora.im>
15:25:28
- How many attendees did we get? What is the growth from F41?
<@rwright:fedora.im>
15:25:36
Two simple questions and easily reported on IMO
<@zodbot:fedora.im>
15:25:44
neil gave a cookie to rwright. They now have 17 cookies, 3 of which were obtained in the Fedora 41 release cycle
<@jflory7:fedora.im>
15:25:56
Don't lick that one :P
<@rwright:fedora.im>
15:26:16
No no not licking
<@jflory7:fedora.im>
15:26:29
These are good but I don't want to focus so much on the release parties
<@jflory7:fedora.im>
15:27:00
I spoke recently with Aoife Moloney and she is considering to take more ownership on the release events as part of her work, but we have not landed on a specific place there yet
<@jflory7:fedora.im>
15:27:15
For me personally, I have to stop licking the virtual event cookies :/
<@jflory7:fedora.im>
15:27:40
I am thinking about the onboarding path
<@jflory7:fedora.im>
15:27:47
I had a TO-DO for today's meeting that I did not get done
<@rwright:fedora.im>
15:27:51
I think CommOps should be the community arm that Aoife works with though
<@jflory7:fedora.im>
15:28:05
Someone recently asked about the Pantheon SIG, and helping improve the onboarding experience for new packagers and contributors to that SI
<@jflory7:fedora.im>
15:28:08
Someone recently asked about the Pantheon SIG, and helping improve the onboarding experience for new packagers and contributors to that SIG
<@jflory7:fedora.im>
15:28:17
It got me thinking, how can we make the onboarding experience an area of focus?
<@jflory7:fedora.im>
15:28:29
This was part of the Initiative, but it was a part that did not get a lot of focus
<@rwright:fedora.im>
15:28:31
- We should should train people how to consume data from the bus and to do basic analysis
<@rwright:fedora.im>
15:28:31
- <Something else>
<@rwright:fedora.im>
15:28:31
OK - fast answer on my view for 2025.
<@rwright:fedora.im>
15:28:31
<@rwright:fedora.im>
15:28:31
- We should host and deliver on the Release Parties with support from other teams like Marketing, FESCo, Council, and more for content.
<@jflory7:fedora.im>
15:28:31
In 2024, I mean
<@rwright:fedora.im>
15:28:44
This could be the something else.
<@rwright:fedora.im>
15:29:13
I just like 3's - they're odd numbers.
<@jflory7:fedora.im>
15:29:33
> We should host and deliver on the Release Parties with support from other teams like Marketing, FESCo, Council, and more for content.
<@jflory7:fedora.im>
15:29:33
For this one, I am not going to stand in the way of anyone to do this work, but for me personally, I am not going to help with this work actively because I have to put my priority on Flock as far as events are concerned. Someone else will have to take ownership and lead it.
<@jflory7:fedora.im>
15:29:33
<@nhanlon:beeper.com>
15:29:49
I think focusing on Onboarding is the right thing, particularly in light of 2028 being really close, all things considered
<@jflory7:fedora.im>
15:30:04
This makes sense. Although it is not something I feel empowered to lead on, but I am happy to be a supporting role here as I am able
<@jflory7:fedora.im>
15:30:04
<@jflory7:fedora.im>
15:30:04
> We should should train people how to consume data from the bus and to do basic analysis
<@rwright:fedora.im>
15:30:06
I think that's where we work with Aoife Moloney to support and drive it with everyone
<@nhanlon:beeper.com>
15:30:19
and being able to measure the impact is obviously cruicial, to Robert's point(s)
<@jflory7:fedora.im>
15:30:22
<@jflory7:fedora.im>
15:30:22
I would really like this to be something about onboarding specifically.
<@jflory7:fedora.im>
15:30:22
> <Something else>
<@rwright:fedora.im>
15:30:23
I actually like this a lot.
<@rwright:fedora.im>
15:30:29
I think we really struggle with Onboarding.
<@jflory7:fedora.im>
15:30:37
How could we narrow down onboarding to something more specific.
<@jflory7:fedora.im>
15:30:40
How could we narrow down onboarding to something more specific?
<@jflory7:fedora.im>
15:30:45
Yes.
<@nhanlon:beeper.com>
15:30:53
onboarding and retention
<@rwright:fedora.im>
15:30:58
We loose a lot of people in the pipe of making a FAS account on a weekly basis to actually doing something.
<@rwright:fedora.im>
15:31:04
https://i.snap.as/pFKc8EMb.png
<@jflory7:fedora.im>
15:31:16
We probably need to ask Aoife if she wants to drive this through CommOps or some other way. For all practical purposes, I think Aoife is considering to be the owner of this, but I don't want to put words in her mouth.
<@jflory7:fedora.im>
15:31:39
This challenge is as old as I have been a contributor to Fedora :)
<@nhanlon:beeper.com>
15:31:40
zoinks.
<@rwright:fedora.im>
15:31:59
I stole an image from my second agenda item ;)
<@amoloney:fedora.im>
15:32:04
three pings, Im gere
<@amoloney:fedora.im>
15:32:10
three pings, Im here
<@rwright:fedora.im>
15:32:29
Idk why but that's super good to know you work like Beetlejuice.
<@jflory7:fedora.im>
15:32:34
This looks interesting but I think I need a subtitle or annotation to make sense of what I am seeing. It is a lot of numbers and I am not sure what they are telling me.
<@amoloney:fedora.im>
15:32:45
Im making the beetlejuice face with the jazzhands now
<@amoloney:fedora.im>
15:33:15
fwiw, yeah I would like to take on ownership of the release parties, but supported through commops
<@rwright:fedora.im>
15:33:18
I'll do this in part 2 of the agena.
<@nhanlon:beeper.com>
15:33:26
you don't have the LLM Glasses integration that just interprets graphs right in your brainstem?
<@jflory7:fedora.im>
15:33:33
What about focusing on the SIG experience specifically? Guidelines and best practices on how to create functional, healthy teams in Fedora, and some sort of metrics framework to know whether you are doing it right or not?
<@jflory7:fedora.im>
15:34:10
That is helpful to know. So, if this is your preference, then we make the F42 and F43 virtual release events a 2025 focus for the team.
<@jflory7:fedora.im>
15:34:30
!info @amoloney wishes to take ownershio of the release events, with support and organization via CommOps.
<@rwright:fedora.im>
15:34:33
2. Identify a set of recommendations for improvement based on feedback from stakeholders
<@rwright:fedora.im>
15:34:33
1. Identify how the process typically is done today across Fedora
<@rwright:fedora.im>
15:34:33
3. Optionally - identify a path for implementing those recommendations?
<@rwright:fedora.im>
15:34:33
Could we say -
<@jflory7:fedora.im>
15:34:56
What is "the process" mean here? Starting a SIG?
<@rwright:fedora.im>
15:35:04
Joining a SIG
<@rwright:fedora.im>
15:35:12
Sorry - I should claritfy
<@jflory7:fedora.im>
15:35:19
Who is our target audience?
<@jflory7:fedora.im>
15:35:28
Is it new contributors, SIG leads/owners, or someone else?
<@jflory7:fedora.im>
15:35:50
IMHO, we should focus on community leads and empower them to be onboarding experts in their own circles
<@rwright:fedora.im>
15:35:54
We are working to identify Pain Points in New Contributors joining SIGs by providing a set of recommendations to Mindshare / FESCo
<@jflory7:fedora.im>
15:35:59
Instead of CommOps trying to define onboarding for newcomers
<@jflory7:fedora.im>
15:36:01
If this makes sense
<@rwright:fedora.im>
15:36:34
FESCo probably cares more about Engineering SIGs and Mindshare about community. Probably FESCo more? Or does that not make sense - I know they're a Engineering body, so Idk
<@jflory7:fedora.im>
15:37:18
Do we specifically want Mindshare/FESCo to "own" the best practices and guidelines, and act as a ratifying body on those best practices? Or is it better to keep it more autonomous to CommOps to maintain and update the guidelines? Would Mindshare/FESCo want this work of maintaining the guidelines? Or another way to ask it, do they have capacity for that?
<@nhanlon:beeper.com>
15:37:28
I think it's for three groups:
<@nhanlon:beeper.com>
15:37:28
<@nhanlon:beeper.com>
15:37:28
* New contributors wishing to see how to join something and get involved -- but this should be very last because the above two should naturally guide folks, IMO
<@nhanlon:beeper.com>
15:37:28
* SIG Leads - giving the tools (a framework, if you will) to create and nurture healthy communities/groups
<@nhanlon:beeper.com>
15:37:28
* Mindshare/Fesco - To understand how the SIG works and not have it be a black box until there's a problem
<@rwright:fedora.im>
15:37:46
I think both Neil and Justin are saying the same thing which I realize is an unknown
<@rwright:fedora.im>
15:37:52
Who owns SIGs as a concept?
<@rwright:fedora.im>
15:37:57
And does it matter?
<@jflory7:fedora.im>
15:38:07
Anyone and everyone. Which is why it is so difficult, I think :D
<@rwright:fedora.im>
15:38:08
Or are we just publishing a set of recommendations with a FYI to those two major bodies
<@jflory7:fedora.im>
15:38:18
I like this
<@jflory7:fedora.im>
15:38:31
CommOps-maintained guidelines and processes on how to start a successful team/SIG in Fedora
<@rwright:fedora.im>
15:38:32
I think we could treat it like a Research activity - "were here to provide a set of recommendations to the governing bodies of Fedora"
<@jflory7:fedora.im>
15:38:33
And
<@jflory7:fedora.im>
15:38:38
Especially with Forgejo on the horizon
<@rwright:fedora.im>
15:38:40
But not own the implementaiton
<@jflory7:fedora.im>
15:38:50
This is a great way that we could help standardize how to work as a team within Forgejo
<@nhanlon:beeper.com>
15:38:58
i have a draft of a fun thing I've been working on for Rocky.. one sec
<@jflory7:fedora.im>
15:39:02
Not to get _too_ specific, but to give an idea of what this implementation work could look like
<@rwright:fedora.im>
15:39:15
Well - in sprit of not licking cookies, we shouldn't say they should, but we recommend.
<@jflory7:fedora.im>
15:39:35
+1
<@rwright:fedora.im>
15:39:49
Do folks in Rocky say "we have a rocky draft"? I'm just wondering
<@nhanlon:beeper.com>
15:39:50
https://rpa.st/VPJAPFA3AOSEJUXDFVHEAXQHDE
<@nhanlon:beeper.com>
15:40:13
dangit see I already gave you a cookie this cycle and now I can't give another :(
<@rwright:fedora.im>
15:40:38
Well - I also think one thing that is a weird item - unrelated
<@rwright:fedora.im>
15:40:45
But do we have a master list of all the teams, SIGs, etc in Fedora
<@rwright:fedora.im>
15:40:51
There's a old repo where someone was making meta data
<@jflory7:fedora.im>
15:41:05
This is a great example of something I would like for Fedora to have too, but maybe more like a handbook
<@nhanlon:beeper.com>
15:41:06
FAS i guess should, theoretically (?)
<@jflory7:fedora.im>
15:41:09
Similar to how Mentored Projects did it
<@jflory7:fedora.im>
15:41:34
The org chart is the closest thing, IMHO. That or docs.fp.o, but spread out across several pages
<@nhanlon:beeper.com>
15:41:46
I have a more finished draft... somewhere. I think I lost it 😂 but yeah, a Handbook is sorta what I was going for
<@rwright:fedora.im>
15:41:49
K - I'll take offline but maybe something we figure out
<@nhanlon:beeper.com>
15:42:13
and as you said, with Forgejo on the horizon, a handbook is an excellent opportunity to also give some info about how _that_ all works, too
<@jflory7:fedora.im>
15:42:14
I feel like we are approaching a consensus on possible 2025 goals
<@rwright:fedora.im>
15:42:28
Can you restate them? I feel like we wondered a bit.
<@jflory7:fedora.im>
15:42:30
Let me recap what I think I am hearing from y'all
<@rwright:fedora.im>
15:42:41
our mind brains are connected
<@jflory7:fedora.im>
15:43:21
So, generally, as a team, we should have a few, clearly-defined goals for us to focus on as a team in 2025. We also acknowledge that we need to do less "cookie licking" and make sure we take on a reasonable amount of work, and not overcommit ourselves.
<@jflory7:fedora.im>
15:43:29
Because we also have our own newcomers to onboard into CommOps :D
<@jflory7:fedora.im>
15:43:31
So!
<@jflory7:fedora.im>
15:43:37
I am hearing three goals.
<@jflory7:fedora.im>
15:44:07
1. Release Events: Supporting Aoife Moloney as the owner of the F42 and F43 release events, and defining an organizing timeline and key areas for the community to help with organizing these.
<@jflory7:fedora.im>
15:44:51
2. Defining best practices and guidelines to experienced Fedora contributors on how to create and maintain healthy teams/SIGs, and advice and tools to help them be more effective and efficient with onboarding new contributors.
<@jflory7:fedora.im>
15:45:17
3. Using our existing metrics tools to support goals #1 and #2, but also defining a common pathway for how we measure impact/success of goals #1 and #2.
<@jflory7:fedora.im>
15:45:23
How do these sound?
<@jflory7:fedora.im>
15:46:27
shaunm bt0dotninja Yaash Y'all have been quiet, so I am curious for your input especially here too :) Since we are talking big picture for the whole 2025!
<@jflory7:fedora.im>
15:46:50
Do you have questions? Do these make sense? Are these things y'all are interested in too?
<@thisisyaash:fedora.im>
15:49:40
<@thisisyaash:fedora.im>
15:49:40
..
<@thisisyaash:fedora.im>
15:49:40
well, yes this is interesting to work on!
<@thisisyaash:fedora.im>
15:49:40
as Ive actually mentioned about onboarding process is quite complex (for me)
<@thisisyaash:fedora.im>
15:49:40
even I was able to find that there's team named Community Operations after checking the https://whatcanidoforfedora.org/en
<@thisisyaash:fedora.im>
15:50:13
im interested in helping out :D
<@thisisyaash:fedora.im>
15:50:13
so yes these goals seem good
<@jflory7:fedora.im>
15:50:39
Figuring out that WCIDFF website as part of the onboarding guidelines is not a bad idea actually -- helping document how a team can update their own entry in that website, so the work is not on an overburdened maintainer.
<@jflory7:fedora.im>
15:50:46
Awesome!
<@jflory7:fedora.im>
15:50:54
We would be honored to have you on the journey 😎
<@jflory7:fedora.im>
15:51:03
OK, so we 10 minutes left for our meeting today.
<@jflory7:fedora.im>
15:51:10
I know Robert had some metrics and data.
<@jflory7:fedora.im>
15:51:42
In lieu of the rest of you sharing input, I will assume your silence is your agreement that I am so well-spoken and well-articulated and the goals that I wrote are exactly what was in your minds 😉
<@jflory7:fedora.im>
15:52:16
😌
<@rwright:fedora.im>
15:52:52
<@rwright:fedora.im>
15:52:52
- https://rwright.co/grep2parquet (How to get Bus data to work with offline)
<@rwright:fedora.im>
15:52:52
I'll yield to this conversation but will drop a set of 4 blog posts which are more of a rant:
<@rwright:fedora.im>
15:52:52
- https://rwright.co/processing-messagages-from-the-bus (How to process and extract FAS Accounts from messages)
<@rwright:fedora.im>
15:52:52
- https://rwright.co/can-we-see-if-community-comes-back (About the chart above that Neil Hanlon and JWF (he/him) asked about)
<@rwright:fedora.im>
15:52:52
- https://rwright.co/can-we-see-trends-in-the-topics (An idea about the Fedora 2028 Strategy)
<@jflory7:fedora.im>
15:52:53
!info CommOps should have a few, clearly-defined goals for us to focus on as a team in 2025. We also acknowledge that we need to do less "cookie licking" and make sure we take on a reasonable amount of work, and not overcommit ourselves. We are discussing three goals/priorities for CommOps in 2025:
<@jflory7:fedora.im>
15:53:09
!info 1. Release Events: Supporting @amoloney as the owner of the F42 and F43 release events, and defining an organizing timeline and key areas for the community to help with organizing these.
<@jflory7:fedora.im>
15:53:18
!info 2. Defining best practices and guidelines to experienced Fedora contributors on how to create and maintain healthy teams/SIGs, and advice and tools to help them be more effective and efficient with onboarding new contributors.
<@jflory7:fedora.im>
15:53:29
!info 3. Using our existing metrics tools to support goals #1 and #2, but also defining a common pathway for how we measure impact/success of goals #1 and #2.
<@jflory7:fedora.im>
15:54:00
!topic Review of Jupyter Style Data Analysis on CommuniShift
<@rwright:fedora.im>
15:54:12
So - my only thing here iwth this agenda item
<@jflory7:fedora.im>
15:54:49
!info === "How to get Bus data to work with offline" ===
<@jflory7:fedora.im>
15:54:52
!link https://rwright.co/grep2parquet
<@jflory7:fedora.im>
15:54:56
!info === "How to process and extract FAS Accounts from messages" ===
<@jflory7:fedora.im>
15:55:00
!link https://rwright.co/processing-messagages-from-the-bus
<@jflory7:fedora.im>
15:55:20
!info === "About the chart above that" ===
<@jflory7:fedora.im>
15:55:22
!link https://rwright.co/can-we-see-if-community-comes-back
<@jflory7:fedora.im>
15:55:36
!info === "An idea about the Fedora 2028 Strategy" ===
<@jflory7:fedora.im>
15:55:37
!link https://rwright.co/can-we-see-trends-in-the-topics
<@jflory7:fedora.im>
15:55:43
Wow, Meet Bot, you are so spammy
<@jflory7:fedora.im>
15:55:45
So, so spammy
<@rwright:fedora.im>
15:55:46
- And then we teach people to just play around in Jupyter?
<@rwright:fedora.im>
15:55:46
Is I think it's worth saying that my new idea to reduce the number of cookies I could lick by baking a set of new cookies which are easy:
<@rwright:fedora.im>
15:55:46
<@rwright:fedora.im>
15:55:46
- Is it too hard right now to get a clone of Datagrepper's DB to AWS and instead to just host offline copies in our CommuniShift
<@rwright:fedora.im>
15:55:46
- And then to just host using the native OpenShift's Jupyter hosting
<@jflory7:fedora.im>
15:55:54
Your only thing is?
<@jflory7:fedora.im>
15:56:05
Ah
<@rwright:fedora.im>
15:56:16
I think that reduces the workload for Infra, is easier to push deploy, and then supports the things above
<@rwright:fedora.im>
15:56:17
AND
<@rwright:fedora.im>
15:56:28
Supports the overall risk I have around equitable data access for the community
<@rwright:fedora.im>
15:56:39
Because then people don't have to download and process
<@jflory7:fedora.im>
15:56:53
I cannot comment on #1 and #2, but #3 makes sense and Jupyter is kinda a leading tool for this kind of stuff
<@jflory7:fedora.im>
15:57:01
So, it means there might be more people out there who want to help us with this
<@rwright:fedora.im>
15:57:48
If it makes sense, I'll check in with Infra, ask how far along they are in that endeavor and pause it. And then ask to reuse our Comunishift project to setup a Jupyter hosting and then load the Parquet files there.
<@rwright:fedora.im>
15:58:04
And then boom boom boom - data, science, magic, analysis
<@jflory7:fedora.im>
15:58:07
Theoretically, that sounds good to me.
<@rwright:fedora.im>
15:58:13
And for now that could do
<@jflory7:fedora.im>
15:58:15
I am ready for the magic, when does that come? :D
<@rwright:fedora.im>
15:58:58
When we convert people to long term contributors. I don't have a magic book - wait is this a CHAOSS reference to Grimore?
<@jflory7:fedora.im>
15:59:08
I need to practice my timeliness more in 2025 :P
<@jflory7:fedora.im>
15:59:28
Hahah no, I am just ready to be impressed with flashy data and sparkly metrics :D
<@nhanlon:beeper.com>
15:59:30
With what time!
<@jflory7:fedora.im>
15:59:46
lolol
<@jflory7:fedora.im>
15:59:51
OK, so we do need to yield the meeting room.
<@jflory7:fedora.im>
16:00:04
This was a packed discussion. We did not cover everything. But I like this 2025 goal-setting we did.
<@rwright:fedora.im>
16:00:14
!action Robert to investigate with Infra on transitioning from SQL hosting to Jupyter hosting for Data Lab
<@jflory7:fedora.im>
16:00:17
I need to think about getting the CommOps issue tracker up to date.
<@nhanlon:beeper.com>
16:00:19
Thank you all! Have a great rest of the week
<@jflory7:fedora.im>
16:00:36
Thanks folks! Have a great beginning to your 2025!
<@jflory7:fedora.im>
16:00:42
See you in #commops:fedoraproject.org and around Fedora :)
<@jflory7:fedora.im>
16:00:47
!endmeeting