Skip to content

Commit d743f99

Browse files
committed
Add it as an extra page
1 parent 11ee68c commit d743f99

File tree

3 files changed

+43
-34
lines changed

3 files changed

+43
-34
lines changed

community/_sidebar.json

Lines changed: 14 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -14,15 +14,25 @@
1414
"contracting",
1515
{
1616
"type": "category",
17-
"label": "Meeting minutes",
17+
"label": "Meetings",
1818
"link": {
1919
"type": "doc",
20-
"id": "minutes"
20+
"id": "meetings"
2121
},
2222
"items": [
2323
{
24-
"type": "autogenerated",
25-
"dirName": "minutes"
24+
"type": "category",
25+
"label": "Minutes archive",
26+
"link": {
27+
"type": "doc",
28+
"id": "minutes"
29+
},
30+
"items": [
31+
{
32+
"type": "autogenerated",
33+
"dirName": "minutes"
34+
}
35+
]
2636
}
2737
]
2838
}

community/meetings.mdx

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
# Community meetings
2+
3+
We hold a series of recurring meetings:
4+
5+
- `⚫ [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).
6+
- `⚫ [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).
7+
8+
We encourage contributors to join the meetings and learn more about and from the community. Look for the events in the calendar below!
9+
10+
## Calendar
11+
12+
import Calendar from '@site/src/components/Calendar';
13+
14+
<Calendar />
15+
16+
## Setup
17+
18+
Our [meeting notes](https://conda-forge.org/community/minutes/) record important points discussed during the meetings and serve as a record for upcoming meetings.
19+
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.
20+
21+
We use a Github Actions [workflow][gha-workflow] to create an automated PR with the meeting notes
22+
template for each session, which is automatically published to our HackMD team account. During the
23+
meeting, attendees will edit the HackMD document. After the meeting, the document is saved and the
24+
PR is synced with the changes by adding the `sync-hackmd-notes` label. Once satisfied, the PR is
25+
merged and the website will be updated with the new meeting notes.
26+
27+
[gha-workflow]: https://github.com/conda-forge/conda-forge.github.io/actions/workflows/meeting-notes.yml

community/minutes.mdx

Lines changed: 2 additions & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -1,34 +1,6 @@
1-
# Community meetings
1+
# Meeting minutes
22

3-
## Calendar
4-
5-
We hold a series of recurring meetings:
6-
7-
- `⚫ [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!
8-
- `⚫ [conda-forge] bot sync`: first Friday of the month at 15:00 (UTC). These are technical meetings meant for infrastructure and tooling contributors.
9-
10-
Look for the events in the calendar below:
11-
12-
import Calendar from '@site/src/components/Calendar';
13-
14-
<Calendar />
15-
16-
We encourage contributors to join the meetings and learn more about and from the community.
17-
18-
## Setup
19-
20-
Our [meeting notes](https://conda-forge.org/community/minutes/) record important points discussed during the meetings and serve as a record for upcoming meetings.
21-
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.
22-
23-
We use a Github Actions [workflow][gha-workflow] to create an automated PR with the meeting notes
24-
template for each session, which is automatically published to our HackMD team account. During the
25-
meeting, attendees will edit the HackMD document. After the meeting, the document is saved and the
26-
PR is synced with the changes by adding the `sync-hackmd-notes` label. Once satisfied, the PR is
27-
merged and the website will be updated with the new meeting notes.
28-
29-
[gha-workflow]: https://github.com/conda-forge/conda-forge.github.io/actions/workflows/meeting-notes.yml
30-
31-
## Minutes
3+
This is an archive of all the conda-forge core meeeting minutes:
324

335
import DocCardList from '@theme/DocCardList';
346

0 commit comments

Comments
 (0)