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

<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 5, 2024, 2:50pm UTC](https://forum.ansible.com/t/vote-ended-on-2024-10-07-should-we-remove-community-network-from-the-ansible-community-package/8030/13 "2024-09-05T14:50:31Z")

</div>

> [@Andersson007](#):
>
> So what does the plan exactly look like?  
> I think we should:
> 
> 1. vote on removal
> 2. if positive, proceed with removal according to the [removal process](https://docs.ansible.com/ansible/devel/community/collection_contributors/collection_package_removal.html#general-processes)

I guess it would be best if the collection would declare its deprecation because no one is actively maintaing it itself on Bullhorn to begin with. Like [frr.frr and openvswitch.openvswitch](http://forum.ansible.com/t/the-bullhorn-123/2568#project-updates-8) did. Ideally mentioning that `This collection is not supported with ansible-core>2.17` or `There will be no work done on making this collection work with ansible-core>2.17` or similar.

I don’t want to do this because I haven’t worked on this collection at all. I suggest someone who _has_ worked on this collection recently ( **hint**  **hint** @Andersson007).

This would change the situation considerably for us. We wouldn’t start a vote on a collection that’s considered unmaintained or that we know is unmaintained, but on one that declared itself unmaintained. And denies compatibility with / supporting ansible-core 2.18, which the next Ansible Community Package will be based on.

---

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