Monthly Comms Team Meeting: Feb 14th 2020

[MmeMarieLouise]

Monthly Comms Team Meeting

Attendees:

• @marie-l
• @AbigailDogbe

Date:

• February 14th 2020

Agenda

Please add items as needed. If you add a topic please make sure to attend the meeting.
NOTE: Topics for discussion have been carried over from January, extra comments have been added relating to this months objectives or progress

Topic for discussion	Sub Topic	Notes	Action points	Person Responsible
PyLadies Global Election 2020	PyLadies Global Council Election 2020 Comms Strategy	PyLadies Global Council will be selected by a public election and nomination process. We need to start a Comms strategy for this.	Get Project Comms point person to work with Global interim team (@lorenanicole / Lorena Mesa), Develop Comms Strategy, Publish content (for now on old blog of website) with Global Interim team (Debora Azevedo) for translation Coordinate, Find out more about global Election 2020 - TO DO THIS MONTH: Break down issue into epic	@lorenanicole (point of contact with election), TODO: Caroline & ML would like to be involved
Onboarding
PyLadies code of conduct			@marie-l
New issue template	#21		@albendz COMPLETED
Contributor template	contributor template		@marie-l COMPLETED (awaiting review)
Pending requests to join & intake dates		@marie-l must do by 19/01/20 And schedule call with @eyspahn to plan how to work on #3, Contact @kittylon to make new request, Find out about other request	@marie-l
User manual for me	As part of onboarding this will be worked on until the end of the month	Alena, Alicia, Bethany, Carolina	@eyspahn
readme	Update with correct details for Alicia’s chapter : Remote	Correct file and make PR	@marie-l COMPLETED
Members directory	We can replace the list of members on the readme.md with a link to the directory	Find out from lorena when this will be created and launched	@marie-l
Meetings
convenient dates for monthly meetings ( for example every 1st Tuesday of the month)	world clock, doodle	Set up a UberConference account and get info on everyone’s availability And also propose that we schedule our meeting the first friday of every month and then we can match up the best times across the time zones on that day	@marie-l
Monthly meeting template	1. Co-leads send the meeting organiser a link to the meetings template 2. They should check last month’s meeting notes 3. Post an announcement on slack about our upcoming meeting (2 weeks in advance) 4. 3 weeks in advance, co-lead will send topics for the agenda and issues for sprint planning 5. They need to use the google docs agenda template to add the new topics 6. Post the agenda in the slack channel 7. Create an event using the bot 8. Enable google hangouts in the calendar and create a conference call 9. Post a reminder one week before the meeting 10. Conduct the meeting 11. Take notes in the google docs template during the meeting 12. Push the notes for the meeting and sprint planning into the markdown template on github
Use the notes to create the template on github, put it in the main repo (readme.md) add links to each monthly meeting in the README.md)	@marie-l
Who’ll run the next meeting		TBC
Date of next months meeting		TBC

Sprint Planning

Issue	Notes	Action points	Person Responsible
Rebuilding the PyLadies Blog #1		Find out how much are we going to rebuild and what is the strategy. Contact Lorena	@marie-l
Encouraging all chapters to support & engage remote learners #2
Research PyLadies & other programming blogs #3			@eyspahn @marie-l
Make a list of the current contributors / editors of the blog #5
find out whether processes for contributing have been documented #6
Write use cases #7
write PyLadies blog case study #8
Search for a few blogs which have similar use cases #9
Write case studies for each blog researched #10
List action points which are a direct result of the research #11
Criteria and Workflow for New Members and Approvals #13
Create Getting Started with ... and Next Steps with ... pages or cheatsheets #17
Future post: How PyLadies can help you find a job / change careers / etc #18			@eyspahn
Investigate Video and Voice Communications #19
Investigate Social Media for PyLadies Communications #20			@kittylon
Create a new issue template for generic issues #21
After an issue is opened, who will and when will we be adding new folks to the GitHub team #22
Slack Engagement #29	Abigail has already started working on this issue. She has been writing descriptions for the various channels that we have on slack	Abigail will share with me the work that she’s done so far and I will make a PR, Assign abigail to that ticket	@AbigailMesranyameDogbe

cc / @pyladies/communications