Merge pull request #1553 from BastianZim/contact-core

How to contact core and deal with abandoned feedstocks.

Author: isuruf

src/maintainer/infrastructure.rst

@@ -128,6 +128,13 @@ Entering this command in the PR of a feedstock or staged-recipes will have the a
 associated with the repo. This command can be useful for people who are not yet members of conda-forge and
 so cannot @-mention the ``staged-recipes`` team for PR reviews.
 
+@conda-forge-admin, please ping conda-forge/<team>
+------------------------------------
+
+Entering this command in the PR of a feedstock or staged-recipes will have the admin bot @-mention the respective team.
+This command can be useful for people who are not yet members of conda-forge and
+so cannot @-mention someone due to the general GitHub limitations.
+
 @conda-forge-admin, please rerun bot
 ------------------------------------
 
@@ -291,23 +298,23 @@ GitHub Actions.
 Automerge
 .........
 
-The automerge service uses the GitHub action in this `repo <https://github.com/conda-forge/automerge-action>`_. This action runs out of a 
-Docker `container <https://hub.docker.com/repository/docker/condaforge/automerge-action>`_ on the ``prod`` tag. See the 
-repo `README.md <https://github.com/conda-forge/automerge-action#readme>`_ for more details. PRs are automatically merged if they satisfy either 
+The automerge service uses the GitHub action in this `repo <https://github.com/conda-forge/automerge-action>`_. This action runs out of a
+Docker `container <https://hub.docker.com/repository/docker/condaforge/automerge-action>`_ on the ``prod`` tag. See the
+repo `README.md <https://github.com/conda-forge/automerge-action#readme>`_ for more details. PRs are automatically merged if they satisfy either
 of the two following sets of conditions:
 
 1. are from the ``regro-cf-autotick-bot``, have ``[bot-automerge]`` in the title, all statuses are passing, and the feedstock allows automerge
-2. have the ``automerge`` label and all statuses are passing. 
+2. have the ``automerge`` label and all statuses are passing.
 
-For PRs from the ``regro-cf-autotick-bot``, it can be useful to remove the ``[bot-automerge]`` slug from the PR title if you are making 
+For PRs from the ``regro-cf-autotick-bot``, it can be useful to remove the ``[bot-automerge]`` slug from the PR title if you are making
 edits to the PR.
 
 Rerendering
 ...........
 
-The rerendering service is triggered by the Heroku app. It uses the GitHub action in this `repo <https://github.com/conda-forge/webservices-dispatch-action>`_. 
-This action runs out of a Docker `container <https://hub.docker.com/repository/docker/condaforge/webservices-dispatch-action>`_ on the ``prod`` tag. See the 
-repo `README.md <https://github.com/conda-forge/webservices-dispatch-action#readme>`_ for more details. 
+The rerendering service is triggered by the Heroku app. It uses the GitHub action in this `repo <https://github.com/conda-forge/webservices-dispatch-action>`_.
+This action runs out of a Docker `container <https://hub.docker.com/repository/docker/condaforge/webservices-dispatch-action>`_ on the ``prod`` tag. See the
+repo `README.md <https://github.com/conda-forge/webservices-dispatch-action#readme>`_ for more details.
 
 
 Skipping CI builds

src/maintainer/maintainer_faq.rst

@@ -164,3 +164,28 @@ FAQ
     build:
       script_env:
         - QT_QPA_PLATFORM=offscreen
+
+
+.. _mfaq_contact_core:
+
+:ref:`(Q) <mfaq_contact_core>` **How can I contact conda-forge/core?**
+
+  When in an issue or PR, you can contact `conda-forge/core <https://conda-forge.org/docs/orga/governance.html#teams-roles>`_ by simply mentioning ``@conda-forge/core`` in a comment.
+  If you don't receive an an answer after a couple of days, feel free to reach out to us via the public `gitter <https://gitter.im/conda-forge/conda-forge.github.io>`_ channel.
+
+  .. note::
+
+    Due to a GitHub limitation, this is disabled for new members.
+    In that case, you can ping core using the bot command `@conda-forge-admin, please ping conda-forge/core <https://conda-forge.org/docs/maintainer/infrastructure.html#conda-forge-admin-please-ping-conda-forge-team>`_.
+
+  In case your issue is longer or you would like to contact us privately, feel free to reach out to us via the options listed `here <https://conda-forge.org/docs/orga/governance.html#teams-roles>`_.
+
+.. _mfaq_abandoned_feedstock:
+
+:ref:`(Q) <mfaq_abandoned_feedstock>` **A feedstock has been abandoned and I would like to take over maintenance.**
+
+  A  feedstock is generally considered abandoned when the maintainer isn't around anymore and doesn't merge new PRs or answer any issues. If that is the case, you can add yourself to the team by using the `@conda-forge-admin, please add user @username <https://conda-forge.org/docs/maintainer/infrastructure.html#conda-forge-admin-please-add-user-username>`_ command. If the maintainer doesn't merge it after roughly a week, :ref:`contact conda-forge/core<mfaq_contact_core>` to have it merged. Once added, you have full rights to the feedstock and can continue its maintenance.
+
+  .. note::
+
+    Even if the maintainer isn't active anymore, we generally like to keep them in the list of maintainers and not remove them, in case they want to take up maintenance at a later date.