.. _communication: Communication ============= We welcome your feedback, questions and ideas. Here's how to reach the community. .. _code_of_conduct: Code of Conduct --------------- All communication and interactions in the Ansible Community are governed by our :ref:`code_of_conduct`. Please read and abide by it! Reach out to our community team at `codeofconduct@ansible.com `_ if you have any questions or need assistance. .. _forum: Forum ----- Join the `Ansible Forum `_ as a single starting point and our default communication platform for questions and help, development discussions, events, and much more. `Register `_ to join the community. Search by categories and tags to find interesting topics or start a new one; subscribe only to topics you need! * `Get Help `_: get help or help others. Please add appropriate tags if you start new discussions, for example `awx`, `ee`, and `documentation`. * `Posts tagged with 'awx' `_: subscribe to participate in project/technology-related conversations. There are other related tags in the forum you can use. * `Bullhorn newsletter `_: used to announce releases and important changes. * `Social Spaces `_: gather and interact with fellow enthusiasts. * `News & Announcements `_: track project-wide announcements including social events. For more information on the forum navigation, see `Navigating the Ansible forum `_ post. Matrix ------ For real-time interactions, conversations in the AWX community happen over the Matrix protocol in the following channels: * `#awx:ansible.com `_: AWX project-related discussions. * `#docs:ansible.im `_: Ansible and AWX documentation-related discussions. For more information, see the community-hosted `Matrix FAQ `_.