# Reducing fragmentation: Add Communication section emphasizing Forum to collections READMEs in ansible-collections org

**URL:** <https://forum.ansible.com/t/reducing-fragmentation-add-communication-section-emphasizing-forum-to-collections-readmes-in-ansible-collections-org/7242>\
**Category:** Project Discussions\
**Tags:** community, mindshare, community-wg, collections\
**Created:** [July 12, 2024, 7:14am UTC](https://forum.ansible.com/t/reducing-fragmentation-add-communication-section-emphasizing-forum-to-collections-readmes-in-ansible-collections-org/7242 "2024-07-12T07:14:47Z")\
**Posts on this page:** 2\
**Page:** 1

<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:** [July 12, 2024, 7:14am UTC](https://forum.ansible.com/t/reducing-fragmentation-add-communication-section-emphasizing-forum-to-collections-readmes-in-ansible-collections-org/7242/1 "2024-07-12T07:14:47Z")

</div>

As a part of reducing fragmentation and [consolidating Ansible discussion platforms](http://forum.ansible.com/t/proposal-consolidating-ansible-discussion-platforms/6812) effort, we’d like to prioritize the Forum across the collections under the ansible-collections organization.

A large portion of the collections in the org is included in the Ansible package.  
The communication is very important for the overall user/contributor experience around the collections and Ansible in general, therefore, it’s important to have the Forum, as our default platform, easily accessible for users/contributors from collection docs.

While working on improving such information in a few collections and the project template, we developed a Communication section template for README.  
You can see the example of applying the template to the community.network collection README file in the [pull request](https://github.com/ansible-collections/community.network/pull/608/files).

The template:

- Simplifies things; we tried to make it minimalist and concise.
- Emphasizes the Forum.
- Removes general Matrix information (collections still can refer to their specific channels if they actively use them, but we’d encourage them to make an emphasis on the Forum as a default place for discussions).

What’s your opinion on applying this template to all collections under the ansible-collections org?

---

<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:** [July 12, 2024, 1:31pm UTC](https://forum.ansible.com/t/reducing-fragmentation-add-communication-section-emphasizing-forum-to-collections-readmes-in-ansible-collections-org/7242/2 "2024-07-12T13:31:55Z")

</div>

Looks OK to me. I would update `community.vmware` accordingly once it’s clear that this is really the way to go.
