community_steering_committee.rst: update with respect to forum and collection requirements (#997)

* community_steering_committee.rst: update with respect to forum and collection requirements

* Update docs/docsite/rst/community/steering/community_steering_committee.rst

Co-authored-by: Felix Fontein <[email protected]>

* Simplify links.

Co-authored-by: Maxwell G <[email protected]>

---------

Co-authored-by: Felix Fontein <[email protected]>
Co-authored-by: Maxwell G <[email protected]>

Author: 3 people

docs/docsite/rst/community/steering/community_steering_committee.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 `community topic <https://forum.ansible.com/new-topic?category=project&tags=community-wg>`_ to discuss them.
    (Creating a draft PR for this file and mentioning it in the community topic is also OK.)
 
 .. _steering_responsibilities:
@@ -73,22 +73,20 @@ Committee members are selected based on their active contribution to the Ansible
 Creating new policy proposals & inclusion requests
 ----------------------------------------------------
 
-The Committee uses the `community-topics repository <https://github.com/ansible-community/community-topics/issues>`_ to asynchronously discuss with the Community and vote on Community topics in corresponding issues.
+The Committee uses the `Ansible Forum <https://forum.ansible.com/>`_ to asynchronously discuss with the Community and vote on the proposals in corresponding `community topics <https://forum.ansible.com/tags/c/project/7/community-wg>`_.
 
-You can create a new issue in the `community-topics repository <https://github.com/ansible-community/community-topics/issues>`_ as a discussion topic if you want to discuss an idea that impacts any of the following:
+You can create a `community topic <https://forum.ansible.com/new-topic?category=project&tags=community-wg>`_ 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
   * Other proposals of importance that need the Committee's or overall Ansible community attention
 
+To request changes to the inclusion policy and :ref:`collections_requirements`:
 
-To request changes to the inclusion policy and collection requirements:
-
-#. Submit a new pull request to the `ansible-collections/overview <https://github.com/ansible-collections/overview>`_ repository.
-
-#. Create a corresponding issue containing the rationale behind these changes in the `community-topics repository <https://github.com/ansible-community/community-topics/issues>`_ repository.
+#. Submit a new pull request against the document by clicking the ``Edit`` button on its web page.
+#. Create a `community topic <https://forum.ansible.com/new-topic?category=project&tags=community-wg>`_ containing the rationale for the proposed changes.
 
 To submit new collections for inclusion into the Ansible package:
 
@@ -103,7 +101,7 @@ Depending on a topic you want to discuss with the Community and the Committee, a
 Community topics workflow
 ^^^^^^^^^^^^^^^^^^^^^^^^^
 
-The Committee uses the `Community-topics workflow <https://github.com/ansible-community/community-topics/blob/main/community_topics_workflow.md>`_ to asynchronously discuss and vote on the `community-topics <https://github.com/ansible-community/community-topics/issues>`_.
+The Committee uses the `Community-topics workflow <https://github.com/ansible-community/community-topics/blob/main/community_topics_workflow.md>`_ to asynchronously discuss and vote on the `community topics <https://forum.ansible.com/tags/c/project/7/community-wg>`_.
 
 The quorum, the minimum number of Committee members who must vote on a topic in order for a decision to be officially made, is half of the whole number of the Committee members. If the quorum number contains a fractional part, it is rounded up to the next whole number. For example, if there are thirteen members currently in the committee, the quorum will be seven.
 
@@ -116,7 +114,7 @@ For votes with more than two options, one choice must have at least half of the
 Community topics triage
 ^^^^^^^^^^^^^^^^^^^^^^^
 
-The Committee conducts a triage of `community topics <https://github.com/ansible-community/community-topics/issues>`_ periodically (every three to six months).
+The Committee conducts a triage of `community topics <https://forum.ansible.com/tags/c/project/7/community-wg>`_ periodically (every three to six months).
 
 The triage goals are:
 
@@ -154,7 +152,7 @@ When reviewing community collection `inclusion requests <https://github.com/ansi
   * For a Non-Steering Committee review to be counted for inclusion, it MUST be checked and approved by *another* Steering Committee member.
   * Reviewers must not be involved significantly in development of the collection. They must declare any potential conflict of interest (for example, being friends/relatives/coworkers of the maintainers/authors, being users of the collection, or having contributed to that collection recently or in the past).
 
-#. After the collection gets two or more Committee member approvals, a Committee member creates a `community topic <https://github.com/ansible-community/community-topics/issues>`_ linked to the corresponding inclusion request. The issue's description says that the collection has been approved by two or more Committee members and establishes a date (a week by default) when the inclusion decision will be considered made. This time period can be used to raise concerns.
+#. After the collection gets two or more Committee member approvals, a Committee member creates a `community topic <https://forum.ansible.com/new-topic?category=project&tags=community-wg>`_ linked to the corresponding inclusion request. The issue's description says that the collection has been approved by two or more Committee members and establishes a date (a week by default) when the inclusion decision will be considered made. This time period can be used to raise concerns.
 
 #. If no objections are raised up to the established date, the inclusion request is considered successfully resolved. In this case, a Committee member:
 
@@ -167,10 +165,9 @@ When reviewing community collection `inclusion requests <https://github.com/ansi
 Community Working Group meetings
 ---------------------------------
 
-See the Community Working Group meeting `schedule <https://github.com/ansible/community/blob/main/meetings/README.md#wednesdays>`_. Meeting summaries are posted in the `Community Working Group Meeting Agenda <https://github.com/ansible/community/issues?q=is%3Aopen+label%3Ameeting_agenda+label%3Acommunity+>`_ issue.
+See the Community Working Group meeting `schedule <https://github.com/ansible-community/meetings/tree/main#wednesdays>`_. Meeting summaries are posted on the `Forum <https://forum.ansible.com/tags/c/workflow/meetbot/16/community-wg>`_.
 
 .. note::
 
-  Participation in the Community Working Group meetings is optional for Committee members. Decisions on community topics are made asynchronously in the `community-topics <https://github.com/ansible-community/community-topics/issues>`_ repository.
+  Participation in the Community Working Group meetings is optional for Committee members. Decisions on `community topics <https://forum.ansible.com/tags/c/project/7/community-wg>`_ are made asynchronously in the topics themselves.
 
-The meeting minutes can be found at the `fedora meetbot site <https://meetbot.fedoraproject.org/sresults/?group_id=ansible-community&type=channel>`_ and the same is posted to `Ansible Devel Mailing List <https://groups.google.com/g/ansible-devel>`_ after every meeting.