18:00:42 #startmeeting Ansible Community Meeting 18:00:42 Meeting started Wed May 10 18:00:42 2023 UTC. 18:00:42 This meeting is logged and archived in a public location. 18:00:42 The chair is felixfontein. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 18:00:42 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:42 The meeting name has been set to 'ansible_community_meeting' 18:00:42 #topic Agenda https://github.com/ansible/community/issues/679 18:00:48 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, oranod, resmo, russoz, samccann, thaumos, wbentley15[m], zbr: The Ansible community meeting is starting 18:00:52 now! 18:00:54 The ping list is stored at https://kutt.it/meeting-people. Feel free to add or remove yourself. 18:00:57 #info Agenda: https://github.com/ansible/community/issues/679 / Topics: https://github.com/ansible-community/community-topics 18:01:00 #topic Updates 18:01:04 o/ 18:01:14 o/ 18:01:17 #chair andersson007___ cybette_ 18:01:17 Current chairs: andersson007___ cybette_ felixfontein 18:01:18 o/ 18:01:21 #chair oranod 18:01:21 Current chairs: andersson007___ cybette_ felixfontein oranod 18:02:11 .hi 18:02:12 gotmax23: gotmax23 'Maxwell G' 18:02:42 * gotmax23 notes that there's been some Matrix <-> IRC bridge issues today 18:02:49 #info There's a antsibull-docs 2.0.0a1 prerelease for testing; please note that the sphinx-init subcommand currently generates an unsatisfyable version range, this should get fixed by a 2.0.0a2 release later today. 18:02:53 #chair gotmax23 18:02:53 Current chairs: andersson007___ cybette_ felixfontein gotmax23 oranod 18:03:00 #info the [PR](https://github.com/ansible/ansible/pull/74901) to ansible-core adding a new nice feature to ansible-galaxy command is still vacant to finish. If you're interested, put a comment in the PR that you're in . 18:03:06 yeah, it might be better to watch from IRC today :) 18:03:33 #info Please take a look at the Proposed Ansible Community Forum layout and add your comments/feedback: https://github.com/ansible-community/community-topics/issues/202#issuecomment-1542420839 18:03:47 now I remember what I wanted to read before the meeting... 18:03:50 * gotmax23 has both Element and The Lounge open 18:05:07 * andersson007___ always uses irc for community meetings 18:05:17 hmm, I see on matrix that maxamillion wrote .hello2, but that doesn't show up here and his nick isn't available on IRC... 18:05:49 maxamillion: you're not visible from IRC right now; the bridge has some problems today 18:06:23 18:05 hmm, I see on matrix that maxamillion wrote .hello2, but that doesn't show up here and his nick isn't available on IRC... 18:06:30 ironically didn't show up on Matrix 18:06:39 yep :) 18:06:53 yeah, there are lags at least sometimes 18:07:08 heard that it's because of overloaded matrix.org servers 18:07:35 permanently overloaded:) 18:07:36 * gotmax23 take a look at community-topics 18:07:43 gwmngilfen-work had some links about that, they are doing some work on the bridge, and something isn't right yet 18:07:43 fun day, github and matrix issues galore 18:07:47 (or something like that) 18:07:51 yeah, that too :) 18:08:00 I have updates regarding #218 and #226 18:08:03 https://www.githubstatus.com/ is more colorful today... 18:08:11 with which do you want to start? 18:08:14 we've reached the point today that the whole internet started lagging 18:08:36 We can start with #226 about the ansible-build-data docs 18:08:48 but if anyone else has something feel free to go ahead first 18:08:49 #topic ansible-build-data release docs 18:08:53 I'm finishing my lunch :) 18:08:54 #link https://github.com/ansible-community/community-topics/issues/226 18:09:02 tada, here it is ;) 18:09:08 sorry, read the lunch message too late ;) 18:09:15 (and I'm not sure there is something else) 18:09:46 So, I've been working on documenting the release process in the ansible-build-data repository 18:09:52 I proposed an outline in https://github.com/ansible-community/ansible-build-data/issues/221#issuecomment-1531996313 18:10:09 anwesha[m] isn't around for today's meeting, pinging her so she can look at the logs later :) 18:10:35 So far, we've merged a PR setting up the doc scaffolding and adding docs for how to handle the  Enforce collection tagging policy as a release blocker #218 issue 18:11:02 I opened https://github.com/ansible-community/ansible-build-data/pull/227 to add docs for the actual release process 18:11:03 It provides a step-by-step guide 18:11:11 anwesha has commented on https://github.com/ansible-community/ansible-build-data/pull/227 that she'll share something by this week 18:11:25 I'm waiting for feedback from anwesha and/or previous release managers who want to chime in 18:11:40 dmsimard[m]: dericcrago: ^ :) 18:11:46 don't worry :) 18:11:56 yeah, I saw :) 18:11:57 * andersson007___ is sure step-by-step guides is always a great thing 18:12:21 * andersson007___ like when a random community person can release using it 18:12:33 * andersson007___ successfully at the first try 18:12:49 maybe also ompragash, deric.crago , dmsimard etc. 18:12:52 18:11 * @andersson007___ is sure step-by-step guides is always a great thing 18:12:52 18:12 * @andersson007___ like when a random community person can release using it 18:12:52 Me too :) 18:12:54 yeah, that random community person just needs a PyPI token ;) 18:13:06 ah I'm too slow (or there's a lag) 18:13:08 👍 18:13:19 there's a decent sized lag :) 18:13:48 felixfontein: yeah, the community person would need a PyPI token or we'd need some sort of GH Action or something that could push it 18:13:53 felixfontein: i hope one day they even don't need tokens 18:14:06 I'd be happy to help with releases in the future 18:14:26 Hi all! 👋 18:14:36 I already do the releases in Fedora 18:14:39 👋 18:14:46 so I could just do them in the same time 18:14:49 #chair Leo[m] 18:14:49 Current chairs: Leo[m] andersson007___ cybette_ felixfontein gotmax23 oranod 18:14:53 * gotmax23 waves to Leo 18:15:00 @cybette:ansible.im cyb-clock chimes every 15 minutes during the community meeting 18:15:24 gotmax23: it sounds great to me, thanks for desire to help 18:15:48 anyways, if anyone has other concrete feedback, feel free to chime in on https://github.com/ansible-community/ansible-build-data/issues/221 18:16:01 andersson007___: thanks :) 18:16:03 I can also help, but I'm also happy if I don't have to do more than reviewing PRs for that ;) 18:16:21 hehe 18:16:38 too much stuff going on at the moment 18:17:05 * andersson007___ feeling the same 18:17:20 yeah... 18:17:39 gotmax23: should we switch to #218? 18:17:49 sure 18:18:00 #topic Enforce collection tagging policy as a release blocker 18:18:04 #link https://github.com/ansible-community/community-topics/issues/218 18:18:26 different topic? 18:18:36 cybette_: yes 18:18:53 As I said, we merged https://github.com/ansible-community/ansible-build-data/commit/950e2d650b5ec0fd748f686e5a9ec2c84c8d227d to document this new policy 18:19:31 Currently, the release playbook just warns about tag validation errors, but they'll become actual errors and block the release starting in 9.0.0a1 18:19:57 If anyone wants me to summarize the discussion we had about this in last meeting, let me know :) 18:20:53 by tag validation errors, I mean collection releases that are available on Galaxy but not tagged in the collections' git repository 18:22:18 :+1: 18:22:38 did we loose Matrix or is my Element client just broken? 18:22:49 i can't read effectively right now but the idea sgtm, happy to see the work going 18:22:54 "anyways, if anyone has other..." <- previous topic sorry! late arrival, gotmax let me know if Is it useful to share a few of the related links to the existing documentation for the collections in the issue. I'm guessing you are pointing towards the "including a collection in ansible community package" for the docs/adding.md right? 18:22:59 I was just about to write that matrix hasn't seen up updates for 7-8 minutes 18:23:21 I think someone forgot to pay off the bridge goblins :) 18:23:30 lol 18:23:34 hehe 18:23:44 I don't see that message by Leo on matrix at all 18:23:52 me neither 18:24:13 hmm... chaos :) 18:24:22 Leo[m]: that proposal is specifically about the changes that need to be made to the ansible-build-data repository 18:24:26 felixfontein: I'm on matrix and I'm seeing your messages, but it has been misbehaving today :D 18:24:37 the lats one I see is "gotmax23 waves to Leo", and nothing since then 18:24:46 Leo[m]: hmm, funny :) 18:24:51 but we can link to the full collection inclusion process in the ansible-build-data doc and vice versa 18:25:00 "to pay bridge goblins" will be the joke of today and tomorrow for me 18:25:07 gotmax: ohh ok, sorry, missed that bit. ty 18:25:12 :) 18:25:15 * gotmax wonders if there's something different between the matrix.org and ansible.im homeserver 18:25:24 Leo[m]: sure, thanks for asking! 18:25:39 I'm using matrix.org as a homeserver right now 18:26:07 yeah the homeserver probably makes a difference. my matrix.org account only sees "gotmax23 waves to Leo" as well 18:26:17 Im using my own but havent seen any burps in the flow 18:26:28 #chair Landrash[m] 18:26:28 Current chairs: Landrash[m] Leo[m] andersson007___ cybette_ felixfontein gotmax23 oranod 18:26:32 matrix.org is probably overloaded 18:26:37 yeah... 18:26:48 ah, now updates are coming on matrix for me... 18:27:15 "the time traveller meeting" ;) 18:27:26 should we move open floor? it seems enough of the messages are falling through anyways. 18:27:59 +1 18:28:21 sounds good to me 18:28:24 #topic Open Floor 18:28:30 with a special trapdoor for messages! ;) 18:28:48 :) 18:29:11 gotmax: I wasn't sure whether your pun was intended, but I liked it ;) 18:29:18 it was :) 18:29:20 hehe 18:29:35 we have been working away on antsibull-core and antsibull-docs v2 18:29:52 antsibull-core 2.0.0 was released a couple days ago 18:30:00 @cybette:ansible.im cyb-clock chimes every 15 minutes during the community meeting 18:30:15 antsibull-docs 2.0.0a1 was released but we need to do a hotfix due to an issue with the sphinx-init command 18:30:42 gotmax: there's a PR already, once it's merged I'll do the 2.0.0a2 release :) 18:30:43 we've announced the releases on the Bullhorn but thought I'd bring it up here :) 18:30:50 https://github.com/ansible-community/antsibull-docs/pull/149 18:30:57 ah, I didn't see that yet 18:30:59 thanks 18:31:09 I created it shortly before the meeting started 18:31:31 and then noticed that GH has some problems since there were some unexpected CI failures without logs ;) 18:31:54 fortunately they just have partial outages, so with the retry functionality everything passed in the end 18:32:02 I think the internet is cursed today 18:32:19 maybe the internet needs a reboot 18:32:28 unplug it and plug it back in? 18:32:42 hehe exactly 18:32:57 shut down all computers in the world 18:33:06 and all switches 18:33:07 etc. 18:33:23 just shut it down and ... notice you don't have a way to restart it remotely :D 18:33:31 chatGPT screams 18:33:34 lol 18:34:33 you can call a person in datacenter to kickstart it 18:35:01 i mean a classical phone if you have 18:35:07 yeah, but to call them you need internet, because everyone uses VoIP nowadays ;) 18:35:45 even classical phones usually only are analog til the next phone switch station, then it's VoIP... 18:36:02 or you can use your bike then if you have 18:36:30 carrier pigeon? 18:36:43 which reminds me I have to replace our last analog phone, or alternatively the analog-VoIP adapter next to it, since Cisco screwed up and the current adapter has a remote command execution vuln... 18:36:49 also, felixfontein I acked your antsibull-docs PR, but made a suggestion to improve the changelog fragment 18:37:07 what fun... 18:37:21 gotmax: thanks, applied! 18:38:06 should we end early or does anyone else have something? 18:38:14 yeah, and I also just read that the Linux kernel has a privilege escalation problem, local users can get root rights, with a reproducer available now, and patches haven't really been distributed yet... 18:38:29 so time to upgrade kernels soon ;) 18:38:31 😬 18:39:01 not today:) 18:39:20 yeah, the updates need to be out first ;) 18:39:33 ok, let's stop early. the shortest community meeting for a long time :) 18:39:39 ack 18:39:41 #endmeeting