# Possibly unmaintained collections in Ansible 10 **URL:** \ **Category:** Project Discussions\ **Tags:** resolved, collections, community-wg\ **Created:** [June 4, 2024, 6:01pm UTC](https://forum.ansible.com/t/possibly-unmaintained-collections-in-ansible-10/6162 "2024-06-04T18:01:22Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [June 4, 2024, 6:01pm UTC](https://forum.ansible.com/t/possibly-unmaintained-collections-in-ansible-10/6162/1 "2024-06-04T18:01:22Z")
This is a follow-up to [Possibly unmaintained collections in Ansible 9](http://forum.ansible.com/t/2569). `unchanged-dependencies.py 10.0.0 8.0.0`: - ansible.posix There has been a new release both on [GitHub](https://github.com/ansible-collections/ansible.posix/releases/tag/1.6.0) and [Galaxy](https://galaxy.ansible.com/ui/repo/published/ansible/posix/?version=1.6.0) - community.proxysql There has been a new release both on [GitHub](https://github.com/ansible-collections/community.proxysql/releases/tag/1.6.0) and [Galaxy](https://galaxy.ansible.com/ui/repo/published/community/proxysql/?version=1.6.0) - frr.frr [Remove frr.frr and openvswitch.openvswitch](https://github.com/ansible-community/ansible-build-data/pull/437) - inspur.sm [Remove inspur.sm from Ansible 11](https://github.com/ansible-community/ansible-build-data/issues/363) - netapp\_eseries.santricity There has been a new release both on [GitHub](https://github.com/NetApp/santricity/releases/tag/v1.4.1) and [Galaxy](https://galaxy.ansible.com/ui/repo/published/netapp_eseries/santricity/?version=1.4.1) - ngine\_io.cloudstack [maintained, just nothing significant to release](http://forum.ansible.com/t/6840/3) - openvswitch.openvswitch [Remove frr.frr and openvswitch.openvswitch](https://github.com/ansible-community/ansible-build-data/pull/437) Additionally, I’ve been approached by people who think that these collections also look unmaintained: - google.cloud There has been a new release both on [GitHub](https://github.com/ansible-collections/google.cloud/releases/tag/v1.4.1) and [Galaxy](https://galaxy.ansible.com/ui/repo/published/google/cloud/?version=1.4.1) - vyos.vyos There has been a new release both on [GitHub](https://github.com/ansible-collections/vyos.vyos/releases/tag/v5.0.0) and [Galaxy](https://galaxy.ansible.com/ui/repo/published/vyos/vyos/?version=5.0.0) ---
**Author:** ![gotmax23](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gotmax23/32/106_2.png) [@gotmax23](https://forum.ansible.com/u/gotmax23)\ **Post date:** [June 4, 2024, 7:07pm UTC](https://forum.ansible.com/t/possibly-unmaintained-collections-in-ansible-10/6162/2 "2024-06-04T19:07:15Z")
`ansible.posix` should definitely stay. I’m not sure about the others. ---
**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\ **Post date:** [June 5, 2024, 5:58am UTC](https://forum.ansible.com/t/possibly-unmaintained-collections-in-ansible-10/6162/3 "2024-06-05T05:58:33Z")
I agree, ansible.posix should stay, even though it doesn’t look _very_ maintained, but it’s also far from unmaintained. TBH I never really understood what’s going on with it and if it does have dedicated maintainers, and if yes, who these are 🙂 ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [June 5, 2024, 4:34pm UTC](https://forum.ansible.com/t/possibly-unmaintained-collections-in-ansible-10/6162/4 "2024-06-05T16:34:06Z")
I think ansible.posix doesn’t test with ansible-core 2.17, which is a problem. But I might be wrong there. Anyway, even if they don’t and start to do now this doesn’t mean they’ll release another version. And that’s what I’m checking. This is a very simple way to find unmaintained collections, but it’s easy to do and I haven’t find a better one until now. At least not if you want to do it semi-automatically. Anyway, this is just a list of _possibly_ unmaintained collections 😏 I’ll create separate discussions for every collection. This thread is just to keep track. ---
**Author:** ![sivel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/sivel/32/1198_2.png) [@sivel](https://forum.ansible.com/u/sivel)\ **Post date:** [June 5, 2024, 4:50pm UTC](https://forum.ansible.com/t/possibly-unmaintained-collections-in-ansible-10/6162/5 "2024-06-05T16:50:59Z")
While one may be able to make the case that ansible.posix doesn’t appear actively maintained, and hasn’t released a new version in a while, or potentially even updated it’s testing, it is an officially supported and certified collection. I cannot say how quickly a github issue may take to resolve, but at a minimum for AAP customers, regardless of whether it has an official maintainer at Red Hat right now, it will get support and fixes (fixes would obviously go out publicly too). I do know that the team that is largely responsible for all of the internally supported collections, is aware that there is no official owner, and assigning maintainership is being looked into. In short, I’d ignore ansible.posix, and probably any certified collection that is also owned by RH. Out partner engineering team does also reach out to partners in regards to certified collections that RH does not maintain, when they haven’t updated or released a new version at least yearly iirc. ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [June 5, 2024, 5:22pm UTC](https://forum.ansible.com/t/possibly-unmaintained-collections-in-ansible-10/6162/6 "2024-06-05T17:22:16Z")
@sivel No worries. As I’ve said, this is just a just a list of _possibly_ unmaintained collections. However, I don’t want to ignore it or any other certified collection that is also owned by RH. There’s a risk of missing collections that really are unmaintained if I do. BTW I haven’t created a discussion about removing ansible.posix yet. If I do, we should move the discussion there. At the moment, it looks like the outcome would be to not remove the collection. So I guess I won’t. But please don’t discuss ansible.posix here any further. Open your own thread, or comment in the thread to remove the collection _if_ I decide to open one. At the moment, there’s no question about removing the collection from the community package. ---
**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\ **Post date:** [June 5, 2024, 5:38pm UTC](https://forum.ansible.com/t/possibly-unmaintained-collections-in-ansible-10/6162/7 "2024-06-05T17:38:26Z")
(In case it’s unclear, the “you” in most of @mariolenz’s message isn’t directed (directly) at @sivel, but at _everyone_ looking at this thread. Including myself 🙂 ) ---
**Author:** ![sivel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/sivel/32/1198_2.png) [@sivel](https://forum.ansible.com/u/sivel)\ **Post date:** [June 5, 2024, 5:47pm UTC](https://forum.ansible.com/t/possibly-unmaintained-collections-in-ansible-10/6162/8 "2024-06-05T17:47:42Z")
> [@mariolenz](#): > > But please don’t discuss ansible.posix here any further. Open your own thread, or comment in the thread to remove the collection _if_ I decide to open one. At the moment, there’s no question about removing the collection from the community package. +1, just providing whatever clarification I could, and insight into how some of these things are managed. ---
**Author:** ![samccann](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/samccann/32/18_2.png) [@samccann](https://forum.ansible.com/u/samccann)\ **Post date:** [June 6, 2024, 8:26pm UTC](https://forum.ansible.com/t/possibly-unmaintained-collections-in-ansible-10/6162/9 "2024-06-06T20:26:13Z")
Pointed out in an unrelated topic, but an old bullhorn had a deprecation announcement for some of these collections - [The Bullhorn #123](http://forum.ansible.com/t/the-bullhorn-123/2568). ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [June 7, 2024, 4:17pm UTC](https://forum.ansible.com/t/possibly-unmaintained-collections-in-ansible-10/6162/10 "2024-06-07T16:17:38Z")
Thanks @samccann, this is really helpful! I’ve created discussions on those collections and linked them in my list. I’ve also mentioned them on Matrix in order to get them in the next Bullhorn. ---
**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\ **Post date:** [June 29, 2024, 9:13am UTC](https://forum.ansible.com/t/possibly-unmaintained-collections-in-ansible-10/6162/11 "2024-06-29T09:13:57Z")
Leave `ansible.posix` with me. I’ll get back to you in ~10 days (lots of folks out next week due to US holidays). ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [July 9, 2024, 5:50pm UTC](https://forum.ansible.com/t/possibly-unmaintained-collections-in-ansible-10/6162/12 "2024-07-09T17:50:47Z")
This is weird. It looks like there’s been an [ansible.posix release 1.5.4 on GitHub](https://github.com/ansible-collections/ansible.posix/releases/tag/1.5.4) a couple of hours ago. But on galaxy this version shows up as [having been released one year ago](https://galaxy.ansible.com/ui/repo/published/ansible/posix/?version=1.5.4). This doesn’t make sense to me. ---
**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\ **Post date:** [July 9, 2024, 6:15pm UTC](https://forum.ansible.com/t/possibly-unmaintained-collections-in-ansible-10/6162/13 "2024-07-09T18:15:30Z")
It might simply have been a GH release created for a tag that was created a year ago. ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [July 9, 2024, 7:09pm UTC](https://forum.ansible.com/t/possibly-unmaintained-collections-in-ansible-10/6162/14 "2024-07-09T19:09:41Z")
Yes, you’re right! Looks like like the tag has been created a year ago, and the GitHub release today.