Update checklist for community calls

.github/pull_request_template.md → .github/ISSUE_TEMPLATE/community-call.md

@@ -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
-- [ ] Tweet (on personal account, request [Project Jupyter retweet](https://twitter.com/ProjectJupyter/)) 2 weeks before
-- [ ] Post on the [Jupyter mailing list](https://groups.google.com/g/jupyter/) 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) 
 - [ ] 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
+- [ ] Join subproject meetings?
 
 ### Recording