|
| 1 | +--- |
| 2 | +title: "Community Meetings" |
| 3 | +--- |
| 4 | + |
| 5 | +## How to initiate a community meeting? |
| 6 | +- 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 | +- Issues or PRs from the GitHub repositories which need attention |
| 8 | +- Announcing any upcoming events/conferences to check if someone is going to attend them or is planning to |
| 9 | +- 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 |
| 15 | + |
| 16 | +## Ice-breakers |
| 17 | +- Ice-breakers are usually effective when the participants are not familiar with each other |
| 18 | +- 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? |
| 22 | + |
| 23 | +## How to address any critical issues in the project/community |
| 24 | +- Sometimes, there are certain matter which needs to be brought up before the community for a more open and inclusive discussion |
| 25 | +- 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 | + |
| 27 | +## How to keep the conversation going? |
| 28 | +- 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 |
| 34 | + |
| 35 | +## How to conclude the meeting successfully |
| 36 | +- 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 |
| 40 | + |
| 41 | +## How to run office hours? |
| 42 | +- 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 |
| 48 | + |
| 49 | +## How to take meeting notes? |
| 50 | +- 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 |
| 55 | + |
| 56 | +## Some tips for your meetings |
| 57 | + |
| 58 | +- 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 |
| 61 | +- 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 |
| 68 | + |
| 69 | +## Meeting templates (TODO) |
| 70 | +[NumPy Community Meeting template](https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg) |
0 commit comments