Merge pull request #1529 from Andersson007/update_overview_links

Requesting a collection: replace overview links

docs/docsite/rst/community/communication.rst

@@ -187,9 +187,15 @@ Anyone can request to start a Working Group, for any reason.
 If you need only a `Forum group <https://forum.ansible.com/g>`_, 
 request it in the `forum topic <https://forum.ansible.com/t/requesting-a-forum-group/503>`_.
 
-
 If you also need a real-time chat channel, you can `request one <https://hackmd.io/@ansible-community/community-matrix-faq#How-do-I-create-a-public-community-room>`_.
 
+.. _request_coll_repo:
+
+Requesting a community collection repository
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Working groups are often built around Ansible community collections. You can use a repository under your organization or request one under `ansible-collections <https://github.com/ansible-collections>`_ on the forum by creating a topic in the `Project Discussions category and the coll-repo-request tag <https://forum.ansible.com/new-topic?category=project&tags=coll-repo-request>`_.
+
 .. _community_topics:
 
 Ansible Community Topics

docs/docsite/rst/dev_guide/developing_collections.rst

@@ -43,8 +43,6 @@ For instructions on developing modules, see :ref:`developing_modules_general`.
        Learn how to install and use collections in playbooks and roles
    :ref:`contributing_maintained_collections`
        Guidelines for contributing to selected collections
-   `Ansible Collections Overview and FAQ <https://github.com/ansible-collections/overview/blob/main/README.rst>`_
-       Current development status of community collections and FAQ
    `Mailing List <https://groups.google.com/group/ansible-devel>`_
        The development mailing list
    :ref:`communication_irc`

docs/docsite/rst/dev_guide/developing_collections_creating.rst

@@ -26,23 +26,23 @@ Collection names consist of a namespace and a name, separated by a period (``.``
 
     Usually namespaces and names use lower-case letters, digits, and underscores, but no upper-case letters.
 
-You should make sure that the namespace you use is not registered by someone else by checking on `Ansible Galaxy's namespace list <https://galaxy.ansible.com/ui/namespaces/>`__. If you chose a namespace or even a full collection name that collides with another collection on Galaxy, it can happen that if you or someone else runs ``ansible-galaxy collection install`` with your collection name, you end up with another collection. Even if the namespace currently does not exist, it could be created later by someone else.
+You should make sure that the namespace you use is not registered by someone else by checking on `Ansible Galaxy's namespace list <https://galaxy.ansible.com/ui/namespaces/>`_. If you chose a namespace or even a full collection name that collides with another collection on Galaxy, it can happen that if you or someone else runs ``ansible-galaxy collection install`` with your collection name, you end up with another collection. Even if the namespace currently does not exist, it could be created later by someone else.
 
-If you want to request a new namespace on Ansible Galaxy, `create an issue on github.com/ansible/galaxy <https://github.com/ansible/galaxy/issues/new?assignees=thedoubl3j%2C+alisonlhart%2C+chynasan%2C+traytorous&labels=area%2Fnamespace&projects=&template=New_namespace.md&title=namespace%3A+FIXME>`__.
+If you want to request a new namespace on Ansible Galaxy, `create an issue on github.com/ansible/galaxy <https://github.com/ansible/galaxy/issues/new?assignees=thedoubl3j%2C+alisonlhart%2C+chynasan%2C+traytorous&labels=area%2Fnamespace&projects=&template=New_namespace.md&title=namespace%3A+FIXME>`_.
 
 There are a few special namespaces:
 
 :ansible:
 
-  The `ansible namespace <https://galaxy.ansible.com/ui/namespaces/ansible/>`__ is owned by Red Hat and reserved for official Ansible collections. Two special members are the synthetic ``ansible.builtin`` and ``ansible.legacy`` collections. These cannot be found on Ansible Galaxy, but are built-in into ansible-core.
+  The `ansible namespace <https://galaxy.ansible.com/ui/namespaces/ansible/>`_ is owned by Red Hat and reserved for official Ansible collections. Two special members are the synthetic ``ansible.builtin`` and ``ansible.legacy`` collections. These cannot be found on Ansible Galaxy, but are built-in into ansible-core.
 
 :community:
 
-  The `community namespace <https://galaxy.ansible.com/ui/namespaces/community/>`__ is owned by the Ansible community. Collections from this namespace generally live in the `GitHub ansible-collection organization <https://github.com/ansible-collections/>`__. If you want to create a collection in this namespace, it is best to `create an issue in github.com/ansible-collections/overview <https://github.com/ansible-collections/overview/issues/new?assignees=&labels=repo&projects=&template=request-a-new-repo.md&title=repo%3A+%24NAME>`__.
+  The `community namespace <https://galaxy.ansible.com/ui/namespaces/community/>`_ is owned by the Ansible community. Collections from this namespace generally live in the `GitHub ansible-collection organization <https://github.com/ansible-collections/>`_. If you want to create a collection in this namespace, :ref:`request<request_coll_repo>` it on the forum.
 
 :local:
 
-  The `local namespace <https://galaxy.ansible.com/ui/namespaces/local/>`__ does not contain any collection on Ansible Galaxy, and the intention is that this will never change. You can use the ``local`` namespace for collections that are locally on your machine or locally in your git repositories, without having to fear collisions with actually existing collections on Ansible Galaxy.
+  The `local namespace <https://galaxy.ansible.com/ui/namespaces/local/>`_ does not contain any collection on Ansible Galaxy, and the intention is that this will never change. You can use the ``local`` namespace for collections that are locally on your machine or locally in your git repositories, without having to fear collisions with actually existing collections on Ansible Galaxy.
 
 .. _creating_new_collections:
 

docs/docsite/rst/dev_guide/developing_collections_path.rst

@@ -79,7 +79,7 @@ Publish your collection source code
 Publish your collection on a platform for software development and version control such as `GitHub <https://github.com/>`_.
 
 It can be your personal repository or your organization's one.
-You can also `request <https://github.com/ansible-collections/overview/issues>`_ a repository under the `ansible-collections <https://github.com/ansible-collections/>`_ organization.
+You can also :ref:`request<request_coll_repo>` a repository under the `ansible-collections <https://github.com/ansible-collections/>`_ organization.
 
 Make sure your collection contains exhaustive license information.
 Ansible is an open source project, so we encourage you to license it under one of open source licenses.