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

As a part of reducing fragmentation and consolidating Ansible discussion platforms 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.

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?

3 Likes

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

3 Likes