<@jflory7:fedora.im>
14:01:12
!startmeeting Fedora CommOps
<@meetbot:fedora.im>
14:01:13
Meeting started at 2024-05-28 14:01:12 UTC
<@meetbot:fedora.im>
14:01:13
The Meeting name is 'Fedora CommOps'
<@nhanlon:beeper.com>
14:01:16
!hi
<@zodbot:fedora.im>
14:01:18
Neil Hanlon (neil) - he / him / his
<@rwright:fedora.im>
14:01:19
!hi
<@zodbot:fedora.im>
14:01:20
Robert Wright (rwright) - he / him / his
<@jflory7:fedora.im>
14:01:41
!topic Agenda
<@jflory7:fedora.im>
14:01:41
!info (2) Team announcements & news
<@jflory7:fedora.im>
14:01:41
!info (1) Intros, welcomes, hellos
<@jflory7:fedora.im>
14:01:41
!info (6) Open floor
<@jflory7:fedora.im>
14:01:41
!info (5) Ticket-driven discussion
<@jflory7:fedora.im>
14:01:41
!info (4) Follow-ups from last meeting
<@jflory7:fedora.im>
14:01:41
!info (3) Initiative Lead updates to the team
<@jflory7:fedora.im>
14:01:46
!topic Intros, welcomes, hellos
<@jflory7:fedora.im>
14:01:58
If this is your first time at a CommOps Team meeting, please say hello! If you have questions before we start the meeting, now is also a good time to ask.
<@jflory7:fedora.im>
14:01:59
!hi
<@zodbot:fedora.im>
14:02:01
Justin W. Flory (jflory7) - he / him / his
<@tosin_doreen:matrix.org>
14:02:03
!hi
<@zodbot:fedora.im>
14:02:05
Oluwatosin Olatunji (tosindoreen) - she / her / hers
<@jflory7:fedora.im>
14:02:30
Hello hello Adrian Edwards, Robert Wright (he/him), Neil Hanlon, and tosin_doreen! 👋
<@rwright:fedora.im>
14:02:40
hello Justin W. Flory (he/him)
<@rwright:fedora.im>
14:03:06
Adrian Edwards: +1 welcome aboard btw
<@jflory7:fedora.im>
14:03:08
While everyone is getting plugged in…
<@jflory7:fedora.im>
14:03:14
Please take a look at the agenda here: https://pad.sfconservancy.org/p/fedora-commops-meetings
<@jflory7:fedora.im>
14:03:23
And write your name in for the attendance today
<@jflory7:fedora.im>
14:03:31
And importantly, today's icebreaker question is………
<@jflory7:fedora.im>
14:03:38
Coffee, tea, or something else???
<@jflory7:fedora.im>
14:03:49
Write your answer in the pad and let us know 😀
<@tosin_doreen:matrix.org>
14:03:51
What is the purpose of this meeting is the only question I have. Is there a particular initiative which this meeting is the driving force for?
<@jonatoni:fedora.im>
14:04:20
!hi
<@zodbot:fedora.im>
14:04:21
Jona Azizaj (jonatoni) - she / her / hers
<@jflory7:fedora.im>
14:05:11
Good question. This ties into a new Community Initiative to reboot the CommOps team from its previously dormant state. Although, the Initiative is about the team, it is also a fully-functioning team focused on two types of contributions: process improvement & contributor experience, and community social analysis.
<@jflory7:fedora.im>
14:05:14
More details: https://fedoraproject.org/wiki/Initiatives/Community_Ops_2024_Reboot
<@jflory7:fedora.im>
14:05:22
Hey Jona Azizaj (she/her)! 👋
<@jflory7:fedora.im>
14:06:14
I am loving the out-of-the-box responses there so far 🙂
<@moralcode:fedora.im>
14:06:46
im sorta tangentially curious about the sfconservancy domain there
<@tosin_doreen:matrix.org>
14:06:47
Thank you
<@moralcode:fedora.im>
14:06:56
like does fedora do work with conservancy?
<@jflory7:fedora.im>
14:07:06
Adrian Edwards: I like their Etherpad instance. That is about it, in this specific case.
<@jflory7:fedora.im>
14:07:23
tosin_doreen: No problem! Also, we will have some time at the end of this meeting for questions too.
<@jflory7:fedora.im>
14:07:24
OK. We are 6 minutes past, so let me log the attendance and then we will get into today's agenda!
<@jflory7:fedora.im>
14:07:55
!info Present: @moralcode, @rwright, @neil, @tosindoreen, @jonatoni, @jflory7
<@jflory7:fedora.im>
14:08:02
!topic Team announcements & news
<@jflory7:fedora.im>
14:08:24
!info Elections are underway until May 30th! Please make sure to cast a vote in the Fedora Elections before the deadline.
<@jflory7:fedora.im>
14:08:58
!link https://elections.fedoraproject.org/
<@jflory7:fedora.im>
14:09:03
!link https://communityblog.fedoraproject.org/elections-voting-is-now-open/
<@jflory7:fedora.im>
14:09:26
That double-posting for links is a bit annoying 😅
<@jflory7:fedora.im>
14:09:37
Anyone else have news or announcements they would like to share?
<@jflory7:fedora.im>
14:09:45
Anything cool or interesting happening out there in the Fedora-verse?
<@jflory7:fedora.im>
14:09:49
FWD? :)
<@roseline:matrix.org>
14:10:36
!hi
<@zodbot:fedora.im>
14:10:38
Roseline Bassey (roseline-bassey) - she / her / hers
<@jflory7:fedora.im>
14:10:43
Hey Roseline Bassey!
<@moralcode:fedora.im>
14:10:48
ill go raise it as an issue haha
<@jflory7:fedora.im>
14:10:52
!info +Present: @roseline-bassey
<@jonatoni:fedora.im>
14:10:55
oh yeah, we have open registrations for FWD
<@rwright:fedora.im>
14:11:07
link for FWD?
<@jonatoni:fedora.im>
14:11:10
https://pretix.eu/fedora/fwd2024/
<@jflory7:fedora.im>
14:11:34
!info Registration is now open for Fedora Week of Diversity! Register now and claim your free ticket to the event next month.
<@jflory7:fedora.im>
14:11:37
!link https://pretix.eu/fedora/fwd2024/
<@jflory7:fedora.im>
14:11:43
It is just around the corner now 🤩
<@jonatoni:fedora.im>
14:12:03
I'm super excited about it 🎉
<@jflory7:fedora.im>
14:12:30
Any other announcements?
<@jflory7:fedora.im>
14:12:40
Oh, well, maybe an obvious one actually :)
<@jflory7:fedora.im>
14:13:20
!info Officially welcoming Adrian Edwards, tosin_doreen, and Roseline Bassey as our new Community Architect interns working in Fedora for the next few months! Expect to see them more around the community. Please give them a warm Fedora welcome!
<@rwright:fedora.im>
14:13:41
welcome tosin_doreen Roseline Bassey !
<@nhanlon:beeper.com>
14:13:53
welcome!
<@rwright:fedora.im>
14:13:57
I already said welcome to Adrian Edwards earlier in chat! lol
<@tosin_doreen:matrix.org>
14:15:00
Thank you everyone for the warm welcome 🫡💃
<@jflory7:fedora.im>
14:15:23
OK. I think that is it for announcements. 🙂 Let's move on to Initiative Lead updates.
<@jflory7:fedora.im>
14:15:30
!topic Initiative Co-Lead updates to the team
<@jflory7:fedora.im>
14:15:35
Robert Wright (he/him): Baton pass over to you?
<@rwright:fedora.im>
14:15:43
Yes! I have a few updates.
<@rwright:fedora.im>
14:16:00
👋 Hello - sorry for my quiet period, it's been busy with work for reasons. :)
<@rwright:fedora.im>
14:16:31
1. We are setting up a bi-weekly co-working call with the community ops team here. So we want to solicit feedback of when folks could attend.
<@rwright:fedora.im>
14:16:50
We think this would be a great way for folks to hop in for an hour and just work on things together, or just hang out while we hack on different tickets.
<@jflory7:fedora.im>
14:17:06
Bringing back the hack sessions! 😎
<@roseline:matrix.org>
14:17:11
Thanks everyone! Glad to be a part of Fedora.
<@rwright:fedora.im>
14:17:17
Justin came up with this as something he's done in the past. And we would like to make it happen!
<@rwright:fedora.im>
14:18:06
I think we will just throw out a time to the community and we will move it around based on availability, but it's a open call where folks can jsut hang out and work, screenshare, and get help.
<@jflory7:fedora.im>
14:18:19
No coding required :)
<@rwright:fedora.im>
14:18:30
Justin W. Flory (he/him): I don't know if we have a time or date really set yet, but just we'll throw one out here soon ya?
<@jflory7:fedora.im>
14:18:34
Although coding is certainly welcome too
<@rwright:fedora.im>
14:18:46
Low-Code 🤣
<@jflory7:fedora.im>
14:19:10
Nothing set yet. We can put together a Rallly poll or throw down some times that work for facilitating. Also, it does have to be only me or Robert running them, but anyone could theoretically pick these up and hold a time for people to come together to work on things.
<@jflory7:fedora.im>
14:19:19
I think for now, the answer is "stay tuned for more"
<@rwright:fedora.im>
14:19:26
+1 to that :D
<@jflory7:fedora.im>
14:19:26
Soon™
<@moralcode:fedora.im>
14:19:37
+1 for rallly - its a cool platform
<@moralcode:fedora.im>
14:19:50
+1 for rallly - its a cool (and FOSS) platform
<@rwright:fedora.im>
14:20:15
On that next hacking call, I want to make available some data sets for folks to play with as Parquet or CSV files of some message bus data in a normalized manor to get some feedback.
<@rwright:fedora.im>
14:20:15
Ok - second update.
<@rwright:fedora.im>
14:20:15
<@rwright:fedora.im>
14:20:34
Since in the ticket updates we'll talk about Grafana, I want to get some feedback of where folks do and don't understand some of the bus data, so we can figure out better the approach to documenting it.
<@jflory7:fedora.im>
14:21:02
!info Stay tuned for CommOps Hack Sessions coming to a calendar near you. Hack Sessions are informal calls where you can hang out with your peers and work together on CommOps tasks or ask questions. There is no formal agenda and no requirement to stay for the full period. Come and go as you can. More details about exact timings to be shared soon on Fedora Discussion and Matrix.
<@rwright:fedora.im>
14:21:02
And so Grafana as it comes online will be easier for the community to write queries around and create dashboards for some of the open tickets.
<@rwright:fedora.im>
14:21:35
I think there's a lot of interest in Fedora data, and thanks to Neil Hanlon for fixing the Ansible role 😃 - we can move forward getting this up!
<@rwright:fedora.im>
14:21:49
That's my updates!
<@jflory7:fedora.im>
14:21:50
Grafana being a dashboard web app we use to build charts, graphs, and more from data we have today in Fedora
<@moralcode:fedora.im>
14:22:20
i have worked with parquet before (slightly - for a big data class where we analyzed the data that NYC published of every taxi or rideshare ride taken since like 2009)- looking forward to being part of that meeting
<@jflory7:fedora.im>
14:22:44
!info One analytics goal for the next hack sessions will be to provide more data for use outside of the Fedora messaging bus, therefore making it easier to play around with using other data viz tools and libraries.
<@jflory7:fedora.im>
14:22:57
Robert Wright (he/him): Thanks for the updates! Let's move forward.
<@jflory7:fedora.im>
14:23:05
!topic Ticket-driven discussion & notes
<@jflory7:fedora.im>
14:23:12
!link https://gitlab.com/fedora/commops/home/-/issues/?label_name%5B%5D=meeting%20topic%20request
<@jflory7:fedora.im>
14:23:31
!topic #35 — Fedora Linux 40 Release Party planning & execution
<@jflory7:fedora.im>
14:23:41
!link https://gitlab.com/fedora/commops/home/-/issues/35
<@jflory7:fedora.im>
14:23:43
OK!
<@jflory7:fedora.im>
14:23:49
This one should be quick-ish :)
<@jflory7:fedora.im>
14:23:57
The F40 Release Party is a wrap 🥳
<@jflory7:fedora.im>
14:24:11
Thanks everyone who participated in the behind the scenes work to make it happen.
<@jflory7:fedora.im>
14:24:18
I wanted to save this time in our meeting to run a brief retrospective.
<@jflory7:fedora.im>
14:24:21
What worked well?
<@jflory7:fedora.im>
14:24:27
What was painful?
<@moralcode:fedora.im>
14:24:30
ooh i took notes one sec
<@jflory7:fedora.im>
14:24:31
What could be better for next time?
<@jflory7:fedora.im>
14:24:52
This is an open brainstorm. Feel free to share your thoughts and ideas with the `!idea` command so they make it into our minutes!
<@jflory7:fedora.im>
14:25:08
!info Retrospective on how things went! What worked well, what was difficult, what could be better for next time?
<@jflory7:fedora.im>
14:25:27
I have a couple of thoughts too that I will put out there, but anyone is welcome to go ahead and type directly in chat!
<@moralcode:fedora.im>
14:25:51
restream seemed good
<@moralcode:fedora.im>
14:25:51
what went well:
<@moralcode:fedora.im>
14:25:51
"the backstage thing was nice to idle in with my camera off to avoid the youtube livestream lag" @carlwgeorge:matrix.org
<@moralcode:fedora.im>
14:25:51
the stream managed to handle justin losing power
<@jflory7:fedora.im>
14:25:53
!idea Earlier start for communications. We got the word out too late. Early promotion and a more firm schedule earlier would be helpful.
<@moralcode:fedora.im>
14:26:01
embed in element. Seems to be very Element client-specific experience
<@moralcode:fedora.im>
14:26:01
restream is freezing
<@moralcode:fedora.im>
14:26:01
stream lag
<@moralcode:fedora.im>
14:26:01
cookie bot spam
<@moralcode:fedora.im>
14:26:01
heavy reliance on QR codes without links to manually type for those watching on their phones
<@moralcode:fedora.im>
14:26:01
What didnt go so well:
<@moralcode:fedora.im>
14:26:20
i should probably have made those more clearly separated bullet points - oops
<@jflory7:fedora.im>
14:26:36
!idea What worked well: "the backstage thing was nice to idle in with my camera off to avoid the youtube livestream lag" @carlwgeorge:matrix.org. the stream managed to handle justin losing power. restream seemed good.
<@moralcode:fedora.im>
14:26:44
2: the stream managed to handle justin losing power
<@moralcode:fedora.im>
14:26:44
1: "the backstage thing was nice to idle in with my camera off to avoid the youtube livestream lag" @carlwgeorge:matrix.org
<@moralcode:fedora.im>
14:26:44
what went well:
<@moralcode:fedora.im>
14:26:44
3: restream seemed good overall. justin was praising it in some of the editing im doing now
<@jflory7:fedora.im>
14:27:11
!idea What didn't go so well: heavy reliance on QR codes without links to manually type for those watching on their phones. Cookie bot spam. Stream lag. Embed in Element seems to be a Element client-specific experience. Restream freezing occasionally.
<@jflory7:fedora.im>
14:27:20
This is a good start.
<@moralcode:fedora.im>
14:27:27
2: cookie bot spam in chat
<@moralcode:fedora.im>
14:27:27
What didnt go so well:
<@moralcode:fedora.im>
14:27:27
5: restream freezing for justin (?)
<@moralcode:fedora.im>
14:27:27
4: embed in element. Seems to be very Element client-specific experience
<@moralcode:fedora.im>
14:27:27
3: stream lag
<@moralcode:fedora.im>
14:27:27
1: heavy reliance on QR codes without links to manually type for those watching on their phones - the audience didnt seem to like the qr code only format for transmitting links
<@jflory7:fedora.im>
14:27:36
I am going to put some people in the hot seat :)
<@jflory7:fedora.im>
14:27:55
Jona Azizaj (she/her): Since we are looking at the same approach for FWD, what are things you would like to see improved before we repeat this event recipe for FWD next month?
<@moralcode:fedora.im>
14:28:17
i already opened an issue against the bot for the cookie spam thing btw: https://github.com/fedora-infra/maubot-fedora/issues/89
<@jflory7:fedora.im>
14:28:21
tosin_doreen, Roseline Bassey: Since this was your very first Release Party, how was your experience? Were you able to follow along well?
<@jonatoni:fedora.im>
14:28:51
+1 to all what you and Adrian mentioned, maybe what I can add is having a video chat networking possibility
<@jflory7:fedora.im>
14:29:13
!idea Bring back hallway track! We did not have A/V for the hallway track / break sessions this time.
<@moralcode:fedora.im>
14:29:22
ah yes, A/V for hallway track - i loved the BBB room at the end of day 2
<@jonatoni:fedora.im>
14:30:08
+1 to have room moderators, it helped a lot to manage the chat, and Q&A
<@jflory7:fedora.im>
14:30:11
!idea BigBlueButton hosted by the GNOME Foundation worked decently for the social activity.
<@jflory7:fedora.im>
14:30:26
!idea Having many chat room moderators helped to manage the chat and Q&A.
<@tosin_doreen:matrix.org>
14:30:45
It was interesting at the beginning, then there was information overload after.
<@tosin_doreen:matrix.org>
14:30:45
Couldn't join the next day because I had other things pre-planned.
<@tosin_doreen:matrix.org>
14:30:45
<@tosin_doreen:matrix.org>
14:30:45
I planned to have a sneak peak at the videos for both days after (since it ties into a task I am to do)
<@nhanlon:beeper.com>
14:30:45
https://github.com/owncast/owncast
<@nhanlon:beeper.com>
14:30:45
<@nhanlon:beeper.com>
14:30:45
So, I know I said a bunch of stuff about not running our own stuff for streaming; but I did recently become aware of this and am working with someone to bring it into Fedora. While I don't think it's a perfect fit for events, it could be an option to 'customize' the experience (?). I dunno, brain is still waking up this morning.
<@jflory7:fedora.im>
14:30:49
I am especially curious for feedback about what was sticky or thorny too :)
<@jflory7:fedora.im>
14:31:24
Neil Hanlon: Oh, that is interesting 👀
<@moralcode:fedora.im>
14:31:26
im working on editing the clips down today so remind me later and ill get those to you if they dont get up on the youtube channel today
<@roseline:matrix.org>
14:31:36
It was definitely a learning experience. Since this was my first Release Party, so there was a lot to take in. I was able to follow some points, but I'd love to hear a recording again to catch everything.
<@jflory7:fedora.im>
14:31:38
!idea Owncast may land in Fedora before the next Release Party: https://github.com/owncast/owncast
<@jonatoni:fedora.im>
14:32:10
pinned messages were great - but not for every client that were visible, so it would be great to find some alternative (?)
<@tosin_doreen:matrix.org>
14:32:14
Thanks loads
<@moralcode:fedora.im>
14:32:27
the full recordings are already on fedoras yourube, theyre just a 5+ hour and a 2+ hour long video
<@jflory7:fedora.im>
14:32:30
tosin_doreen, Roseline Bassey: Information overload makes a lot of sense! Is there anything that might have made it a little less intense? Whether in terms of content, interactivity, or something else?
<@nhanlon:beeper.com>
14:33:01
It's 'spammy', but the old-school way of just making a bot repeat something every 30 minutes or something at least brings the content in front of new joiners
<@jflory7:fedora.im>
14:33:02
!idea Pinned messages worked well, but not all clients show them in the same way, or even show them all. Are there alternative options for organizing key messages?
<@tosin_doreen:matrix.org>
14:33:05
Cries in 7+ hours
<@jflory7:fedora.im>
14:33:43
!idea Getting a chat bot to repeat messages at a regular interval could be useful
<@roseline:matrix.org>
14:33:55
Thanks, I'll take a look later
<@jflory7:fedora.im>
14:33:59
tosin_doreen: I don't think you will have to watch all 7 hours for the event report :D We can chat more about this soon too.
<@moralcode:fedora.im>
14:34:00
could also be kinda spammy
<@moralcode:fedora.im>
14:34:07
maybe a static read only #announcements channe
<@moralcode:fedora.im>
14:34:19
especially if matrix invites are automated
<@moralcode:fedora.im>
14:34:51
a solid chunk of that first 5 hr video is breaks too
<@jflory7:fedora.im>
14:34:52
!idea An event-specific Announcements chat room would make it easier for key messages to be shared with attendees, without them being buried in the backscroll.
<@nhanlon:beeper.com>
14:35:22
I retract my idea in favor of this more better idea :)
<@jonatoni:fedora.im>
14:35:36
this would be awesome 😅 not sure if we can manage this for FWD, but I will definitely need some help with this
<@tosin_doreen:matrix.org>
14:35:39
Plus everyone that asked questions got answers.
<@tosin_doreen:matrix.org>
14:35:39
But I think going forward, as opposed to asking questions in the chat room on threads, there can be a doc where every question can be on. Everyone would have access to the doc and its just better on a doc for easy reference
<@tosin_doreen:matrix.org>
14:35:39
<@tosin_doreen:matrix.org>
14:35:39
It was very interactive though. I enjoyed the introductions part especially 🤣
<@tosin_doreen:matrix.org>
14:35:59
That way, those can feed into like short articles to the general public
<@moralcode:fedora.im>
14:36:22
oh yeah im noticing the threads of question overflow wont be available to people watching on youtube publicly
<@moralcode:fedora.im>
14:36:33
so having public, more permanent Q+A docs would be awesome
<@jflory7:fedora.im>
14:36:39
!idea Interactivity was great, introductions were helpful! People who asked questions got answers.
<@jonatoni:fedora.im>
14:36:54
I think https://matrix.to/#/#creativefreedom:fedora.im was using etherpad/hackmd for this
<@jflory7:fedora.im>
14:37:01
!idea A doc to manage Q&A might be easier than using threads. (Etherpad integration with Matrix, maybe???)
<@moralcode:fedora.im>
14:37:07
+1 for etherpad
<@jflory7:fedora.im>
14:37:09
Same wavelength!
<@nhanlon:beeper.com>
14:37:20
Yeah. A dedicated per-session Q&A 'widget' would be cool (where it automatically ranks them, based on upvotes or w/e); though that again brings up the accessibility/client usage stuff we're talking about w.r.t. pinned messages.
<@jflory7:fedora.im>
14:38:02
!idea A custom widget to help manage Q&A, allows attendees to upvote questions, and rank them automatically for a moderator.
<@jflory7:fedora.im>
14:38:30
I wonder how that would work, re: custom widgets. Definitely a thorny part of Matrix is that people use a variety of clients, and not all of those clients have the same experience with features of Element 🤔
<@jflory7:fedora.im>
14:39:06
Well, this brainstorming is super helpful, and we have captured a lot of feedback so far! 🤩
<@jflory7:fedora.im>
14:39:18
I'll give a couple more minutes to finish up any last messages!
<@nhanlon:beeper.com>
14:39:21
yeah i am guessing some external service that people go use would be the most 'sane' option. but, yeah. we can explore more later :D
<@moralcode:fedora.im>
14:39:23
i found myself as an organizer keeping a note of all the useful links in case i had to repost them
<@moralcode:fedora.im>
14:39:26
maybe automating that?
<@jflory7:fedora.im>
14:39:30
Then I will baton pass to Robert Wright (he/him), I know he had some more topics for today too :)
<@moralcode:fedora.im>
14:39:45
or having bot auto responses to common quesions (like how slackbot does it)
<@moralcode:fedora.im>
14:40:02
like have some trigger text that will caust it to autopost the lievstream link if someone asks
<@jflory7:fedora.im>
14:40:09
!idea Organizers were keeping track of useful links to share them again later. A better way of managing key information for distribution among organizers and chat moderators?
<@rwright:fedora.im>
14:40:09
Ticket 25 is next once we're done here. :)
<@moralcode:fedora.im>
14:40:09
like have some trigger text that will cause it to autopost the lievstream link if someone asks
<@rwright:fedora.im>
14:40:15
But I can do mine in 5 mins short.
<@rwright:fedora.im>
14:40:35
So if people want to keep thinking ideas, I'm good here :)
<@jflory7:fedora.im>
14:40:45
I want to leave you with more time than that, I don't want to crunch you up to the end of the hour :)
<@rwright:fedora.im>
14:40:54
no no it's fine :)
<@rwright:fedora.im>
14:40:59
This conversation is interesting ot watch
<@jflory7:fedora.im>
14:41:01
Well, this is a good reminder that the ticket is also a great place to collect feedback!
<@jflory7:fedora.im>
14:41:22
I will work on adding the feedback from the `!idea` commands into the GitLab issue for a retrospective
<@jflory7:fedora.im>
14:41:28
But more ideas are always welcome later too
<@jflory7:fedora.im>
14:42:06
OK, I think messages are slowing down here… let's go ahead and transition over to #25 :)
<@jflory7:fedora.im>
14:42:09
Thanks all for this feedback!
<@jflory7:fedora.im>
14:42:16
The lightning brainstorm was super useful! 🔍️
<@jflory7:fedora.im>
14:42:23
We will definitely use this feedback for next time 💪
<@jflory7:fedora.im>
14:42:32
Next up…
<@jflory7:fedora.im>
14:42:37
!topic #25 — 2024 Initiative Output - Community Social Analytics: Data Dictionary
<@jflory7:fedora.im>
14:42:44
!link https://gitlab.com/fedora/commops/home/-/issues/25
<@jflory7:fedora.im>
14:42:49
Robert Wright (he/him): Over to you, sir!
<@rwright:fedora.im>
14:42:53
So my quick update on #25 is - I wrote a step by step for this ticket.
<@rwright:fedora.im>
14:43:03
If someone wants to pick this up to start working on, it's a pretty simple one but it is important.
<@rwright:fedora.im>
14:43:17
One of the biggest things when you start a data program is making sure there is alignment and understanding around what data is.
<@rwright:fedora.im>
14:43:30
And the two main parts is "how do we speak about data" and "where do we get data".
<@rwright:fedora.im>
14:43:59
So to summarize this ticket, I put in some easy steps someone could do to get started with this. It is a good fact finding and hunt and gather of terms and data sources around fedora.
<@rwright:fedora.im>
14:44:09
I wanted to ask if anyone wanted to take this one on.
<@jflory7:fedora.im>
14:44:11
I like the step-by-step guide
<@jflory7:fedora.im>
14:44:14
I am wondering…
<@roseline:matrix.org>
14:44:21
<@roseline:matrix.org>
14:44:21
For a more interactive experience, we can explore ways to make the speakers engage with the audience during their presentations. At the party, the speakers were only able to interact with the audience after their session.
<@jflory7:fedora.im>
14:44:31
Would it be helpful to brainstorm now and see if we can come up with five terms?
<@jflory7:fedora.im>
14:44:45
Maybe some examples of terms/phrases in the dictionary would also be helpful :)
<@rwright:fedora.im>
14:44:51
I'll drop the easiest one:
<@rwright:fedora.im>
14:44:51
<@rwright:fedora.im>
14:44:51
Contributor
<@rwright:fedora.im>
14:45:00
What is a contributor? And the definition of it.
<@jflory7:fedora.im>
14:45:01
lol. The easiest one 😆
<@moralcode:fedora.im>
14:45:11
contribution may be another related one
<@jflory7:fedora.im>
14:45:12
lol. The "easiest" one 😆
<@rwright:fedora.im>
14:45:14
I think Matthew has a good example definition of this.
<@rwright:fedora.im>
14:45:34
Another is "packager" and "package".
<@jflory7:fedora.im>
14:45:34
So, I take it that yes, brainstorming would be helpful here :D
<@jflory7:fedora.im>
14:45:42
A reminder for folks:
<@jflory7:fedora.im>
14:45:42
> "Explain that this resource is intended to unify and clarify terminology and data used across Fedora"
<@jflory7:fedora.im>
14:45:42
<@roseline:matrix.org>
14:45:52
For a more interactive experience, we can explore ways to make the speakers engage with the audience during their presentations. At the party, the speakers were only able to interact with the audience after their session.
<@moralcode:fedora.im>
14:46:26
im stealing this from a meeting last week, but clarifying what is AI, or types/uses/a taxonomy of AI systejs may be helpful when doign data and metrics around
<@moralcode:fedora.im>
14:46:32
im stealing this from a meeting last week, but clarifying what is AI, or types/uses/a taxonomy of AI systejs may be helpful when doign data and metrics around AI in the community
<@jflory7:fedora.im>
14:46:43
!info What are common terms we would like to see defined in a common way in Fedora? What are terms that people use, and may mean different things to different people? Can we come up with single definitions?
<@tosin_doreen:matrix.org>
14:47:05
Ah yes. Please lets.
<@tosin_doreen:matrix.org>
14:47:05
After all the meetings I will get to my Blog post task, then come to collect insight for the report task then I can commence tackling them tomorrow
<@jflory7:fedora.im>
14:47:11
Adrian Edwards: I think that is a good idea, but it might be out of scope for what we want to make for this data dictionary.
<@jflory7:fedora.im>
14:47:32
Things like "contributor", "contribution", "packager", "package", etc. are the kinds of examples here
<@jflory7:fedora.im>
14:47:40
But I feel like those terms are actually some of the hardest
<@jflory7:fedora.im>
14:47:53
I wonder if there are some easier ones we could brainstorm in our final 13 minutes together
<@rwright:fedora.im>
14:47:56
"bug" vs "issue" - is there a difference or si this the same term
<@rwright:fedora.im>
14:47:56
another could be:
<@tosin_doreen:matrix.org>
14:48:14
Ah yes. Please let us do that Justin W. Flory (he/him)
<@tosin_doreen:matrix.org>
14:48:14
After all the meetings I will get to my Blog post task, then come to collect insight for the report task then I can commence tackling them tomorrow
<@jflory7:fedora.im>
14:48:49
Adrian Edwards, tosin_doreen, Roseline Bassey: While you have gotten started in Fedora, are there words or phrases you have seen Fedora people use that were confusing? Or were used in different ways by different people?
<@moralcode:fedora.im>
14:49:17
community vs SIG vs wirking group (i.e. all the different types, levels, and scopes of groups involved)
<@jflory7:fedora.im>
14:49:22
Jona Azizaj (she/her): I am also thinking about non-engineering sort of contributions too. Have we ever tried to define "mindshare" or "DEI" contributions before? Should we?
<@rwright:fedora.im>
14:49:28
That's a good on Adrian Edwards
<@tosin_doreen:matrix.org>
14:49:30
Garanfa? Or Grafana? Which one is it now. But you already explained it
<@rwright:fedora.im>
14:49:39
That's a good one Adrian Edwards
<@jflory7:fedora.im>
14:50:03
!idea Does "bug" and "issue" mean the same thing in Fedora, or are they different?
<@moralcode:fedora.im>
14:50:10
idk ifany of it is neceserily confusing, im just approaching this from a data definitions standpoint (like each column in a table needs a clear definition of what it is/what it means to avoid edge cases and assumptions when building code against it)
<@moralcode:fedora.im>
14:50:21
NYC has a good example of this for their taxi datasets
<@moralcode:fedora.im>
14:50:23
lemme get a link
<@jflory7:fedora.im>
14:50:36
!idea Does Special Interest Group (SIG) and Working Group (WG) mean the same thing in Fedora, or are they different? (Different types, levels, and scopes of groups involved)
<@roseline:matrix.org>
14:50:44
EPEL
<@jonatoni:fedora.im>
14:50:50
we have tried 😅 with ambassadors, but it's a bit hard
<@jflory7:fedora.im>
14:50:59
!idea Grafana. How is Grafana used in Fedora and what is it used for?
<@moralcode:fedora.im>
14:51:25
https://www.nyc.gov/site/tlc/about/tlc-trip-record-data.page this page, under "data dictionaries and metadata" theres some PDFs explaining each column of the aparquet data
<@moralcode:fedora.im>
14:51:28
that could be a good model
<@jflory7:fedora.im>
14:51:28
!idea EPEL. What is EPEL, what is an EPEL contribution, who is an EPEL contributor?
<@jflory7:fedora.im>
14:51:43
!link https://www.nyc.gov/site/tlc/about/tlc-trip-record-data.page
<@moralcode:fedora.im>
14:51:50
also what is (and where can i find/see) the fedora message bus
<@roseline:matrix.org>
14:51:58
"Atomic desktops" was kinda confusing
<@jflory7:fedora.im>
14:52:03
I think meetings will be less overwhelming when Meet Bot does not double-post things as much 😅
<@tosin_doreen:matrix.org>
14:52:16
Strongly agree
<@moralcode:fedora.im>
14:52:32
ill include that in my issue when they enable issues on that repo
<@jflory7:fedora.im>
14:53:01
!idea Fedora message bus. What happens on the bus? What is tracked there? What is NOT tracked there?
<@jflory7:fedora.im>
14:53:34
!idea Atomic Desktops. What is an Atomic Desktop? Can anything with rpm-ostree be an Atomic Desktop, or is there a threshold to meet for a desktop to be considered an Atomic Desktop?
<@jflory7:fedora.im>
14:53:59
Adrian Edwards: Thanks for helping out with the bug report on Meetbot :)
<@jflory7:fedora.im>
14:54:17
This was a very recent change it seems, to support multi-line messages. But it is very verbose, so hopefully the devs will consider that feedback
<@jflory7:fedora.im>
14:54:26
OK! The pace of typing is slowing down a bit.
<@jflory7:fedora.im>
14:54:31
I think this is a good list.
<@jflory7:fedora.im>
14:54:39
We didn't end up with many definitions though 😂
<@jflory7:fedora.im>
14:54:41
Just more questions!
<@jflory7:fedora.im>
14:54:44
But the questions are good.
<@jflory7:fedora.im>
14:54:52
And this is what a data dictionary should try to address.
<@jflory7:fedora.im>
14:54:59
Robert Wright (he/him): Anything else you want to cover here?
<@jflory7:fedora.im>
14:55:02
Time check: 5 minutes
<@rwright:fedora.im>
14:55:14
Nope - other than this is a good first issue for someone to take on and start to gether info around :)
<@jflory7:fedora.im>
14:56:01
!halp We could use YOUR help to start building this data dictionary on the Fedora Wiki. If you are interested, comment on the GitLab issue and work through the step-by-step guide.
<@jflory7:fedora.im>
14:56:04
https://gitlab.com/fedora/commops/home/-/issues/25
<@jflory7:fedora.im>
14:56:26
I don't think we have enough time left to get through #28.
<@jflory7:fedora.im>
14:56:39
But this meeting has been super interactive, which is nice
<@jflory7:fedora.im>
14:56:52
I would be fine to switch to Open Floor from here and then wrap up :)
<@jflory7:fedora.im>
14:57:02
!topic Open floor
<@jflory7:fedora.im>
14:57:12
OK! We are nearly at the end of our time together.
<@jflory7:fedora.im>
14:57:21
Thanks everyone for the engagement and participation! This has been great!
<@jflory7:fedora.im>
14:57:29
Does anyone have any questions? Comments? Suggestions?
<@rwright:fedora.im>
14:57:31
thank you thank you everyone! :)
<@jflory7:fedora.im>
14:57:37
Anything that can fit in our last three minutes 😁
<@moralcode:fedora.im>
14:57:52
no problem! glad i could contribute!
<@moralcode:fedora.im>
14:57:52
<@moralcode:fedora.im>
14:57:52
in general im just interested in col data/programming/automation tasks like the various bot things
<@moralcode:fedora.im>
14:58:06
so im super down to just hack on stuff to make it better
<@tosin_doreen:matrix.org>
14:58:15
Send snacks🫠
<@jflory7:fedora.im>
14:58:36
This is a good reminder for the hack sessions :)
<@jflory7:fedora.im>
14:58:47
!action @jflory7 @rwright Schedule CommOps hack sessions in the not so distant future
<@moralcode:fedora.im>
14:59:14
glad i can be useful even when i didnt intend to be haha
<@jflory7:fedora.im>
14:59:17
In Fedora, we have a longstanding tradition of swapping candies 🍬 🍭
<@jflory7:fedora.im>
14:59:34
Need to find a good way of doing that virtually and not only at our events :)
<@jflory7:fedora.im>
15:00:16
Alright. We are at the end of the hour.
<@jflory7:fedora.im>
15:00:24
Thanks everyone for your engagement and enthusiasm today!
<@zodbot:fedora.im>
15:00:30
jonatoni has already given cookies to jflory7 during the F40 timeframe
<@jflory7:fedora.im>
15:00:31
Keep an eye on the GitLab issues for post-meeting follow-ups.
<@jflory7:fedora.im>
15:00:42
Until next time! Catch ya around in the Fedora-verse! 🏄️
<@jflory7:fedora.im>
15:00:44
!endmeeting