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: content/_index.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,6 +28,14 @@ body = '''
28
28
Numerical computing lectures that teach key packages in the scientific Python ecosystem, such as NumPy, SciPy, Matplotlib, scikit-learn, and scikit-image.
29
29
'''
30
30
31
+
[[item]]
32
+
type = 'card'
33
+
title = 'Community Guide'
34
+
link = '/community'
35
+
body = '''
36
+
Learn how to manage the community of your open-source project.
Copy file name to clipboardExpand all lines: content/community/community-meetings.md
+57-24Lines changed: 57 additions & 24 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,75 +4,108 @@ title: "Community Meetings"
4
4
5
5
## How to initiate a community meeting?
6
6
7
-
- Before starting the meeting, having a few items and discussion points in the agenda will help kick-start the meeting. These discussion points could be a mix of:
7
+
- Before starting the meeting, having a few items and discussion points in the
8
+
agenda will help kick-start the meeting. These discussion points could be a
9
+
mix of:
8
10
- Issues or PRs from the GitHub repositories which need attention
9
-
- Announcing any upcoming events/conferences to check if someone is going to attend them or is planning to
11
+
- Announcing any upcoming events/conferences to check if someone is going to
12
+
attend them or is planning to
10
13
- Important updates:
11
14
- These could be recent releases/new feature additions
12
15
- Addition/changes in the maintainer/contributor team
13
-
- Convergence of an ongoing discussion - a summary of how the community reached a decision
16
+
- Convergence of an ongoing discussion - a summary of how the community
17
+
reached a decision
14
18
- Anything important which needs to be brought up before the community
15
19
- Let everyone know that the meeting is governed by a CoC
16
20
17
21
## Ice-breakers
18
22
19
-
- Ice-breakers are usually effective when the participants are not familiar with each other
20
-
- Apart from the general introduction, which is usually name and role, it’s effective to add a fun question (generally non-technical) to ask around; these are:
23
+
- Ice-breakers are usually effective when the participants are not familiar with
24
+
each other
25
+
- Apart from the general introduction, which is usually name and role, it’s
26
+
effective to add a fun question (generally non-technical) to ask around;
27
+
these are:
21
28
- Favourite song, movie, dish, sport, game, tourist spot etc.
22
29
- If you could teach the world one thing, what would it be?
23
30
- What’s one interesting fact about yourself?
24
31
25
32
## How to address any critical issues in the project/community
26
33
27
-
- Sometimes, there are certain matter which needs to be brought up before the community for a more open and inclusive discussion
28
-
- This helps in taking into account various perspectives from the community and choosing a solution which is in the best interest of the community
34
+
- Sometimes, there are certain matter which needs to be brought up before the
35
+
community for a more open and inclusive discussion
36
+
- This helps in taking into account various perspectives from the community and
37
+
choosing a solution which is in the best interest of the community
29
38
30
39
## How to keep the conversation going?
31
40
32
-
- Occasionally, there are situations when the conversation during a community meeting dies, and it feels like you’re in a graveyard 🪦
33
-
- Having a set up of backup discussion points can help remove the awkward silence
34
-
- Going around in the audience to ask if they have something interesting to share with the community
41
+
- Occasionally, there are situations when the conversation during a community
42
+
meeting dies, and it feels like you’re in a graveyard 🪦
43
+
- Having a set up of backup discussion points can help remove the awkward
44
+
silence
45
+
- Going around in the audience to ask if they have something interesting to
46
+
share with the community
35
47
- What projects are they working on?
36
48
- Something they learned which could be shared with the community
37
49
- Asking around if the attendees need any help
38
50
39
51
## How to conclude the meeting successfully
40
52
41
-
- The meeting should end on a positive note - if there has been any heated discussion/arguments, try to conclude before the end. And generally, in the end, you should:
53
+
- The meeting should end on a positive note - if there has been any heated
54
+
discussion/arguments, try to conclude before the end. And generally, in the
55
+
end, you should:
42
56
- Conclude important points
43
-
- Revise tabled items - which were supposed to be discussed but didn’t get time
57
+
- Revise tabled items - which were supposed to be discussed but didn’t get
58
+
time
44
59
- Tell them about the next meeting
45
60
46
61
## How to run office hours?
47
62
48
-
- Office hours are a great way to invite the community and answer their questions, guide them, help them understand any specific about your OSS project etc.
49
-
- Usually, the structure of office hours is open, but there are certain tips which could make it run smoother; they are:
63
+
- Office hours are a great way to invite the community and answer their
64
+
questions, guide them, help them understand any specific about your OSS
65
+
project etc.
66
+
- Usually, the structure of office hours is open, but there are certain tips
67
+
which could make it run smoother; they are:
50
68
- Greet and acknowledge every participant during the office hours
51
69
- Try to answer at least 1 question from everyone
52
-
- Maintain a document so that everyone can jot down their questions, so it’s easier to go through them
70
+
- Maintain a document so that everyone can jot down their questions, so it’s
71
+
easier to go through them
53
72
- Invite them to the community meetings for broader discussions
54
73
55
74
## How to take meeting notes?
56
75
57
-
- Every community meeting should have some form of public record which can be stored as an archive - taking meeting notes is one way to do it. There are several ways to take notes efficiently, which is helpful for the community
58
-
- Record the essential things, decisions, and resolutions that were discussed during the meeting
59
-
- Writing cues during the meeting and then converting them into proper sentences is a helpful thing to do when you’re moderating/running the meeting
60
-
- Try to have a TL;DR section at the top - this would help the reader to decide if they want to dive into the full notes or not
76
+
- Every community meeting should have some form of public record which can be
77
+
stored as an archive - taking meeting notes is one way to do it. There are
78
+
several ways to take notes efficiently, which is helpful for the community
79
+
- Record the essential things, decisions, and resolutions that were discussed
80
+
during the meeting
81
+
- Writing cues during the meeting and then converting them into proper
82
+
sentences is a helpful thing to do when you’re moderating/running the
83
+
meeting
84
+
- Try to have a TL;DR section at the top - this would help the reader to
85
+
decide if they want to dive into the full notes or not
61
86
- Example at: https://zarr.dev/community-calls/2023/2023-05-03.html
62
87
63
88
## Some tips for your meetings
64
89
65
90
- Make time for demos/showcases/presentation
66
-
- The community members are always looking for exciting/innovative ways to use OSS projects in their workflow, and making time to showcase the work is a good element of a community meeting
67
-
- The demos/showcases could be - how your project is used to solve a problem in a specific domain
91
+
- The community members are always looking for exciting/innovative ways to use
92
+
OSS projects in their workflow, and making time to showcase the work is a
93
+
good element of a community meeting
94
+
- The demos/showcases could be - how your project is used to solve a problem
95
+
in a specific domain
68
96
- Make time for newcomers
69
-
- New contributors or newcomers are the users who have the potential of becoming future maintainers and helping them in the initial phase is beneficial for both the project and the individual and is in the spirit of open-source
97
+
- New contributors or newcomers are the users who have the potential of
98
+
becoming future maintainers and helping them in the initial phase is
99
+
beneficial for both the project and the individual and is in the spirit of
100
+
open-source
70
101
- Having a dedicated time slot for the newcomers to help them
71
102
- Make community meetings accessible to the broader community
72
-
- Take into account community members in different time zones, differently abled, unavailability etc.
103
+
- Take into account community members in different time zones, differently
104
+
abled, unavailability etc.
73
105
- Take notes and upload them to the website
74
106
- Record the meeting
75
107
76
-
## Meeting templates (TODO)
108
+
## Meeting templates
77
109
110
+
[Zarr Community Meeting template](https://hackmd.io/tFcffc__QRuo1UdGcGUbsg)
78
111
[NumPy Community Meeting template](https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg)
0 commit comments