18:03:16 #startmeeting Ansible Community Meeting 18:03:16 Meeting started Wed Oct 5 18:03:16 2022 UTC. 18:03:16 This meeting is logged and archived in a public location. 18:03:16 The chair is andersson007__. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 18:03:16 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:03:16 The meeting name has been set to 'ansible_community_meeting' 18:03:42 #topic Agenda https://github.com/ansible/community/issues/645 18:03:54 * gotmax[m] is kind of here 18:03:54 o/ 18:04:04 #chair mariolenz[m] 18:04:04 Current chairs: andersson007__ mariolenz[m] 18:04:09 o/ 18:04:39 #chair cybette_ 18:04:39 Current chairs: andersson007__ cybette_ mariolenz[m] 18:04:56 o/ 18:04:59 hi all 18:05:08 #chair DonNaro[m] 18:05:09 Current chairs: DonNaro[m] andersson007__ cybette_ mariolenz[m] 18:05:13 hi DonNaro[m] 18:05:17 o/ 18:05:24 #chair acozine 18:05:24 Current chairs: DonNaro[m] acozine andersson007__ cybette_ mariolenz[m] 18:05:33 troubleshooting with a colleague, but I will keep my eye on the channel 18:05:42 thanks:) 18:06:30 #info Agenda: https://github.com/ansible/community/issues/645 / Topics: https://github.com/ansible-community/community-topics 18:06:37 #topic Updates 18:06:38 felixfontein: briantist are you around? 18:06:55 #info Ansible Contributor Summit 2022.10 HackMD - work in progress, bookmark it and check back for more info! https://hackmd.io/@ansible-community/contrib-summit-202210 18:06:55 gundalow: ? 18:06:56 I believe felixfontein said he couldn't come 18:07:06 #chair gotmax[m] 18:07:06 Current chairs: DonNaro[m] acozine andersson007__ cybette_ gotmax[m] mariolenz[m] 18:07:13 gotmax[m]: ah, thanks for the info 18:07:55 #info ansible-core 2.14.0b2 has been released: https://groups.google.com/g/ansible-devel/c/tiWZifuROq8 18:08:03 cybette_: the summit's agenda looks descent 18:08:19 ah, FYI: I won't be around for tomorrow's community meeting 18:08:36 okay 18:09:04 o/ sorry for the latness 18:09:04 lateness even 18:09:05 I'm not nearly as good as Felix in leading meetings, so if anyone wants to try, welcome! 18:09:12 thanks andersson007__ ! many thanks to all the presenters as well, and many others helping to make contrib summit happen 18:09:16 #chair samccann 18:09:16 Current chairs: DonNaro[m] acozine andersson007__ cybette_ gotmax[m] mariolenz[m] samccann 18:09:35 cybette_: yep +1:) 18:10:01 remeber to join in-person or virtually folks 18:10:58 any other updates? 18:11:03 I've lead IRC meetings before, but I'm not the best at keeping time 18:11:09 And I'm not on the SC 18:11:19 gotmax[m]: no problem:) 18:11:28 it's not an obstacle 18:12:01 #info looking for quick feedback on docs improvement -https://github.com/ansible-community/community-topics/issues/143 18:12:13 We'll likely finalize tomorrow, or Friday the latest 18:12:16 i copy-paste things from the previous log which can be found in https://github.com/ansible/community/issues/645#issuecomment-1261349821 18:12:41 gotmax (He/Him): you don't have to be on the SC to lead a meeting :) anyone in the community are welcome to do that if they wish to :) 18:12:47 gotmax[m]: ^ just fyi, if you wanna try, welcome 18:13:32 Maybe another day. I'm a bit distracted today 18:13:40 samccann: thanks for reminding, I'll try to take a look tomorrow 18:13:51 gotmax[m]: yep, sure 18:14:03 just let us know a bit in advance 18:15:02 @cybette:ansible.im cyb-clock chimes every 15 minutes during the community meeting 18:15:20 plus we have cyb-clock ^ to keep time ;) 18:15:39 #info mariolenz[m] is doing a great job with cleaning up the package! Thanks mariolenz[m] ! 18:15:43 hi Sergio Oliveira ! we're having the Ansible Community Meeting now. are you here for this? 18:15:51 Hello! :) 18:15:51 I'm trying to run the tests in community.rabbitmq locally but I'm facing some issues. I wonder if someone could give me some help to setup my local dev environment. That's what I'm getting: https://paste.ubuntu.com/p/CB2XdvzZrC/ 18:16:03 thanks mariolenz ! 18:16:32 I haven't joinned for that reason but I'd love to participate 18:16:41 I'm working on official Ansible Collection Packaging Guidelines for Fedora and making changes to the ansible-packaging macros 18:17:03 SergioOliveira[m: hello, please write to csmart, its maintainer 18:17:30 We have a fair amount of collections packaged and a couple other people packaging collections beside me, which I'm happy about 18:17:44 gotmax[m]: sounds interesting! 18:18:02 Also, anybody is welcome to join #packaging:ansible.com / #ansible-packaging :) 18:18:20 gotmax[m]: if you need any community feedback / if you want to announce something related, feel free to leverage Bullhorn 18:18:52 you could tag this with #info 18:18:57 Yeah, I probably should do that 18:19:35 #info gotmax[m] is working on official Ansible Collection Packaging Guidelines for Fedora and making changes to the ansible-packaging macros, anybody is welcome to join #packaging:ansible.com / #ansible-packaging :) 18:19:39 #info join #packaging:ansible.com (Matrix) / #ansible-packaging (IRC) if you're interested to discuss/participate in the packaging of Ansible collections 18:19:47 :) 18:19:55 The more the merrier 18:20:35 I'll also probably package the ansible{,-core} pre-releases like I did last time 18:20:35 * cybette_ is too slow as always :P 18:20:52 in Bullhorn it'd be seen by more people 18:20:54 Is 2.14 the release with the new galaxy.yml file manifest stuff? 18:21:21 yep +1 for sharing to the Bullhorn 📯 18:21:30 * gotmax[m] will do that later 18:21:57 gotmax[m]: thanks for doing this! 18:22:46 gotmax[m]: i personally don't know 18:23:02 FWIW, I am a Fedora packager sponsor if people feel like getting involved with Ansible packaging in Fedora 18:23:15 I think devel channel is a good place to ask 18:23:59 Seems so: https://github.com/ansible/ansible/commit/d2f80991180337e2be23d6883064a67dcbaeb662 18:25:00 * andersson007__ needs to read the details 18:25:09 yep I see this in the 2.14.0b1 changelog: collections - ansible-galaxy collection build can now utilize MANIFEST.in style directives from galaxy.yml instead of build_ignore effectively inverting the logic from include by default, to exclude by default. 18:26:12 haha I'm just repeating what everyone types :P 18:26:59 cybette_: if you use a matrix.org account delays can happen:) 18:27:14 I think sivel gave a good description of it in some community-topics issue, but for collections that opt in, it would automatically exclude .gitignore and other dotfiles that shouldn't be part of built collections 18:27:31 I probably should educate myself more about this before proposing anything, but the SC might want to have some policy about this 18:28:04 andersson007__: thanks for making me look good (by blaming matrix ;) ❤️ 18:28:14 hehe 18:28:29 https://github.com/ansible-community/community-topics/issues/126#issuecomment-1220056484 18:29:08 gotmax[m]: thanks for the link! 18:29:49 yep, let's see, maybe we can introduce/recommend it in the requirements 18:30:01 @cybette:ansible.im cyb-clock chimes every 15 minutes during the community meeting 18:30:12 I remember about Questions to Legal topic btw 18:30:19 other tasks pop up 18:30:50 but one day i consolidate all the stuff in one consistent question to Legal 18:30:56 #action gotmax to open a community-topics issue about galaxy.yml manifest directives in community collections 18:31:13 gotmax[m]: great, thanks! 18:31:48 Does anyone want to discuss any particular topic from community-topics or whatever? Feel free to suggest 18:32:34 andersson007__: is there something to discuss about the questions to Legal? (i.e. should we change the topic? we're still at "Updates" :) 18:33:10 We could update the Zuul Galaxy publishing jobs to use ansible-core 2.14 once it is released, but if collections have this, `ansible-galaxy collection build` won't work at all with older versions 18:33:11 So we'll probably need to hold off 18:33:15 cybette_: i don't think so (about the Legal) 18:33:41 ok, thanks for doing the work and keeping us updated 18:33:48 +1 18:34:19 cybette_: if we have a topic we can change of course:) 18:34:30 Basically, the question is https://github.com/ansible-community/community-topics/issues/131#issuecomment-1239727559. I think we agreed that was the main issue. 18:35:33 We could go through the backlog: https://github.com/ansible-community/community-topics/issues?q=is%3Aissue+is%3Aopen+sort%3Acreated-asc 18:36:29 I'll try to make time this week for Legal, or next week on Monday 18:36:48 some topics have been opened quite a while 😅 18:37:04 any chance anwesha is around? they have a bit of legal chops 18:37:11 the backlog is huge anyway:) 18:38:19 btw folks who haven't vote yet on Vote ends topics, please do it 18:38:29 Picking a random one `Custom GitHub actions related to Ansible #40`, I think we already have those? 18:38:54 yep, and if anything needs more attention (since not many people can join the community meeting), feel free to add it as an item for Bullhorn! 18:39:40 samccann: i worked as a lawyer too and stopped 8 years ago:) Now i wouldn't trust my judgment 18:40:04 Or we could end early :) 18:40:43 oh haha TIL! didn't know that about your background! 18:41:17 yep, spent 5 years at Uni.. worked for 3 years 18:41:31 Apropos backlog, do you think we could close https://github.com/ansible-community/community-topics/issues/82 or not? 18:41:36 though the area was far from licensing 18:41:56 we have a diverse team with interesting skillset :) 18:42:38 was it criminal law? 18:43:49 mariolenz: was a concensus reached? (I haven't read through everything in #82) 18:43:50 mariolenz[m]: done, thanks! 18:44:06 cybette_: vast majority was for inclusion 18:44:12 ok nevermind :P 18:44:25 DonNaro[m]: no 18:44:32 civil law 18:44:33 * cybette_ should be renamed to snail 18:44:39 hi sorry, been really busy lately 18:44:40 o/ 18:44:41 hehe 18:45:00 @cybette:ansible.im cyb-clock chimes every 15 minutes during the community meeting 18:45:07 briantist: no problem, hi, we perform asynchronously well imo 18:45:13 mariolenz: I much prefer using individual collections over `ansible`, but I don't think it's a good idea to deprecate `ansible` 18:45:28 woah what did I walk into lol 18:45:50 hehe 18:46:14 I think we got a bit bored :) 18:46:39 imo these meeting shouldn't feel like something obligatory like it was 1-2 years ago 18:46:49 it's just a good place to chat (for me) 18:47:05 with active community folks and SC 18:47:20 i.e. time dedicated to that 18:47:28 socializing, etc. 18:48:00 yep, most discussions can and should be done asynchronously, and we can use the meetings to tie up some loose ends 18:48:04 it was so crazy, say, 1.5 year ago:) 18:48:05 qq I hope, re: opening a vote, how do I determine when a vote should end? 18:48:10 last I looked at the open voting issues, folks had chimed in on all fo them 18:48:16 cybette_: +1 18:48:43 usually votes have an end date. If they don't I suggest we add one now 18:48:49 briantist: iirc there's something written in README of community-topics 18:48:53 briantist: when they are on GitHub they generally have a date on them, a deadline for voting 18:49:05 1.5 years ago every meeting was going over 90 minutes, sometimes 2 hours. that's why we needed the cyb-clock 18:49:06 heh, what samccann said 18:49:15 right, I'm asking how do I determine the date I should add to them 😅 18:49:25 briantist: i think a week is more than enough for that topic 18:49:30 also I am looking at the README too, doesn't say anything in there 18:49:34 ok sounds good to me 18:49:36 ah 18:49:55 https://github.com/ansible-community/community-topics/blob/main/community_topics_workflow.md 18:49:56 it seems 18:50:25 briantist: as a general rule - trust your judgment when establishing the date:) 18:50:46 gotmax[m]: yep, exactly 18:50:46 thanks! 18:50:49 thanks 18:50:55 briantist: I suggest you give enough time to put it in at least one issue of Bullhorn (e.g. next bullhorn release + 1 week) 18:51:12 gotmax[m]: briantist but it's a kind of set of recommendations 18:51:18 it's not a policy 18:51:24 cybette: Out of curiosity, what's the cyb-clcok running on? 18:51:33 so sane judgment is what we should use 18:51:58 cybette_: I would like to keep it slightly shorter.. just because I will be away for fest after that and this is a small topic, but generally I would agree 18:52:14 we're out of the "everyone is on vacation" months, so a week seems reasonable 18:52:25 +1 18:52:41 gotmax[m]: I kind of want to ~~steal~~ reuse it 18:52:41 it's a matrix bot 18:52:49 #chair dmsimard[m] 18:52:49 Current chairs: DonNaro[m] acozine andersson007__ cybette_ dmsimard[m] gotmax[m] mariolenz[m] samccann 18:52:55 hey David! 18:53:03 * samccann waves to dmsimard 18:53:24 gotmax (He/Him): yeah it's remindbot, I'm trying to find the repo 18:53:56 * gotmax[m] waves to dmsimard 18:54:25 babby's first vote topic: https://github.com/ansible-community/community-topics/discussions/146 18:55:09 I think it's this one https://github.com/anoadragon453/matrix-reminder-bot 18:56:27 hi dmsimard ! 18:56:30 briantist iirc we decided to use YYYY-MM-DD format 18:56:41 to avoid confusion 18:56:49 dmsimard: Great that you're here! I think you've been working on running tests on the collections that are part of the community package. But I don't find it right at the moment. Do you have the link? It was really great work! 18:56:52 oof.. yeah that's my preferred format too, my brain is just mush 18:56:52 it's called ISO format or something like that 18:57:32 * gotmax[m] wishes the US would use sane measurement systems/date formats 18:57:32 I call it "make it obvious" format - start with the year and everyone knows the next thing is the month, not the day 18:57:33 yeah.. when stressed, the cursed American date formats take advantage and avoid suppression ;) 18:58:20 samccann, I could not attend the meeting today since I had PyLadies Stockholm meetup going on till late evening. Then had to put the cranky little one to bed :). Reading back the logs now. 18:59:07 mariolenz: I'm not actively working on anything like that at this time but it's likely it was something that I would have liked to do -- can you help my memory about what kind of tests ? 18:59:34 I'll close the meeting in 1 minute, though it won't be an obstacle for chatting who wants 19:00:03 thanks andersson007__ ! 19:00:07 there some amount of testing coverage encapsulated in https://github.com/ansible-community/antsibull/blob/main/roles/build-release/tasks/tests.yaml and https://github.com/ansible-community/antsibull/blob/main/playbooks/nested-ansible-tests.yaml which was meant to be designed to make it easy to add more tests in there 19:00:07 #endmeeting