# Proposal: Consolidating Ansible discussion platforms

**URL:** <https://forum.ansible.com/t/proposal-consolidating-ansible-discussion-platforms/6812>\
**Category:** Project Discussions\
**Tags:** community, mindshare, awx\
**Created:** [June 27, 2024, 1:48pm UTC](https://forum.ansible.com/t/proposal-consolidating-ansible-discussion-platforms/6812 "2024-06-27T13:48:32Z")\
**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:** [August 5, 2024, 7:10am UTC](https://forum.ansible.com/t/proposal-consolidating-ansible-discussion-platforms/6812/21 "2024-08-05T07:10:33Z")

</div>

> [@gotmax23](#):
>
> I do not support this. Synchronous communication via Matrix and asynchronous communication via the forum each serve their own purpose. It should be up to individual groups to decide which mode of communication they prefer or if they use both, like the Steering Committee does.

I think the idea is to remove most of narrow-scope Matrix links from sources like Ansible communication guide, not all - those `social`, `users`, `community`, etc. links are not gonna go away from there. The idea is to make Forum the entry point when WGs can refer from their group pages to their matrix channels if they want, e.g. like we do in [Postgresql ansible collection working group - Ansible](http://forum.ansible.com/g/PostgreSQLTeam)  
So Matrix will still be around, look at [Communicating with the Ansible community — Ansible Community Documentation](https://docs.ansible.com/ansible/devel/community/communication.html#real-time-chat) , it’s going to be like this

---

_[View the full topic](https://forum.ansible.com/t/proposal-consolidating-ansible-discussion-platforms/6812)._
