Ansible Community Working Group | Ansible Community Working Group | #community:ansible.com
Meeting started by @samccann:ansible.im at 2024-05-01 18:03:33Meeting summary
- INFO: Agenda: https://forum.ansible.com/tags/c/project/7/community-wg-nextmtg / Topics: https://forum.ansible.com/tags/c/project/7/community-wg (@samccann:ansible.im, 18:03:55)
- INFO: Past meeting logs https://forum.ansible.com/t/meeting-log-ansible-community-working-group-2024-04-24-1801/5132 (@samccann:ansible.im, 18:04:11)
- TOPIC: Updates (@samccann:ansible.im, 18:04:37)
- INFO: Ansible 10.0.0 alpha2 released! https://forum.ansible.com/t/release-announcement-ansible-community-package-10-0-0a2-pre-release/5230 (@samccann:ansible.im, 18:06:00)
- 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 (@samccann:ansible.im, 18:06:57)
- 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 (@samccann:ansible.im, 18:08:55)
- 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 (@samccann:ansible.im, 18:10:19)
- INFO: we did move the docs just about a year ago.. out of ansible/ansible (@samccann:ansible.im, 18:11:34)
- TOPIC: Archiving community-topics repo (@samccann:ansible.im, 18:14:52)
- 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 (@samccann:ansible.im, 18:15:30)
- INFO: we are down to 18 issues (plus one to say weve moved lol) (@samccann:ansible.im, 18:16:04)
- 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... (@samccann:ansible.im, 18:16:25)
- TOPIC: collection inclusion requests (@samccann:ansible.im, 18:18:13)
- 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 (@samccann:ansible.im, 18:22:32)
- 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 (@samccann:ansible.im, 18:29:13)
- TOPIC: Collection inclusion for realz this time (@samccann:ansible.im, 18:31:05)
- INFO: 4 new collections are waiting for first reviews - https://github.com/ansible-collections/ansible-inclusion/discussions/categories/new-collection-reviews (@samccann:ansible.im, 18:31:34)
- INFO: 1 collection waiting for second review - https://github.com/ansible-collections/ansible-inclusion/discussions/categories/second-review-needed (@samccann:ansible.im, 18:31:57)
- 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 (@samccann:ansible.im, 18:33:47)
- INFO: any amount of review helps move these issues along and thanks! (@samccann:ansible.im, 18:34:03)
- TOPIC: Open Floor (@samccann:ansible.im, 18:36:53)
- 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 (@samccann:ansible.im, 18:38:20)
- 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 (@samccann:ansible.im, 18:39:44)
Meeting ended at 2024-05-01 18:41:55
Action items
- (none)
People present (lines said)
- @samccann:ansible.im (59)
- @sivel:matrix.org (10)
- @acozine:ansible.im (7)
- @remindbot:ansible.im (2)
- @anwesha:ansible.im (2)
- @ansibot:ansible.im (2)
Full logs: full_log.txt