Skip to content

Monthly PyLadies Meeting Notes: Tuesday May 5th, 2026 #175

@BethanyG

Description

@BethanyG

PyLadies Global Meeting

Agenda

New Business

  • Kelly: updated financial report, but nothing has really changed
    • consulting company doing expenses like PEX and such - still needing to be completed
    • still backlogged, but up to March now
    • will share folder to just dump new versions in folder
    • blog post to include high-level numbers (not identifying details)
  • Charter update
    • responded to PSF, no response back
    • will make another request for a collab session, after pycon
    • AI still remain:
      • @econchick to draft post
        • will do before PyCon! so it can be talked about at PyCon if needed
      • @JUpani & @BethanyG to sort comment threads into categories
        simple response vs simple updates to doc vs we should have a discussion and sort out topic/question
        • @JUpani some initial progress
        • next steps: sort out action items; need to establish which of the policies we should tackle next
        • @JUpani and @BethanyG to meet to tackle together
    • @econchick reached out to OSS legal contact - no response yet
  • new website status
    • energy behind this has dwindled
    • new repo for new site to be merged into a branch of the old site
    • @BethanyG to figure out what can be done in a sprint @ PyConUS
      • mostly it's content that is needed (photos, chapter logos, new "pyladies of note" posts), most of the design implementation is done
  • [ ]
  • [ ]
  • [ ]

Old Business: Follow up items from prior meeting:

  • carrying over charter remaining todos from last month
    • later:
      • member verification <- highest priority
      • next: election policy <- next highest priority
        • what can we reuse, what should we update/change from last elections
        • relatedly: where's the old elections.pyladies.com microsite? DNS issue - does it still exist; repo)
        • relatedly: was this repo of election scripts ever used for last one?
      • next/soon: financial policy
      • timeline/deadlines
      • next: blog post for update - particularly about community input and transparency on next steps
      • later: review the process for improvements <- after election process/policy review
  • [ ]
  • [ ]
  • [ ]
  • [ ]
  • [ ]

Action Items and Assignees for Next Meeting

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

Metadata

Metadata

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions