Merge branch 'main' into 2024-11-13-meeting-notes

beckermr · web-flow · commit 314e6c8b25bd · 2024-11-07T05:30:54.000-06:00
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
@@ -1,11 +1,11 @@
 blank_issues_enabled: true
 contact_links:
-  - name: Conda-forge Element chatroom
-    url: https://app.element.io/#/room/#conda-forge:matrix.org
+  - name: Conda-forge Zulip chatroom
+    url: https://conda-forge.zulipchat.com/
     about: Chat to us about conda-forge and ask general questions.
   - name: Conda-forge documentation
     url: https://conda-forge.org/docs/
     about: The complete conda-forge documentation.
   - name: Conda-forge packages
-    url: https://conda-forge.org/feedstock-outputs/
+    url: https://conda-forge.org/packages/
     about: For when you have an issue with a specific package.
diff --git a/.github/workflows/deploy.yml b/.github/workflows/deploy.yml
@@ -12,7 +12,7 @@ jobs:
     name: deploy
     runs-on: "ubuntu-latest"
     steps:
-      - uses: actions/checkout@d632683dd7b4114ad314bca15554477dd762a938 # v4.2.0
+      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
 
       - uses: conda-incubator/setup-miniconda@a4260408e20b96e80095f42ff7f1a15b27dd94ca # v3.0.4
         with:
@@ -43,10 +43,9 @@ jobs:
           user_email: pelson.pub+conda-forge@gmail.com
 
       - name: Link Checker
-        uses: lycheeverse/lychee-action@2b973e86fc7b1f6b36a93795fe2c9c6ae1118621 # v1.10.0
+        uses: lycheeverse/lychee-action@7cd0af4c74a61395d455af97419279d86aafaede # v2.0.2
         with:
           token: ${{ secrets.GITHUB_TOKEN }}
-          lycheeVersion: "0.14.3"
           args: >
             --no-progress
             --timeout 60
diff --git a/.pre-commit-config.yaml b/.pre-commit-config.yaml
@@ -15,7 +15,7 @@ repos:
       - id: prettier
         types_or: [markdown, mdx, json, yaml, css, javascript]
   - repo: https://github.com/astral-sh/ruff-pre-commit
-    rev: v0.7.1
+    rev: v0.7.2
     hooks:
       - id: ruff-format
 ci:
diff --git a/README.md b/README.md
@@ -52,19 +52,6 @@ All reports will be kept confidential. Please have a look at the [Reporting guid
 
 conda-forge's team and/or our event staff will try to ensure your safety and help with any immediate needs, particularly at an in-person event. Once we have received the report through the relevant authorities, conda-forge will make every effort to acknowledge the receipt and take action. Have a look at the process of [What Happens After a Report is Filed?](https://numfocus.org/code-of-conduct#enforcement).
 
-## conda-forge dev meetings
+## conda-forge meetings
 
-We hold biweekly meetings every second Wednesday from 17:00-18:00 (UTC). Feel free to stop by!
-Up-to-date invites are always available in the [conda.org community calendar](https://conda.org/community/calendar). Look for the `[conda-forge] core meeting` events!
-
-Our [meeting notes](https://conda-forge.org/docs/orga/minutes/00_intro.html) record important points discussed during the meetings and serve as a record for upcoming meetings. We make use of [HackMd](https://hackmd.io/) and a [template](https://github.com/conda-forge/conda-forge.github.io/blob/main/misc/DEV_MEETING_TEMPLATE.md) to create the meeting notes.
-
-We use a Github Actions [workflow][gha-workflow] to create an automated PR with the meeting notes
-template for each session, which is automatically published to our HackMD team account. During the
-meeting, attendees will edit the HackMD document. After the meeting, the document is saved and the
-PR is synced with the changes by adding the `sync-hackmd-notes` label. Once satisfied, the PR is
-merged and the website will be updated with the new meeting notes.
-
-We encourage contributors to join the meetings and learn more about and from the community.
-
-[gha-workflow]: https://github.com/conda-forge/conda-forge.github.io/actions/workflows/meeting-notes.yml
+Refer to our [Community > Meeting minutes](https://conda-forge.org/community/minutes/) page.
diff --git a/SECURITY.md b/SECURITY.md
@@ -101,7 +101,7 @@ The role responsible for each step is noted at the beginning.
     [private advisory](https://github.com/conda-forge/conda-forge.github.io/security/advisories) for the text.
   - **Coordinator**: Publish the security advisory on the announcement date. If applicable, GitHub
     will post the CVE to the MITRE database.
-  - **Coordinator**: Publish the blog post and other announcements (Element chat room, Twitter,
+  - **Coordinator**: Publish the blog post and other announcements (Zulip, Twitter,
     etc) as necessary.
 - **Coordinator**: Notify the **Reporter** of the releases
 - **Coordinator**: Close the issue in the tracking repository
diff --git a/community/_sidebar.json b/community/_sidebar.json
@@ -14,15 +14,25 @@
   "contracting",
   {
     "type": "category",
-    "label": "Meeting minutes",
+    "label": "Meetings",
     "link": {
       "type": "doc",
-      "id": "minutes"
+      "id": "meetings"
     },
     "items": [
       {
-        "type": "autogenerated",
-        "dirName": "minutes"
+        "type": "category",
+        "label": "Minutes archive",
+        "link": {
+          "type": "doc",
+          "id": "minutes"
+        },
+        "items": [
+          {
+            "type": "autogenerated",
+            "dirName": "minutes"
+          }
+        ]
       }
     ]
   }
diff --git a/community/contracting.md b/community/contracting.md
@@ -8,7 +8,7 @@ If you are interested in a contractual engagement to solve a specific problem th
 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 [Element](https://app.element.io/#/room/#conda-forge:matrix.org) or via emailing the core team directly at [conda-forge-core@googlegroups.com](mailto:conda-forge-core@googlegroups.com) 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 [Zulip](https://conda-forge.zulipchat.com/) or via emailing the core team directly at [conda-forge-core@googlegroups.com](mailto:conda-forge-core@googlegroups.com) 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.
diff --git a/community/getting-in-touch.md b/community/getting-in-touch.md
@@ -14,8 +14,20 @@ The main issue trackers that you will interact with are
 - [Our main website 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.
 
+## Zulip
+
+The main chat platform in use. Sign up at [conda-forge.zulipchat.com](https://conda-forge.zulipchat.com/).
+
 ## Gitter and Element
 
+:::{warning}
+As per CFEP-23, the Gitter/Matrix/Element rooms are no longer in use. Please use [Zulip](#zulip) instead.
+:::
+
+<details>
+
+<summary>Links to deprecated Matrix.io rooms</summary>
+
 The main chat rooms that you'll interact with are
 
 - [gitter: general](https://gitter.im/conda-forge/conda-forge.github.io): Our general chat room for all things conda-forge. Pretty much any question can be asked here and others in the community may be able to help.
@@ -31,6 +43,8 @@ The main chat rooms that you'll interact with are
 
 Note: All Gitter room links forward to Element
 
+</details>
+
 ## Forum
 
 - [conda community discourse forum](https://conda.discourse.group/): The [conda-forge section](https://conda.discourse.group/c/pkg-building/conda-forge/25) is dedicated to discussions of conda-forge.
diff --git a/community/governance.md.tmpl b/community/governance.md.tmpl
@@ -162,11 +162,11 @@ This vote will end on {date}.
   time.  In order for a timeout to occur, the vote must have:
       * 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 element core
+      * been advertised on at least 3 separate occasions on the Zulip 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 element chatroom: at least 3 times,
+        sent to the core email list in a manner similar to the Zulip chatroom: at least 3 times,
         occurring as beginning of voting period, middle, and one day
         prior to proposed timeout.
 
diff --git a/community/index.md b/community/index.md
@@ -8,4 +8,4 @@ title: 'conda-forge community'
 - [Governance](governance.md)
 - [Joining the team](joining-the-team.md)
 - [Contracting](contracting.md)
-- [Meeting minutes](minutes.mdx)
+- [Meetings](meetings.mdx)
diff --git a/community/joining-the-team.md b/community/joining-the-team.md
@@ -21,7 +21,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
-[Element chatroom](https://app.element.io/#/room/#conda-forge:matrix.org).
+[Zulip chatroom](https://conda-forge.zulipchat.com/).
 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
-[Element chatroom](https://app.element.io/#/room/#conda-forge:matrix.org).
+[Zulip chatroom](https://conda-forge.zulipchat.com/).
 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
diff --git a/community/meetings.mdx b/community/meetings.mdx
@@ -0,0 +1,27 @@
+# Community meetings
+
+We hold a series of recurring meetings:
+
+- `⚫ [conda-forge] core meeting`: every second Wednesday, alternating between 17:00-18:00 and 14:00-15:00 (UTC). Despite the name, they are open to everyone. Feel free to stop by! Meeting notes available at [Minutes](minutes.mdx).
+- `⚫ [conda-forge] bot sync`: first Friday of the month at 15:00 (UTC). These are technical meetings meant for infrastructure and tooling contributors. Meeting notes available in [HackMD](https://hackmd.io/@conda-forge/BJE6E1VY2).
+
+We encourage contributors to join the meetings and learn more about and from the community. Look for the events in the calendar below!
+
+## Calendar
+
+import Calendar from '@site/src/components/Calendar';
+
+<Calendar />
+
+## Setup
+
+Our [meeting notes](https://conda-forge.org/community/minutes/) record important points discussed during the meetings and serve as a record for upcoming meetings.
+We make use of [HackMD](https://hackmd.io/) and a [template](https://github.com/conda-forge/conda-forge.github.io/blob/main/misc/DEV_MEETING_TEMPLATE.md) to create the meeting notes.
+
+We use a Github Actions [workflow][gha-workflow] to create an automated PR with the meeting notes
+template for each session, which is automatically published to our HackMD team account. During the
+meeting, attendees will edit the HackMD document. After the meeting, the document is saved and the
+PR is synced with the changes by adding the `sync-hackmd-notes` label. Once satisfied, the PR is
+merged and the website will be updated with the new meeting notes.
+
+[gha-workflow]: https://github.com/conda-forge/conda-forge.github.io/actions/workflows/meeting-notes.yml
diff --git a/community/minutes.mdx b/community/minutes.mdx
@@ -1,25 +1,6 @@
-# Core team meetings
+# Meeting minutes
 
-We hold biweekly meetings every second Wednesday from 17:00-18:00 (UTC). Feel free to stop by!
-Up-to-date invites are always available in the [conda.org community calendar](https://conda.org/community/calendar).
-Look for the `[conda-forge] core meeting` events!
-
-We encourage contributors to join the meetings and learn more about and from the community.
-
-## Setup
-
-Our [meeting notes](https://conda-forge.org/community/minutes/) record important points discussed during the meetings and serve as a record for upcoming meetings.
-We make use of [HackMD](https://hackmd.io/) and a [template](https://github.com/conda-forge/conda-forge.github.io/blob/main/misc/DEV_MEETING_TEMPLATE.md) to create the meeting notes.
-
-We use a Github Actions [workflow][gha-workflow] to create an automated PR with the meeting notes
-template for each session, which is automatically published to our HackMD team account. During the
-meeting, attendees will edit the HackMD document. After the meeting, the document is saved and the
-PR is synced with the changes by adding the `sync-hackmd-notes` label. Once satisfied, the PR is
-merged and the website will be updated with the new meeting notes.
-
-[gha-workflow]: https://github.com/conda-forge/conda-forge.github.io/actions/workflows/meeting-notes.yml
-
-## Minutes
+This is an archive of all the conda-forge core meeeting minutes:
 
 import DocCardList from '@theme/DocCardList';
 
diff --git a/docs/index.md b/docs/index.md
@@ -28,7 +28,7 @@ Chances are we have already packaged it for you. You can [search](https://anacon
 - To see our governance policies, see [Governance](/community/governance/).
 - 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)
-  - [Element chatroom](https://app.element.io/#/room/#conda-forge:matrix.org)
+  - [Zulip chatroom](https://conda-forge.zulipchat.com/)
   - [Discourse group](https://conda.discourse.group)
   - [Mailing list (archived)](https://groups.google.com/forum/#!forum/conda-forge)
 
diff --git a/docs/maintainer/knowledge_base.md b/docs/maintainer/knowledge_base.md
@@ -809,11 +809,11 @@ build:
 
 requirements:
   host:
-    - python
+    - python {{ python_min }}.*
     - nodejs
     - pip
   run:
-    - python
+    - python >={{ python_min }}
     - nodejs
     - jupyterlab >=2
 ```
@@ -1480,6 +1480,31 @@ In order to qualify as a noarch python package, all of the following criteria mu
   in the `build` section of `meta.yaml`
 - No activate scripts
 
+All recipes employing `noarch: python` should use the `python_min` variable per the following example:
+
+```yaml title="recipe/meta.yaml"
+name: package
+source:
+  # ...
+build:
+  noarch: python
+  # ...
+requirements:
+  host:
+    - python {{ python_min }}
+    # ...
+  run:
+    - python >={{ python_min }}
+    # ...
+
+test:
+  requires:
+    - python {{ python_min }}
+    # ...
+```
+
+See [CFEP-25](https://github.com/conda-forge/cfep/blob/main/cfep-25.md) for more details on this syntax.
+
 :::note
 
 While `noarch: python` does not work with selectors, it does work with version constraints.
@@ -1576,10 +1601,10 @@ build:
   noarch: python
 requirements:
   host:
-    - python >=3.7
+    - python {{ python_min }}.*
     # ...
   run:
-    - python >=3.7
+    - python >={{ python_min }}
     - numpy
     - __unix  # [unix]
     - __win   # [win]
@@ -1614,7 +1639,7 @@ build:
 requirements:
   # ...
   run:
-    - python
+    - python >={{ python_min }}
     - numpy
     - __linux  # [linux]
     - __osx    # [osx]
diff --git a/docs/maintainer/maintainer_faq.md b/docs/maintainer/maintainer_faq.md
@@ -174,7 +174,7 @@ build:
 ## How can I contact conda-forge/core?
 
 When in an issue or PR, you can contact [conda-forge/core](/community/governance/#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 [Element](https://app.element.io/#/room/#conda-forge:matrix.org) chatroom.
+If you don't receive an an answer after a couple of days, feel free to reach out to us via the public [Zulip chatroom](https://conda-forge.zulipchat.com/).
 
 :::note
 
diff --git a/docs/maintainer/updating_pkgs.md b/docs/maintainer/updating_pkgs.md
@@ -179,7 +179,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 [Element](https://app.element.io/#/room/#conda-forge:matrix.org) to know about those).
+- Build issues that a feedstock configuration update will fix (follow us on [Zulip](https://conda-forge.zulipchat.com/) to know about those).
 
 <a id="updating-for-newly-released-python-version"></a>
 
@@ -301,7 +301,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 [Element](https://app.element.io/#/room/#conda-forge:matrix.org).
+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 [Zulip chatroom](https://conda-forge.zulipchat.com/).
 
 :::note
 
diff --git a/docs/user/faq.md b/docs/user/faq.md
@@ -36,7 +36,7 @@ You can open an issue in the packages feedstock repository on GitHub. Search for
 
 ## I have a question/suggestion. How can I contact you?
 
-Please join us on our [Element chatroom](https://app.element.io/#/room/#conda-forge:matrix.org). We are always happy to answer questions and help beginners.
+Please join us on our [Zulip chatroom](https://conda-forge.zulipchat.com/). We are always happy to answer questions and help beginners.
 
 <a id="faq-teams"></a>
 
diff --git a/docs/user/how_to_get_help.md b/docs/user/how_to_get_help.md
@@ -6,14 +6,14 @@ title: 'How to get help at conda-forge'
 
 # How to get help at conda-forge
 
-You could connect with us via **Element, GitHub Issues or Discourse Group**.
+You could connect with us via **Zulip, GitHub Issues or Discourse Group**.
 We would be happy to hear from you!
 
 <a id="element-chatroom"></a>
 
-## Element chatroom
+## [Zulip chatroom](https://conda-forge.zulipchat.com/) chatroom
 
-If you are just starting out with conda-forge and/or feel completely lost, we recommend getting in touch through [Element chatroom](https://app.element.io/#/room/#conda-forge:matrix.org). Our community members will direct
+If you are just starting out with conda-forge and/or feel completely lost, we recommend getting in touch through [Zulip chatroom](https://conda-forge.zulipchat.com/). Our community members will direct
 you to the proper documentation and/or help you via the chat.
 
 <a id="github-issues"></a>
diff --git a/docusaurus.config.js b/docusaurus.config.js
@@ -383,11 +383,11 @@ const config = {
             className: "fab fa-lg fa-github",
           },
           {
-            to: "https://twitter.com/condaforge",
-            title: "Twitter",
+            to: "https://conda-forge.zulipchat.com",
+            title: "Zulip",
             position: "right",
             target: "_blank",
-            className: "fab fa-lg fa-twitter",
+            className: "fa-solid fa-comments",
           },
         ],
       },
@@ -473,8 +473,8 @@ const config = {
                 href: "https://github.com/conda-forge",
               },
               {
-                label: "Element",
-                href: "https://app.element.io/#/room/#conda-forge:matrix.org",
+                label: "Zulip",
+                href: "https://conda-forge.zulipchat.com",
               },
               {
                 label: "Discourse",
diff --git a/news/2024-11-04-moving-to-zulip.md b/news/2024-11-04-moving-to-zulip.md
diff --git a/news/2024-11-07-new-time-core-meetings.md b/news/2024-11-07-new-time-core-meetings.md
diff --git a/src/components/Calendar/index.jsx b/src/components/Calendar/index.jsx
diff --git a/src/components/Contributing/index.jsx b/src/components/Contributing/index.jsx
