# Future of the Ansible Community package

**URL:** <https://forum.ansible.com/t/future-of-the-ansible-community-package/4902>\
**Category:** Project Discussions\
**Tags:** community-wg\
**Created:** [April 11, 2024, 8:54am UTC](https://forum.ansible.com/t/future-of-the-ansible-community-package/4902 "2024-04-11T08:54:55Z")\
**Posts on this page:** 1\
**Showing post:** 21

<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:16am UTC](https://forum.ansible.com/t/future-of-the-ansible-community-package/4902/21 "2024-04-12T09:16:30Z")

</div>

My proposal (something can be kick out/added and don’t go into details too much right now - if it’s OK I can raise a dedicated topic):  
1. **Replace package inclusion** with `community-approved collections process` by SC. the approved collections:

- docs will be present on [docs.ansible.com](http://docs.ansible.com) (or maybe there’ll be just a link to Galaxy filtered with the badge)
- will have the galaxy badge mentioned by @bcoca

2. **Trim the package down to essential things decided by SC**

- [don’t focus on the details now] the new trimmed-down package will start with ansible-core, ansible.utils, ansible.posix, ansible.windows and community.core (SC will decide what to move to it from c.general)

3. **SC will continue to decide what will be in the package including community.core’s content** (i.e. to vote on new plugins/modules)

IMO with this approach, we’ll keep the collection maintainers motivated and users informed providing a still good batteries included package. And it doesn’t feel like more work for SC (maybe on the initial stage only)

---

_[View the full topic](https://forum.ansible.com/t/future-of-the-ansible-community-package/4902)._