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/community/community-meetings.md
+42-34Lines changed: 42 additions & 34 deletions
Original file line number
Diff line number
Diff line change
@@ -3,68 +3,76 @@ title: "Community Meetings"
3
3
---
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
8
- Issues or PRs from the GitHub repositories which need attention
8
9
- Announcing any upcoming events/conferences to check if someone is going to attend them or is planning to
9
10
- Important updates:
10
-
- These could be recent releases/new feature additions
11
-
- Addition/changes in the maintainer/contributor team
12
-
- Convergence of an ongoing discussion - a summary of how the community reached a decision
13
-
- Anything important which needs to be brought up before the community
14
-
- Let everyone know that the meeting is governed by a CoC
11
+
- These could be recent releases/new feature additions
12
+
- Addition/changes in the maintainer/contributor team
13
+
- Convergence of an ongoing discussion - a summary of how the community reached a decision
14
+
- Anything important which needs to be brought up before the community
15
+
- Let everyone know that the meeting is governed by a CoC
15
16
16
17
## Ice-breakers
18
+
17
19
- Ice-breakers are usually effective when the participants are not familiar with each other
18
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:
19
-
- Favourite song, movie, dish, sport, game, tourist spot etc.
20
-
- If you could teach the world one thing, what would it be?
21
-
- What’s one interesting fact about yourself?
21
+
- Favourite song, movie, dish, sport, game, tourist spot etc.
22
+
- If you could teach the world one thing, what would it be?
23
+
- What’s one interesting fact about yourself?
22
24
23
25
## How to address any critical issues in the project/community
26
+
24
27
- Sometimes, there are certain matter which needs to be brought up before the community for a more open and inclusive discussion
25
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
26
29
27
30
## How to keep the conversation going?
31
+
28
32
- Occasionally, there are situations when the conversation during a community meeting dies, and it feels like you’re in a graveyard 🪦
29
-
- Having a set up of backup discussion points can help remove the awkward silence
30
-
- Going around in the audience to ask if they have something interesting to share with the community
31
-
- What projects are they working on?
32
-
- Something they learned which could be shared with the community
33
-
- Asking around if the attendees need any help
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
35
+
- What projects are they working on?
36
+
- Something they learned which could be shared with the community
37
+
- Asking around if the attendees need any help
34
38
35
39
## How to conclude the meeting successfully
40
+
36
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:
37
-
- Conclude important points
38
-
- Revise tabled items - which were supposed to be discussed but didn’t get time
39
-
- Tell them about the next meeting
42
+
- Conclude important points
43
+
- Revise tabled items - which were supposed to be discussed but didn’t get time
44
+
- Tell them about the next meeting
40
45
41
46
## How to run office hours?
47
+
42
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.
43
-
- Usually, the structure of office hours is open, but there are certain tips which could make it run smoother; they are:
44
-
- Greet and acknowledge every participant during the office hours
45
-
- Try to answer at least 1 question from everyone
46
-
- Maintain a document so that everyone can jot down their questions, so it’s easier to go through them
47
-
- Invite them to the community meetings for broader discussions
49
+
- Usually, the structure of office hours is open, but there are certain tips which could make it run smoother; they are:
50
+
- Greet and acknowledge every participant during the office hours
51
+
- 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
53
+
- Invite them to the community meetings for broader discussions
48
54
49
55
## How to take meeting notes?
56
+
50
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
51
-
- Record the essential things, decisions, and resolutions that were discussed during the meeting
52
-
- 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
53
-
- 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
54
-
- Example at: https://zarr.dev/community-calls/2023/2023-05-03.html
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
61
+
- Example at: https://zarr.dev/community-calls/2023/2023-05-03.html
55
62
56
63
## Some tips for your meetings
57
64
58
65
- Make time for demos/showcases/presentation
59
-
- 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
60
-
- The demos/showcases could be - how your project is used to solve a problem in a specific domain
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
61
68
- Make time for newcomers
62
-
- 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
63
-
- Having a dedicated time slot for the newcomers to help them
64
-
- Make community meetings accessible to the broader community
65
-
- Take into account community members in different time zones, differently abled, unavailability etc.
66
-
- Take notes and upload them to the website
67
-
- Record the meeting
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
70
+
- Having a dedicated time slot for the newcomers to help them
71
+
- Make community meetings accessible to the broader community
72
+
- Take into account community members in different time zones, differently abled, unavailability etc.
73
+
- Take notes and upload them to the website
74
+
- Record the meeting
68
75
69
76
## Meeting templates (TODO)
70
-
[NumPy Community Meeting template](https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg)
77
+
78
+
[NumPy Community Meeting template](https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg)
Copy file name to clipboardExpand all lines: content/community/onboarding.md
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -7,6 +7,6 @@ This is a draft document.
7
7
{{< /notice >}}
8
8
9
9
- Organizing sprints
10
-
- Organising sprints are an excellent way to invite new collaborators, solve issues, gather contributions and broaden the project community. Some helpful tips for organising a sprint efficiently:
11
-
- Have a list of issues from the issue tracker that can be worked on. The issues should have a mix of code (bugs, features, fixes) and no-code (documentation) tasks so that they can accommodate a diverse set of participants
12
-
- Handling a storm of new contributors during peak season (GSoC, Outreachy, GSOD etc.)
10
+
- Organising sprints are an excellent way to invite new collaborators, solve issues, gather contributions and broaden the project community. Some helpful tips for organising a sprint efficiently:
11
+
- Have a list of issues from the issue tracker that can be worked on. The issues should have a mix of code (bugs, features, fixes) and no-code (documentation) tasks so that they can accommodate a diverse set of participants
12
+
- Handling a storm of new contributors during peak season (GSoC, Outreachy, GSOD etc.)
Copy file name to clipboardExpand all lines: content/community/role.md
+5-4Lines changed: 5 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -3,22 +3,23 @@ title: "Community Manager Role"
3
3
---
4
4
5
5
## Who’s a community manager?
6
-
A community manager for an Open Source scientific Python project is a dedicated and enthusiastic contributor who plays an important role in building and nurturing a thriving community. They act as a bridge between the project and its community members, creating an inclusive and collaborative environment.
6
+
7
+
A community manager for an Open Source scientific Python project is a dedicated and enthusiastic contributor who plays an important role in building and nurturing a thriving community. They act as a bridge between the project and its community members, creating an inclusive and collaborative environment.
7
8
This person has a strong understanding of scientific Python and open source principles. They actively engage with community members, address their needs, offer support, and encourage their active participation. By organizing community events, facilitating discussions, and promoting knowledge-sharing, they ensure that the project's community remains vibrant and connected. The community manager is passionate about Python programming and committed to promoting diversity and inclusion in the scientific open source software community.
8
9
9
10
## What is the role of a community manager?
10
11
11
12
- Designate time for engaging community. (Social media, hosting events)
12
13
- Empowering others to become leaders.(Setting example, having initiatives)
13
-
- Guidance for conflict resolution.
14
+
- Guidance for conflict resolution.
14
15
- Making the community "Welcoming". (Having resources that make people want to stay, Good communication)
15
16
- Being a communication channel between users and developers (Understanding the user's needs to be able to participate in the road map.)
16
-
17
+
17
18
## Why do you need a community manager?
18
19
19
20
1. A community manager acts as a bridge between the project and its community members. They facilitate communication, engagement, and collaboration, ensuring that users feel heard, valued, and supported. By fostering a sense of belonging and inclusivity, a community manager helps to create a strong and loyal user community.
20
21
2. A community manager plays a critical role in building and sustaining an active and vibrant community around the project. They organize and promote community events, facilitate discussions, and encourage knowledge-sharing. This helps to foster connections, drive participation, and create a positive and collaborative atmosphere within the community.
21
-
3. A community manager serves as a trusted resource for community members, offering support, answering questions, and resolving conflicts. They act as a point of contact, providing guidance, feedback, and assistance when needed.
22
+
3. A community manager serves as a trusted resource for community members, offering support, answering questions, and resolving conflicts. They act as a point of contact, providing guidance, feedback, and assistance when needed.
22
23
4. A community manager helps to promote the project's values, goals, and mission. They advocate for the project and its benefits, both within the existing user community and to potential new users. This can lead to increased visibility, growth, and adoption of the project.
23
24
5. A community manager plays a crucial role in gathering user feedback and insights. They act as the voice of the community, conveying user needs, preferences, and concerns to the project team.
0 commit comments