diff --git a/docs/docsite/rst/community/collection_contributors/collection_requirements.rst b/docs/docsite/rst/community/collection_contributors/collection_requirements.rst index 581ae8d60fc..f682894f100 100644 --- a/docs/docsite/rst/community/collection_contributors/collection_requirements.rst +++ b/docs/docsite/rst/community/collection_contributors/collection_requirements.rst @@ -1,7 +1,7 @@ .. THIS DOCUMENT IS OWNED BY THE ANSIBLE COMMUNITY STEERING COMMITTEE. ALL CHANGES MUST BE APPROVED BY THE STEERING COMMITTEE! For small changes (fixing typos, language errors, etc.) create a PR and ping @ansible/steering-committee. - For other changes, create a discussion in https://github.com/ansible-community/community-topics/ to discuss the changes. + For other changes, create a :ref:`topic` on the Forum to discuss the changes. (Creating a draft PR for this file and mentioning it in the community topic is also OK.) .. _collections_requirements: @@ -23,7 +23,7 @@ This section provides help, advice, and guidance on making sure your collections .. note:: - `Inclusion of a new collection `_ in the Ansible package is ultimately at the discretion of the :ref:`community_steering_committee`. Every rejected candidate will get feedback. Differences of opinion should be taken to a dedicated `Community Topic `_ for discussion and a final vote. + `Inclusion of a new collection `_ in the Ansible package is ultimately at the discretion of the :ref:`community_steering_committee`. Every rejected candidate will get feedback. Differences of opinion should be taken to a dedicated :ref:`community topic` for discussion and a final vote. Feedback and communications ============================== diff --git a/docs/docsite/rst/community/communication.rst b/docs/docsite/rst/community/communication.rst index 0a47bc5b582..079b296a2f4 100644 --- a/docs/docsite/rst/community/communication.rst +++ b/docs/docsite/rst/community/communication.rst @@ -194,16 +194,18 @@ If you also need a real-time chat channel, you can `request one `_ uses the `community-topics repository `_ to asynchronously discuss with the Community and vote on Community topics in corresponding issues. +The :ref:`Ansible Community Steering Committee` uses the :ref:`ansible_forum` to asynchronously discuss with the Community and vote on Community topics. -Create a new issue in the `repository `_ if you want to discuss an idea that impacts any of the following: +Create a `new topic `_ if you want to discuss an idea that impacts any of the following: * Ansible Community -* Community collection best practices and `requirements `_ -* `Community collection inclusion policy `_ -* `The Community governance `_ +* Community collection best practices and :ref:`requirements` +* :ref:`Community collection inclusion policy` +* :ref:`The Community governance` * Other proposals of importance that need the Committee or overall Ansible community attention +See the `Community topics workflow `_ to learn more. + Ansible Automation Platform support questions ============================================= diff --git a/docs/docsite/rst/community/contributor_path.rst b/docs/docsite/rst/community/contributor_path.rst index d3a57e54311..a5171c0af04 100644 --- a/docs/docsite/rst/community/contributor_path.rst +++ b/docs/docsite/rst/community/contributor_path.rst @@ -82,7 +82,7 @@ See :ref:`communication` for ways to communicate and engage with the Ansible com Teach others ============ -Share your experience with other contributors through :ref:`improving documentation`, answering questions from other contributors and users on :ref:`Matrix/Libera.Chat IRC`, giving advice on issues and pull requests, and discussing `Community Topics `_. +Share your experience with other contributors through :ref:`improving documentation`, answering questions from other contributors and users on :ref:`Matrix/Libera.Chat IRC`, giving advice on issues and pull requests, and discussing topics on the :ref:`ansible_forum`. Become a collection maintainer =============================== @@ -105,10 +105,10 @@ Become a steering committee member You do NOT have to be a programmer to become a steering committee member. -The :ref:`Steering Committee ` member status reflects the highest level of trust which allows contributors to lead the project by making very important `decisions `_ for the Ansible project. The Committee members are the community leaders who shape the project's future and the future of automation in the IT world in general. +The :ref:`Steering Committee ` member status reflects the highest level of trust and allows contributors to lead the project by making important decisions for the Ansible project. The Committee members are community leaders who shape the project's future and the future of automation in the IT world in general. To reach the status, as the current Committee members did before getting it, along with the things mentioned in this document, you should: -* Subscribe to, comment on, and vote on the `Community Topics `_. +* Subscribe to, comment on, and vote on the `community topics`. * Propose your topics. * If time permits, join the `Community meetings `_. Note this is **NOT** a requirement. diff --git a/docs/docsite/rst/community/maintainers_guidelines.rst b/docs/docsite/rst/community/maintainers_guidelines.rst index c85f8a21b5e..af4912b57da 100644 --- a/docs/docsite/rst/community/maintainers_guidelines.rst +++ b/docs/docsite/rst/community/maintainers_guidelines.rst @@ -70,7 +70,7 @@ See the :ref:`Communication guide ` to learn more about real- Community Topics ---------------- -The Community and the `Steering Committee `_ asynchronously discuss and vote on the `Community Topics `_ which impact the whole project or its parts including collections and packaging. +The Community and the :ref:`Steering Committee ` asynchronously discuss and vote on the :ref:`community topics` which impact the whole project or its parts including collections and packaging. Share your opinion and vote on the topics to help the community make the best decisions. diff --git a/docs/docsite/rst/community/steering/community_steering_committee.rst b/docs/docsite/rst/community/steering/community_steering_committee.rst index a0390d95547..cf779152b8b 100644 --- a/docs/docsite/rst/community/steering/community_steering_committee.rst +++ b/docs/docsite/rst/community/steering/community_steering_committee.rst @@ -68,12 +68,14 @@ John Barker (`gundalow `_) has been elected by the Committee members are selected based on their active contribution to the Ansible Project and its community. See :ref:`community_steering_guidelines` to learn details. +.. _creating_community_topic: + Creating new policy proposals & inclusion requests ---------------------------------------------------- The Committee uses the `Ansible Forum `_ to asynchronously discuss with the Community and vote on the proposals in corresponding `community topics `_. -You can create a `community topic `_ if you want to discuss an idea that impacts any of the following: +You can `create a community topic `_ (make sure you use the ``Project Discussions`` category and the ``community-wg`` tag) if you want to discuss an idea that impacts any of the following: * Ansible Community * Community collection best practices and requirements @@ -96,6 +98,8 @@ Depending on a topic you want to discuss with the Community and the Committee, a * :ref:`collections_requirements`. * `Ansible Collection Inclusion Checklist `_. +.. _community_topics_workflow: + Community topics workflow ^^^^^^^^^^^^^^^^^^^^^^^^^ diff --git a/docs/docsite/rst/community/steering/community_topics_workflow.rst b/docs/docsite/rst/community/steering/community_topics_workflow.rst index 5cc0a0ead50..dd2f1b2024e 100644 --- a/docs/docsite/rst/community/steering/community_topics_workflow.rst +++ b/docs/docsite/rst/community/steering/community_topics_workflow.rst @@ -4,8 +4,6 @@ For other changes, create a `community topic `_ to discuss them. (Creating a draft PR for this file and mentioning it in the community topic is also OK.) -.. _community_topics_workflow: - Ansible community topics workflow ================================= @@ -118,7 +116,7 @@ Implementation stage * Checks if there is a corresponding milestone in the `ansible-build-data `_ repository. If there is no milestone, the person creates it. - * Creates an issue in ansible-build-data that references the topic in community-topics, and adds it to the milestone. + * Creates an issue in ansible-build-data that references the :ref:`community topic`, and adds it to the milestone. Tools ----- diff --git a/docs/docsite/rst/community/steering/steering_committee_membership.rst b/docs/docsite/rst/community/steering/steering_committee_membership.rst index 36db0ab76e2..12b25c0e649 100644 --- a/docs/docsite/rst/community/steering/steering_committee_membership.rst +++ b/docs/docsite/rst/community/steering/steering_committee_membership.rst @@ -1,7 +1,7 @@ .. THIS DOCUMENT IS OWNED BY THE ANSIBLE COMMUNITY STEERING COMMITTEE. ALL CHANGES MUST BE APPROVED BY THE STEERING COMMITTEE! For small changes (fixing typos, language errors, etc.) create a PR and ping @ansible/steering-committee. - For other changes, create a discussion in https://github.com/ansible-community/community-topics/ to discuss the changes. + For other changes, create a :ref:`community topic` to discuss the changes. (Creating a draft PR for this file and mentioning it in the community topic is also OK.) .. _community_steering_guidelines: diff --git a/docs/docsite/rst/community/steering/steering_committee_past_members.rst b/docs/docsite/rst/community/steering/steering_committee_past_members.rst index f193c39a230..e1960857483 100644 --- a/docs/docsite/rst/community/steering/steering_committee_past_members.rst +++ b/docs/docsite/rst/community/steering/steering_committee_past_members.rst @@ -1,7 +1,7 @@ .. THIS DOCUMENT IS OWNED BY THE ANSIBLE COMMUNITY STEERING COMMITTEE. ALL CHANGES MUST BE APPROVED BY THE STEERING COMMITTEE! For small changes (fixing typos, language errors, etc.) create a PR and ping @ansible/steering-committee. - For other changes, create a discussion in https://github.com/ansible-community/community-topics/ to discuss the changes. + For other changes, create a :ref:`community topic` to discuss the changes. (Creating a draft PR for this file and mentioning it in the community topic is also OK.) .. _steering_past_members: diff --git a/docs/docsite/rst/community/steering/steering_index.rst b/docs/docsite/rst/community/steering/steering_index.rst index 877324072b7..0a0f04c183f 100644 --- a/docs/docsite/rst/community/steering/steering_index.rst +++ b/docs/docsite/rst/community/steering/steering_index.rst @@ -1,7 +1,7 @@ .. THIS DOCUMENT IS OWNED BY THE ANSIBLE COMMUNITY STEERING COMMITTEE. ALL CHANGES MUST BE APPROVED BY THE STEERING COMMITTEE! For small changes (fixing typos, language errors, etc.) create a PR and ping @ansible/steering-committee. - For other changes, create a discussion in https://github.com/ansible-community/community-topics/ to discuss the changes. + For other changes, create a :ref:`community topic` to discuss the changes. (Creating a draft PR for this file and mentioning it in the community topic is also OK.) .. _community_steering_committee: