Fix TODOs for Community Guide #246
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for learn-scientific-python-org ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
for more information, see https://pre-commit.ci
|
build is failing, looks like a missing image: |
munkm
reviewed
May 14, 2025
|
|
||
| [Zarr Community Meeting template](https://hackmd.io/tFcffc__QRuo1UdGcGUbsg) |
There was a problem hiding this comment.
These two render alongside each other. What do you think about making this a bulleted list instead?
Comment on lines
+103
to
+104
| - Take into account community members in different time zones, differently | ||
| abled, unavailability etc. |
There was a problem hiding this comment.
this is a minor nit, but I think it's a bit clearer
Suggested change
| - Take into account community members in different time zones, differently | |
| abled, unavailability etc. | |
| - Take into account community members in different time zones, differently | |
| abled, availability (or lack of) etc. |
| - Make time for newcomers | ||
| - 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 | ||
| - New contributors or newcomers are the users who have the potential of | ||
| becoming future maintainers and helping them in the initial phase is |
There was a problem hiding this comment.
Based on previous conversations we talked about also wanting to embrace people who contribute but don't maintain. I think this helps capture that for consistency across our project.
Suggested change
| becoming future maintainers and helping them in the initial phase is | |
| becoming future maintainers or long-term contributors and helping them in the initial phase is |
| - Example at: https://zarr.dev/community-calls/2023/2023-05-03.html | ||
|
|
||
| ## Some tips for your meetings | ||
|
|
||
| - Make time for demos/showcases/presentation | ||
| - 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 | ||
| - The demos/showcases could be - how your project is used to solve a problem in a specific domain | ||
| - The community members are always looking for exciting/innovative ways to use |
There was a problem hiding this comment.
I think "the community members" reads a bit ambiguously.
Suggested change
| - The community members are always looking for exciting/innovative ways to use | |
| - Members of a project's community are always looking for exciting/innovative ways to use |
| sentences is a helpful thing to do when you’re moderating/running the | ||
| meeting | ||
| - 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 | ||
| - Example at: https://zarr.dev/community-calls/2023/2023-05-03.html | ||
|
|
||
| ## Some tips for your meetings |
There was a problem hiding this comment.
Suggested change
| ## Some tips for your meetings | |
| ## Some tips and ideas for your meetings |
| - What projects are they working on? | ||
| - Something they learned which could be shared with the community | ||
| - Asking around if the attendees need any help | ||
|
|
||
| ## How to conclude the meeting successfully | ||
|
|
||
| - 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: | ||
| - 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 |
There was a problem hiding this comment.
I think clarifying here would be helpful. Is the point to conclude before arguments end? Or to end on a positive note before the end of the meeting?
| - 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: | ||
| - 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: |
There was a problem hiding this comment.
Suggested change
| end, you should: | |
| end, one should: |
| - Conclude important points | ||
| - Revise tabled items - which were supposed to be discussed but didn’t get time | ||
| - Revise tabled items - which were supposed to be discussed but didn’t get | ||
| time | ||
| - Tell them about the next meeting |
There was a problem hiding this comment.
Suggested change
| - Tell them about the next meeting | |
| - Announce the next meeting time | |
| - State what will be covered in the next meeting |
| - Tell them about the next meeting | ||
|
|
||
| ## How to run office hours? | ||
|
|
||
| - 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. | ||
| - Usually, the structure of office hours is open, but there are certain tips which could make it run smoother; they are: | ||
| - Office hours are a great way to invite the community and answer their |
There was a problem hiding this comment.
Suggested change
| - Office hours are a great way to invite the community and answer their | |
| - Office hours are a great way to invite the community to engage with maintainers and answer their |
| questions, guide them, help them understand any specific about your OSS | ||
| project etc. | ||
| - Usually, the structure of office hours is open, but there are certain tips | ||
| which could make it run smoother; they are: | ||
| - Greet and acknowledge every participant during the office hours | ||
| - Try to answer at least 1 question from everyone |
There was a problem hiding this comment.
Suggested change
| - Try to answer at least 1 question from everyone | |
| - Try to answer at least 1 question from each attendee (if time is limited, try to prioritize new attendees) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi all.
I've fixed the various TODOs across the community guide.