# Vote to promote Seth Larson

**URL:** <https://discuss.python.org/t/vote-to-promote-seth-larson/107622>\
**Category:** Committers\
**Tags:** promotion\
**Created:** [June 4, 2026, 12:27pm UTC](https://discuss.python.org/t/vote-to-promote-seth-larson/107622 "2026-06-04T12:27:12Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Stanfromireland](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/stanfromireland/32/10102_2.png) [@Stanfromireland](https://discuss.python.org/u/Stanfromireland)\
**Post date:** [June 4, 2026, 12:27pm UTC](https://discuss.python.org/t/vote-to-promote-seth-larson/107622/1 "2026-06-04T12:27:12Z")

</div>

@hugovk and I would like to promote Seth Larson ([@sethmlarson](https://github.com/sethmlarson) on GitHub) to the Python core team.

Seth is the PSF Security Developer-in-Residence and has done a tremendous amount of work to improve both the security of CPython and its security processes. For example, he has authored three PEPs:

- [PEP 761 – Deprecating PGP signatures for CPython artifacts](https://peps.python.org/pep-0761/)
- [PEP 770 – Improving measurability of Python packages with Software Bill-of-Materials](https://peps.python.org/pep-0770/)
- [PEP 811 – Defining Python Security Response Team membership and responsibilities](https://peps.python.org/pep-0811/)

The last of these formalised the [Python Security Response Team (PSRT)](https://devguide.python.org/security/psrt/index.html) and brought nine new people onto the team since February; helping us deal with the [recent increase](https://mastodon.social/@sethmlarson/116680835974208152) in vulnerability reports. Seth also helps lead and manage the team.

Seth has authored [numerous](https://github.com/pulls?q=is%3Apr+author%3Asethmlarson+org%3Apython+is%3Amerged+sort%3Acreated-asc+) merged pull requests across the Python organisation, ranging from security fixes in CPython to various improvements to Python’s infrastructure and tooling, including improvements to the security of the CPython release process. Seth was also promoted to the triage team in [late 2023](https://github.com/python/core-workflow/issues/515) and has participated in a [large number](https://github.com/search?q=involves%3Asethmlarson+archived%3Afalse+org%3Apython&type=issues) of issues.

In addition, he [regularly blogs](https://sethmlarson.dev/) about security for both [C](https://sethmlarson.dev/security-developer-in-residence-report-38)[P](https://sethmlarson.dev/security-developer-in-residence-weekly-report-35)[y](https://sethmlarson.dev/security-developer-in-residence-weekly-report-33)[t](https://sethmlarson.dev/security-developer-in-residence-weekly-report-29)[h](https://sethmlarson.dev/security-developer-in-residence-weekly-report-28)[o](https://sethmlarson.dev/security-developer-in-residence-weekly-report-19)[n](https://sethmlarson.dev/security-developer-in-residence-weekly-report-14) and the wider [P](https://sethmlarson.dev/deprecate-confusing-apis-like-os-path-commonprefix)[y](https://sethmlarson.dev/respecting-maintainer-time-should-be-in-security-policies)[t](https://sethmlarson.dev/security-work-isnt-special)[h](https://sethmlarson.dev/un-open-source-week-2025-security-for-the-long-haul)[o](https://sethmlarson.dev/slop-security-reports)[n](https://sethmlarson.dev/security-developer-in-residence-weekly-report-17) ecosystem and co-organised the [Trailblazing Python Security track](https://us.pycon.org/2026/tracks/security/) at PyCon US this year. Seth is also consistently helpful and constructive in discussions, reviews, and community interactions. We already have a lot of trust in Seth, and he is well-deserving of promotion to the core team.

_Poll ([view on site](https://discuss.python.org/t/vote-to-promote-seth-larson/107622/1))_

---

<div class="post-metadata">

**Author:** ![gpshead](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/gpshead/32/54_2.png) [@gpshead](https://discuss.python.org/u/gpshead)\
**Post date:** [June 4, 2026, 4:15pm UTC](https://discuss.python.org/t/vote-to-promote-seth-larson/107622/2 "2026-06-04T16:15:01Z")

</div>

Yes please! +1 This is another case of _“oh right, they’re not yet? oops, lets fix that!”_ given the great work and great communicating Seth has been doing.

---

<div class="post-metadata">

**Author:** ![savannahostrowski](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/savannahostrowski/32/25496_2.png) [@savannahostrowski](https://discuss.python.org/u/savannahostrowski)\
**Post date:** [June 4, 2026, 4:19pm UTC](https://discuss.python.org/t/vote-to-promote-seth-larson/107622/3 "2026-06-04T16:19:17Z")

</div>

Huge +1!

Seth is super awesome and we’ve already been benefitting from his great work for a long time (thanks Seth!).

---

<div class="post-metadata">

**Author:** ![storchaka](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/storchaka/32/217_2.png) [@storchaka](https://discuss.python.org/u/storchaka)\
**Post date:** [June 4, 2026, 7:42pm UTC](https://discuss.python.org/t/vote-to-promote-seth-larson/107622/4 "2026-06-04T19:42:54Z")

</div>

He was not?!

---

<div class="post-metadata">

**Author:** ![hugovk](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/hugovk/32/14505_2.png) [@hugovk](https://discuss.python.org/u/hugovk)\
**Post date:** [June 11, 2026, 12:50pm UTC](https://discuss.python.org/t/vote-to-promote-seth-larson/107622/5 "2026-06-11T12:50:04Z")

</div>

Thanks everyone for voting, the result is 44 positive and no negative votes! 🎉

We’ve emailed the Steering Council, and assuming they don’t veto, welcome to the core team, Seth!

---

<div class="post-metadata">

**Author:** ![Loren](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/loren/32/30770_2.png) [@Loren](https://discuss.python.org/u/Loren)\
**Post date:** [June 11, 2026, 4:45pm UTC](https://discuss.python.org/t/vote-to-promote-seth-larson/107622/6 "2026-06-11T16:45:17Z")

</div>

Yay, congrats Seth!

---

<div class="post-metadata">

**Author:** ![diegor](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/diegor/32/34816_2.png) [@diegor](https://discuss.python.org/u/diegor)\
**Post date:** [June 12, 2026, 10:56am UTC](https://discuss.python.org/t/vote-to-promote-seth-larson/107622/7 "2026-06-12T10:56:53Z")

</div>

@sethmlarson Congratulations! This is indeed an excellent result! It’s all well deserved. Security in the Python world has reached another level thanks your continuous effort. Keep up with the excellent work and welcome to the team! 🎉

---

<div class="post-metadata">

**Author:** ![sethmlarson](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/sethmlarson/32/1644_2.png) [@sethmlarson](https://discuss.python.org/u/sethmlarson)\
**Post date:** [June 12, 2026, 1:24pm UTC](https://discuss.python.org/t/vote-to-promote-seth-larson/107622/8 "2026-06-12T13:24:16Z")

</div>

Thank you @Stanfromireland and @hugovk for nominating me and everyone for the kind words 🙂 I’m grateful for the opportunity to contribute back to the community that has done so much for me and others, thank you all 💜

---

<div class="post-metadata">

**Author:** ![barry](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/barry/32/42_2.png) [@barry](https://discuss.python.org/u/barry)\
**Post date:** [June 12, 2026, 11:04pm UTC](https://discuss.python.org/t/vote-to-promote-seth-larson/107622/9 "2026-06-12T23:04:50Z")

</div>

> [@hugovk](#):
>
> We’ve emailed the Steering Council, and assuming they don’t veto, welcome to the core team, Seth!

Unanimously, we do not! Welcome and congrats Seth!
