Merge pull request #2357 from jaimergp/calendar-embed

Embed timezone-aware calendar for community meetings

Author: beckermr

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.

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"
+          }
+        ]
       }
     ]
   }

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)

community/meetings.mdx

@@ -0,0 +1,27 @@
+# Community meetings
+
+We hold a series of recurring meetings:
+
+- `⚫ [conda-forge] core meeting`: every second Wednesday from 17:00-18: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

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';
 

src/components/Calendar/index.jsx

@@ -0,0 +1,29 @@
+import { React, useEffect, useState } from "react";
+import { useColorMode } from "@docusaurus/theme-common";
+
+export default function Calendar() {
+  const [firstDay, setFirstDay] = useState(1);
+  const [timezone, setTimezone] = useState("UTC");
+  const [themeMode, setThemeMode] = useState("light");
+  const { colorMode } = useColorMode();
+  useEffect(() => {
+    if (Intl) {
+      const locale = Intl.DateTimeFormat().resolvedOptions().locale;
+      setFirstDay((new Intl.Locale(locale)?.weekInfo?.firstDay ?? 0) + 1);
+      setTimezone(Intl.DateTimeFormat().resolvedOptions().timeZone);
+    }
+    setThemeMode(colorMode);
+  });
+  return (
+    <iframe
+      src={`https://calendar.google.com/calendar/embed?height=500&wkst=${firstDay}&ctz=${timezone}&showTitle=0&showTz=1&showPrint=0&src=ODgwNTU3MGE0ZTFjYTIzMTk4NDI5NzFkYjQzODBlZDUxOGM0OTA1NzdjMDY0NTRhZGYyMzAzNzM0NTA2ZjM5N0Bncm91cC5jYWxlbmRhci5nb29nbGUuY29t&color=%2333b679`}
+      width="100%"
+      height="500"
+      style={
+        themeMode === "dark"
+          ? { filter: "invert(95%) brightness(95%) hue-rotate(180deg)" }
+          : {}
+      }
+    ></iframe>
+  );
+}