19:00:02 #startmeeting Ansible Community Meeting 19:00:02 Meeting started Wed Nov 23 19:00:02 2022 UTC. 19:00:02 This meeting is logged and archived in a public location. 19:00:02 The chair is felixfontein. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 19:00:02 Useful Commands: #action #agreed #halp #info #idea #link #topic. 19:00:02 The meeting name has been set to 'ansible_community_meeting' 19:00:02 #topic Agenda https://github.com/ansible/community/issues/645 19:00:02 acozine andersson007_ baptistemm bcoca briantist cyberpear cybette dericcrago dmsimard felixfontein geerlingguy gundalow gwmngilfen ikhan_ jillr jtanner lmodemal misc nitzmahone resmo samccann tadeboro cidrblock thaumos zbr: ping! 19:00:06 #info Agenda: https://github.com/ansible/community/issues/645 / Topics: https://github.com/ansible-community/community-topics 19:00:09 #topic Updates 19:00:25 .hello gotmax23 19:00:26 gotmax: gotmax23 'Maxwell G' 19:00:31 o/ 19:00:36 #chair gotmax andersson007__ 19:00:36 Current chairs: andersson007__ felixfontein gotmax 19:00:37 o/ 19:00:41 \o 19:00:44 o/ 19:00:50 #chair acozine samccann cybette_ 19:00:50 Current chairs: acozine andersson007__ cybette_ felixfontein gotmax samccann 19:00:51 I'm not sure how much turn out we'll have given it's Thanksgiving weekend in the US 19:01:28 Hello all amazing people 19:01:28 hmm, btw, what happened to the idea of storing the pinglist somewhere? I see mine is pretty out of date... 19:01:34 #chair anwesha 19:01:34 Current chairs: acozine andersson007__ anwesha cybette_ felixfontein gotmax samccann 19:01:42 * gotmax wishes a happy Thanksgiving to those who celebrate and happy Not Having To Deal With American Colleagues Day to everyone else 19:02:03 AAAHAHAHAHA 19:02:14 🤣 19:02:19 omgosh an international holiday from 'mericans! 19:02:19 lol 19:02:25 felixfontein: I started doing it yesterday but never submitted the PR 19:02:47 heh 19:03:03 gotmax: no worries, we have some more weeks to do this ;) 19:03:27 o/ 19:03:37 #chair mariolenz[m] 19:03:37 Current chairs: acozine andersson007__ anwesha cybette_ felixfontein gotmax mariolenz[m] samccann 19:04:05 Any topics? 19:04:08 #info Ansible 7.0.0 has been released! https://groups.google.com/g/ansible-project/c/_in8jqIr7BE/m/m485FzmLAQAJ 19:04:21 Thank you to the collection maintainers, release engineers, and all of the other contributors who made this happen! 19:04:27 +1 19:04:49 mariolenz[m]: There's https://github.com/ansible-community/community-topics/issues/131#issuecomment-1325267227 19:04:54 Thank you everyone for all your hard work :) 19:04:58 #info we finally got a response from RH legal on our questions on excluding files; a preliminary summary can be found here: https://github.com/ansible-community/community-topics/issues/131#issuecomment-1325267227 19:05:35 anwesha: thanks to you and chadams[m] for working on the release! 19:06:00 #topic Questions to legal and unnecessary files 19:06:02 #link https://github.com/ansible-community/community-topics/issues/131 19:06:31 huzzah for getting an answer! 19:06:35 indeed! 19:06:55 the way I understand it is that we can exclude tests and CI configs from collection tarballs 19:07:15 * gotmax is excited to finally be able to upstream his Fedora patches for this 19:07:34 yep. that's my understanding, too. 19:07:34 I've already started digging out dmsimard's PR for c.g and adding some comments :) 19:08:13 I agree with felixfontein in https://github.com/ansible-collections/community.general/pull/3517 that removing tests from the tarballs is a breaking change 19:08:15 i think we can also exclude gitignores 19:08:22 andersson007__: Indeed 19:08:27 we need to make sure to not accidentally exclude stuff we need (like changelogs/ and docs/docsite/), and I would say that excluding tests etc. is a breaking change that should wait for a new major release 19:08:58 Yes .gitignored can (safely) be excluded. 19:09:22 👍 19:09:36 I'd also like to add support to antsibull for downloading the missing tests 19:10:12 But overall I'm very happy about this! 19:10:14 gotmax: you mean for creating a source release? 19:10:29 Yes, a source release of the ansible package 19:10:43 do we need anything besides running sanity tests? 19:11:09 I guess one question is whether we want to include things needed for sanity testing in the collection release 19:11:26 excluding tests/ also removes tests/sanity/ignore-xxx.txt 19:11:36 Debian's ansible package runs these tests and I believe that dmsimard's sanity test work relies on them as well 19:11:37 good point 19:12:41 including tests/sanity/ignore-xxx.txt but excluding other files is problematic though, since tests/sanity/ignore-xxx.txt could reference excluded files, which would cause sanity tests to fail 19:12:46 i think we should be able to run sanity tests against the tarbals 19:13:06 for example tests/sanity/ignore-2.15.txt in community.general references .azure-pipelines/scripts/publish-codecov.py 19:13:32 This could be a separate tarball that includes everything so we can keep the sdist slim. 19:13:39 andersson007__: I'm not sure, that would make excluding stuff a lot harder 19:13:59 maybe a separate tarball as gotmax is suggesting? 19:14:21 not sure 19:14:24 andersson007__: you mean for the collection, or for ansible? 19:14:49 felixfontein: not sure:) 19:15:01 @cybette:ansible.im cyb-clock chimes every 15 minutes during the community meeting 19:15:08 We could take the existing sources and layer the test directories from Git on top or just download everything from Git and publish that as one source tarball. 19:15:19 I'm talking about ansible 19:16:52 I like the idea, though it would make the release process more complicated 19:17:44 also some collections have 'funny stuff' in their repos, like older releases as tarballs 19:17:51 felixfontein: I think it's worth it, but I don't deny that it would do that :) 19:17:57 (/me remembers one collection that forgot to exclude these from releases) 19:18:08 felixfontein: And entire venvs... 19:18:25 yes... I don't really want to have all that crap in the source release :) 19:18:42 hehe 19:19:41 I'm still wishing for collections publishing both a source and 'user' release on galaxy... 19:19:55 like sdists and wheels on pypi 19:20:21 felixfontein: I don't think all of that is published in their git repositories, though. 19:20:51 The venv directory issue was probably because ansible-galaxy collection build was run in a dirty checkout 19:21:50 the tarball issue was actually for tarballs in the git repo 19:21:56 I forgot which collection that was though 19:22:33 I can look into to adding support to antsibull for downloading missing test directories. So e.g. community.general could add an entry to collection-meta.yaml that they want the tests directory included in the source release. 19:22:37 oh, it was this one: https://github.com/CiscoDevNet/ansible-ucs/tree/master/releases 19:22:51 Yeah, I thought it was one of the cisco ones 19:23:48 hmm, you mean an explicit "reverse exclude"? it might be better to keep that information in the collection itself instead of having it in collection-meta.yaml 19:24:02 that increases he chances of that information not being out of date, or at least I would hope so 19:24:36 felixfontein: Good point 19:25:15 I might need help from you or someone else more familar with the antsibull code base, but I think this is a workable idea :) 19:25:40 I'll try to help! 19:26:17 The nice thing about keeping it in collection-meta.yaml is avoiding the need to download all of the collections to get this data, but I think having stale data is a bigger problem 19:26:41 well, the data could be included in the collection's release tarball ;) 19:26:52 as meta/community.yml or something like that ;) 19:27:18 #action gotmax and felixfontein to look into adding support to antsibull for creating an ansible source distribution 19:27:50 felixfontein: Also, thank you for all of your work with antsibull! I know you've been maintaining it yourself for a while :) 19:28:11 thanks! 19:28:26 +1 19:30:02 @cybette:ansible.im cyb-clock chimes every 15 minutes during the community meeting 19:32:55 Does anyone have anything else they want to discuss? 19:33:04 weather is nice ... 19:33:11 :) 19:33:14 I was just glancing over the community topics, but didn't see something for now 19:33:49 my head is full of pie recipes 19:34:03 not really Ansible-related 19:34:20 for the private plugins in collections topic, I've created a new implementation using meta/runtime.yml (https://github.com/ansible/ansible/pull/79370, https://github.com/ansible-community/antsibull-docs/pull/65) and am currently waiting for feedback (mainly from core on the ansible-core PR) 19:34:46 pieable-playbook pies.yml 19:35:47 ansible-cookbook 19:35:52 should that be pieable-playbook pies.yum? 19:36:18 also, if someone is familiar with the redhat_subscription module, there are some PRs looking for reviewers: https://github.com/ansible-collections/community.general/pull/5583 https://github.com/ansible-collections/community.general/pull/5581 19:36:22 heh 19:36:22 good one :) 19:36:31 acozine: even better! 19:36:39 If it was pies.yum, you'd have to rewrite it a bunch of times 19:36:47 I don't think we ever discussed andersson007__'s collection inclusion issue. I have a follow up on release tagging. Not sure if there's anything else re. removing dead content from c.g. (https://github.com/ansible-community/community-topics/issues/20). 19:36:55 #topic open floor 19:37:17 (That was a comment about yum/dnf ;) 19:37:25 heh 19:37:25 gotmax: i need to drop now unfortunately 19:37:39 I think for removing dead content from c.g and others, we first need to collect some data (even if 'just' grazing github.com and galaxy) 19:37:42 * gotmax waves to andersson007__ 19:37:46 bye andersson007__! 19:37:51 see y'a! thanks 19:37:53 #info We love and appreciate your feedback! Please take the Contributor Survey and help us improve the Ansible Community - https://www.surveymonkey.co.uk/r/7PVX5S2 19:37:56 Thanks to those who've already filled in the survey! 19:38:10 see you andersson007__! 19:38:25 * felixfontein looks forward to the next contributor summit in ghent :) 19:38:41 * cybette_ too! 19:39:25 Is that hybrid or only in person? 19:39:56 we're planning for hybrid! 19:39:59 I would guess hybrid 19:40:11 Cool 19:40:15 so far I've only seen hybrid and online-only ones :) 19:41:01 Re. the release tagging issues we've opened, there's been no response from cyberark.pas or cisco.nso 19:41:17 :( 19:41:23 We may need to start the removal process for cyberark.pas 19:41:29 I guess it's time to start cleaning up... 19:41:44 how about waiting another week (until thanksgiving is over) and start it next week? 19:41:54 felixfontein and I both pinged them again so hopefully they'll respond 19:42:00 felixfontein: Wfm 19:42:51 I also opened issues against hpe.nimble and inspur.sm which tagged their other releases but not the most recent ones 19:43:23 thanks! 19:43:26 There was a response for both fortinet.fortimanager and fortinet.fortios, but I think only the latter was fixed 19:45:03 @cybette:ansible.im cyb-clock chimes every 15 minutes during the community meeting 19:48:49 if there's no more stuff to discuss, I guess we can also close early :) 19:49:27 yeah I guess we can close early :) 19:49:49 Okay with me 19:50:15 I just submitted https://github.com/ansible-community/community-topics/pull/159 19:50:29 To add the ping list 19:51:38 \o/ 19:51:44 will take a look at that later :) 19:51:51 thanks! 19:51:54 ok, time to end 19:51:55 #endmeeting