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: README.md
+12-4Lines changed: 12 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,9 +28,17 @@ If you have questions or need help, please check out our documentation for a [li
28
28
29
29
## conda-forge dev meetings
30
30
31
-
Our documentation contains a section with [minutes from previous dev meetings]([https://conda-forge.org/docs/minutes/00_intro.html]). These meetings occur every two weeks on Wednesday from 17:00-18:00 UTC.
32
-
A link to the google calendar item can be found [here](https://calendar.google.com/event?action=TEMPLATE&tmeid=bTk5ZzBoMDEzaW11cmZiNWJnNmNkbThocDRfMjAyMjA1MThUMTcwMDAwWiBlcmljQHZvbHRyb25kYXRhLmNvbQ&tmsrc=eric%40voltrondata.com&scp=ALL).
31
+
We hold biweekly meetingsevery second Wednesday from 17:00-18:00 (UTC). Feel free to stop by!
32
+
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!
33
33
34
-
We use https://hackmd.io/ for taking meeting minutes and will (eventually) upload the resultant markdown file after the meeting has concluded.
34
+
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.
35
35
36
-
There is a template provided in [`misc/DEV_MEETING_TEMPLATE.md`](https://github.com/conda-forge/conda-forge.github.io/tree/main/misc/DEV_MEETING_TEMPLATE.md) that you should use to create a new hackmd document.
36
+
We use a Github Actions [workflow][gha-workflow] to create an automated PR with the meeting notes
37
+
template for each session, which is automatically published to our HackMD team account. During the
38
+
meeting, attendees will edit the HackMD document. After the meeting, the document is saved and the
39
+
PR is synced with the changes by adding the `sync-hackmd-notes` label. Once satisfied, the PR is
40
+
merged and the website will be updated with the new meeting notes.
41
+
42
+
We encourage contributors to join the meetings and learn more about and from the community.
0 commit comments