FEDIDEVS

For too long the same voices have dominated the #PyConUS LobbyCon.

It's time for change we can believe in: The Patio at the Hyatt!

Feel the cool ocean breezes as you gaze over the heart of West Coast commerce.

Play your boardgames at the port they all came through!

The outdoor revolution is at hand, join me in two weeks, #pythonistas!

The fire under my behind to get a Trusted Publishing setup for something not GitHub/gitlab based continues to grow.

We must remove every barrier to getting off github.

#PyConUS

I have made it to my first talk at #PyConUS

First up: Python Security with @sethmlarson and @miketheman

#PyConUS

Good morning #PyConUS and @elthenerd

Hello #PyConUS! It's time for @kattni's talk: "Switching from Sphinx to Markdown"

Come join us in Ballroom B

“There’s no ROI on hope” @amcasari at #PyConUS ✨✨✨

@kattni is a Core Developer on @beeware, as well as being the Chair of @pyohio

She led the documentation migration project for #BeeWare

#PyConUS

Hello #PyConUS folks! There’s an unofficial signal group myself and some other familiar faces have put together.

We have:
- cool people
- a code of conduct
- a 4-week message retention policy
- at least one doctor

If you’re attending #PyCon and want to join, reply or DM me 🐍✨

At current pace, there will be 65 CVEs that affect the #python package ecosystem this year.

This is easily 3x-4x previous years.

One response to this is PEP-811: defining a Python security response team, membership and responsibilities (https://peps.python.org/pep-0811/)

This makes it easier to add more members and spread the load.

One result already in place: a formal vulnerability report response framework, uniting Github security policies and docs and the security response team.

#PyConUS #PyCon

“Reviews used to be a conversation. That created maintainers”

Pablo Galindo Salgado at #PyConUS