replace gitter with element

Author: mhmohona

.github/ISSUE_TEMPLATE/config.yml

@@ -1,7 +1,7 @@
 blank_issues_enabled: true
 contact_links:
-  - name: Conda-forge gitter chat
-    url: https://gitter.im/conda-forge/conda-forge.github.io
+  - name: Conda-forge Element chatroom
+    url: https://app.element.io/#/room/#conda-forge:matrix.org
     about: Chat to us about conda-forge and ask general questions.
   - name: Conda-forge documentation
     url: https://conda-forge.org/docs/

index.html.tmpl

@@ -294,7 +294,7 @@
                       </ul>
                     </p>
                     <p>
-                        Please consider joining our <a href="https://gitter.im/conda-forge/conda-forge.github.io">Gitter</a> channel if you want to ask something, need help, or just want to chat with our maintainers. We would love to see you there!
+                        Please consider joining our <a href="https://app.element.io/#/room/#conda-forge:matrix.org">Element</a> chatroom if you want to ask something, need help, or just want to chat with our maintainers. We would love to see you there!
                     </p>
                 </div>
             </div>

newsfeed/demo/announcements.rst

@@ -32,7 +32,7 @@ Announcements
     to anaconda.org. Direct uploads to the ``conda-forge`` channel will no
     longer work. If you are having trouble with package uploads, please
     rerender your feedstock with the latest version of ``conda-smithy``.
-    As always, if you need help, bump us on gitter or GitHub!
+    As always, if you need help, bump us on element chatroom or GitHub!
 
 :2020-08-06: Fixed Maintenance Process for Feedstock Teams
 
@@ -173,7 +173,7 @@ Announcements
 
     Despite our extensive testing, we do not expect this change to be completely smooth,
     so please bear with us. As always, if you have any questions, concerns, or trouble, you
-    can find us on gitter or bump us directly on github!
+    can find us on Element chatroom or bump us directly on github!
 
 :2020-03-24: ``vs2015`` to ``vs2017`` Transition
 

src/contracting/00_intro.rst

@@ -6,7 +6,7 @@ However, there are a number of community members that you may engage with.
 Conda-forge does not endorse anyone (individuals or companies) listed on this page.
 
 
-If you are interested in a service that is not listed on this page, please reach out to us on our `issue tracker <https://github.com/conda-forge/conda-forge.github.io/issues>`__, on  `gitter <https://gitter.im/conda-forge/conda-forge.github.io>`__  or via emailing the core team directly at [email protected] and we will help to circulate your request more broadly within the community.
+If you are interested in a service that is not listed on this page, please reach out to us on our `issue tracker <https://github.com/conda-forge/conda-forge.github.io/issues>`__, on  `Element <https://app.element.io/#/room/#conda-forge:matrix.org>`__  or via emailing the core team directly at [email protected] and we will help to circulate your request more broadly within the community.
 
 Our intent with this page is to communicate whom you should contact and negotiate a contract with.
 We hold no liability for the outcome of those negotiations or the results of any work that is done under those terms.

src/index.rst

@@ -19,7 +19,7 @@ Chances are we have already packaged it for you. You can `search <https://anacon
 - If you find bugs, need help, or want to talk to the developers, use our mailing lists or chat rooms:
 
   - `GitHub issues <https://github.com/conda-forge/conda-forge.github.io/issues>`_
-  - `Gitter channel <https://gitter.im/conda-forge/conda-forge.github.io>`_
+  - `Element chatroom <https://app.element.io/#/room/#conda-forge:matrix.org>`_
   - `Discourse group <https://conda.discourse.group>`_
   - `Mailing list (archived) <https://groups.google.com/forum/#!forum/conda-forge>`_
 

src/maintainer/maintainer_faq.rst

@@ -146,7 +146,7 @@ FAQ
 :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.
+  If you don't receive an an answer after a couple of days, feel free to reach out to us via the public `element <https://app.element.io/#/room/#conda-forge:matrix.org>`__ chatroom.
 
   .. note::
 

src/maintainer/updating_pkgs.rst

@@ -168,7 +168,7 @@ We need to re-render when there are changes in the following parts of the feedst
 - ``yum_requirements.txt`` or ``conda-forge.yml``.
 - Updates in the build matrix due to new versions of Python, NumPy, PERL, R, etc.
 - Updates in conda-forge pinning that affect the feedstock.
