You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/maintainer/maintainer_faq.rst
+13-11Lines changed: 13 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -168,22 +168,24 @@ FAQ
168
168
169
169
.. _mfaq_contact_core:
170
170
171
-
:ref:`(Q) <mfaq_contact_core>` **How can I contact `conda-forge/core <https://conda-forge.org/docs/orga/governance.html?highlight=core#teams-roles>`_?**
171
+
:ref:`(Q) <mfaq_contact_core>` **How can I contact conda-forge/core?**
172
+
173
+
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.
174
+
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.
172
175
173
-
When in an issue or PR, you can contact core 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.
174
-
175
176
.. note::
176
-
177
-
Due to a GitHub limitation, this is disabled for new members.
178
-
In that case, we suggest asking your question in our public `gitter <https://gitter.im/conda-forge/conda-forge.github.io>`_ channel.
179
177
178
+
Due to a GitHub limitation, this is disabled for new members.
179
+
In that case, we suggest asking your question in our `gitter <https://gitter.im/conda-forge/conda-forge.github.io>`_ channel instead.
180
+
181
+
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>`_.
180
182
181
183
.. _mfaq_abandoned_feedstock:
182
184
183
-
:ref:`(Q) <mfaq_abandoned_feedstock>` **A feedstock has been abandoned and I would like to take over maintenance?**
185
+
:ref:`(Q) <mfaq_abandoned_feedstock>` **A feedstock has been abandoned and I would like to take over maintenance.**
186
+
187
+
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.
188
+
189
+
.. note::
184
190
185
-
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 it's maintenance.
186
-
187
-
.. note::
188
-
189
191
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.
0 commit comments