Monthly PyLadies Meeting Notes: Tuesday, August 5th, 2025

[BethanyG]

PyLadies Global Meeting

• Date: August 5th, 2025
• Previous meeting issue link: Monthly PyLadies Meeting Notes: Tuesday, July 8th, 2025 #164
• Current meeting attendees: trallard (Tania), JessicaUpani, BethanyG, econchick (Lynn)

Agenda

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

New Business

• Note-taking for council meetings, and how updates and questions from the community are handled

  • turn Gemini on as first pass? do we have access to this? (afak, after doing some digging we do not have access with our current permissions. Whomever administers our account at the PSF would need to turn the feature on. -BethanyG)
  • someone to add ancillary notes
  • Hackpad feels like too much friction
  • problem to solve: all of us want to participate in convo, no one is great at keeping notes; how can we capture what's discussed in meetings and share it to community without someone always unable to participate fully because they are taking notes?
  • slack integration w/ github action
    • make PR -> post to a specific slack channel
    • global org repo
    • also GH actions to trigger an email
  • AI: @BethanyG to try PoC with slack integration & email

• Website next steps/proposed frameworks (postponed from July 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
  • how can we just hand it over to Maria Jose and folks?
  • just want to hand over the static website redesign
    • should be well/tight scoped, very clear
    • reqs: static, nothing fancy, keep existing hosting & deployment setup;
      • what's the easiest to maintain? this team may not be around forever for maintenance
      • just implement the design
      • no integrations, no database, no member or other portal
      • just have a map
    • using mkdocs? jekyll? hugo? python-only?
    • regular checkins like with Smera & the design?
      • include a "here's what we anticipate working on in the next month"
    • initial meeting about processes & ways of working
    • AI: @trallard schedule final design review with Smera
    • AI: @econchick to do an initial reach out/reply
    • AI: 1-pager doc of of scope then reach out
    • AI: after doc, schedule a kick-off chat

• Invite to sponsor PyCon Ghana (email received July 16th)

  • AI: @econchick : reply asking to use the new intake form; need alignment with our mission
  • potential: $500 (same as PyHo)

• taking questions from the community - how/where do we answer

  • seems like no clarity as to how community members can pose questions, and how/if they can get answers to them
    • some slack channel? or direct to specific areas?
    • define expectations e.g. of when to expect an answer?
    • a designated "somewhere" feel like a good idea
    • do we want to better leverage the discussion board?
      • give it a try! let's announce, see how it works
      • AI: @BethanyG to volunteer to monitor, announce in slack
      • council members should agree: are we going to say we'll answer once a month? or as needed? or what else?
      • may be a good angle to socialize what the council is responsible for, what it isn't responsible for - the way we answer those will set expectation

• Governance:

  • have charter ready for elections
  • goal of elections in Q1 2026? or by PyCon 2026?
    • how to we take a stab at ensuring pyladies members vote and not randos?
      • will this push back the goal of election by a certain time?
      • need to have enough lead time to have candidates be known, to have election be known
    • promote election during PyLadiesCon
    • should we have the charter "ratified" by community before election?

Old Business: Follow up items from prior meeting:

• 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
  • AI: @BethanyG to look into what it will take to set this up via GHActions
• Punt to next meeting 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 (Scheduled for Thursday, August 7th at 2pm PDT)

Action Items and Assignees for Next Meeting

Action Item	Owner	Relevant links

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