<@jflory7:fedora.im>
14:01:13
!startmeeting Fedora Community Ops Team - 2024-09-17
<@meetbot:fedora.im>
14:01:15
Meeting started at 2024-09-17 14:01:13 UTC
<@meetbot:fedora.im>
14:01:15
The Meeting name is 'Fedora Community Ops Team - 2024-09-17'
<@jflory7:fedora.im>
14:01:17
!meetingname commops
<@meetbot:fedora.im>
14:01:20
The Meeting Name is now commops
<@jflory7:fedora.im>
14:01:21
!topic Agenda
<@jflory7:fedora.im>
14:01:34
!info (1) Intros, welcomes, hellos
<@jflory7:fedora.im>
14:01:38
!info (2) Team announcements & news
<@jflory7:fedora.im>
14:01:41
!info (3) Initiative Co-Lead updates to the team
<@jflory7:fedora.im>
14:01:43
!info (4) Follow-ups from last meeting
<@jflory7:fedora.im>
14:01:47
!info (5) Ticket-driven discussion
<@jflory7:fedora.im>
14:01:50
!info (6) Open floor
<@jflory7:fedora.im>
14:01:55
!topic Intros, welcomes, hellos
<@jflory7:fedora.im>
14:02:06
If this is your first time at a CommOps 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:02:07
!hi
<@zodbot:fedora.im>
14:02:08
Justin W. Flory (jflory7) - he / him / his
<@gwmngilfen:ansible.im>
14:02:15
!hi
<@zodbot:fedora.im>
14:02:16
Greg Sutcliffe (gwmngilfen) - he / him / his
<@shaunm:matrix.org>
14:02:23
!hi
<@zodbot:fedora.im>
14:02:24
Shaun McCance (shaunm) - he / him / his
<@jflory7:fedora.im>
14:02:37
Good morning, good afternoon, good time of day!
<@jflory7:fedora.im>
14:02:42
How are folks doing today? :)
<@jflory7:fedora.im>
14:02:53
It is a very wet, rainy day here. ๐ŸŒง๏ธ
<@gwmngilfen:ansible.im>
14:02:59
after a rubbish summer, it is finally sunny here ๐Ÿ™‚
<@nhanlon:beeper.com>
14:03:13
!hi
<@zodbot:fedora.im>
14:03:15
Neil Hanlon (neil) - he / him / his
<@jflory7:fedora.im>
14:03:15
Sunny? In the UK? ๐Ÿ˜
<@gwmngilfen:ansible.im>
14:03:28
pfft
<@jflory7:fedora.im>
14:03:31
Howdy Neil Hanlon ๐Ÿ‘‹
<@jflory7:fedora.im>
14:04:30
We will give it another minute or so for folks to arrive :)
<@jflory7:fedora.im>
14:05:03
Also, happy release day! ๐ŸŽ‰
<@gwmngilfen:ansible.im>
14:05:09
oh, i hadnt spotted you were using Beeper Neil, how's that looking these days?
<@gwmngilfen:ansible.im>
14:05:13
Happy release!
<@jflory7:fedora.im>
14:05:15
(Beta, that is.)
<@nhanlon:beeper.com>
14:05:23
mornin' folks. sorry, getting started here with a RHEL bug I filed that wasn't actually a RHEL bug and now I am scraping the egg off my face ;)
<@jflory7:fedora.im>
14:05:39
All good and fine :D
<@gwmngilfen:ansible.im>
14:06:03
i dislike eggs *on my face*
<@jflory7:fedora.im>
14:06:08
๐Ÿณ
<@gwmngilfen:ansible.im>
14:06:09
i prefer them *in* my face
<@jflory7:fedora.im>
14:06:15
I think we have quorum :)
<@jflory7:fedora.im>
14:06:48
!info Present: @jflory7 @gwmngilfen @shaunm @neil
<@jflory7:fedora.im>
14:07:00
I know Robert said he is out for today due to a conflict. Plus it is silly early for him.
<@nancywrites:matrix.org>
14:07:03
present
<@jflory7:fedora.im>
14:07:13
Hey nancywrites! ๐Ÿ‘‹ Welcome welcome :)
<@jflory7:fedora.im>
14:07:28
If your Matrix ID is linked to your FAS account, you can type `!hi` and the bot will introduce you :)
<@nancywrites:matrix.org>
14:07:42
!hi
<@zodbot:fedora.im>
14:07:44
Nancy Nwankwo (nancywrites) - she / her / hers
<@jflory7:fedora.im>
14:07:50
Nice ๐Ÿ™Œ
<@jflory7:fedora.im>
14:07:56
!info +Present: @nancywrites
<@jflory7:fedora.im>
14:08:07
With thatโ€ฆ let's get started!
<@jflory7:fedora.im>
14:08:08
!topic Team announcements & news
<@jflory7:fedora.im>
14:08:19
Any exciting and interesting things happening around in Fedora?
<@jflory7:fedora.im>
14:08:24
I think I have a few, actually :)
<@jflory7:fedora.im>
14:08:59
!info === "Announcing Fedora Linux 41 Beta" ===
<@jflory7:fedora.im>
14:09:03
<@jflory7:fedora.im>
14:09:08
This is today! ๐Ÿ™Œ
<@gwmngilfen:ansible.im>
14:09:19
Woop
<@jflory7:fedora.im>
14:09:21
!info === "Communishift namespace creation - commops-analytics" ===
<@jflory7:fedora.im>
14:09:26
<@jflory7:fedora.im>
14:10:02
!info Fedora Infra has created a new Communishift environment for some of the sandbox projects we want to work on with analytics work. For now, @jflory7 and @rwright have administrator access and can share access via membership in a new FAS group.
<@gwmngilfen:ansible.im>
14:10:25
oooh, me me
<@gwmngilfen:ansible.im>
14:10:30
I want access ๐Ÿ˜‰
<@jflory7:fedora.im>
14:10:40
<@gwmngilfen:ansible.im>
14:11:03
I *may* have been badgering Matthew about this last week, so I'm keen. I was *trying* to get datagrepper to work, I was so keen ๐Ÿ˜‰
<@jflory7:fedora.im>
14:11:06
Gwmngilfen: ๐Ÿช„
<@jflory7:fedora.im>
14:11:31
There are some other related CommOps tickets in the Infra queue, but they are as of yet, unactioned.
<@jflory7:fedora.im>
14:11:36
But slow and steady progress :)
<@jflory7:fedora.im>
14:11:59
I think these are all the news and announcements I have for nowโ€ฆ
<@gwmngilfen:ansible.im>
14:11:59
ok, cool. so how does this relate to the plans around synthetic data, bus extracts, etc?
<@jflory7:fedora.im>
14:12:06
There is probably moreโ€ฆ
<@jflory7:fedora.im>
14:12:48
Gwmngilfen: As I understand, there was a discussion at Flock about replicating parts of the fedora-messaging DB into a separate database that is meant as a sandbox for safe experimentation, without hitting the main messaging-bus DB itself
<@jflory7:fedora.im>
14:13:22
Robert Wright (he/him) is better able to talk about that than me, or perhaps another member of Fedora Infra. I know Steve and nirik were in the room for this topic, but I have been catching up still and have not gotten the full update.
<@gwmngilfen:ansible.im>
14:13:58
right ok. you told me about that a few meetings back, but I've heard nothing more and didn't know who to poke - I'll follow up with Steve and Nirik
<@jflory7:fedora.im>
14:14:04
Oh, I do have one more announcement.
<@jflory7:fedora.im>
14:14:09
Sounds good Gwmngilfen!
<@jflory7:fedora.im>
14:14:12
!info === "Fedora Mentored Projects โ€“ Council Hackfest" ===
<@jflory7:fedora.im>
14:14:16
<@jflory7:fedora.im>
14:14:40
!info This overview post goes over the Mentored Projects Initiative, progress made to date, and what the closing steps are for the initiative this year.
<@jflory7:fedora.im>
14:14:48
Okay, that is all from me :)
<@jflory7:fedora.im>
14:14:51
<eof>
<@jflory7:fedora.im>
14:14:57
Any other news or announcements?
<@jflory7:fedora.im>
14:15:02
๐Ÿ‘‚๏ธ
<@jflory7:fedora.im>
14:15:25
Going onceโ€ฆ
<@jflory7:fedora.im>
14:15:35
Going twiceโ€ฆ
<@jflory7:fedora.im>
14:15:50
Going thriceโ€ฆ
<@jflory7:fedora.im>
14:16:00
๐Ÿ’ฅ
<@jflory7:fedora.im>
14:16:16
!topic Initiative Co-Lead updates to the team
<@jflory7:fedora.im>
14:16:24
A quick one, and then moving on to tickets.
<@jflory7:fedora.im>
14:17:02
!info @rwright and @jflory7 are beginning to discuss the path forward for concluding the Initiative and mapping out team goals that go beyond the Initiative, ultimately transitioning this from an Initiative-driven effort to a full community team. More to come on this soon.
<@jflory7:fedora.im>
14:17:12
!topic Ticket-driven discussion
<@jflory7:fedora.im>
14:17:46
(Please hold, GitLab re-authingโ€ฆ)
<@jflory7:fedora.im>
14:18:46
<@jflory7:fedora.im>
14:19:06
I am a bad meeting chair. I did not properly triage the tickets like I wanted. And there were actually two tickets I wanted to open before this meeting, but did not.
<@jflory7:fedora.im>
14:19:14
However, I have some ideas to improvise though.
<@gwmngilfen:ansible.im>
14:19:37
hmm that link has no tickets in it for me
<@jflory7:fedora.im>
14:19:52
Gwmngilfen: Exactly, shame on me ๐Ÿ˜
<@jflory7:fedora.im>
14:19:54
I received a request for support for helping the Pantheon SIG onboard as a new community SIG.
<@gwmngilfen:ansible.im>
14:19:57
ah, ok ๐Ÿ˜‰
<@jflory7:fedora.im>
14:20:10
Are any of you familiar with Pantheon?
<@gwmngilfen:ansible.im>
14:20:12
๐Ÿ‘€ what is Pantehon?
<@gwmngilfen:ansible.im>
14:20:17
๐Ÿ‘€ what is Pantheon?
<@jflory7:fedora.im>
14:20:38
It is the desktop environment that elementaryOS ships on their OS, and Fabio Valentini is doing a heroic work of packaging it up.
<@jflory7:fedora.im>
14:20:48
But as I understand, it is a slow journey and a lot of work.
<@gwmngilfen:ansible.im>
14:20:53
ah
<@jflory7:fedora.im>
14:21:02
Joseph Gayoso flagged it to me as an area that he thought CommOps could possibly mentor and support.
<@jflory7:fedora.im>
14:21:31
I thought this could be a good exercise for us to draft a new document: "How to create a Fedora SIG or Working Group"
<@jflory7:fedora.im>
14:21:40
We could edit it at first as a Google Doc
<@jflory7:fedora.im>
14:21:46
And then move into docs.fp.o once we are happy with it.
<@jflory7:fedora.im>
14:22:12
It is not the targeted, focus work on the Pantheon SIG, but I think starting a doc like this would make it easier to have more conversations like this.
<@jflory7:fedora.im>
14:22:15
This was my thinking!
<@jflory7:fedora.im>
14:22:23
I wanted to write it down into a ticket, butโ€ฆ urgh. :)
<@jflory7:fedora.im>
14:22:30
I am almost finished with Flock follow-ups. Almost.
<@jflory7:fedora.im>
14:23:18
Maybe one way we could make this interactive is if we brainstormed a laundry list of items for how to (or how not to) run a Fedora SIG/WG :)
<@jflory7:fedora.im>
14:23:39
!topic Pending ticket: Support request for Pantheon SIG onboarding and launching new teams in Fedora
<@jflory7:fedora.im>
14:23:51
I am curious. We have folks who are both veterans of Fedora, and also folks are relatively new.
<@jflory7:fedora.im>
14:24:00
This is a nice, mixed perspective on Fedora contributing :)
<@jflory7:fedora.im>
14:24:07
Soโ€ฆ I am curious to ask you all.
<@jflory7:fedora.im>
14:24:14
What makes for a good team onboarding experience?
<@jflory7:fedora.im>
14:24:37
If you are a new contributor, what are things you look for when getting started? What resources are you looking out for? What do you need to feel more confident about getting started?
<@nhanlon:beeper.com>
14:24:43
snacks
<@jflory7:fedora.im>
14:25:01
If you are a long-time contributor, what are the pain points? What are the horrible things you have seen? What are the best, most memorable things you have seen?
<@jflory7:fedora.im>
14:25:14
Don't be shy :)
<@gwmngilfen:ansible.im>
14:25:28
hmm, that's interesting. I think the word "expectations" jumps out to me
<@jflory7:fedora.im>
14:25:29
Neil Hanlon: Honestly, same.
<@jflory7:fedora.im>
14:25:40
Gwmngilfen: How so?
<@gwmngilfen:ansible.im>
14:26:04
whether thats docs, or meetings, or whatever, knowing what to expect (of myself, of those around me, etc) is key to feeling like I'm being useful
<@jflory7:fedora.im>
14:26:32
!info Open brainstorm by the team on what makes for a good or bad onboarding experience into a new team in Fedora (or for that matter, any other open source community you have participated in).
<@jflory7:fedora.im>
14:27:13
!idea Clear expectations. Knowing what is expected by myself and those around me. Docs? Meetings? Issue trackers? This is key to feeling like I am being useful.
<@gwmngilfen:ansible.im>
14:27:27
perhaps "clarity" is more what I'm looking for. the msgbus data is a great example, I've been wwaiting since beofre Flock to make progress on it, yet I don't know how to progress it (well, until today anyway). if that happens elsewhere too (i.e it's not just us) then we should think about that more
<@jflory7:fedora.im>
14:27:31
Yaash: Hey there, I saw you typing earlier :) Feel free to drop a `!hi` in the chat if you want to join in!
<@nhanlon:beeper.com>
14:27:42
real answer: I think an important thing is doing *something* all the way through, so that the person can see the payoff for their effort. That helps to build confidence and, as Greg said, feel I'm being helpful.
<@gwmngilfen:ansible.im>
14:27:55
๐Ÿ’ฏ
<@thisisyaash:fedora.im>
14:28:04
!hi
<@zodbot:fedora.im>
14:28:05
Yashwanth Rathakrishnan (thisisyaash)
<@gwmngilfen:ansible.im>
14:28:35
one sec, let me break out the book I was using to write my DevConf talk on building community ... it has a whole chapter on encouraging newcomers ๐Ÿ˜›
<@jflory7:fedora.im>
14:28:42
!idea Clarity. Knowing where to get help when I get stuck. Who do I talk to? Where do I get guidance? Does this happen elsewhere or only for us?
<@jflory7:fedora.im>
14:29:08
!idea Going start to finish. Contributing to something from the beginning to the end, so you see the payoff for the effort. This builds confidence and makes me feel like I am being helpful.
<@jflory7:fedora.im>
14:29:16
Welcome welcome Yaash! ๐Ÿ‘‹
<@jflory7:fedora.im>
14:29:30
These are good ideas :)
<@thisisyaash:fedora.im>
14:29:59
I'm not sure if supposed to talk in the meeting, so I stopped typing that's why!
<@thisisyaash:fedora.im>
14:29:59
As I have been contributing for few weeks , can I point out my opinion about **new contributor** experience?
<@thisisyaash:fedora.im>
14:29:59
<@gwmngilfen:ansible.im>
14:30:07
Justin W. Flory (he/him): are we looking for "what do newcomers need" or "what to new SIGs need to help *their* newcomers"?
<@gwmngilfen:ansible.im>
14:30:15
Justin W. Flory (he/him): are we looking for "what do newcomers need" or "what do new SIGs need to help _their_ newcomers"?
<@jflory7:fedora.im>
14:30:22
I am curious for feedback from folks who are earlier on in their Fedora or open source journeys, and may have ran into successes or bumps in Fedora along the way. Yaash and nancywrites, feel free to share your thoughts and ideas here too on what would make it easier for you to contribute to a new team in Fedora or elsewhere in the open source world.
<@gwmngilfen:ansible.im>
14:30:25
Yaash: please!
<@jflory7:fedora.im>
14:30:33
Yaash: Absolutely! You can speak up any time during our meetings :D
<@jflory7:fedora.im>
14:30:37
And please do share ๐Ÿ™Œ
<@jflory7:fedora.im>
14:31:04
!info +Present: @thisisyaash
<@jflory7:fedora.im>
14:31:22
I will also think of my own ideas for a minute tooโ€ฆ
<@gwmngilfen:ansible.im>
14:32:17
๐Ÿ‘†๏ธthese have different answers in my head, fwiw, so I'm curious which one we're answering ๐Ÿ˜‰
<@jflory7:fedora.im>
14:32:28
!idea Timeline. Knowing when something needs to be started and when something needs to be finished. We all have different things going on in our lives and we all contribute to Fedora in different capacities. Knowing the timeline for a task or project helps me make the responsible decision about my time commitments and making sure I can meet deadlines.
<@jflory7:fedora.im>
14:32:47
Gwmngilfen: Both, although for experienced contributors, I think the second question is more interesting. For new contributors, the first question is better.
<@gwmngilfen:ansible.im>
14:33:43
i'm trying to think in the context of the Pantheon discussion. if our remit is not "help do Pantheon work" but rather "help them set up a SIG and document the process" then the latter is important
<@jflory7:fedora.im>
14:34:11
Our remit is not to do the Pantheon work, but the second: help them set up a SIG and document the process.
<@jflory7:fedora.im>
14:35:06
!idea Good First Issues. Clear, easily-triaged tasks for newcomers to take on. For newcomers, this is something that is bite-sized, clearly-defined, and there are resources for getting help. For maintainers, this is keeping an eye on tasks in the issue tracker, triaging beginner-friendly tasks accordingly, and prioritizing the creation of beginner-friendly tasks when there are none or few available.
<@jflory7:fedora.im>
14:35:49
Any other Fedora SIGs/WGs or open source life lessons to share? :)
<@gwmngilfen:ansible.im>
14:35:56
for the SIG organisers then - know your audience. what motivates them? why would they join your SIG? make sure they can achieve that (eg with the first-issues as above)
<@jflory7:fedora.im>
14:37:04
!idea Maintainers: Know your audience and their motivations. Why would they want to join your SIG? Make sure they can achieve those things.
<@jflory7:fedora.im>
14:37:08
Good one!
<@thisisyaash:fedora.im>
14:39:20
At first I'll share my on-boarding experience, the doc feel bit tedious at first, especially when i'm new. The **shift from pagure to gitlab** made me think about where to contribute and how things are organized. basically i have no idea where to start or whom to ask!
<@thisisyaash:fedora.im>
14:39:20
<@thisisyaash:fedora.im>
14:39:20
sry: i can't type fast :|
<@thisisyaash:fedora.im>
14:39:20
<@thisisyaash:fedora.im>
14:39:20
Other thing is we still use repo in pagure, that tracks the new contributors, it's helpful but the transition from pagure to gitllab is bit confusing. Over time i got used to it and things became smoother.
<@jflory7:fedora.im>
14:39:56
No need to apologize :)
<@jflory7:fedora.im>
14:40:01
Good feedback too!
<@gwmngilfen:ansible.im>
14:40:04
i type too fast, you can balance me out ๐Ÿ˜‰
<@jflory7:fedora.im>
14:40:44
!idea Clear entrypoints. It is confusing today about the various git forges where we work. Pagure? GitLab? It is hard to know where to start or whom to ask for help.
<@gwmngilfen:ansible.im>
14:41:14
Yes! that's really important, and something we've been working on in Ansible-land
<@gwmngilfen:ansible.im>
14:41:31
we're very close to a blanket recommendation that everything starts in the forum ๐Ÿ˜‰
<@thisisyaash:fedora.im>
14:41:35
What I basically think is that having a streamlined environment for new contributors might be useful, since switching between many tabs can be confusing for someone new.
<@jflory7:fedora.im>
14:41:39
shaunm: Any famous pinch points that you have seen in contributing to Fedora or CentOS? Is there one thing you would advise someone to do or not to do when starting a new community SIG?
<@jflory7:fedora.im>
14:41:57
#DefaultToOpen ๐Ÿ˜„
<@jflory7:fedora.im>
14:42:25
Yaash: What does streamlined look like to you here?
<@jflory7:fedora.im>
14:43:21
nancywrites: As someone who contributed a lot during the Mentored Projects round, your feedback is also welcome too! If you are just thinking, that's okay too :)
<@shaunm:matrix.org>
14:43:23
In CentOS, we've seen quite a few cases where SIGs were started because people thought they needed one to do anything, then they didn't pan out.
<@jflory7:fedora.im>
14:44:19
That's a good one.
<@gwmngilfen:ansible.im>
14:44:42
I forsee a "Do I need a SIG?" heading coming, and it's a good one
<@jflory7:fedora.im>
14:45:27
!idea Maintainers: Do you need to start a SIG to do something meaningful? Or are there other channels to lean into before trying to start something new? Explore around more before starting something new.
<@nhanlon:beeper.com>
14:45:33
Right, and.. "is there a SIG already that fits the needs" is a good first question
<@gwmngilfen:ansible.im>
14:45:42
ooh, yes, that too
<@nhanlon:beeper.com>
14:45:53
more SIGs is not necessarily more better
<@jflory7:fedora.im>
14:45:59
!idea Is there a SIG already that fits this need?
<@jflory7:fedora.im>
14:46:04
For sure.
<@jflory7:fedora.im>
14:46:24
Let's give it four more minutes, and then I'd like to look at open MRs on the repo, for our final ten minutes together.
<@nhanlon:beeper.com>
14:46:32
CentOS has good examples of this, even -- with the ISA SIG being spun out of the Hyperscale one.. incubated, almost
<@jflory7:fedora.im>
14:49:05
OK. Well, the feedback and furious typing is slowing down :)
<@jflory7:fedora.im>
14:49:08
This was a good brainstorm.
<@jflory7:fedora.im>
14:49:15
I'm going to use this as the basis for the new ticket.
<@jflory7:fedora.im>
14:49:41
I'd like to kick off a Google Doc with some of these ideas, and then in our next video meeting, we could edit it together into something more comprehensive.
<@jflory7:fedora.im>
14:50:06
!action @jflory7 Open a new CommOps issue for SIG onboarding support and documentation, use meeting brainstorm as a starting point
<@jflory7:fedora.im>
14:50:41
We can keep this conversation going in the team chat, but I am going to transition this to the end of our meeting!
<@jflory7:fedora.im>
14:50:53
!topic Open floor
<@thisisyaash:fedora.im>
14:50:57
Also when i started going through fedora for contributors, I stumbled upon few 404 pages, I wasn't even sure where to contribute or if there was specfic team.
<@thisisyaash:fedora.im>
14:50:57
finding this page took me few hours of searching
<@thisisyaash:fedora.im>
14:50:57
<@thisisyaash:fedora.im>
14:50:57
https://whatcanidoforfedora.org/en/#designexclamation
<@thisisyaash:fedora.im>
14:50:57
Honestly, I wasn;t entirely sure at that point. But eventually I landed on this page which showed me the team
<@thisisyaash:fedora.im>
14:50:57
well i'm not entirely sure, since I'm still new, so I don't think I can clearly point out specifics yet๐Ÿ˜ถ.
<@thisisyaash:fedora.im>
14:50:57
But I feel like having everything in one place would be help make the onboarding process smoother.
<@thisisyaash:fedora.im>
14:50:57
<@jflory7:fedora.im>
14:51:04
OK. Open floor. This is for all other business and topics.
<@jflory7:fedora.im>
14:51:45
Yaash: Great feedback here too.
<@jflory7:fedora.im>
14:51:53
I think more organized onboarding path would help a lot
<@jflory7:fedora.im>
14:52:04
Instead of six different places to look for information ๐Ÿคช
<@thisisyaash:fedora.im>
14:52:29
thanks for waiting to hear my opinion!
<@gwmngilfen:ansible.im>
14:52:57
!info https://support.mozilla.org/en-US/contribute is decent
<@gwmngilfen:ansible.im>
14:53:04
pfft, not a mod ๐Ÿ˜‰
<@gwmngilfen:ansible.im>
14:53:08
oh, just slow
<@jflory7:fedora.im>
14:53:16
I had one open floor topicโ€ฆ
<@jflory7:fedora.im>
14:53:18
<@jflory7:fedora.im>
14:53:28
There areโ€ฆ quite a few MRs here :)
<@jflory7:fedora.im>
14:53:34
And I could really use some help to review them.
<@jflory7:fedora.im>
14:53:43
Most of them are docs-related.
<@jflory7:fedora.im>
14:54:00
One of them is some scripts for the video editing pipeline. Mostly Python.
<@jflory7:fedora.im>
14:54:18
Would anyone be up for taking on some MR review?
<@jflory7:fedora.im>
14:54:31
Here are two great ones:
<@jflory7:fedora.im>
14:54:32
<@jflory7:fedora.im>
14:54:37
<@jflory7:fedora.im>
14:55:16
I can help close out !17 and !18, but I could use the coverage on !20 and !21 :)
<@gwmngilfen:ansible.im>
14:55:21
i'm going to say no to reviews, but only because I'm about to start looking at the survey data ๐Ÿ˜‰
<@jflory7:fedora.im>
14:55:30
Gwmngilfen: Granted, that is fair.
<@nhanlon:beeper.com>
14:56:20
I... will help.
<@nhanlon:beeper.com>
14:56:56
!info Neil will take #20 and #21
<@jflory7:fedora.im>
14:57:00
Neil Hanlon: <3
<@nhanlon:beeper.com>
14:57:08
zodbot no like me RIP
<@jflory7:fedora.im>
14:57:08
Are you feeling like docs or Python? ๐Ÿ
<@jflory7:fedora.im>
14:57:14
Oh, awesome <3
<@jflory7:fedora.im>
14:57:24
Thank you Neil Hanlon! ๐Ÿ™Œ
<@jflory7:fedora.im>
14:57:39
Yaash: Keep an eye out for feedback on those MRs. We will get them merged and rolled out ๐Ÿ’ช
<@jflory7:fedora.im>
14:57:59
Thanks for being patient all this time. The timing with the Flock to Fedora conference did slow down some momentum, but we are picking back up :)
<@jflory7:fedora.im>
14:58:05
Neil Hanlon++
<@zodbot:fedora.im>
14:58:06
jflory7 has already given cookies to neil during the F40 timeframe
<@thisisyaash:fedora.im>
14:58:08
yeah sure ๐Ÿ™Œ๐Ÿผ!
<@jflory7:fedora.im>
14:58:22
Of course I have already ๐Ÿ˜
<@nhanlon:beeper.com>
14:58:40
next quarter we gotta work on the cookie supply...
<@jflory7:fedora.im>
14:58:47
!action @neil Review CommOps MRs !20 (@moralcode) and !21 (@thisisyaash)
<@jflory7:fedora.im>
14:59:01
!action @jflory7 Close our CommOps MR review on !17 and !18
<@jflory7:fedora.im>
14:59:19
Neil Hanlon: ๐Ÿช ๐Ÿช
<@jflory7:fedora.im>
14:59:35
Yaash: We will have to teach you about Fedora karma cookies if you don't know about them already :)
<@jflory7:fedora.im>
14:59:37
With that folksโ€ฆ
<@jflory7:fedora.im>
14:59:42
We are at the end of our hour slot!
<@nhanlon:beeper.com>
14:59:46
actually you gave me an idea...
<@jflory7:fedora.im>
14:59:49
Thank you all for your participation and attention.
<@jflory7:fedora.im>
14:59:59
We can keep the conversation going in #commops:fedoraproject.org :)
<@jflory7:fedora.im>
15:00:07
Have a great rest of your week, folks!
<@nhanlon:beeper.com>
15:00:08
thanks justin!
<@jflory7:fedora.im>
15:00:10
!endmeeting