Monthly Comms Team Meeting: June 19th 2020

[MmeMarieLouise]

Monthly Comms Team Meeting

Attendees:

• @marie-l
• @BethanyG
• @lorenanicole
• @kittylon

Date:

• June 19th 2020

Previous meeting issue link:

• Monthly Comms Team Meeting: May 8th & 15th 2020 #48

Agenda

Please add items as needed. If you add a topic please make sure to attend the meeting.

Topic for discussion	Sub Topic	Notes	Action points	Person Responsible
PyLadies Global Election 2020	PyLadies Global Council Election 2020 Comms Strategy	NEW DEADLINE: August	TO DO THIS MONTH: 1)receive approval for blog post PR, 2) raise issue - start writing comms strategy and integrate content for the build up to the election	@marie-l @AbigailDogbe
Social Media Guide		1st draft is completed	make PR ASAP	@marie-l
Metrics		should be able to access GA dashboard using pyladies account, contact or cc Reshama Shaikh	TO DO THIS MONTH: 1) -- Open an issue to discuss where -- GA analytics Marie Louise will look into -- Buffer analytics and twitter analytics	@marie-l
Automation		@BethanyG suggested that instead of promoting chapters to complete google docs form, we might be able to create an interactive form within slack	TO DO THIS MONTH: 1) add issue #50 to hack day projects board- Slack automation with Zapier https://zapier.com/apps/buffer/integrations 2) find out about becoming an admin - look into slack workflow	@marie-l
Communications as a product		discussion around areas that comms team will manage or need to approve	issue template will be updated to resolve this matter	@marie-l
Hack day		check out projects board, @kittylon mentioned that Hack days will be great for our team to have every month so that we could all have specific time to work through issue, therefore from next month the comms team will be taking ownership and will arrange monthly hack days	TO DO THIS MONTH: 1) raise issue - include details for how the next days will be organised and how we can attract more teams/ everyone to join	@marie-l
PyLadies logos			-- todo: @BethanyG is going work on a write up on how to do your own pyladies logo work -- todo: design open call	@BethanyG
Blog Revamp		#475 -- Need to keep this on the radar for Project Comms - let's update the issue https://github.com/pyladies/pyladies/tree/master/.github/ISSUE_TEMPLATE	TO DO THIS MONTH: 1) -- Setup template on pyladies -- @marie-l will own, update issue template in main repo (with options to cc team concerned with approving) & make PR, 2) -- todo: project comms and discussions https://github.blog/2020-05-06-new-from-satellite-2020-github-codespaces-github-discussions-securing-code-in-private-repositories-and-more/ do we want to setup?	@marie-l
Onboarding
	PyLadies code of conduct		1)need to make a PR to update NOTE: in future there could be a blog post to document the process	@marie-l
User manual for me	As the LAST part of onboarding this will be worked on until the end of the month		TO DO THIS MONTH: 1) raise issue - for final push for members to complete user manual for me ( tag @kittylon & @BethanyG)	@marie-l

Sprint Planning

• @marie-l Election Comms Strategy : election announcement #36 Research PyLadies & other programming websites #3 Rebuilding the PyLadies website & blog #1 Twitter review policies #45 Automating slack channels to increase efficiency #50 , social media guide PR, contributing PR, issue template PR, raise analytics/ metrics issue, raise monthly hack day issue, raise user manual for me issue
• @BethanyG organise design files
• @AbigailDogbe Election Comms Strategy : election announcement #36
• @kittylon Write case studies for each blog researched #10 Future post: How PyLadies can help you find a job / change careers / etc #18 Slack Engagement #29 Rebuilding the PyLadies website & blog #1
• @albendz is working on an issue she raised in the infra repro #475

Next Meeting:

Friday 3rd July 2020

cc / @pyladies/communications