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
Date: Dec 14
Previous meeting issue link: #85
Current meeting attendees: @cecivieira @valerybriz @JUpani @econchick @sonacrystal @Marie-L @BethanyG
Agenda
Please add items as needed. If you add a topic please make sure to attend the meeting.
Mini-update: a total of 6 :+1: (myself plus 5 others) have agreed this is a good idea. I (Lynn) will go ahead and get started on the old meeting minutes.
In oct. (thread) we talked about rename the files to YYYY-MM-DD. I renamed, but didn't close the PR yet. We can adopt this new file name model in the next minutes note because it's easier to sort the files (Ana Cecília)
[x] Create e-mail to council
Who or which workgroup will management the messages and answer it?
We could create a e-mail to council members and redirect all messages to everyone, however I think (Ana Cecília) only one workgroup or member should answer.
Notes:
AI: lynn to investigate the setup of council email address with people's desired email address
What about info@? It currently goes to one person (Mariatta); we should figure out how to maintain this so that one person doesn't have to be responsible
Need to think through how information is propagated
@Valery interested in helping
Can info@ be maintained by a working group? comms wg?
AI: Bethany to setup info@ with voluneer helpers (Valery, ...)
[ ] Governance Structure
The structure will be:
Roles to Chair and Vice Chair
This chairs need to be location and ethnic representative? We have more than a half members from south, it's important? Rotation? (Ana Cecília)
Old Business: Follow up items from prior meeting:
[x] Mission, Purpose and main responsibilities
[x] From previous meeting: agreed to work offline
[ ] Set "working group"/doc to work on
[ ] Schedule meeting with advisors for review
Action Items and Assignees for Next Meeting
Action Item
Owner
Relevant links
set up an async discussion with Lynn and Bethany about the Pyladies auction
Decide how we can communicate our chosen model to the world (ideas from Valery: produce one or multiple articles about why we agreed on the model chair, vice chair and workgroups/leaderships, explain how it is going to work, in the social network mention this article, provide a resume about how we are assigned as workgroups/leaderships and chair, vice chair in the page of pyladies, we could also post the same article or something like the agreement, maybe we can also add in the page our leaderships/workgroups responsible names so people can know who to reach out for the different things)
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: https://github.com/pyladies/project-admin-logisitics )
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
[x] Resolution: Publish meeting minutes directly in the global-organizing repo instead of as github issues (github discussion) (via Lynn)
[x] Create e-mail to council
Notes:
AI: lynn to investigate the setup of council email address with people's desired email address
What about info@? It currently goes to one person (Mariatta); we should figure out how to maintain this so that one person doesn't have to be responsible
[ ] Governance Structure
Old Business: Follow up items from prior meeting:
Action Items and Assignees for Next Meeting
@pyladies/pyladies-global-contributors @pyladies/pyladies-global-admin