Merge branch 'main' into 2023-04-19-meeting-notes

Author: jakirkham

src/conf.py

@@ -131,6 +131,7 @@
     r'https://app.element.io/#/room/#conda-forge-space:matrix.org',  # needs login
     r'https://anacondacon.io/.*$',  # website is gone
     r'https://matrix.to/#.*$',  # anchors are generated dynamically
+    r'https://app.element.io/#.*$',  # anchors are generated dynamically
     r'https://wave.webaim.org/report#.*$',  # anchors are generated dynamically
 ] + anchor_check_fps
 

src/maintainer/infrastructure.rst

@@ -101,14 +101,6 @@ Note that this update command is kind of a hack, and things might go wrong. Make
 
 Entering the above phrase in a PR of a feedstock will lint the PR again.
 
-.. _ci_update_circle:
-
-@conda-forge-admin, please update circle
-----------------------------------------
-
-Entering the above phrase in an issue of a feedstock will update the Circle-CI SSH deploy key. This will fix the
-``permission denied (public key)`` issue in Circle-CI's checkout phase; it shouldn't be needed otherwise.
-
 
 @conda-forge-admin, please update team
 --------------------------------------
@@ -202,10 +194,10 @@ of the feedstock.
   certain very old packages that require VC9 will fail.
 
 
-TravisCI (OSX, IBM Power 8+)
+TravisCI (IBM Power 8+, ARM)
 ------------------------------
 
-TravisCI is used to build packages for IBM Power 8+. After merging a staged-recipes pull request, it might be necessary to
+TravisCI is used to build packages for IBM Power 8+ and ARM. After merging a staged-recipes pull request, it might be necessary to
 force sync your repositories in TravisCI to see the reload and cancel buttons. To do this please visit `<https://app.travis-ci.com/account/repositories>`__
 and click the "Sync accounts" button.
 
@@ -221,64 +213,11 @@ Enable a build by adding the following to ``conda-forge.yml`` in the root of the
     provider:
       osx: travis
 
-For IBM Power 8+ builds, add the name of your feedstock to the list `here
+For IBM Power 8+ and/or ARM builds, add the name of your feedstock to the list `here
 <https://github.com/conda-forge/conda-forge-pinning-feedstock/blob/master/recipe/migrations/arch_rebuild.txt>`__
 via a pull request.
 
 
-CircleCI (Linux, OSX)
-----------------------
-CircleCI is a container-based CI service that conda-forge uses to build
-Linux packages. It can optionally build OSX packages.
-
-Linux builds are identical to those on Azure as both are built inside Docker containers.
-
-
-Using Circle for both Linux and OSX
-....................................
-
-To use CircleCI for OSX, add the following to ``conda-forge.yml`` in the root of the feedstock.
-
-.. code-block:: yaml
-
-    provider:
-      osx: circle
-      linux: circle
-
-CircleCI for OSX should be used for OSX, only when TravisCI resources (50 minutes of build time per job) are not enough as CircleCI gives more resources (2 hours of build time per job).
-
-Note that you need to rerender the feedstock, once this change has been made.
-
-
-Debugging permission errors
-...........................
-
-If CircleCI lacks permissions to checkout the source code, it will produce an error as follows::
-
-    Cloning into '.'...
-    Warning: Permanently added the RSA host key for IP address '192.30.253.113' to the list of known hosts.
-    Permission denied (publickey).
-    fatal: Could not read from remote repository.
-
-When this happens for a feedstock, it can be fixed using the `webservice <ci_update_circle>`, by posting the following comment::
-
-  @conda-forge-admin, please update circle
-
-Otherwise (e.g. in a PR to staged-recipes), here are some things you can try:
-
-* Log in and out of Circle CI.
-* Revoke CircleCI's access and then enable it again.
-* In the "Checkout SSH keys" section of your Circle CI project settings, press "add user key".
-
-
-Drone.io
---------
-
-We use `Drone.io <https://drone.io>`__ for Linux ARMv8 builds. To enable these builds on your feedstock, make a pull request to add your feedstock to the list
-in the `arch_rebuild.txt file <https://github.com/conda-forge/conda-forge-pinning-feedstock/blob/master/recipe/migrations/arch_rebuild.txt>`__.
-Read :ref:`using_arch_rebuild` to learn more.
-
-
 GitHub Actions
 --------------
 

src/maintainer/maintainer_faq.rst

@@ -1,25 +1,6 @@
 FAQ
 ===
 
-.. _mfaq_update_circle:
-
-:ref:`(Q) <mfaq_update_circle>` **How to address** ``permission denied (publickey)`` **in circle builds?**
-
-  When you see this error in a circle build:
-  ::
-
-    Permission denied (publickey).
-
-    fatal: Could not read from remote repository.
-
-    Please make sure you have the correct access rights
-    and the repository exists.
-    Exited with code 128
-
-  Open a new issue with a comment :ref:`ci_update_circle`.
-  Once our web services have updated the circle configuration, restart the build.
-
-
 .. _mfaq_py37_selector:
 
 :ref:`(Q) <mfaq_py37_selector>` **Why does conda-build ignore the** ``py37`` **selector in meta.yaml?**

src/orga/getting-in-touch.rst

@@ -14,8 +14,8 @@ The main issue trackers that you will interact with are
 * `Our main docs repo <https://github.com/conda-forge/conda-forge.github.io/issues>`__: You'll use this repo as a catch-all for issues where you're not sure where else to put them
 * `Our enhancement proposals repo <https://github.com/conda-forge/cfep/issues>`__: You'll use the enhancement proposals repo if you're interested in substantially changing the way conda-forge operates.
 
-Gitter
------------------
+Gitter and Element
+-------------------------
 
 The main chat rooms that you'll interact with are
 
@@ -26,6 +26,11 @@ The main chat rooms that you'll interact with are
 * `gitter: bot subteam <https://gitter.im/conda-forge/regro-cf-autotick-bot>`__: Public chat room for all things related to the conda-forge automation infrastructure.
   Our automation infrastructure is colloquially referred to as "the bot".
 * `gitter: compilers <https://gitter.im/conda-forge/conda-forge-compilers>`__: Public chat room focused on the conda-forge compiler stack.
+* `element: conda-forge-space <https://app.element.io/#/room/#conda-forge-space:matrix.org>`__: An element space listing all conda-forge rooms.
+* `element: interns <https://app.element.io/#/room/#conda-forge_conda-forge-interns:gitter.im>`__: Public chat room for conda-forge interns to discuss projects and seek guidance from the community.
+* `element: general <https://app.element.io/#/room/#conda-forge:matrix.org>`__: Public chat room for the conda-forge community to discuss anything related to conda-forge.
+
+Note: All Gitter room links forward to Element
 
 Mailing List
 -----------------

src/user/tipsandtricks.rst

@@ -101,6 +101,12 @@ the local version matches the ``conda`` version within the proper ABI range, the
 work. At runtime, the ``conda-forge`` package that depends on MPI should find the 
 local copy of ``mpich``/``openmpi`` and link to it.
 
+Another point for using your own MPI binaries specialized for the system is that
+if you care about ultimate performance, you should build/install your MPI backend yourself,
+and not rely on ``conda-forge`` packages (they are built for compatibility rather than performance).
+Due to the constrained build environment of ``conda-forge`` packages there might be the lack of such important features
+as XPMEM and CMA for ``mpich`` and ``openmpi``, respectively.
+
 
 .. _apple_silicon_rosetta: