1:14 p.m.
Hi all,
Following up on the Town Hall we held on June 17 (thank you to the 20+ of
you who joined — recording, slides, and notes are here
<https://github.com/IdentityPython/Meetings/tree/de0977c302ec7bf8b6086ecdd6539c92351620bd/2026-06-17%20IdPY%20Town%20Hall>
if you missed it), the technical group formally re-kicked off on June 26,
and we now have the beginnings of a plan for the rest of the year.
Who's at the table
Representatives from RDCT, NCSA/CILogon, Signatura, RENU, SUNET, and others
joined the re-kickoff, bringing both core-maintainer and
production-operator perspective on SaToSa and the other tools under the
Identity Python Project.
What we accomplished
The group agreed on a work plan
<https://github.com/IdentityPython/Meetings/tree/de0977c302ec7bf8b6086ecdd6539c92351620bd/Working%20Meetings-2026%20Technical%20Re-engagement>
for the next six months, organized around three workstreams:
-
Governance & Maintainer Model — a contributor ladder, documented release
and vulnerability-reporting processes, automated release/SBOM practices.
-
Fork Review & Integration Roadmap — cataloging known forks (thanks to
those who shared your own at the Town Hall!) and prioritizing security
fixes and integration.
-
Documentation Roadmap — easier deployment guidance, better onboarding
docs, automated doc publishing tied to releases.
Full notes: Re-Kickoff Notes
<https://github.com/IdentityPython/Meetings/tree/de0977c302ec7bf8b6086ecdd6539c92351620bd/2026-06-29%20IdPy%20Technical%20Re-Kickoff>
.
How to join
This work is only as good as the people contributing to it. If you'd like
to participate in one of the three workstreams above, reply to this email
or reach out to me directly, and I'll add you to the relevant group and
calendar invites.
Thanks for sticking with this project — the energy from the Town Hall
carried straight into the re-kickoff, and we're glad to have you along for
the next stretch.
Best, Laura