# \[Vote ended on 2024-01-31\] Unmaintained collection: inspur.sm **URL:** \ **Category:** Project Discussions\ **Tags:** community-wg, collections\ **Created:** [December 11, 2023, 7:18pm UTC](https://forum.ansible.com/t/vote-ended-on-2024-01-31-unmaintained-collection-inspur-sm/2854 "2023-12-11T19:18:33Z")\ **Posts on this page:** 8\ **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:** [December 11, 2023, 7:18pm UTC](https://forum.ansible.com/t/vote-ended-on-2024-01-31-unmaintained-collection-inspur-sm/2854/1 "2023-12-11T19:18:33Z")
The [inspur.sm](https://github.com/ISIB-Group/inspur.sm) collection looks unmaintained / abandoned, it has: - no new commits since October 2022 - no new release since [Oct 31, 2022](https://github.com/ISIB-Group/inspur.sm/releases/tag/2.3.0) - no GHA CI run since [Apr 07, 2023](https://github.com/ISIB-Group/inspur.sm/actions/runs/4635966184) - tests defined up to ansible-core 2.14 but not with the current release - no reaction on [Consider using true/false for all booleans in docs](https://github.com/ISIB-Group/inspur.sm/issues/58) ---
**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:** [December 18, 2023, 4:11pm UTC](https://forum.ansible.com/t/vote-ended-on-2024-01-31-unmaintained-collection-inspur-sm/2854/2 "2023-12-18T16:11:22Z")
For the record: [Unmaintained collection: Removal from Ansible (community) package](https://github.com/ISIB-Group/inspur.sm/issues/59) ---
**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:** [January 16, 2024, 7:39pm UTC](https://forum.ansible.com/t/vote-ended-on-2024-01-31-unmaintained-collection-inspur-sm/2854/3 "2024-01-16T19:39:28Z")
I’d like to vote on removing this collection from Ansible 11 since it looks unmaintained. The vote will end 2024-01-31. _Poll ([view on site](https://forum.ansible.com/t/vote-ended-on-2024-01-31-unmaintained-collection-inspur-sm/2854/3))_ _Poll ([view on site](https://forum.ansible.com/t/vote-ended-on-2024-01-31-unmaintained-collection-inspur-sm/2854/3))_ ---
**Author:** ![Leo](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/leo/32/23_2.png) [@Leo](https://forum.ansible.com/u/Leo)\ **Post date:** [January 19, 2024, 8:33pm UTC](https://forum.ansible.com/t/vote-ended-on-2024-01-31-unmaintained-collection-inspur-sm/2854/4 "2024-01-19T20:33:53Z")
Looks like they migrated it, from the [Github README](https://github.com/ISIB-Group/inspur.sm#inspur-sm-collection): > This repo contains the `inspur.sm` Ansible Collection. Inspur server supports ansible management device,Basic management of the server based on restful interface. Collections functionality will migrate to the [inspur.ispim](https://galaxy.ansible.com/inspur/ispim) collection, head over to the new collection. ---
**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:** [January 19, 2024, 8:48pm UTC](https://forum.ansible.com/t/vote-ended-on-2024-01-31-unmaintained-collection-inspur-sm/2854/5 "2024-01-19T20:48:28Z")
Considering that this apparently happened at least 2 years ago, and they didn’t bother to tell us, I think we should really remove this collection. ---
**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:** [January 20, 2024, 1:04pm UTC](https://forum.ansible.com/t/vote-ended-on-2024-01-31-unmaintained-collection-inspur-sm/2854/6 "2024-01-20T13:04:24Z")
> [@Leo](#): > > Looks like they migrated it Thanks, I haven’t seen this! Yes, it looks like they’ve migrated the functionality to a new collection. So this one really seems abandoned. The new one (`inspur.ispim`) already seems to be part of ansible. It looks like they didn’t tell us we can remove `inspur.sm` in the [inclusion request for inspur.ispim](https://github.com/ansible-collections/ansible-inclusion/discussions/47) :-/ ---
**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:** [January 26, 2024, 6:02pm UTC](https://forum.ansible.com/t/vote-ended-on-2024-01-31-unmaintained-collection-inspur-sm/2854/7 "2024-01-26T18:02:57Z")
Since there are _still_ not enough votes to get a decision, I’ll extend the vote until 2024-01-31. [@SteeringCommittee](https://forum.ansible.com/groups/steeringcommittee) please vote! Or consider [leaving the SC](https://docs.ansible.com/ansible/devel/community/steering/steering_committee_membership.html#voluntarily-leaving-the-steering-committee). This “quorum begging” is getting a little bit annoying… ---
**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:** [January 31, 2024, 4:14pm UTC](https://forum.ansible.com/t/vote-ended-on-2024-01-31-unmaintained-collection-inspur-sm/2854/8 "2024-01-31T16:14:32Z")
The vote ended today. 8 steering committee voted in favor of removing `inspur.sm` from Ansible 11, which means we’ve reached the quorum and the vote is accepted. There were also 2 votes from the community in favor of this, and none (neither from the steering committee nor from the community) against it.