18:02:47 #startmeeting Ansible Community Meeting 18:02:47 Meeting started Wed Jul 26 18:02:47 2023 UTC. 18:02:47 This meeting is logged and archived in a public location. 18:02:47 The chair is gotmax23. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 18:02:47 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:02:47 The meeting name has been set to 'ansible_community_meeting' 18:03:00 #topic Hello world 18:03:00 o/ 18:03:01 .hi 18:03:02 gotmax23: gotmax23 'Maxwell G' 18:03:17 o/ 18:03:17 Hello hello 18:03:27 Landrash[m], acozine, andersson007_, anwesha, ascherbaum, baptistemm, bcoca, briantist, cidrblock, cyberpear, cybette, dericcrago, dmsimard, felixfontein, geerlingguy, gotmax, gundalow, gwmngilfen, ikhan_, jillr, jtanner, lmodemal, mariolenz[m], markuman, maxamillion, misc, nitzmahone, ompragash, oranod, resmo, russoz, samccann, thaumos, wbentley15[m], zbr: The Ansible community meeting is starting now! 18:03:27 The ping list is stored at https://kutt.it/meeting-people. Feel free to add or remove yourself. 18:03:27 hello 18:03:28 o/ 18:03:31 #chair gotmax 18:03:31 Current chairs: gotmax gotmax23 18:03:45 #chair oranod anwesha[m] samccann cybette_ 18:03:45 Current chairs: anwesha[m] cybette_ gotmax gotmax23 oranod samccann 18:04:23 #info There are multiple votes in progress (https://github.com/ansible-community/community-topics/discussions/categories/votes-in-progress). SC members, please take a look and vote 18:05:14 #info See https://github.com/ansible-community/community-topics/issues/202#issuecomment-1652014661 for an update from Gwmngilfen on the community Discourse forum proposal 18:06:10 #info [antsibull-changelog 0.22.0](https://github.com/ansible-community/antsibull-changelog/blob/0.22.0/CHANGELOG.rst#v0-22-0) has been released. 18:06:10 #info ansible 8.2.0 has been released https://groups.google.com/g/ansible-devel/c/3vegFcBVOO4 18:06:27 (it was released last week but I think it wasn't shared in the meeting) 18:06:46 Cool, thanks 18:06:58 Is there anything in particular folks want to talk about? 18:07:19 I think I'm the only SC member here? 18:08:51 Hi all 18:08:58 yeah it seems kind of quiet. I'm still trying to get back up to speed after pto. seems like there's been a lot of great stuff happening in the documentation repo, which is awesome to see. 18:09:06 hey Leo 18:09:21 #chair Leo[m] 18:09:21 Current chairs: Leo[m] anwesha[m] cybette_ gotmax gotmax23 oranod samccann 18:10:10 Yeah. There's been a lot of solid community involvement even after the switch. I also worked on some triage automation. 18:10:13 I have a random question if no one has anything 18:10:37 Thanks samccann for all your feedback on that automation :) 18:10:53 samccann: Sure, go ahead 18:11:21 Certified collections have their own set of requirements... I'm wondering if there's any benefit with trying to compare with the upstream requirements or not worth mixing streams so to speak? 18:12:02 #topic Certified Collection Requirements and community Collection Requirements 18:12:15 Is that information public? 18:13:06 I'd prefer if the community kept what we had, but if anyone wants to use it as inspiration and propose changes, then sure 18:15:01 @cybette:ansible.im cyb-clock chimes every 15 minutes during the community meeting 18:15:30 I think most of it is probably at least under a RH signin 18:16:19 on the certified stuff. I guess I worry the two worlds will diverge and a certified collection owner who wants to also be in the Ansible package will be caught in the cross-hairs at some point in the future 18:16:35 but yeah, hard to coordinate if the certified stuff is hidden somewhere 18:17:13 Right. 18:17:37 I guess that's something to keep in mind, but not much we can do if the certified requirements aren't public 18:18:09 ok if you think it's worthwhile, I can see if it's documented at some place that only requires a RH login. That way we can at least compare 18:18:31 Cool, thanks 18:19:15 +1 samccann @samccann:ansible.im: and I think most are public. There might be some support related stuff, but otherwise it should be simple guidelines. 18:19:29 #topic Open Floor 18:19:39 cool I'll dig up a link to whatever is public 18:20:34 Does anyone else have something to bring up? 18:21:08 probably safe to call it 18:21:21 btw, I'll be in London with family and then at the last two days of Flock to Fedora next week, so don't expect to see too much of me around :) 18:21:37 I'll actually see you at Flock next week 18:22:12 I hope you all have a great time at flock! 18:22:35 Ahh, now I am sad that I will not be there :( 18:22:44 enjoy flock Don Naro and gotmax23 ! 18:22:54 Don Naro and I are both giving talks about Ansible 18:23:04 your talks are at the same time xD 18:23:08 fun times 18:23:11 yes, they are 18:23:15 and right before lunch 18:23:32 gotmax23: That reminds me, we need to promote those a bit. I will share later! 18:24:04 gotmax23: Take some. Snacks for the ones asking questions 😅 18:24:46 I'm sorry the sessions have those time conflicts. I'd like to attend yours gotmax23 18:24:50 I also would've liked to attend yours :) 18:24:50 Gwmngilfen: will be there too so I'm sure he'll come along. but I'm def looking forward to meeting you in person! 18:25:09 They're all recorded at least. It'll be nice to see you all! 18:25:26 Is the community team having a booth or are you just speaking? 18:25:58 I think it's just me speaking this time 18:26:44 #info oranod and gotmax23 are giving talks (https://flock2023.sched.com/event/1Or6d/ansible-in-fedora-and-epel, https://flock2023.sched.com/event/1PCu2/scaling-the-ansible-community-to-new-heights) at Flock to Fedora. They'll be live streamed and recorded. 18:27:03 Okay, I guess I'll end this now, as we're getting a bit into the weeds :) 18:27:05 yeah we won't have a booth this time, but we should encourage and enable anyone in the community to organize a booth next time! 18:27:15 Thanks everyone! 18:27:23 #endmeeting