-- Build issues that a feedstock configuration update will fix (follow us on `gitter <https://gitter.im/conda-forge/conda-forge.github.io>`_ to know about those).
+- Build issues that a feedstock configuration update will fix (follow us on `element <https://app.element.io/#/room/#conda-forge:matrix.org>`_ to know about those).
 
 Updating for newly released Python version
 ==========================================
@@ -286,7 +286,7 @@ an issue in the feedstock repository with the following title:
 
 where ``username`` is the username of the new maintainer to be added.
 A PR will be automatically created and a maintainer or a member of the ``core`` team, in case no maintainer is active anymore, can then merge this PR to add the user. 
-To contact core, ping them by mentioning @conda-forge/core in a comment or, if you haven't heard back in a while or are new to conda-forge, contact them through the community `gitter <https://gitter.im/conda-forge/conda-forge.github.io>`__.
+To contact core, ping them by mentioning @conda-forge/core in a comment or, if you haven't heard back in a while or are new to conda-forge, contact them through the community `element <https://app.element.io/#/room/#conda-forge:matrix.org>`__.
 
 .. note::
 

src/orga/governance.rst

@@ -160,11 +160,11 @@ To call for a standard vote, here is a template PR comment:
 
          * been open for at least 2 weeks
          * been presented and discussed at a Core team meeting
-         * been advertised on at least 3 separate occasions on the gitter core
-           channel (beginning of voting period, middle, and one day prior to
+         * been advertised on at least 3 separate occasions on the element core
+           chatroom (beginning of voting period, middle, and one day prior to
            proposed timeout)
          * been sent to core members via email.  Email reminders must have been
-           sent to the core email list in a manner similar to the gitter channel: at least 3 times,
+           sent to the core email list in a manner similar to the element chatroom: at least 3 times,
            occurring as beginning of voting period, middle, and one day
            prior to proposed timeout.
 

src/orga/joining-the-team.rst

@@ -19,7 +19,7 @@ for officially interfacing with external communities, organizations, non-profits
 and companies. They are also responsible for maintaining conda-forge's infrastructure.
 
 If you are interested in joining the core team, please get in touch with us on our
-`Gitter Channel <https://gitter.im/conda-forge/conda-forge.github.io>`__.
+`Element Chatroom <https://app.element.io/#/room/#conda-forge:matrix.org>`__.
 Core members are added via a vote amongst the current core team. The core team
 member who is running your vote will ask you to provide sufficient justification
 as to why you should be nominated to core. Prior service to the community, including
@@ -46,7 +46,7 @@ Generally speaking, your role is as follows:
 4. Helping recipe maintainers who bump the ``conda-forge/help-*`` teams.
 
 To join the staged-recipes team, please ask one of the core members on our
-`Gitter Channel <https://gitter.im/conda-forge/conda-forge.github.io>`__.
+`Element Chatroom <https://app.element.io/#/room/#conda-forge:matrix.org>`__.
 We will then reach consensus in private and let you know our decision.
 Our decision will likely be "yes" but it could be "please get more involved
 with the review process on staged recipes first" if we have not seen you

src/user/announcements.rst

@@ -13,7 +13,7 @@ Our announcements are published to an RSS feed `here <https://conda-forge.org/do
 
 We have made the ``conda-forge`` Google Group read-only. Please use the new 
 ``conda-forge`` `discourse forum <https://conda.discourse.group/c/pkg-building/conda-forge/25>`_, 
-our `Gitter room <https://gitter.im/conda-forge/conda-forge.github.io>`_, or it's `Matrix/Element 
+our `Element Chatroom <https://app.element.io/#/room/#conda-forge:matrix.org>`_, or it's `Matrix/Element 
 counterpart <https://app.element.io/#/room/#conda-forge-space:matrix.org>`_ instead.
 
 
@@ -313,7 +313,7 @@ We have now completed rolling out the new staging process for uploads
 to anaconda.org. Direct uploads to the ``conda-forge`` channel will no
 longer work. If you are having trouble with package uploads, please
 rerender your feedstock with the latest version of ``conda-smithy``.
-As always, if you need help, bump us on Gitter or GitHub!
+As always, if you need help, bump us on Element chatroom or GitHub!
 
 
 2020-08-06: Fixed Maintenance Process for Feedstock Teams
@@ -476,7 +476,7 @@ What will you see as a feedstock maintainer?
 
 Despite our extensive testing, we do not expect this change to be completely smooth,
 so please bear with us. As always, if you have any questions, concerns, or trouble, you
-can find us on Gitter or bump us directly on Github!
+can find us on Element chatroom or bump us directly on Github!
 
 
 2020-03-24: ``vs2015`` to ``vs2017`` Transition