# \[Vote ended on 2024-10-07\] Should we remove community.network from the Ansible community package?

**URL:** <https://forum.ansible.com/t/vote-ended-on-2024-10-07-should-we-remove-community-network-from-the-ansible-community-package/8030>\
**Category:** Project Discussions\
**Tags:** fortinet, routeros, resolved, community-wg, network\
**Created:** [August 21, 2024, 7:17pm UTC](https://forum.ansible.com/t/vote-ended-on-2024-10-07-should-we-remove-community-network-from-the-ansible-community-package/8030 "2024-08-21T19:17:09Z")\
**Posts on this page:** 1\
**Showing post:** 32

<div class="post-metadata">

**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 20, 2024, 12:00pm UTC](https://forum.ansible.com/t/vote-ended-on-2024-10-07-should-we-remove-community-network-from-the-ansible-community-package/8030/32 "2024-09-20T12:00:05Z")

</div>

Based on the discussion above, I think we should vote on the following: First deprecate the `community.network` collection itself since there’s nobody really maintaining anymore, then deprecate it in Ansible 10 and remove it from **Ansible 11** as officially unsupported.

If you prefer to keep the collection in 11 and remove it from 12, please vote `Reject`. If there’s no majority for removing it from 11, I would open a new vote to remove it from 12.

_Poll ([view on site](https://forum.ansible.com/t/vote-ended-on-2024-10-07-should-we-remove-community-network-from-the-ansible-community-package/8030/32))_

_Poll ([view on site](https://forum.ansible.com/t/vote-ended-on-2024-10-07-should-we-remove-community-network-from-the-ansible-community-package/8030/32))_

---

_[View the full topic](https://forum.ansible.com/t/vote-ended-on-2024-10-07-should-we-remove-community-network-from-the-ansible-community-package/8030)._
