Steering Council meeting, 20 Apr 2026

Members

Emma: Draft blog post on 6.x Features: Rob is the only one who answered positively
- Paste - plan publish - communicate with other authors on slack - Emma
- Share on #marketing channel in Slack
Sovereign Tech Fund
- Emma: Get one or more project(s) ready (maybe Admin or at least list of places to start)
- Plan another meeting with Lexi once the above is done
Tim: Technical Governance document
- Collecting feedback at https://github.com/django/deps/pull/107
Tim: Teams Charters
- Security - Transitioning last open items to team discussions
- Translations - Need to reach out to Claude
Carlton: Annual release DEP
- Working on it, should target for a month

Tom raised a concern about dropping the core team designation without mention
This was allowed in DEP 10, but doesn’t appear to be awarded out
Should this go in DEP 19 or not?
The board previously looked into titles, awards.
Who would identify people?
- Could be automatically identified from GitHub and Trac
- Quarterly review- perhaps conferring with the fellows as a double check quarterly
Tim: Relay this with the rest of the SC.

A Q&A with past Djangonauts to help identify next steps for agreed upon new features
The goal would be to get people moving forward on the feature ideas and bringing these people further into the fold as regular contributors.
- This likely would serve as a trial for a broader Django event

https://github.com/django/dsf-working-groups/pull/74/
Tim: The board may be maxed out for WG support in their current shape, and we (the SC) expressed a preference to do less on the liaison side of things
Frank: There’s probably room for liaisons in the “contact when needed” realm
Tom: This seems useful, but more in the SC area.