# Unmaintained collection: netapp\_eseries.santricity **URL:** \ **Category:** Project Discussions\ **Tags:** resolved, community-wg, collection-exclusion, collections\ **Created:** [June 16, 2024, 12:22pm UTC](https://forum.ansible.com/t/unmaintained-collection-netapp-eseries-santricity/6574 "2024-06-16T12:22:09Z")\ **Posts on this page:** 18\ **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 16, 2024, 12:22pm UTC](https://forum.ansible.com/t/unmaintained-collection-netapp-eseries-santricity/6574/1 "2024-06-16T12:22:09Z")
The [netapp\_eseries.santricity](https://github.com/NetApp/santricity) collection looks unmaintained / abandoned, it has: - no new commits since January 2023 - no new release since [Jan 31, 2023](https://github.com/NetApp/santricity/releases) - no reaction on [Community package requirements: sanity tests](https://github.com/NetApp/santricity/issues/23) ---
**Author:** ![Andersson007](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/andersson007/32/89_2.png) [@Andersson007](https://forum.ansible.com/u/Andersson007)\ **Post date:** [June 24, 2024, 8:04am UTC](https://forum.ansible.com/t/unmaintained-collection-netapp-eseries-santricity/6574/3 "2024-06-24T08:04:22Z")
let’s start the process then:) ---
**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 24, 2024, 3:16pm UTC](https://forum.ansible.com/t/unmaintained-collection-netapp-eseries-santricity/6574/4 "2024-06-24T15:16:04Z")
I did, there’s an [issue in the repository](https://github.com/NetApp/santricity/issues/24) and I’ve mentioned this to `@newsbot` to get it into the next Bullhorn. According to the [process](https://docs.ansible.com/ansible/devel/community/collection_contributors/collection_package_removal.html#id6) we now have to wait a couple of weeks until we start a vote. I’ll try to remember opening a vote 4 weeks after the next Bullhorn release. ---
**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 31, 2024, 8:11pm UTC](https://forum.ansible.com/t/unmaintained-collection-netapp-eseries-santricity/6574/5 "2024-07-31T20:11:50Z")
> [@mariolenz](#): > > I’ve mentioned this to `@newsbot` to get it into the next Bullhorn For the record: [The Bullhorn #143](http://forum.ansible.com/t/6832) ---
**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:** [August 8, 2024, 3:30pm UTC](https://forum.ansible.com/t/unmaintained-collection-netapp-eseries-santricity/6574/6 "2024-08-08T15:30:55Z")
I’d like to vote on removing this collection from Ansible 11 since it looks unmaintained. The vote will end 2024-08-21. _Poll ([view on site](https://forum.ansible.com/t/unmaintained-collection-netapp-eseries-santricity/6574/6))_ _Poll ([view on site](https://forum.ansible.com/t/unmaintained-collection-netapp-eseries-santricity/6574/6))_ ---
**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:** [August 13, 2024, 12:20pm UTC](https://forum.ansible.com/t/unmaintained-collection-netapp-eseries-santricity/6574/7 "2024-08-13T12:20:01Z")
I’ve asked internally to see if we’ve got any contacts. Though seems like one of the maintainers left NetApp over a year ago, and the other maintainer hasn’t been active on GitHub for over a year. ---
**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:** [August 13, 2024, 4:00pm UTC](https://forum.ansible.com/t/unmaintained-collection-netapp-eseries-santricity/6574/8 "2024-08-13T16:00:49Z")
Sounds pretty unmaintained to me 🙂 ---
**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:** [August 13, 2024, 6:12pm UTC](https://forum.ansible.com/t/unmaintained-collection-netapp-eseries-santricity/6574/9 "2024-08-13T18:12:01Z")
[Two maintainers](https://github.com/NetApp/santricity/issues/24) have appeared. I’ve asked if they can look at the [CI Failures](https://github.com/NetApp/santricity/issues/23) in that collection. So let’s give them a few weeks to see if they get it sorted. ---
**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:** [August 14, 2024, 3:36pm UTC](https://forum.ansible.com/t/unmaintained-collection-netapp-eseries-santricity/6574/10 "2024-08-14T15:36:47Z")
Not to put too fine a point on this, but even if they do I have feeling we’ll see netapp\_eseries.santricity on my list of possibly unmaintained collections next year again 😟 ---
**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:** [August 14, 2024, 5:16pm UTC](https://forum.ansible.com/t/unmaintained-collection-netapp-eseries-santricity/6574/11 "2024-08-14T17:16:53Z")
I agree. Let’s suspend the vote and take another look in a couple of weeks. (I’ll change my vote to “keep” for now.) ---
**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:** [September 12, 2024, 4:39pm UTC](https://forum.ansible.com/t/unmaintained-collection-netapp-eseries-santricity/6574/12 "2024-09-12T16:39:39Z")
@gundalow @felixfontein What do you mean with a few / couple of weeks? Not to put too fine a point on this, but there hasn’t been _any_ activity. I don’t see any commits and no PRs, either, since those [two “maintainers”](https://github.com/NetApp/santricity/issues/24#issuecomment-2286275077) have appeared and claimed they’re working on the collection. How long do we want to wait? If they really want to stay in the Ansible Community Package, I think they should have done something already. Not to put too fine a point on this, but @gotmax23 updated [collection failures](https://github.com/ansible-community/package-test-results/issues/1#issuecomment-2344820857) today. It looks like there are still some problems… of course there are, since there hasn’t been any new release. I think we should remove them from the ACP. This doesn’t mean they can’t publish on galaxy and are still be part of the ansible community at large. But I think we should throw this collection out of the ACP. [@SteeringCommittee](https://forum.ansible.com/groups/steeringcommittee) I think we should try to keep the ACP healthy. And removing this collection would really help there. Should we start another vote? ---
**Author:** ![mcwhiteside](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mcwhiteside/32/3902_2.png) [@mcwhiteside](https://forum.ansible.com/u/mcwhiteside)\ **Post date:** [September 12, 2024, 5:00pm UTC](https://forum.ansible.com/t/unmaintained-collection-netapp-eseries-santricity/6574/13 "2024-09-12T17:00:13Z")
We have addressed the majority of failure found in the sanity checks. The fixes will be included in our next update. We are hoping to get the update pushed within a month. ---
**Author:** ![flowerysong](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/flowerysong/32/2305_2.png) [@flowerysong](https://forum.ansible.com/u/flowerysong)\ **Post date:** [September 12, 2024, 5:17pm UTC](https://forum.ansible.com/t/unmaintained-collection-netapp-eseries-santricity/6574/14 "2024-09-12T17:17:32Z")
> [@mcwhiteside](#): > > We have addressed the majority of failure found in the sanity checks. There have been no public commits since January 31, 2023. Fixing them locally does not count as addressing them. Even if you don’t want to commit these changes to the main branch for some reason, you could at least open PRs so that interested collection users can review them. ---
**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:** [September 14, 2024, 12:18pm UTC](https://forum.ansible.com/t/unmaintained-collection-netapp-eseries-santricity/6574/15 "2024-09-14T12:18:24Z")
@mcwhiteside Sorry, but it’s hard to see if anyone is really working on the collection if this happens completely internally. If I’ve seen at least _some_ commits addressing the sanity test issues, even if they haven’t been released yet, I wouldn’t have brought up the question to remove the collection again 🤷 I’m satisfied for now and will wait a couple of more weeks. ---
**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:** [September 14, 2024, 4:36pm UTC](https://forum.ansible.com/t/unmaintained-collection-netapp-eseries-santricity/6574/16 "2024-09-14T16:36:57Z")
Only publishing changes on release time is not good practice. Let’s re-evaluate it in mid October; then we have ~two weeks time before the Ansible 11 feature freeze. ---
**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:** [October 4, 2024, 3:48pm UTC](https://forum.ansible.com/t/unmaintained-collection-netapp-eseries-santricity/6574/17 "2024-10-04T15:48:22Z")
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). I’ll tick this off on my lists in [Possibly unmaintained collections in Ansible 10](http://forum.ansible.com/t/6162) and [Possibly unmaintained collections in Ansible 11](http://forum.ansible.com/t/9300). ---
**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:** [November 24, 2025, 5:45pm UTC](https://forum.ansible.com/t/unmaintained-collection-netapp-eseries-santricity/6574/18 "2025-11-24T17:45:48Z")
> [@mariolenz](#): > > Not to put too fine a point on this, but even if they do I have feeling we’ll see netapp\_eseries.santricity on my list of possibly unmaintained collections next year again 😟 I _really_ don’t want to say “told you so”, but… well: [Told you so](https://forum.ansible.com/t/44873) 🤪 ---
**Author:** ![Andersson007](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/andersson007/32/89_2.png) [@Andersson007](https://forum.ansible.com/u/Andersson007)\ **Post date:** [November 27, 2025, 8:09am UTC](https://forum.ansible.com/t/unmaintained-collection-netapp-eseries-santricity/6574/19 "2025-11-27T08:09:49Z")
hehe, let’s let it go then:)