18:04:21 #startmeeting Ansible Community Meeting 18:04:21 Meeting started Wed Aug 2 18:04:21 2023 UTC. 18:04:21 This meeting is logged and archived in a public location. 18:04:21 The chair is mariolenz[m]. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 18:04:21 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:04:21 The meeting name has been set to 'ansible_community_meeting' 18:05:42 #chair anwesha 18:05:42 Current chairs: anwesha mariolenz[m] 18:05:43 #chair samccann 18:05:43 Current chairs: anwesha mariolenz[m] samccann 18:06:48 #chair samccann anwesha 18:06:48 Current chairs: anwesha mariolenz[m] samccann 18:08:05 Not sure if I'm doing this the right... well, anything to discuss? I done see any [#startmeeting Ansible Community Meeting](https://github.com/ansible-community/community-topics/labels/next_meeting) stuff at the moment. 18:14:37 If there's nothing important to discuss, maybe we should move to: 18:14:44 #topic Open Floor 18:15:01 @cybette:ansible.im cyb-clock chimes every 15 minutes during the community meeting 18:15:13 #chair Leo 18:15:13 Current chairs: Leo anwesha mariolenz[m] samccann 18:15:25 sure, why not? 18:24:10 At the spur of the moment, I should say that having an upstream name and a downstream name sounds like a bad idea. If it's one collection, I think it should have one name. But maybe I just don't understand the problem. Could you give a example? 18:26:07 and for Ansible community package collections requirements: https://docs.ansible.com/ansible/latest/community/collection_contributors/collection_requirements.html#collection-naming 18:30:01 @cybette:ansible.im cyb-clock chimes every 15 minutes during the community meeting 18:32:50 o/ 18:32:54 sorry I'm late 18:37:30 #chair acozine 18:37:30 Current chairs: Leo acozine anwesha mariolenz[m] samccann 18:42:22 428116 18:42:50 ? 18:43:23 oops sorry hit my yubikey by accident 18:45:00 @cybette:ansible.im cyb-clock chimes every 15 minutes during the community meeting 18:48:35 Leo: I don't think we'll find a solution for this today. I suggest to create a [community-topics issue](https://github.com/ansible-community/community-topics/issues) if you haven't done yet. This might help to get more opinions. 18:53:08 Anything else to discuss? We only have a couple of minutes left. 18:59:50 As I've said, I've never run a meeting yet. I hope I wasn't to bad and did everything the right way. I especially hope you all turn up in the logs, I'm not 100% sure I've chaired you correctly. 18:59:55 #endmeeting