remove outdated ansible/community links (#913)

---------

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

Author: 3 people

docs/docsite/rst/community/collection_contributors/collection_release_with_branches.rst

@@ -150,7 +150,7 @@ Publishing the collection
 
 4. Add a GitHub release for the new tag. The title should be the version and content, such as -  ``See https://github.com/ansible-collections/community.xxx/blob/stable-X/CHANGELOG.rst for all changes``.
 
-5. Announce the release through the `Bullhorn Newsletter <https://github.com/ansible/community/wiki/News#the-bullhorn>`_.
+5. Announce the release through the `Bullhorn Newsletter <https://forum.ansible.com/c/news/bullhorn/17>`_.
 
 6. Announce the release in the pinned release issue/community pinboard of the collection and in the ``#ansible-community`` `Matrix/Libera.Chat IRC channel <https://docs.ansible.com/ansible/devel/community/communication.html#real-time-chat>`_.
 
@@ -205,7 +205,7 @@ Publishing the collection
 
 3. Add a GitHub release for the new tag. The title should be the version and content, such as -  ``See https://github.com/ansible-collections/community.xxx/blob/stable-X/CHANGELOG.rst for all changes``.
 
-4. Announce the release through the `Bullhorn Newsletter <https://github.com/ansible/community/wiki/News#the-bullhorn>`_.
+4. Announce the release through the `Bullhorn Newsletter <https://forum.ansible.com/c/news/bullhorn/17>`_.
 
 5. Announce the release in the pinned release issue/community pinboard of the collection and in the ``#ansible-community`` `Matrix/IRC channel <https://docs.ansible.com/ansible/devel/community/communication.html#real-time-chat>`_. Additionally, you can announce it using GitHub's Releases system.
 
@@ -289,7 +289,7 @@ Releasing when more minor versions are expected
     This is deliberate, since the next minor release ``X.(Y+1).0`` already contains the changes for ``X.Y.Z`` as well since these were cherry-picked from ``stable-X``.
 
 
-4. Announce the release through the `Bullhorn Newsletter <https://github.com/ansible/community/wiki/News#the-bullhorn>`_.
+4. Announce the release through the `Bullhorn Newsletter <https://forum.ansible.com/c/news/bullhorn/17>`_.
 
 5. Announce the release in the pinned release issue/community pinboard of the collection and in the ``#ansible-community`` `Matrix/IRC channel <https://docs.ansible.com/ansible/devel/community/communication.html#real-time-chat>`.
 
@@ -336,6 +336,6 @@ Releasing when no more minor versions are expected
 
 3. Add a GitHub release for the new tag. Title should be the version and content, such as: ``See https://github.com/ansible-collections/community.xxx/blob/stable-X/CHANGELOG.rst for all changes``.
 
-4. Announce the release through the `Bullhorn Newsletter <https://github.com/ansible/community/wiki/News#the-bullhorn>`_.
+4. Announce the release through the `Bullhorn Newsletter <https://forum.ansible.com/c/news/bullhorn/17>`_.
 
 5. Announce the release in the pinned issue/community pinboard of the collection and in the ``#ansible-community`` `Matrix/IRC channel <https://docs.ansible.com/ansible/devel/community/communication.html#real-time-chat>`_.

docs/docsite/rst/community/collection_contributors/collection_release_without_branches.rst

@@ -110,6 +110,6 @@ Publish the collection
 
 4. Add a GitHub release for the new tag. Title should be the version and content ``See https://github.com/ansible-collections/community.xxx/blob/main/CHANGELOG.rst for all changes``.
 
-5. Announce the release through the `Bullhorn Newsletter issue <https://github.com/ansible/community/wiki/News#the-bullhorn>`_.
+5. Announce the release through the `Bullhorn Newsletter issue <https://forum.ansible.com/c/news/bullhorn/17>`_.
 
 6. Announce the release in the pinned release issue/community pinboard of the collection mentioned in step 3 and in the ``community`` :ref:`Matrix/IRC channel <communication_irc>`.

docs/docsite/rst/community/collection_contributors/collection_requirements.rst

@@ -31,7 +31,7 @@ Feedback and communications
 As with any project it is very important that we get feedback from users, contributors, and maintainers. You can get feedback and help as follows:
 
 * Discussing in the `#community:ansible.com Matrix room <https://matrix.to/#/#community:ansible.com>`_, which is bridged with the ``#ansible-community`` channel on Libera.Chat IRC. See the :ref:`Ansible Communication Guide <communication_irc>` for details.
-* Discussing in the `Community Working Group meeting <https://github.com/ansible/community/blob/main/meetings/README.md#wednesdays>`_.
+* Discussing in the `Community Working Group meeting <https://github.com/ansible-community/meetings/blob/main/README.md#wednesdays>`_.
 * Creating `GitHub Issues <https://github.com/ansible-collections/overview/issues>`_ in the ``ansible-collections`` repository.
 
 Keeping informed
@@ -40,7 +40,7 @@ Keeping informed
 You should subscribe to:
 
 * The `news-for-maintainers repository <https://github.com/ansible-collections/news-for-maintainers>`_ to track changes that collection maintainers should be aware of. Subscribe only to issues if you want less traffic.
-* The `Bullhorn <https://github.com/ansible/community/wiki/News#the-bullhorn>`_ Ansible contributor newsletter.
+* The `Bullhorn <https://forum.ansible.com/c/news/bullhorn/17>`_ Ansible contributor newsletter.
 
 .. _coll_infrastructure_reqs:
 

docs/docsite/rst/community/collection_development_process.rst

@@ -19,7 +19,7 @@ If you want to follow the conversation about what features will be added to the
 
 * the :ref:`roadmaps`
 * the :ref:`Ansible Release Schedule <release_and_maintenance>`
-* the `Ansible Community Working Group <https://github.com/ansible/community/wiki/Community>`_ .
+* the `Ansible Community Working Group <https://forum.ansible.com/tags/c/project/7/community-wg>`_ .
 
 Micro development: the lifecycle of a PR
 ========================================

docs/docsite/rst/community/contributing_maintained_collections.rst

@@ -66,7 +66,7 @@ The following table shows:
     <tr>
       <td><a href="https://galaxy.ansible.com/amazon/aws">amazon.aws</a></td>
       <td><a href="https://galaxy.ansible.com/community/aws">community.aws</a></td>
-      <td><a href="https://github.com/ansible/community/tree/main/group-aws">AWS</a></td>
+      <td><a href="https://forum.ansible.com/g/AWS">AWS</a></td>
       <td>✓**</td>
       <td>**</td>
       <td>✓</td>
@@ -77,7 +77,7 @@ The following table shows:
     <tr>
       <td><a href="https://galaxy.ansible.com/ansible/netcommon">ansible.netcommon***</a></td>
       <td><a href="https://galaxy.ansible.com/community/network">community.network</a></td>
-      <td><a href="https://github.com/ansible/community/wiki/Network">Network</a></td>
+      <td><a href="https://forum.ansible.com/g/network-wg">Network</a></td>
       <td>✓</td>
       <td>✓</td>
       <td>✓</td>
@@ -99,7 +99,7 @@ The following table shows:
     <tr>
       <td><a href="https://galaxy.ansible.com/ansible/windows">ansible.windows</a></td>
       <td><a href="https://galaxy.ansible.com/community/windows">community.windows</a></td>
-      <td><a href="https://github.com/ansible/community/wiki/Windows">Windows</a></td>
+      <td><a href="https://matrix.to:/#/#windows:ansible.com">Windows</a></td>
       <td>✓</td>
       <td>✓****</td>
       <td>✓</td>
@@ -110,7 +110,7 @@ The following table shows:
     <tr>
       <td><a href="https://galaxy.ansible.com/arista/eos">arista.eos</a></td>
       <td><a href="https://galaxy.ansible.com/community/network">community.network</a></td>
-      <td><a href="https://github.com/ansible/community/wiki/Network">Network</a></td>
+      <td><a href="https://forum.ansible.com/g/network-wg">Network</a></td>
       <td>✓</td>
       <td>✓</td>
       <td>✓</td>
@@ -121,7 +121,7 @@ The following table shows:
     <tr>
       <td><a href="https://galaxy.ansible.com/cisco/asa">cisco.asa</a></td>
       <td><a href="https://github.com/ansible-collections/community.asa">community.asa</a></td>
-      <td><a href="https://github.com/ansible/community/wiki/Security-Automation">Security</a></td>
+      <td><a href="https://matrix.to/#/#security-automation:ansible.com">Security</a></td>
       <td>✓</td>
       <td>✓</td>
       <td>✓</td>
@@ -132,7 +132,7 @@ The following table shows:
     <tr>
       <td><a href="https://galaxy.ansible.com/cisco/ios">cisco.ios</a></td>
       <td><a href="https://galaxy.ansible.com/community/network">community.network</a></td>
-      <td><a href="https://github.com/ansible/community/wiki/Network">Network</a></td>
+      <td><a href="https://forum.ansible.com/g/network-wg">Network</a></td>
       <td>✓</td>
       <td>✓</td>
       <td>✓</td>
@@ -143,7 +143,7 @@ The following table shows:
     <tr>
       <td><a href="https://galaxy.ansible.com/cisco/iosxr">cisco.iosxr</a></td>
       <td><a href="https://galaxy.ansible.com/community/network">community.network</a></td>
-      <td><a href="https://github.com/ansible/community/wiki/Network">Network</a></td>
+      <td><a href="https://forum.ansible.com/g/network-wg">Network</a></td>
       <td>✓</td>
       <td>✓</td>
       <td>✓</td>
@@ -154,7 +154,7 @@ The following table shows:
     <tr>
       <td><a href="https://galaxy.ansible.com/cisco/nxos">cisco.nxos</a></td>
       <td><a href="https://galaxy.ansible.com/community/network">community.network</a></td>
-      <td><a href="https://github.com/ansible/community/wiki/Network">Network</a></td>
+      <td><a href="https://forum.ansible.com/g/network-wg">Network</a></td>
       <td>✓</td>
       <td>✓</td>
       <td>✓</td>
@@ -165,7 +165,7 @@ The following table shows:
     <tr>
       <td><a href="https://galaxy.ansible.com/ibm/qradar">ibm.qradar</a></td>
       <td><a href="https://github.com/ansible-collections/community.qradar">community.qradar</a></td>
-      <td><a href="https://github.com/ansible/community/wiki/Security-Automation">Security</a></td>
+      <td><a href="https://matrix.to/#/#security-automation:ansible.com">Security</a></td>
       <td>✓</td>
       <td></td>
       <td>✓</td>
@@ -176,7 +176,7 @@ The following table shows:
     <tr>
       <td><a href="https://galaxy.ansible.com/junipernetworks/junos">junipernetworks.junos</a></td>
       <td><a href="https://galaxy.ansible.com/community/network">community.network</a></td>
-      <td><a href="https://github.com/ansible/community/wiki/Network">Network</a></td>
+      <td><a href="https://forum.ansible.com/g/network-wg">Network</a></td>
       <td>✓</td>
       <td>✓</td>
       <td>✓</td>
@@ -187,7 +187,7 @@ The following table shows:
     <tr>
       <td><a href="https://galaxy.ansible.com/kubernetes/core">kubernetes.core</a></td>
       <td><a href="https://galaxy.ansible.com/kubernetes/core">kubernetes.core</a></td>
-      <td><a href="https://github.com/ansible/community/wiki/Kubernetes">Kubernetes</a></td>
+      <td><a href="https://matrix.to:/#/#kubernetes:ansible.com">Kubernetes</a></td>
       <td>✓</td>
       <td>✓</td>
       <td>✓</td>
@@ -198,7 +198,7 @@ The following table shows:
     <tr>
       <td><a href="https://cloud.redhat.com/ansible/automation-hub/redhat/openshift">redhat.openshift</a></td>
       <td><a href="https://galaxy.ansible.com/community/okd">community.okd</a></td>
-      <td><a href="https://github.com/ansible/community/wiki/Kubernetes">Kubernetes</a></td>
+      <td><a href="https://matrix.to:/#/#kubernetes:ansible.com">Kubernetes</a></td>
       <td>✓</td>
       <td>✓</td>
       <td>✓</td>
@@ -208,7 +208,7 @@ The following table shows:
     <tr>
       <td><a href="https://galaxy.ansible.com/openvswitch/openvswitch">openvswitch.openvswitch</a></td>
       <td><a href="https://galaxy.ansible.com/community/network">community.network</a></td>
-      <td><a href="https://github.com/ansible/community/wiki/Network">Network</a></td>
+      <td><a href="https://forum.ansible.com/g/network-wg">Network</a></td>
       <td>✓</td>
       <td>✓</td>
       <td>✓</td>
@@ -219,7 +219,7 @@ The following table shows:
     <tr>
       <td><a href="https://github.com/ansible-collections/splunk.es">splunk.es</a></td>
       <td><a href="https://github.com/ansible-collections/community.es">community.es</a></td>
-      <td><a href="https://github.com/ansible/community/wiki/Security-Automation">Security</a></td>
+      <td><a href="https://matrix.to/#/#security-automation:ansible.com">Security</a></td>
       <td>✓</td>
       <td></td>
       <td>✓</td>
@@ -230,7 +230,7 @@ The following table shows:
     <tr>
       <td><a href="https://galaxy.ansible.com/vyos/vyos">vyos.vyos</a></td>
       <td><a href="https://galaxy.ansible.com/community/network">community.network</a></td>
-      <td><a href="https://github.com/ansible/community/wiki/Network">Network</a></td>
+      <td><a href="https://forum.ansible.com/g/network-wg">Network</a></td>
       <td>✓</td>
       <td>✓</td>
       <td>✓</td>
@@ -241,7 +241,7 @@ The following table shows:
     <tr>
       <td><a href="https://galaxy.ansible.com/vmware/vmware_rest">vmware.vmware_rest</a></td>
       <td><a href="https://galaxy.ansible.com/vmware/vmware_rest">vmware.vmware_rest</a></td>
-      <td><a href="https://github.com/ansible/community/wiki/VMware">VMware</a></td>
+      <td><a href="https://matrix.to:/#/#vmware:ansible.com">VMware</a></td>
       <td>✓</td>
       <td>✓</td>
       <td>✓</td>

docs/docsite/rst/community/contributor_path.rst

@@ -111,4 +111,4 @@ To reach the status, as the current Committee members did before getting it, alo
 
 * Subscribe to, comment on, and vote on the `Community Topics <https://github.com/ansible-community/community-topics/issues>`_.
 * Propose your topics.
-* If time permits, join the `Community meetings <https://github.com/ansible/community/blob/main/meetings/README.md#schedule>`_. Note this is **NOT** a requirement.
+* If time permits, join the `Community meetings <https://github.com/ansible-community/meetings/blob/main/README.md#schedule>`_. Note this is **NOT** a requirement.

docs/docsite/rst/community/documentation_contributions.rst

@@ -231,7 +231,7 @@ It is recommended to run tests on a clean copy of the repository, which is the p
 Joining the documentation working group
 =======================================
 
-The Documentation Working Group (DaWGs) meets weekly on Tuesdays in the Docs chat (using `Matrix <https://matrix.to/#/#docs:ansible.im>`_ or using IRC at `irc.libera.chat <https://libera.chat/>`_). For more information, including links to our agenda and a calendar invite, please visit the `working group page in the community repo <https://github.com/ansible/community/wiki/Docs>`_.
+The Documentation Working Group (DaWGs) meets weekly on Tuesdays in the Docs chat (using `Matrix <https://matrix.to/#/#docs:ansible.im>`_ or using IRC at `irc.libera.chat <https://libera.chat/>`_). For more information, including links to our agenda and a calendar invite, visit our `forum group <https://forum.ansible.com/g/Docs>`_.
 
 .. seealso::
    :ref:`More about testing module documentation <testing_module_documentation>`