2024-05-01 18:03:33 <@samccann:ansible.im> !startmeeting Ansible Community Working Group 2024-05-01 18:03:35 <@ansibot:ansible.im> Meeting started at 2024-05-01 18:03:33 UTC 2024-05-01 18:03:35 <@ansibot:ansible.im> The Meeting name is 'Ansible Community Working Group' 2024-05-01 18:03:50 <@anwesha:ansible.im> Hello hello folks :) 2024-05-01 18:03:55 <@samccann:ansible.im> ^info Agenda: https://forum.ansible.com/tags/c/project/7/community-wg-nextmtg / Topics: https://forum.ansible.com/tags/c/project/7/community-wg 2024-05-01 18:03:59 <@acozine:ansible.im> hello! 2024-05-01 18:04:11 <@samccann:ansible.im> ^info Past meeting logs https://forum.ansible.com/t/meeting-log-ansible-community-working-group-2024-04-24-1801/5132 2024-05-01 18:04:20 <@samccann:ansible.im> welcome welcome everyone! 2024-05-01 18:04:27 <@samccann:ansible.im> start a meeting....and they will come! 2024-05-01 18:04:37 <@samccann:ansible.im> !topic Updates 2024-05-01 18:06:00 <@samccann:ansible.im> ^info Ansible 10.0.0 alpha2 released! https://forum.ansible.com/t/release-announcement-ansible-community-package-10-0-0a2-pre-release/5230 2024-05-01 18:06:06 <@acozine:ansible.im> heh, we all lurk until someone starts the meeting 2024-05-01 18:06:18 <@samccann:ansible.im> Kudos to Felix Fontein and mariolenz for working on this one! 2024-05-01 18:06:21 <@samccann:ansible.im> lol 2024-05-01 18:06:35 <@acozine:ansible.im> hm, my home network is bouncing now, my messages seem to be failing a few times before they go through 2024-05-01 18:06:54 <@samccann:ansible.im> yeah mine failed a couple of times here in this meeting so maybe it's a matrix thing 2024-05-01 18:06:57 <@samccann:ansible.im> ^info please take part in the polls on the future of the Ansible community package: https://forum.ansible.com/t/future-of-the-ansible-community-package/4902/39 2024-05-01 18:07:18 <@samccann:ansible.im> ok boilerplate fun done, let's see what topics we might have 2024-05-01 18:07:49 <@samccann:ansible.im> So no new topics marked for nextmeeting - https://forum.ansible.com/tag/community-wg-nextmtg 2024-05-01 18:08:09 <@samccann:ansible.im> But we are still discussing the future of the ansible package and improving the inclusion procedures 2024-05-01 18:08:44 <@samccann:ansible.im> I do have one new thing I posted (tho not for the meeting) 2024-05-01 18:08:55 <@samccann:ansible.im> ^info - should we move the docs to ansible-community org? - https://forum.ansible.com/t/should-we-move-the-ansible-documentation-repo-to-ansible-community-org/5224/3 2024-05-01 18:09:17 <@samccann:ansible.im> Since sivel is here - can you think of anything that would cause trouble if we moved the docs (again)? 2024-05-01 18:09:51 <@samccann:ansible.im> Felix mentioned we couldn't transfer ansible/ansible issues over with github. I'm not sure how often that happens these days? 2024-05-01 18:10:04 <@anwesha:ansible.im> Thank you so much Felix Fontein and mariolenz for doing the release. 2024-05-01 18:10:19 <@samccann:ansible.im> ^info driver for moving docs (again) seems to be granting permissions to the docs for the entire steering committee and having better control over that for the community 2024-05-01 18:10:28 <@sivel:matrix.org> I'm not entirely sure how often it happens, but an admin has to do the transfer anyway, so there are only so many people who can transfer as it is 2024-05-01 18:11:02 <@samccann:ansible.im> yep there is that. 2024-05-01 18:11:19 <@sivel:matrix.org> But in the event that we would have transferred it, there would otherwise just be us closing the issue, and pointing people at the correct repo 2024-05-01 18:11:28 <@sivel:matrix.org> Just like with collection related issues 2024-05-01 18:11:34 <@samccann:ansible.im> ^info we did move the docs just about a year ago.. out of ansible/ansible 2024-05-01 18:11:46 <@samccann:ansible.im> ok cool good to know 2024-05-01 18:12:41 <@samccann:ansible.im> The only worry I recall hearing other than no more transferred issues, is would it confuse folks to move the source repo yet again. That said, there were calls for moving some of the docs out (community docs) since we did the initial move so... it's lingered that long too 2024-05-01 18:14:34 <@samccann:ansible.im> Okay add any thoughts you might have about this idea to the forum topic pls. 2024-05-01 18:14:52 <@samccann:ansible.im> !topic Archiving community-topics repo 2024-05-01 18:15:00 <@remindbot:ansible.im> @cybette:ansible.im cyb-clock chimes every 15 minutes during the community meeting 2024-05-01 18:15:30 <@samccann:ansible.im> ^info SC has already moved away from the community-topics repo so it's time to archve it - https://forum.ansible.com/t/community-topics-archiving-the-repo/4990/7 2024-05-01 18:16:04 <@samccann:ansible.im> ^info we are down to 18 issues (plus one to say weve moved lol) 2024-05-01 18:16:09 <@acozine:ansible.im> heh 2024-05-01 18:16:25 <@samccann:ansible.im> ^info if you have a topic there, please close if it's done, close if it isn't done and start a forum topic, etc... 2024-05-01 18:17:20 <@samccann:ansible.im> I'm randomly gonna say maybe in a week we just start closing issues with a generic comment of 'if this is still and issue pls open a forum topic (with instructions on how). and start closing them all and archive the beastie 2024-05-01 18:17:37 <@samccann:ansible.im> ^^ only w/o the obvious grammar problems . 2024-05-01 18:18:13 <@samccann:ansible.im> !topic collection inclusion requests 2024-05-01 18:18:25 <@acozine:ansible.im> that sounds like a good strategy 2024-05-01 18:18:52 <@samccann:ansible.im> worked for the ansible/community repo :-) 2024-05-01 18:18:53 <@acozine:ansible.im> most of the remaining issues are either abandoned, or thorny enough that writing up new tickets would be a good exercise anyway 2024-05-01 18:19:34 <@samccann:ansible.im> yep. oh do you all think it's worth posting a comment to say 'pplease close or move to forum' now, and then just close the remaining in a week? 2024-05-01 18:19:49 <@samccann:ansible.im> I can propose this on the forum topic as well, just want to see what folks think about it here 2024-05-01 18:21:20 <@sivel:matrix.org> possibly important note, since ansible/community was brought up. If community members had membership to the github.com/ansible org through the `ansible-community` team, that was for the `ansible/community` repo, that access will be going away soon 2024-05-01 18:21:39 <@sivel:matrix.org> We archived the ambassadors repo and deleted the associated team and removed membership recently 2024-05-01 18:22:32 <@samccann:ansible.im> ^info If community members had membership to the github.com/ansible org through the ansible-community team, that was for the ansible/community repo, that access will be going away soon 2024-05-01 18:22:41 <@sivel:matrix.org> The team is going to be removed, and anyone without an associated team after the team removal, will be removed 2024-05-01 18:23:04 <@sivel:matrix.org> Hopefully that is clear enough. :) 2024-05-01 18:23:18 <@samccann:ansible.im> hah 2024-05-01 18:23:46 <@sivel:matrix.org> I thought about adding caveats about explicit repo membership, etc, but it seemed redundant 2024-05-01 18:23:50 <@samccann:ansible.im> ok so there are 21 members of the ansible-community team... and those members will no longer exist in the Ansible org, is that it? 2024-05-01 18:24:17 <@sivel:matrix.org> If they only have membership as part of that 1 team. If they are in more than that 1 team, they will remain 2024-05-01 18:25:57 <@acozine:ansible.im> likely only RH employees (who would be members of dev teams on one or more repos in the ansible org) will retain access 2024-05-01 18:25:58 <@samccann:ansible.im> ok just to walk my brain thru - @resmo is a familiar name, but is only a member of the ansible-community team. 2024-05-01 18:26:12 <@samccann:ansible.im> What happens when that's removed? They can still open issues and prs etc right? 2024-05-01 18:26:42 <@sivel:matrix.org> Yes, will still have the ability to open issues and prs. That team didn't grant any special perms past the ansible/community repo 2024-05-01 18:26:54 <@samccann:ansible.im> acozine: there are people like you who are still in the steering-committee so will remain (for now) 2024-05-01 18:27:17 <@samccann:ansible.im> my guess is if we do move the docs repo, we'll delete that team in the Ansible org as well, so... no special perms 2024-05-01 18:29:13 <@samccann:ansible.im> ^info looks like a good handful of people not currently active exist only in the ansible-community team, but since the team had no special permissions, should have no real impact to their future work 2024-05-01 18:30:00 <@remindbot:ansible.im> @cybette:ansible.im cyb-clock chimes every 15 minutes during the community meeting 2024-05-01 18:30:14 <@samccann:ansible.im> ok gonna move onto collections if there's nothing else on this topic? 2024-05-01 18:31:05 <@samccann:ansible.im> !topic Collection inclusion for realz this time 2024-05-01 18:31:34 <@samccann:ansible.im> ^info 4 new collections are waiting for first reviews - https://github.com/ansible-collections/ansible-inclusion/discussions/categories/new-collection-reviews 2024-05-01 18:31:57 <@samccann:ansible.im> ^info 1 collection waiting for second review - https://github.com/ansible-collections/ansible-inclusion/discussions/categories/second-review-needed 2024-05-01 18:33:05 <@samccann:ansible.im> It's interesting that the submission guidelines ask new collection owners to participate in reviewing other collection inclusion requests - https://github.com/ansible-collections/ansible-inclusion?tab=readme-ov-file#submission-process 2024-05-01 18:33:10 <@samccann:ansible.im> Wonder if that ever actually happens? 2024-05-01 18:33:47 <@samccann:ansible.im> ^info consider taking a collection from those lists to review using this process - https://github.com/ansible-collections/ansible-inclusion?tab=readme-ov-file#review-process 2024-05-01 18:34:03 <@samccann:ansible.im> ^info any amount of review helps move these issues along and thanks! 2024-05-01 18:34:44 <@samccann:ansible.im> anything else for collection inclusions folks want to talk about? 2024-05-01 18:36:53 <@samccann:ansible.im> !topic Open Floor 2024-05-01 18:37:03 <@samccann:ansible.im> Anyone have something community-related to talk about today? 2024-05-01 18:38:20 <@samccann:ansible.im> ^info we hope to do more cleanu/archiving of repos in other orgs too https://forum.ansible.com/t/reduce-fragmentation-moving-stuff-to-the-forum-and-archiving-repos/5141 2024-05-01 18:38:40 <@samccann:ansible.im> it hasn't gotten any comments so please take a look to see if something looks important and shouldn't be archived. 2024-05-01 18:39:44 <@samccann:ansible.im> ^info two repos under discussion for archiving are the ansible-inclusion one used for new collections inclusions and the ansible-collections/overview - which has a LOT of docs related to collections overall 2024-05-01 18:40:56 <@samccann:ansible.im> anything else or should we end the meeting? 2024-05-01 18:41:52 <@samccann:ansible.im> silence is golden :-) 2024-05-01 18:41:55 <@samccann:ansible.im> !endmeeting