Monthly PyLadies Meeting Notes: Tuesday, July 8th, 2025 #164
Description
PyLadies Global Meeting
- Date: July 8, 2025
- Previous meeting issue link: Monthly PyLadies Meeting Notes: Tuesday, June 10th 2025 10PM UTC #163
- Current meeting attendees: Jessica, Sarah, Lynn, Bethany, Phyllis
Agenda
New Business
- Refresh of Boston Chapter website.
- AI: @BethanyG to follow up with team to make sure subdomain is sorted and everything is working ok.
- Boston had intro call w/Phillis re:direct sponsorship - Direct fiscal sponsorship for individual chapters : who is asking, and how does this work?
These chapters are under the PyLadies agreement, but would have extra requirements and agreements for "agents", fundraisers, and reimbursement. Chapters can also give the funds to global w/o penalty.
- Chicago (existing)
- NYCity (existing)
- Boston (currently requesting)
Vetting and general procedures are still a WIP (how we check out memebers, how we set up stuff)
What about chapter/membership tracking DB - shouldn't change - How much did we raise in Auction?
- raised $61,000 in total cash
- net cash (after food & bev): $29k (does not include a few fees)
- $6500 in donations come thru for the year (last year $18k)
- $35k given in pyladies travel grants this year
- Governance TODOs continuation
- AI: @econchick to create a fresh doc with a v basic outline, then assign ppl sections
- next steps: very early initial draft of sections, then start inviting for feedback outside the council
- Proposal for monthly/quarterly email newsletter to communicate global council actions
- email council notes & any other announcements to chapter emails (gsuite) - first step
- if others want it, we'll need to figure out a subscribe setup
- maybe add automation from GH issue -> send email
- would we want raw meeting notes, or to edit to add context to actually make sense?
- what is actually feasible for us? start with lowest friction, maybe?
- Potential automation to get council announcements/notes into the council-updates channel
- @BethanyG to look into what it will take to set this up via GHActions
- review microsoft's ask to sponsor pyladies
- @BethanyG will respond but first ask for input in response
- Draft proposal for who gets added to the tech/infra workgroup
- what did the PSF use to do before they hired folks for infra?
- setup confidentiality agreements (GDPR, california privacy)
- draft minimum reqs: e.g. active member for 1 year
- idea: keep group small that has access to private info & passwords, but create a group that allows more contribution activity (e.g. ability to merge PRs, but "admin" group to +1 to deploy)
- AI: @econchick look at permissioning
- AI: @BethanyG what does vetting mean? create check list?
- AI: @econchick clarify what all data can be accessed by group
- idea: focus on organization/perms around new website?
- reach out to Carol & Lorena about scheduling a chat
Pushed to next meeting
- Note-taking for council meetings, and how updates and questions from the community are handled
- Website next steps/proposed frameworks (postponed to August meeting)
Still need to narrow down candidate frameworks to top 3-4 for prototyping.
Still need to build out pyladies map with up-to-date chapter info - taking questions from the community
Old Business: Follow up items from prior meeting:
- [ ]
- [ ]
- [ ]
- [ ]
Action Items and Assignees for Next Meeting
| Action Item | Owner | Relevant links |
|---|
@pyladies/pyladies-global-contributors
@pyladies/pyladies-global-admin