Update checklist for community calls #46
There are no files selected for viewing
This file contains 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
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
| @@ -1,3 +1,7 @@ | ||||||
| --- | ||||||
| name: Community Call Checklist | ||||||
| about: Checklist for hosting Community Calls | ||||||
| --- | ||||||
| ## <!--Add date here--> meeting to dos | ||||||
|
|
||||||
| <!--Use this PR to change the readme with details for the call two months out. That way when this | ||||||
|
|
@@ -6,6 +10,7 @@ links for the upcoming call.--> | |||||
|
|
||||||
| ### Scheduling | ||||||
|
|
||||||
| - [ ] Select date and time (at least 4 weeks in advance) | ||||||
| - [ ] Add event to the [Jupyter community calendar](https://docs.jupyter.org/en/latest/community/content-community.html#jupyter-community-meetings) | ||||||
| - [ ] Make HackMD agenda/notes ([agenda template](https://github.com/Quansight-Labs/jupyter-communitycalls/blob/main/agenda-template.md)) and check the link permissions allow for public access | ||||||
| - [ ] Schedule host (let different people host) | ||||||
|
|
@@ -14,11 +19,15 @@ links for the upcoming call.--> | |||||
| ### Promotion | ||||||
|
|
||||||
| - [ ] Update [Jupyter Discourse wiki](https://discourse.jupyter.org/t/jupyter-community-calls/668) and/or add a comment 2 weeks before | ||||||
| - [ ] Blog (For example: https://blog.jupyter.org/november-2024-jupyter-community-call-f5d0761c67a1) | ||||||
| - [ ] Social media 2 weeks before (email Jupyter media strategy group) | ||||||
|
There was a problem hiding this comment.
Suggested change
OK to leave this out if it would cause spam concerns to have this address on a publicly visible web page. |
||||||
| - [ ] Post issue to [jupyterhub/team-compass](https://github.com/jupyterhub/team-compass/) 2 weeks before | ||||||
| - [ ] Post on [Jupyter Discourse](https://github.com/jupyterhub/team-compass/) 1 week before | ||||||
| - [ ] Post on [Jupyter mailing list](https://groups.google.com/g/jupyter/) 1 week before | ||||||
| - [ ] Discourse: https://discourse.jupyter.org/c/meta/community-building/49 | ||||||
| - [ ] Open an issue on Governance repo: https://github.com/jupyter/governance/issues/241 | ||||||
| - [ ] Send email to SSC and ask them to distribute | ||||||
|
There was a problem hiding this comment.
Suggested change
OK to leave this out if it would cause spam concerns |
||||||
| - [ ] Join subproject meetings? | ||||||
|
|
||||||
| ### Recording | ||||||
|
|
||||||
|
|
||||||
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add a blank line after the frontmatter