# \[Vote ended on 2024-05-13\] Steering Committee: update collection inclusion procedure

**URL:** <https://forum.ansible.com/t/vote-ended-on-2024-05-13-steering-committee-update-collection-inclusion-procedure/4833>\
**Category:** Project Discussions\
**Tags:** resolved, community-wg\
**Created:** [April 9, 2024, 6:31am UTC](https://forum.ansible.com/t/vote-ended-on-2024-05-13-steering-committee-update-collection-inclusion-procedure/4833 "2024-04-09T06:31:31Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**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:** [April 12, 2024, 9:19am UTC](https://forum.ansible.com/t/vote-ended-on-2024-05-13-steering-committee-update-collection-inclusion-procedure/4833/8 "2024-04-12T09:19:22Z")

</div>

As this topic depends on the package future on (thanks @samccann for creating it), let’s wait until there’s more feedback in that one.  
I’ve just suggested one solution, please take a look [Future of the Ansible Community package - #21 by Andersson007](http://forum.ansible.com/t/future-of-the-ansible-community-package/4902/21). I think it promises some very exciting work 😉

---

_[View the full topic](https://forum.ansible.com/t/vote-ended-on-2024-05-13-steering-committee-update-collection-inclusion-procedure/4833)._
