Skip to content

Commit 62561df

Browse files
authored
Merge pull request #1659 from chicken-biryani/Improve-ReadMe
Reword info about dev meetings in Readme.
2 parents e8247b0 + a7c8bcf commit 62561df

File tree

1 file changed

+12
-4
lines changed

1 file changed

+12
-4
lines changed

README.md

Lines changed: 12 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -28,9 +28,17 @@ If you have questions or need help, please check out our documentation for a [li
2828

2929
## conda-forge dev meetings
3030

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 meetings every 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!
3333

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.
3535

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.
43+
44+
[gha-workflow]: https://github.com/conda-forge/conda-forge.github.io/actions/workflows/meeting-notes.yml

0 commit comments

Comments
 (0)