Skip to content

Monthly PyLadies Meeting Notes November 4th, 2025 #169

@BethanyG

Description

@BethanyG

Upcoming Meeting. Please add proposed discussion/agenda items below or in the comments. Thanks!

PyLadies Global Meeting

Agenda

Review Actions Items from Last Meeting

Action Item Owner Relevant links Completed

New Business

  • PyLadiesSF logo update
    • concerns over font - didn't use pyladies wordmark
    • should we forward to PSF trademark committee? we're not experts in trademark law
    • AI: @JUpani to reply to PyLadiesSF and including PSF trademark committee
  • Publish 2025 POA winners
    • need to publish winners on the kit and the blog
    • previous publish PRs: kits, blog
    • AI: @MmeMarieLouise to complete; will send the council a draft ASAP
  • (FYI) Changes to funding request spreadsheet (administrative columns for tracking/paper trail)

Old Business: Follow up items from prior meeting:

  • Chapter Sticker Policy
    • current approach is not sustainable - lynn just shipping whenever someone requests
    • establish a policy: when to ship/not ship, do we want to just have a designated budget
    • idea:
      • have one yearly "call for sticker orders" around PyCon US
      • require low shipping costs or have someone pick up at PyCon US
      • require request via sponsorship request form
      • loose limit of $50 per chapter, would be about 200-250 2" stickers at our scale
      • OK for chapters to want their own custom sticker (and not just global stickers)
      • AI: @econchick to draft this policy in kit for council review
  • PyLadies website update
    • had a meeting - have 3 contenders for the framework
      • trying to go as far as possible with mkdocs with material theme (other frameworks: astro or hugo)
      • splitting up work; have a private repo setup
        • as soon as we get to a point that we're good to go forward w/ framework, then open up repo for contributions
        • once the new site is ready to be deployed, then merge it into existing repo
      • lynn's concerns over not doing it in existing repo from the beginning:
        • preserve git commit history of the new repo when merging into existing repo
          • AI: @BethanyG to make a ticket reflecting this
        • make it SUPER explicit with new repo, once made public, that it's not the website that's deployed
      • hoping for CiviCRM link for member registration
      • will put out a call for chapter logos
      • need footer links
      • need decision for chapter directory
      • need decision for where call to action links lead to
      • need decision to approach for chapter pages - want to make it easy for a chapter to put info in one place and have things magically made for them, or do we want minimal chapter info and links out to each websites
  • Governance update - first draft of PyLadies Chapter
    • current status: lots of bullets, some sections missing
      • lynn needs more help
    • need someone(s) to take on Tania's items she originally assigned herself on
    • AI: @MmeMarieLouise to be the "road manager"
    • AI: @BethanyG to take on some of the items Tania signed up for
    • for next meeting:
      • initial first draft
      • flesh everything out so that it's reviewable
      • turn bullets into prose
      • fill in empty sections
  • delegating social media mgmt
    • denny asked for access for PyLadiesCon cross-posts
      • maybe she could take on more of the general pyladies social media posting? :D
      • AI: @econchick to ask denny if she's interested
    • lynn created a blue sky account for pyladies
    • AI: create a general PyLadies account for Reddit for moderating @BethanyG
    • AI: add bluesky account to pyladies website @BethanyG

Action Items and Assignees for Next Meeting

Action Item Owner Relevant links

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

Metadata

Metadata

Assignees

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