#meeting:fedoraproject.org: commops

Meeting started by @jflory7:fedora.im at 15:02:32 UTC

INFO: Intros, welcomes, hellos (~5m) (@jflory7:fedora.im, 15:03:46)
INFO: Team announcements & news (~5-10m) (@jflory7:fedora.im, 15:03:50)
INFO: Follow-ups from last meeting (if any) (~5-10m) (@jflory7:fedora.im, 15:03:53)
INFO: Ticket discussions (remaining time) (@jflory7:fedora.im, 15:03:56)
INFO: Open floor (remaining 5-10 minutes) (@jflory7:fedora.im, 15:03:59)

INFO: Present: @jflory7 @rwright @thisisyaash @shaunm @bt0dotninja @neil (@jflory7:fedora.im, 15:07:31)

INFO: === "Running Generative AI Models Locally with Ollama and Open WebUI" === (@jflory7:fedora.im, 15:09:12)
LINK: https://fedoramagazine.org/running-generative-ai-models-locally-with-ollama-and-open-webui/ (@jflory7:fedora.im, 15:09:17)
INFO: === "Fedora Chooses Forgejo!" ==== (@jflory7:fedora.im, 15:10:22)
LINK: https://communityblog.fedoraproject.org/fedora-chooses-forgejo/ (@jflory7:fedora.im, 15:10:27)
INFO: FOSDEM 2025 is around the corner, from 1-2 February 2025 (@jflory7:fedora.im, 15:12:15)
LINK: https://fosdem.org/2025/ (@jflory7:fedora.im, 15:12:26)
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:54)
LINK: https://git.resf.org/infrastructure/buzon (@jflory7:fedora.im, 15:14:55)

INFO: Review of "what we want to do in 2025 as CommOps" (@jflory7:fedora.im, 15:16:11)
INFO: Review of Jupyter Style Data Analysis on ComminiShift (@jflory7:fedora.im, 15:16:13)
INFO: F42 Planning! (@jflory7:fedora.im, 15:16:14)

TOPIC:Review of "what we want to do in 2025 as CommOps" (@jflory7:fedora.im, 15:17:32)

LINK: https://www.redhat.com/en/blog/stop-licking-cookie (@jflory7:fedora.im, 15:23:37)
INFO: @amoloney wishes to take ownershio of the release events, with support and organization via CommOps. (@jflory7:fedora.im, 15:34:30)
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:52:53)
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:09)
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:18)
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:53:29)

TOPIC:Review of Jupyter Style Data Analysis on CommuniShift (@jflory7:fedora.im, 15:54:00)

INFO: === "How to get Bus data to work with offline" === (@jflory7:fedora.im, 15:54:49)
LINK: https://rwright.co/grep2parquet (@jflory7:fedora.im, 15:54:52)
INFO: === "How to process and extract FAS Accounts from messages" === (@jflory7:fedora.im, 15:54:56)
LINK: https://rwright.co/processing-messagages-from-the-bus (@jflory7:fedora.im, 15:55:00)
INFO: === "About the chart above that" === (@jflory7:fedora.im, 15:55:20)
LINK: https://rwright.co/can-we-see-if-community-comes-back (@jflory7:fedora.im, 15:55:22)
INFO: === "An idea about the Fedora 2028 Strategy" === (@jflory7:fedora.im, 15:55:36)
LINK: https://rwright.co/can-we-see-trends-in-the-topics (@jflory7:fedora.im, 15:55:37)
ACTION: Robert to investigate with Infra on transitioning from SQL hosting to Jupyter hosting for Data Lab (@rwright:fedora.im, 16:00:14)

Meeting ended at 16:00:47 UTC

Robert to investigate with Infra on transitioning from SQL hosting to Jupyter hosting for Data Lab