You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This template should be used (edited) the month prior and during the meeting. This will ensure we can address all topics added throughout the month; as well as provide minutes and follow up after the meeting is held.
January announcement to the community
The discussion still open until 31th January. On the next week we should write asynchronously the announcement (Discussion)
This template should be used (edited) the month prior and during the meeting. This will ensure we can address all topics added throughout the month; as well as provide minutes and follow up after the meeting is held.
PyLadies Global Meeting
Agenda
Please add items as needed. If you add a topic please make sure to attend the meeting.
Project Updates
Project Comms (Slack: #project-communication / Repo: https://github.com/pyladies/project-communications)
Project Admin & Logistics (Slack: #project-admin-logistics / Repo:
Project Tech & Infra (Slack: #project-tech-infra / Repo: https://github.com/pyladies/pyladies)
Code of Conduct
Finance Work Group
Review Actions Items from Last Meeting
New Business
January announcement to the community
The discussion still open until 31th January. On the next week we should write asynchronously the announcement (Discussion)
GitHub README project (Discussion)
Python's 30th anniversary - 9th October Discussion
Community Liaison responsibilities Discussion
PyCascades have 50 free tickets for PyLadies, how do we go about this? [name=Tania]
Old Business: Follow up items from prior meeting:
Mission, Purpose and main responsibilities
Schedule meeting with advisors for review
Governance structure announcement
chair and vice chair
MSFT partnership [name=Tania]
Action Items and Assignees for Next Meeting
@pyladies/pyladies-global-contributors
@pyladies/pyladies-global-admin
The text was updated successfully, but these errors were encountered: