Bi-Monthly PyLadies Meeting Notes: December 2 2020 @ 7pm UTC

[econchick]

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 2
• Previous meeting issue link: https://github.com/pyladies/global-organizing/issues/84
• Current meeting attendees: @cecivieira @julianafalves @JUpani @econchick @Marie-L

Agenda

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

Project Updates

1. Project Comms (Slack: #project-communication / Repo: https://github.com/pyladies/project-communications) @Marie-L : micro campaign for python steering council

2. Project Admin & Logistics (Slack: #project-admin-logistics / Repo: https://github.com/pyladies/project-admin-logisitics ) No updates

3. Project Tech & Infra (Slack: #project-tech-infra / Repo: https://github.com/pyladies/pyladies) No updates

4. Code of Conduct @trallard : no updates, will breathe new air once we have decided on working groups leads

Review Actions Items from Last Meeting

Action Item	Owner	Relevant Links	Completed
Create discussions for governance and workgroups	Tania	https://github.com/orgs/pyladies/teams/global-council	Yes :ballot_box_with_check:
Set recurrent meetings	Valery	--	Yes :ballot_box_with_check:

New Business

• [x] Resolution: governance structure (https://github.com/orgs/pyladies/teams/global-council/discussions?pinned=1)

Add your names based on your final vote:

Model	Voter
Model 1: based off Marie L update	Tania, Lynn, Marie-L
Model 2: workgroups only
Model 3: Workgroups + internal management +PSF liaison	Juliana Alves, Ana Cecília Vieira, Jessica Upani

Notes: Postponed: Currently a tie (at the time of the meeting) - will need to wait for the others to make a vote. Vote async by Friday. AI: @econchick to post in channel after meeting asking for remaining votes

• [x] Resolution: Working group leads (https://github.com/orgs/pyladies/teams/global-council/discussions/2)

:::warning Using the proposed updates to the working groups by Lynn here :::

Working group	Leadership	Notes
Finance work group	Marie L,
Organiser resources work group	Jessica
Code of Conduct work group	Tania, Valery
Marketing (or "Communications") work group	Juliana, Ana Cecília
Infrastructure work group	Sarah, Lynn
PSF liaison	Tania
Executive / Internal management work group		If elected over model 1 (defining formal roles)

Additional sub-groups or working streams:

• Data + analytics: Marie, Juliana have expressed interest. Would be nice to have an impact report generated over time
• Fundraising: sub-group of finances. Marie expressed interested
• Community liaison: advocacy? Jessica interested

Notes:

• @econchick to reach out to Sarah if she's okay with co-leading Infra WG with me
• Remove the word "Analytics" from "Data & Analytics"? Call it just "Data Work Group"?
• Brainstorm how to setup finance team, fundraising, targets, how much is coming from the PSF, should fundraising be separated from finance (will there be people that will only care about fundraising and not finance)
• Does "community liaison" work with communications in any way?
• Wait until the first resolution is voted upon before defining interest in executive / internal WG

---

• [x] Discussion: Interfacing with the PSF Questions:
  • What the PSF liasion do?
  • Who will be the liaison? There will be rotation?
  • How will we report to the PSF every month?
  • What updates will we include ?
  • Fiscal sponsorship with PSF(ask Lorena more information about this)
  • Note: Tania proposed herself for being the PSF liaison

Notes:

• The liaison would need to sign contracts coming from the PSF
• Setup GitHub sponsorship w/ PSF <-> PyLadies
• Lots of paperwork involved!
• Once all signed, can get started with finances w/ PyLadies
• [name=Marie-Louise] can get the ball rolling since there is some urgency; other people can then join
• Should we do a rotation? 6 months, 1 year?
  • Argument: At least a year is probably enough time to have an effect;
    • it's a lot of work to spread knowledge for a rotation, so a longer one may be better
    • May be a good idea to include more people from the start
  • Argument: A shorter rotation gives opportunity to more people
  • Could match with the rotation timing of the election; at least re-evaluate each year
• How to report to the PSF each month:
  • Idea: a shared document between us and PSF
  • Idea: maybe invited to the PSF meeting?
  • Leave this to the person(s) taking this role
  • AI: @Marie-L to follow up with "how to go about things"

• [x] ~~Replacing Reshama. Any updates from Beth's response?~~ @BethanyG has accepted the 1 year term! :tada: :tada: Welcome Bethany!

Notes: yay Bethany joined! but is quite busy for the remainder of the year - may need to wait to join meetings and such at the beginning of the new year

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

Notes:

• @cecivieira Limit the working groups to 9, since we're only a group of 9.
  • AI: Ana to write up / lead the discussion in the Working Group document
• @Jupani: maybe each working group contributes what they think their responsibilities are

• [x] Discussion: Advocacy
  • How do we define our role as PyLadies ambassadors ?
  • What kind of activities will we be expected to take part in (talks, networking etc.)?

Notes:

• @julianafalves :
  • Answer questions
  • Think in terms of global
  • Bring different experiences, diversity
• @Marie-L :
  • waiving a flag; bringing attention and bring more people to learn Python, new career path
  • networking
  • giving advice w/i community
  • Q: should we be more official in the way that we network? actively recruit maybe? more intentional outreach? reach out to other groups?
  • @JUpani: likes the idea; still trying to understand our role
• AI: LR to make these discussion questions in GitHub
• AI: LR to post this meeting notes and last meeting notes

• [ ] Discussion: Expectation from global advisors about what we take over

  • Will we invite the global advisors to the meeting?

• [ ] Discussion: Update website with names of PyLadies Global Council (name, photo, country), List working groups (“project teams”)

• [ ] How to approve new chapters? Do we need to participate in this? Lynn to update on this

Action Items and Assignees for Next Meeting

Action Item	Owner	Relevant links
post in Slack #globalcouncil channel to ask for an async vote on the Resolution in new business (the governance model)	Lynn
Reach out to Sarah if she’s okay with co-leading Infra WG with Lynn	Lynn
Start the PSF liaison process to get the ball rolling (other people interested can join later, but there's some time sensitivity)	Marie-Louise
Related to the one above: follow up with the PSF on “how to go about things” w/r/t logistics of liaisoning	Marie-Louise
Draft up a proposal for feedback on the over-arching Working Group structure (not including the responsibilities of each WG)	Ana Cecília
Create the remaining discussion questions from this meeting as GitHub discussion threads	Lynn
Post these meeting minutes to the GitHub global council repo as well as last meeting's minutes	Lynn
Create a new meeting agenda for the next meeting (carrying over any old business)	Lynn

@pyladies/pyladies-global-contributors @pyladies/pyladies-global-admin @pyladies/global-council