# \[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:** 35

<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 30, 2024, 10:29am UTC](https://forum.ansible.com/t/vote-ended-on-2024-10-07-should-we-remove-community-network-from-the-ansible-community-package/8030/35 "2024-09-30T10:29:34Z")

</div>

Based on the discussion above and the fact that the vote on removing `community.network` from Ansible 11 has been rejected by the majority of Steering Committee members, I would like to start another one:

_First_ deprecate the `community.network` collection itself since there’s nobody really maintaining it anymore, _then_ deprecate it in Ansible and remove it from **Ansible 12** as officially unsupported.

_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/35))_

_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/35))_

---

_[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)._
