https://django.github.io/steering-council/2026-10-19T00:00:00+00:00Meeting minutes of the Django Steering Council2026-10-19T00:00:00+00:00https://django.github.io/steering-council/meetings/2026/2026-10-19-steering-council/

<h2 id="agenda">Agenda</h2> <ul> <li>Quarterly outreach message</li> <li>Sovereign Tech Agency Resilience Fund</li> <li>VectorField DEP</li> <li>Memcached clients</li> <li>Jazzband updates</li> <li>Triage and Review Team suggestions</li> </ul> <h2 id="action-items">Action items</h2> <ul> <li>Sovereign Tech Fund <ul> <li>Tim, Natalia, Jacob to meet with Erik next week about the Sovereign Tech Agency resilience program</li> </ul> </li> <li>Tim: Teams Charters <ul> <li><a href="https://github.com/django/dsf-working-groups/pull/98">https://github.com/django/dsf-working-groups/pull/98</a></li> </ul> </li> <li>Tim: Post quarterly outreach message</li> <li>Tim: Comment on memcached clients</li> <li>New Features improvements <ul> <li>Revisit the language around closing, so we can close things</li> <li>Create a curated view of issues for people to participate in a high-impact area</li> <li>Create new project board views with documentation/blog post with how to participate in new feature process</li> </ul> </li> <li>Fellows: Review suggested major features</li> <li>Fellows: Give feedback on: <a href="https://docs.google.com/document/d/1DY0UClQ_AgEqT5hDQh4Kr5CQordCyVt5FGEuiAYl5-w/edit?usp=sharing">Quarterly contributor outreach</a></li> <li>Jacob: Review Translators Charter</li> <li>All: Have a week to re-read one last time, will approve at the end of the week if no concerns</li> </ul> <h2 id="quarterly-outreach-message">Quarterly outreach message</h2> <ul> <li><a href="https://docs.google.com/document/d/1DY0UClQ_AgEqT5hDQh4Kr5CQordCyVt5FGEuiAYl5-w/edit?usp=sharing">Quarterly contributor outreach</a></li> <li>Ready to go, there’s the last mention of AI commentary <ul> <li>Tim: I’m going to remove the AI comment and post this</li> </ul> </li> </ul> <p>Sovereign Tech Agency Resilience Program</p> <ul> <li>Emma: If we pursue Sovereign Tech Fund, there may be issues with copyright issue as there were other similar issues with another organization. We do not know the stance of the Sovereign Tech Fund specifically.</li> <li>Tim and Jacob met with Mirko (spelling?) and the meeting was positive. It seemed likely that someone could be paid to work on Django. There would be more to discuss with defining duties and navigating with Fellows to be beneficial without conflict.</li> </ul> <h2 id="vectorfield-dep">VectorField DEP</h2> <ul> <li>The DEP has been updated based on the feedback from others, thank you Lily!</li> <li>The number is now 24. <ul> <li>We’ve been bit by this a few times</li> <li>Python has a request a number and it’s provided</li> <li>We could not give a number until we merge into the repo</li> <li>We don’t need a DEP, and can likely just edit the template</li> </ul> </li> </ul> <h2 id="memcached-clients">Memcached clients</h2> <ul> <li><a href="https://forum.djangoproject.com/t/should-we-stop-recommending-pylibmc/42993/16">https://forum.djangoproject.com/t/should-we-stop-recommending-pylibmc/42993/16</a></li> <li>Tim Graham is willing to maintain python-memcached</li> <li>Remove pylibmc from docs, add python-memcached</li> </ul> <h2 id="jazzband-updates">Jazzband updates</h2> <ul> <li>Jannis has been facilitating projects moving out of Jazzband</li> <li><a href="https://django-commons.org/blog/posts/2026-10-14-policy-changes-for-better-community-maintenance/">Django Commons updated their governance</a> to accept dormant and archived projects</li> </ul> <h2 id="triage-and-review-team-suggestions">Triage and Review Team suggestions</h2> <ul> <li><a href="https://forum.djangoproject.com/t/proposed-changes-to-trac-to-address-problematic-contribution-patterns-please-vote/46191/">https://forum.djangoproject.com/t/proposed-changes-to-trac-to-address-problematic-contribution-patterns-please-vote/46191/</a></li> <li>Frank’s onboard with them.</li> <li>Emma’s unsure about 5, restricting changing triage status to triage and review <ul> <li>We’ve been talking about allowing people to triage tickets to get involved, this would eliminate a recommended easy path to participate</li> <li>Is the team actively adding members? Yes, they’ve added 3+ people in the last six months</li> <li>This would mean a non-member would have to read everything, provide feedback on whether something will work</li> </ul> </li> </ul>

2026-10-05T00:00:00+00:00https://django.github.io/steering-council/meetings/2026/2026-10-05-steering-council-with-fellows/

<h2 id="agenda">Agenda</h2> <ul> <li>Fellows: <ul> <li><a href="https://github.com/django/deps/pull/113/">Set returning DEP</a> really needs reviews <ul> <li>Jacob to nudge next week, otherwise default approved</li> </ul> </li> <li>All memcached python clients are defunct</li> <li>PyPy 8.0 support?</li> <li>Python 3.15 support and makedirs semantics <ul> <li><a href="https://forum.djangoproject.com/t/proposal-make-file-upload-permissions-respect-umask/45022/">https://forum.djangoproject.com/t/proposal-make-file-upload-permissions-respect-umask/45022/</a></li> </ul> </li> </ul> </li> <li>Sovereign Tech Fund resilience program</li> <li>Contributor outreach message</li> </ul> <h2 id="action-items">Action items</h2> <ul> <li>Sovereign Tech Fund <ul> <li>Tim applied for the Sovereign Tech Resilience program</li> <li>Tim, Natalia, Jacob to meet with Erik next week about the Sovereign Tech Fund resilience program</li> </ul> </li> <li>Tim: Teams Charters <ul> <li>Translations Team - Draft initial version for Fellows and Claude to review</li> <li><a href="https://github.com/django/dsf-working-groups/pull/98">https://github.com/django/dsf-working-groups/pull/98</a></li> </ul> </li> <li>New Features improvements <ul> <li>Revisit the language around closing, so we can close things</li> <li>Create a curated view of issues for people to participate in a high-impact area</li> <li>Create new project board views with documentation/blog post with how to participate in new feature process</li> </ul> </li> <li>Fellows: Review suggested major features</li> <li>Fellows: Give feedback on: <a href="https://docs.google.com/document/d/1DY0UClQ_AgEqT5hDQh4Kr5CQordCyVt5FGEuiAYl5-w/edit?usp=sharing">Quarterly contributor outreach</a></li> <li>Jacob: Review Translators Charter</li> <li>Carlton: Post on the forum about the state and migrating away from these packages (memcached python clients are defunct) <ul> <li><a href="https://forum.djangoproject.com/t/should-we-stop-recommending-pylibmc/42993/10">https://forum.djangoproject.com/t/should-we-stop-recommending-pylibmc/42993/10</a></li> </ul> </li> <li>Natalia: Create branch for file upload permissions change</li> <li>All: Have a week to re-read one last time, will approve at the end of the week if no concerns</li> </ul> <h2 id="fellows">Fellows</h2> <h3 id="set-returning-dep-really-needs-reviews"><a href="https://github.com/django/deps/pull/113/">Set returning DEP</a> really needs reviews</h3> <ul> <li><a href="https://github.com/django/deps/pull/113/">https://github.com/django/deps/pull/113/</a></li> <li>Table valued expressions- looking for Steering Council Review and Approval</li> <li>Implementation was reviewed at Django on the Med <ul> <li>Seemed to be in the right direction. Simon provided some feedback on the PR</li> </ul> </li> <li>Want to have the DEP approved so we can merge the PR when it’s ready</li> <li>Tim reviewed and thinks it looks good. His only comments were in regard to technical writing.</li> <li>People have a week to re-read one last time, will approve at the end of the week if no concerns</li> </ul> <h3 id="all-memcached-python-clients-are-defunct">All memcached python clients are defunct</h3> <ul> <li>No memcached clients support Python 3.14 <ul> <li>They haven’t updated the test suites</li> </ul> </li> <li>Tim Graham has been merging changes for <a href="https://github.com/linsomniac/python-memcached/">https://github.com/linsomniac/python-memcached/</a> <ul> <li>He doesn’t have permission to release it</li> </ul> </li> <li><a href="https://github.com/mxamin/pylibmc2">https://github.com/mxamin/pylibmc2</a> <ul> <li>This one was picked up by another open source contributor who maintained another package and needed it</li> </ul> </li> <li>Options <ul> <li>Redirect people to another project from an existing one</li> <li>Extract the MemCached cache wrapper out of Django core under the Django org</li> <li>Work to get a maintainer to pass off the project</li> </ul> </li> <li>Next steps <ul> <li>Carlton: Post on the forum about the state and migrating away from these packages</li> </ul> </li> </ul> <h3 id="pypy-80-support">PyPy 8.0 support?</h3> <ul> <li>PyPy 8.0 release <a href="https://pypy.org/posts/2026/09/pypy-v800-release.html">https://pypy.org/posts/2026/09/pypy-v800-release.html</a></li> <li>This supports Python 3.12</li> <li>Do we want to support this even though we know 3.12 will age out in a few months? <ul> <li>No, this feels like more work than it’s worth right now</li> </ul> </li> <li>Our docs say that PyPy works <ul> <li>We should update this to reflect the reality</li> </ul> </li> <li>Next steps: <ul> <li>Remove PyPy from the docs since we’re not testing against it</li> <li>Remove references to PyPy: <a href="https://code.djangoproject.com/ticket/36123">https://code.djangoproject.com/ticket/36123</a> <ul> <li>Re-adding testing for PyPy: <a href="https://code.djangoproject.com/ticket/37363">https://code.djangoproject.com/ticket/37363</a></li> </ul> </li> <li>Add mention somewhere explaining the removal? (Blog, release notes, ?)</li> </ul> </li> </ul> <h3 id="python-315-support-and-makedirs-semantics">Python 3.15 support and makedirs semantics</h3> <ul> <li><a href="https://forum.djangoproject.com/t/proposal-make-file-upload-permissions-respect-umask/45022/">https://forum.djangoproject.com/t/proposal-make-file-upload-permissions-respect-umask/45022/</a></li> <li>Proposal: Created upload directories takes on umask from the process <ul> <li>Switch for Python 3.15</li> <li>Add mention to release notes</li> </ul> </li> <li>Current: The upload directories takes on the permissions set in <code>FILE_UPLOAD_DIRECTORY_PERMISSIONS</code></li> <li>Natalia to create new branch with proposed changes and get feedback</li> </ul> <h2 id="sovereign-tech-fund-resilience-program">Sovereign Tech Fund resilience program</h2> <ul> <li>We received a positive message that indicated we would be eligible. They had follow-up questions that Tim and Sarah have answered.</li> <li>Tim to respond via email, Tim reiterate uncertainty on our side of things in email</li> <li>Tim, Natalia, Jacob to meet with Erik next week.</li> <li>This meeting is likely to be feeling things out and determining what’s possible.</li> </ul> <h2 id="contributor-outreach-message">Contributor outreach message</h2> <ul> <li>Needs the three major things we want feedback on <ul> <li>Requires Fellows feedback</li> <li>This can be done by the end of month</li> </ul> </li> <li>[not discussed] Should we include a CTA for people to join Translators and GSoC WGs?</li> </ul>

2026-09-21T00:00:00+00:00https://django.github.io/steering-council/meetings/2026/2026-09-21-steering-council/

<h2 id="agenda">Agenda</h2> <ul> <li>Review content for quarterly contributor outreach</li> </ul> <h2 id="action-items">Action items</h2> <ul> <li>Sovereign Tech Fund <ul> <li>Tim applied for the Sovereign Tech Resilience program</li> </ul> </li> <li>Tim: Teams Charters <ul> <li>Translations Team - Draft initial version for Fellows and Claude to review</li> </ul> </li> <li>New Features improvements <ul> <li>Revisit the language around closing, so we can close things</li> <li>Create a curated view of issues for people to participate in a high-impact area</li> <li>Create new project board views with documentation/blog post with how to participate in new feature process</li> </ul> </li> <li>Fellows: Review suggested major features</li> </ul> <h2 id="review-content-for-quarterly-contributor-outreach">Review content for quarterly contributor outreach</h2> <ul> <li>Review New Features queue</li> <li>Write a message to close small things with how to proceed to reopen <ul> <li>Blog post explaining it, where to share, hash tags, forum, discord</li> </ul> </li> <li>Add a historical tag as per Carlton’s suggestion</li> <li>Refinement <ul> <li>On DEP, when there are a bunch of unanswered questions and it’s large</li> <li>Can we identify the next steps?</li> </ul> </li> <li>Create standard sign posting when we advance things <ul> <li>Where is there uncertainty?</li> <li>Can this go into Trac directly?</li> </ul> </li> </ul>

2026-09-07T00:00:00+00:00https://django.github.io/steering-council/meetings/2026/2026-09-07-steering-council-with-fellows/

<h2 id="agenda">Agenda</h2> <ul> <li>DjangoCon US New Features discussion</li> <li>Using extras to package other tools</li> <li><a href="https://github.com/django/new-features/issues/3#issuecomment-5464308812">Experimental features GSoC Project</a></li> <li>Fellows topics <ul> <li>Ping: <a href="https://github.com/django/deps/pull/113">CompositeField DEP</a></li> <li>Status of <a href="https://github.com/django/deps/pull/88">Content Type Parsing DEP</a></li> </ul> </li> <li>Case study blog posts</li> <li>Django usage telemetry/metrics</li> </ul> <h2 id="action-items">Action items</h2> <ul> <li>Sovereign Tech Fund <ul> <li>Emma: Get one or more project(s) ready (maybe Admin or at least list of places to start)</li> <li>Plan another meeting with Lexi once the above is done</li> </ul> </li> <li>Tim: Teams Charters <ul> <li>Translations Team - Need to reach out to Claude</li> </ul> </li> <li>Carlton: DEP 20 <ul> <li><s>Final clean ups</s></li> <li><s>Short sentence describing new release process</s></li> <li><s>Short blog post draft with clear transition timeline statement.</s></li> </ul> </li> <li>New Features improvements <ul> <li>Revisit the language around closing, so we can close things</li> <li>Create a curated view of issues for people to participate in a high-impact area</li> <li>Create new project board views with documentation/blog post with how to participate in new feature process</li> </ul> </li> <li>Tim: Review Lexi’s email and forward along</li> <li>Fellows: Review suggested major features</li> </ul> <h2 id="action-items-review">Action Items Review</h2> <ul> <li>DEP 20 <ul> <li>Have the list of the last bits to implement to get it from accepted to final</li> </ul> </li> <li>Lexi reached out regarding about sovereign tech fund via email <ul> <li> <blockquote> <p>One of the available areas is <strong>Technical Debt Management</strong> – essentially hands-on engineering work aimed at reducing maintenance burden and improving long-term sustainability, with the work delivered as maintainer-ready contributions</p> </blockquote> </li> <li>The other major projects that were originally discussed either turned into GSoC or aren’t properly scoped for the sovereign tech fund.</li> </ul> </li> </ul> <h2 id="djangocon-us-new-features-discussion">DjangoCon US New Features discussion</h2> <ul> <li>Major changes for 6.2 <ul> <li>Big features that may in vicinity of finish lines: <ul> <li><a href="https://github.com/django/django/pull/16905">https://github.com/django/django/pull/16905</a> moving a model between apps</li> <li><a href="https://github.com/django/django/pull/18805">https://github.com/django/django/pull/18805</a> multiline template tags <ul> <li>There were some issues in a test project that suggests it may be a bit further than we’d like for 6.2</li> <li>Could potentially reduce scope</li> </ul> </li> <li><a href="https://github.com/django/django/pull/21226">https://github.com/django/django/pull/21226</a> injectable comments into SQL for tracability (AI heavy)</li> <li><a href="https://github.com/django/django/pull/18863">https://github.com/django/django/pull/18863</a> Composite GFK support</li> <li><a href="https://github.com/django/django/pull/18332">https://github.com/django/django/pull/18332</a> expanding the messages API</li> <li><a href="https://github.com/django/django/pull/20336">https://github.com/django/django/pull/20336</a> initial filters on QuerySet classes</li> <li><a href="https://github.com/django/django/pull/16329">https://github.com/django/django/pull/16329</a> Embed raw queries as subqueries</li> </ul> </li> <li>Highlight/focus/attention: <ul> <li>Moving models between apps <ul> <li>Shai planning on working on during DotM</li> <li>Emma has an django-devs mailing list for proposal for moving models between apps, it was a fairly small change <ul> <li>Premise was to be able to write migrations within the (models?) via contribute_to_class</li> <li><a href="https://stackoverflow.com/questions/24311993/how-to-add-a-new-field-to-a-model-with-new-django-migrations/27450550#27450550">https://stackoverflow.com/questions/24311993/how-to-add-a-new-field-to-a-model-with-new-django-migrations/27450550#27450550</a></li> </ul> </li> </ul> </li> <li><s>Rate limiting</s> <ul> <li>Needs a DEP</li> <li>Need to identify what is the universal functionality we need, “the 80% solution”</li> <li>Likely not a 6.2 release because there isn’t an agreed upon solution yet</li> </ul> </li> <li>Initial filters on QuerySet <ul> <li>Jacob: this seems reasonable</li> </ul> </li> <li>Fellows please review the list of features to see what’s close</li> </ul> </li> <li>Other features: <ul> <li><a href="https://github.com/django/django/pull/21855">https://github.com/django/django/pull/21855</a> Added support for HTTP QUERY method</li> <li><a href="https://github.com/django/django/pull/16381">https://github.com/django/django/pull/16381</a> QuerySet.select_for_share()</li> <li><a href="https://github.com/django/django/pull/19298">https://github.com/django/django/pull/19298</a> Handle returning rows in update and bulk_update</li> </ul> </li> <li>Smaller features <ul> <li><a href="https://github.com/django/django/pull/21847">https://github.com/django/django/pull/21847</a> Improving debug messaging for CSRF errors</li> <li><a href="https://github.com/django/django/pull/18468">https://github.com/django/django/pull/18468</a> Adding QuerySet.executed_queries</li> <li><a href="https://github.com/django/django/pull/19603">https://github.com/django/django/pull/19603</a> Partitioned cookies (AI heavy)</li> </ul> </li> <li>Proposed message <a href="https://docs.google.com/document/d/12qAwQ5g_4yiZa0XtcQpMho6UVVnhEdIVhKKheknh6KU/edit?usp=sharing">6.2 major feature check-in</a> <ul> <li>It’s not necessary for us to have “major features” after big changes in 6.0 and 6.1</li> </ul> </li> </ul> </li> <li>Quarterly outreach to ask for attention in specific areas <ul> <li>Thoughts <ul> <li>Can we add a DSF sponsored email list? <ul> <li>The Board is working on a quarterly newsletter, but was sidelined for ED work</li> </ul> </li> <li>This would start as a blog post and forum post, until newsletter is created</li> </ul> </li> <li>Help filling out <ul> <li>Carlton will help after DotM</li> <li>We should send this after DotM when things are usually better defined</li> </ul> </li> </ul> </li> <li>Django on the Prairie <ul> <li>Paolo convinced Frank to host!</li> <li>Sprint days in Lawrence at the REVSYS office</li> <li>Proposed time is in spring</li> <li>Should we have guidelines on how to host these events? <ul> <li>Goal for DotM is to document how to host and run</li> <li>Have start on Django specific bit here: <a href="https://github.com/django/new-features/blob/main/hosting-new-feature-review.md">https://github.com/django/new-features/blob/main/hosting-new-feature-review.md</a></li> <li>On trademarking and using DjangoCon terminology: <a href="https://www.djangoproject.com/foundation/conferences/">https://www.djangoproject.com/foundation/conferences/</a></li> </ul> </li> </ul> </li> </ul> <h2 id="fellows">Fellows</h2> <ul> <li>FYI: we’re getting confident triage from agent-wielding beginners now. No action needed for now (hopefully) <ul> <li>When new tickets are created, we’re seeing LLM generated triage acceptance messages</li> <li>No action needed for now since Fellows still review latest actions and can revert things as necessary</li> </ul> </li> </ul> <h3 id="compositefield-dep">CompositeField DEP</h3> <ul> <li>Ping: <a href="https://github.com/django/deps/pull/113">CompositeField DEP</a></li> <li>Simon and Lily have taken an initial look <ul> <li>Carlton: Looks amazing and what we need!</li> </ul> </li> <li>Hopefully Simon can review during DotM</li> <li>Needs Steering Council review</li> </ul> <h3 id="content-type-parsing-dep">Content Type Parsing DEP</h3> <ul> <li>Status of <a href="https://github.com/django/deps/pull/88">Content Type Parsing DEP</a></li> <li>Chris M has put up a 3rd party package, but hasn’t marketed it</li> <li>Things have stalled out a bit <ul> <li>There were concerns about JSON parsing on views that didn’t have it before</li> <li>This is a security concern for projects that update into new Django functionality</li> <li>Could be a transitional setting to transition it</li> </ul> </li> <li>We merged in the multipart classer attribute</li> <li>Can we dedicate Fellow time to this? <ul> <li>Yes</li> <li>Jacob may spend time on this after DotM</li> </ul> </li> </ul> <h2 id="using-extras-to-package-other-tools">Using extras to package other tools</h2> <ul> <li>There’s the third-party package perspective from the GSoC project: <a href="https://github.com/django/deps/pull/118">https://github.com/django/deps/pull/118</a></li> <li>Could also be used to build commercial relationships, such as with Mongo, etc <ul> <li>Is there any hesitancy from packaging company sponsored packages with Django, assuming they’re a sponsor of Django?</li> <li>Frank: This seems to make a lot of sense for databases</li> <li>Carlton: Nick Pope did work on this in the past <ul> <li>Memcached, etc</li> </ul> </li> <li>Lily: Sounds good on the vendor extras</li> <li>Emma: We need to discuss what this process would look like <ul> <li>This is likely a board and steering council process.</li> <li>Tim: We can try to redirect the DEP to focus on existing extras rather than experimental</li> </ul> </li> <li>Django[experimental] <ul> <li>This seems like the best way to handle it</li> </ul> </li> </ul> </li> </ul> <h2 id="experimental-features-gsoc-project">Experimental features GSoC Project</h2> <ul> <li>Praful and Andy have things for folks to review</li> <li><a href="https://github.com/django/deps/pull/118">https://github.com/django/deps/pull/118</a> Third-party packages and extras</li> <li>Experimental features as a third-party package <ul> <li><a href="https://github.com/prafulgulani/django-experimental/tree/main">Repository</a></li> <li><a href="https://forum.djangoproject.com/t/implementing-a-formal-experimental-api-for-django/45217">Discussion Thread</a></li> <li>This could be something for 2028</li> </ul> </li> <li><a href="https://github.com/django/deps/pull/117">https://github.com/django/deps/pull/117</a> feature flags <ul> <li><a href="https://github.com/prafulgulani/django-featurevault">Repository</a></li> <li><a href="https://forum.djangoproject.com/t/feature-flags-framework-for-django/45900">Discussion Thread</a></li> </ul> </li> </ul> <h2 id="case-studies-with-django-projects">Case Studies with Django projects</h2> <ul> <li>Tim to start doing case study blog posts for projects using Django</li> <li>If folks have big, old, cool projects, let him know for future iterations</li> </ul> <h2 id="django-usage-telemetrymetrics">Django usage telemetry/metrics</h2> <ul> <li>Tim’s been working on <a href="https://github.com/tim-schilling/django-probe/">Django Probe</a> idea on his own time</li> <li>Opt-in versus opt-out <ul> <li>This is a third party package, with toml file configuration</li> <li>When collecting dependencies, only collect pypi dependencies <ul> <li>Need to look into private pypi</li> </ul> </li> </ul> </li> <li>Would need to be aware of blind spots this would this create <ul> <li>Deprecating something because it’s not used in this could just mean people who use it aren’t opted in</li> <li>Some organizations are unable to respond to surveys or fill this out, but that doesn’t mean their usage isn’t warranted</li> </ul> </li> </ul>

2026-08-03T00:00:00+00:00https://django.github.io/steering-council/meetings/2026/2026-08-03-steering-council-with-fellows/

<h2 id="agenda">Agenda</h2> <ul> <li>Action Item Review</li> <li>DEP 19 membership vote</li> <li>DEP 20 Annual Release Cycle</li> <li>What to do about “Django Core Developer”</li> <li>DjangoCon US goals</li> <li>Fellows: <ul> <li>DEP 19 and enabling mergers to merge <ul> <li>Does anything in the DEP need implementation/docs?</li> </ul> </li> <li>Naming check on RAISE fetch mode: <a href="https://github.com/django/django/pull/21696">https://github.com/django/django/pull/21696</a></li> <li>FYI: DEP: table expressions in ORM: <a href="https://github.com/django/deps/pull/113">https://github.com/django/deps/pull/113</a></li> </ul> </li> </ul> <h2 id="action-items">Action items</h2> <ul> <li>Emma: Draft blog post on 6.x Features: Rob is the only one who answered positively <ul> <li>Paste - plan publish - communicate with other authors on slack - Emma</li> <li>Share on #marketing channel in Slack</li> </ul> </li> <li>Sovereign Tech Fund <ul> <li>Emma: Get one or more project(s) ready (maybe Admin or at least list of places to start)</li> <li>Plan another meeting with Lexi once the above is done</li> </ul> </li> <li>Tim: Teams Charters <ul> <li>Translations Team - Need to reach out to Claude</li> <li>Mergers Team - Modify list of approvers to include Steering Council members</li> </ul> </li> <li>Carlton: DEP 20 <ul> <li>Final clean ups</li> <li>Short sentence describing new release process</li> <li>Short blog post draft with clear transition timeline statement.</li> </ul> </li> <li>Tim: Add link to teams page for historical core contributors page</li> <li>New Features improvements <ul> <li>Revisit the language around closing, so we can close things</li> <li>Create a curated view of issues for people to participate in a high-impact area</li> <li>Create new project board views with documentation/blog post with how to participate in new feature process</li> </ul> </li> </ul> <h2 id="dep-19-membership-vote">DEP 19 membership vote</h2> <ul> <li>DEP 10 stipulates that we must vote on whether we think the membership should vote on adopting any DEP that changes the governance. The board must do the same.</li> <li>Steering Council votes that this does not require a membership vote.</li> </ul> <h2 id="dep-20-annual-release-cycle">DEP 20 Annual Release Cycle</h2> <ul> <li><a href="https://github.com/django/deps/pull/109">https://github.com/django/deps/pull/109</a></li> <li>Carlton: Needs a decision by the SC <ul> <li>Agreed upon by the SC</li> </ul> </li> <li>What if the Board hires an executive director and a lot of money is acquired and multiple more Fellows are hired, does that change anything, like the release schedule?</li> <li>Sarah shared that she would like the same schedule, just more features each schedule.</li> <li>People discuss if the current numbering has the flexibility to change within that. Carlton notes that as long as first number increments, it will still sort properly.</li> <li>Seems consensus on YYYY rather than YY</li> <li>2028.0 in January 2028 replacing 7.0</li> <li>Carlton will write a very short explanation for the users, and will use Sarah’s image:</li> </ul> <p>![][image1]</p> <h2 id="what-to-do-about-django-core-developer">What to do about “Django Core Developer”</h2> <ul> <li><a href="https://forum.djangoproject.com/t/revive-or-retire-the-django-core-developer-status/45509">https://forum.djangoproject.com/t/revive-or-retire-the-django-core-developer-status/45509</a></li> <li>This term drop was identified in DEP 19 by Tom. The term Django Core Developer is dropped in this DEP.</li> <li>Do we want to have some higher tier recognition level? If so, is “Core” the tier of recognition that we want?</li> <li>Do we want it to be purely on code? Should other experience factors into it? How many people should it apply to? Should it retire? Should there be multiple terms? Should Fellow be renamed to something else? Developer in Residence?</li> <li>Sarah notes that highly active people are asked to join the Triage/Review team. <ul> <li>Having people join teams individually allows teams to select members avoiding the board and SC</li> </ul> </li> <li>Add link to teams page for historical core contributors page, defer the rest</li> <li>Carlton to follow-up on the thread</li> </ul> <h2 id="djangocon-us-goals">DjangoCon US goals</h2> <ul> <li>[https://2026.djangocon.us/…</li> </ul>

2026-07-06T00:00:00+00:00https://django.github.io/steering-council/meetings/2026/2026-07-06-steering-council-with-fellows/

<h2 id="agenda">Agenda</h2> <ul> <li>Experimental Flags GSoC Project</li> <li>Action Items Review</li> <li>DEP 19 approval</li> <li>Fellows: <ul> <li>DEP for table-valued expressions</li> <li>Sphinx theme for the local django docs build</li> </ul> </li> <li>Oracle Test Pilot discussion recap</li> </ul> <h2 id="action-items">Action items</h2> <ul> <li>Emma: Draft blog post on 6.x Features: Rob is the only one who answered positively: <a href="https://drive.google.com/file/d/1DwDLCsJ13LeYZWA9-zAFBQccF2zpjzkh/view?usp=drive_link">https://drive.google.com/file/d/1DwDLCsJ13LeYZWA9-zAFBQccF2zpjzkh/view?usp=drive_link</a> ← still to do <ul> <li>Paste - plan publish - communicate with other authors on slack - Emma</li> <li>Share on #marketing channel in Slack</li> </ul> </li> <li>Sovereign Tech Fund <ul> <li>Emma: Get one or more project(s) ready (maybe Admin or at least list of places to start)</li> <li>Plan another meeting with Lexi once the above is done</li> </ul> </li> <li>Tim: Teams Charters <ul> <li>Security - Add explicit line about board having oversight</li> <li>Translations Team - Need to reach out to Claude</li> </ul> </li> <li>Carlton: Finalize DEP 20 and prepare for voting</li> <li>Write a blog post on Triptych project</li> <li>New Features improvements <ul> <li>Revisit the language around closing, so we can close things</li> <li>Create a curated view of issues for people to participate in a high-impact area</li> <li>Create new project board views with documentation/blog post with how to participate in new feature process</li> </ul> </li> </ul> <h2 id="experimental-flags-gsoc-project--with-guest-andy-miller">Experimental Flags GSoC Project- with Guest Andy Miller</h2> <ul> <li>Discussions: <ul> <li>Original with proposed ideas: <a href="https://django-dsf.slack.com/archives/C0871FA52GP/p1769614095013299">https://django-dsf.slack.com/archives/C0871FA52GP/p1769614095013299</a></li> <li>April conversation: <a href="https://django-dsf.slack.com/archives/C0871FA52GP/p1777527929921949">https://django-dsf.slack.com/archives/C0871FA52GP/p1777527929921949</a></li> <li>June conversation: <a href="https://django-dsf.slack.com/archives/C0871FA52GP/p1780431555624099">https://django-dsf.slack.com/archives/C0871FA52GP/p1780431555624099</a></li> </ul> </li> <li>Our notes: <a href="https://docs.google.com/document/d/1lZkYfZA7GAGs3td1vj0rG-spwwWjH222TemyPkCNlnE/edit?tab=t.0">2026-02-02 Steering Council</a></li> <li>Has side things around the project for the mentee, but wants to know what Fellows and SC wants</li> <li>Natalia thought of this as a research project, not expecting actionable things from the project, but options to pursue later. Natalia gave feedback with this in mind, expecting the project to be exploratory. When major changes to Django were being discussed, Natalia felt like she needed to check in. Her preference is that this project stay research focused.</li> <li>Frank agrees with the research aspect of the project. Possibly reconvening and seeing how to go forward after the research is over. What does adding Pluggy to the discussion look like?</li> <li>Jacob: from the Forum discussion, he is reading what has been done so far as an argument designed to convince, rather than a whitepaper style, attempting to be more objective pro and con list, which he would like to see.</li> <li>Andy was not aware of the research aspect, and thinks this will be helpful to reframe this as exploring many avenues and options. He appreciates the clear expected output, for the research to then be available for others.</li> <li>Frank: look at Waffle for reference. Even though they have problems.</li> <li>Frank: notes that he thinks contrib has lost its meaning and suggests moving towards retiring the term.</li> </ul> <h2 id="dep-19-approval">DEP 19 Approval</h2> <ul> <li>We should approve this to get it on the board’s approval for July</li> <li>Frank, Tim, Lily are in agreement with it. Need to follow-up async with Carlton and Emma</li> </ul> <h2 id="fellows">Fellows</h2> <h3 id="sphinx-theme-for-the-local-django-docs-build">Sphinx theme for the local django docs build</h3> <ul> <li>Use a well-known sphinx theme (Furo) for local docs builds?</li> <li>This avoids porting our private CSS to the django/django repo</li> <li>CSS/theme for the built docs <ul> <li>PoC: <a href="https://github.com/nessita/django/pull/53">https://github.com/nessita/django/pull/53</a></li> <li>Frank: do whatever is easiest</li> </ul> </li> </ul> <h3 id="table-valued-expressions-dep">Table-valued expressions DEP</h3> <ul> <li><a href="https://github.com/django/deps/pull/113">https://github.com/django/deps/pull/113</a></li> <li>Earlier feedback would be helpful for the project</li> <li>Should be ready this week</li> <li>Lily to take a deeper look</li> </ul>

2026-06-15T00:00:00+00:00https://django.github.io/steering-council/meetings/2026/2026-06-15-steering-council/

<h2 id="agenda">Agenda</h2> <ul> <li>Triptych Project</li> <li>Technical governance doc open questions</li> <li>New features repo</li> </ul> <h2 id="action-items">Action items</h2> <ul> <li>Emma: Draft blog post on 6.x Features: Rob is the only one who answered positively <ul> <li>Paste - plan publish - communicate with other authors on slack - Emma</li> <li>Share on #marketing channel in Slack</li> </ul> </li> <li>Sovereign Tech Fund <ul> <li>Emma: Get one or more project(s) ready (maybe Admin or at least list of places to start)</li> <li>Plan another meeting with Lexi once the above is done</li> </ul> </li> <li>Tim: Technical Governance document <ul> <li>Tim: Follow-up on Shai’s comments on PR</li> </ul> </li> <li>Tim: Teams Charters <ul> <li>Security - Transitioning last open items to team discussions</li> <li>Translations Team - Need to reach out to Claude</li> </ul> </li> <li>Carlton: Finalize DEP 20 and prepare for voting</li> <li>Write a blog post on Triptych project</li> <li>New Features improvements <ul> <li>Revisit the language around closing, so we can close things</li> <li>Create a curated view of issues for people to participate in a high-impact area</li> <li>Create new project board views with documentation/blog post with how to participate in new feature process</li> </ul> </li> </ul> <h2 id="triptych-project">Triptych Project</h2> <ul> <li>Carlton highlighted this project from Carson Gross (HTMX), and proposed we sign a Letter of Collaboration with them</li> <li><a href="https://triptychproject.org/">https://triptychproject.org/</a></li> <li>Tim: The third proposal is still in progress and hasn’t been completed yet. The alternatives section is what’s not complete.</li> <li>Carson will have a draft of a document for us to fill out</li> <li>Requires us to formalize</li> <li>We should write a blog post about why this is a benefit to the community <ul> <li>Add action items at the end to help bring other communities into it, like Flask</li> </ul> </li> </ul> <h2 id="technical-governance-document-open-questions">Technical governance document open questions</h2> <ul> <li><a href="https://github.com/django/deps/pull/107#discussion_r3104908486">https://github.com/django/deps/pull/107#discussion_r3104908486</a> <ul> <li>The professional skills are private and difficult to verify as a voter</li> <li>These are meant to be for the DSF board to evaluate to determine if someone can stand for election. Not necessarily for voters to vote on.</li> <li>These examples are just indications and are not a complete list of possible ways to show evidence. The indicator is possible evidence of the quality, not the quality itself.</li> </ul> </li> <li><a href="https://github.com/django/deps/pull/107#discussion_r3104955516">https://github.com/django/deps/pull/107#discussion_r3104955516</a> <ul> <li>This is just explicitly mentioning an existing power of the CoC WG</li> <li>We could remove this <ul> <li>This is in the rationale section, explaining why we’re removing the limitation on processing DEPs during elections. It wouldn’t be in the constitution.</li> </ul> </li> <li>There’s value in stating that the SC is subject to CoC WG and and Board, but we want to avoid over-engineering a social structure</li> </ul> </li> <li>Tim to finalize the DEP, we’ll advance it when Lily and Emma review</li> <li>DSF Board will next meet in July to vote on it</li> </ul> <h2 id="new-features-repo">New Features Repo</h2> <ul> <li>What can we do to improve this process? <ul> <li>We can’t see the serious considerations that need opinions</li> <li>Should we close ideas?</li> <li>Frank: C++ alliance is in charge of Boost, well funded and experimenting <ul> <li>Using several agents to review each papers to provide early feedback without requiring a contributor to do that effort</li> <li>Can we use AI to auto-tag and auto-review, identify severity</li> </ul> </li> <li>We should create embeddings and relationships between issues</li> <li>We have two roles for this processing the queue <ul> <li>An earlier triager</li> <li>An curator</li> </ul> </li> <li>How do we triage issues and provide critical feedback, without receiving negative feedback about that criticism?</li> <li>Could use a round-robin approach to designate issues to specific people to dilute feedback</li> <li>The phrase “This would be detrimental to Django” is a really high bar <ul> <li>We could reduce this, but it’s a beneficial one.</li> </ul> </li> <li>We could add a new user interface wrapping GitHub APIs <ul> <li>Andy Miller has been doing work around this for DEPs</li> <li>We want to highlight who has all voted</li> <li>We want to identify who has contributed to Django, who is a DSF individual member</li> <li>New functionality: <ul> <li>Auth</li> <li>Increase vote options a bit more.</li> <li>Add some metadata to the issues, as a summary of issues</li> </ul> </li> </ul> </li> <li>We could encourage people to fill things out <ul> <li>Akin to Trey’s whereabouts Earth game</li> </ul> </li> <li>Next steps: <ul> <li>Revisit the language around closing, so we can close things</li> <li>Create a curated view of issues for people to participate in a high-impact area</li> <li>Create new project board views <ul> <li>Add to documentation/blog post with how to participate in new feature process</li> </ul> </li> </ul> </li> </ul> </li> </ul>

2026-06-01T00:00:00+00:00https://django.github.io/steering-council/meetings/2026/2026-06-01-steering-council-with-fellows/

<h2 id="agenda">Agenda</h2> <ul> <li>Action items review</li> <li>DEP 18 approval</li> <li>Fellows: <ul> <li>AI slop way down after GSoC application season</li> <li>Discussion about PR quality bot auto-close behavior</li> <li>DEP for table-valued expressions (GSoC)</li> <li>Async model instantiation (because setting a GFK touches the db)</li> <li>Moving models between apps (<a href="https://github.com/django/django/pull/16905">PR</a>)</li> <li>Oracle test pilot (<a href="https://forum.djangoproject.com/t/proposal-leverage-oracle-test-pilot-for-django-ci/45197">forum</a>)</li> <li>Redistributing licenses when ingesting community packages</li> </ul> </li> <li>Advertising on <a href="http://djangoproject.com">djangoproject.com</a></li> <li>PyCon US recap</li> </ul> <h2 id="action-items">Action items</h2> <ul> <li>Emma: Draft blog post on 6.x Features: Rob is the only one who answered positively <ul> <li>Paste - plan publish - communicate with other authors on slack - Emma</li> <li>Share on #marketing channel in Slack</li> </ul> </li> <li>Sovereign Tech Fund <ul> <li>Emma: Get one or more project(s) ready (maybe Admin or at least list of places to start)</li> <li>Plan another meeting with Lexi once the above is done</li> </ul> </li> <li>Tim: Technical Governance document</li> <li>Tim: Teams Charters <ul> <li>Security - Transitioning last open items to team discussions</li> <li>Translations Team - Need to reach out to Claude</li> </ul> </li> <li>Tim: Follow up on Oracle thread</li> </ul> <h2 id="actions-review">Actions Review</h2> <ul> <li>Tim: Need to revisit tech governance forum thread</li> <li>Security charter <ul> <li>Sarah Boyce merged several changes</li> <li>We want to wrap this up and merge it</li> <li>Jacob to follow up with Sarah to transition last open items</li> <li>Frank is still pending joining the security list</li> </ul> </li> </ul> <h2 id="dep-18-mailers-setting">DEP 18 (MAILERS setting)</h2> <ul> <li><a href="https://github.com/django/deps/pull/111">https://github.com/django/deps/pull/111</a></li> <li>Need to post consensus on the DEP</li> </ul> <h2 id="ai-slop">AI Slop</h2> <ul> <li>This appears to be related to GSoC application window</li> <li>The PR auto-closing tool is helping as well <ul> <li>We’re getting people caught by the PR being auto closed because the Trac “Has Ticket” isn’t set</li> <li>The auto-closer may need a little help <ul> <li>Could re-run the checker on the PR to re-open the PR</li> <li>Step 3 description is invalid for what we actually want to happen</li> </ul> </li> <li>We should improve messaging about remediation step</li> <li>Ideally the bot would auto-reopen if issues are fixed. This would require switching to a bot approach.</li> </ul> </li> <li>Tim: Will follow up with GSoC WG on applicants and how many PRs they opened</li> </ul> <h2 id="dep-table-valued-expressions">DEP Table-valued expressions</h2> <ul> <li><a href="https://github.com/p-r-a-v-i-n/deps/blob/relation-api/draft/table_value_expression.rst">Early draft</a></li> <li>Jacob has solicited feedback from ORM contributors and helped Pravin to create a draft</li> <li>Pravin should be creating a public DEP PR soon</li> </ul> <h2 id="async-model-instantiation">Async model instantiation</h2> <ul> <li>Use case: acreate() delegating to asave(), see <a href="https://code.djangoproject.com/ticket/36888#comment:11">ticket</a></li> <li>Maybe a DEP?</li> <li>To solve Model.objects.acreate(), we need to support async model instantiation, which likely means we need an aset <ul> <li><a href="https://github.com/django/django/pull/20602#pullrequestreview-4391796527">https://github.com/django/django/pull/20602#pullrequestreview-4391796527</a></li> </ul> </li> <li>Jacob wants to know if this is a good idea and/or next steps</li> <li>Emma: This may be a place we could use Raphael’s async/sync generation code <ul> <li><a href="https://github.com/django/deps/pull/99">https://github.com/django/deps/pull/99</a></li> </ul> </li> </ul> <h2 id="moving-models-between-apps">Moving models between apps</h2> <ul> <li><a href="https://github.com/django/django/pull/16905">PR</a></li> <li>Bhuvnesh worked on polishing and incorporating latest feedback</li> <li>Should be ready for a final review</li> <li>Could be a headline feature for 6.2!!</li> </ul> <h2 id="oracle-test-pilot">Oracle Test Pilot</h2> <ul> <li><a href="https://forum.djangoproject.com/t/proposal-leverage-oracle-test-pilot-for-django-ci/45197">Forum</a></li> <li>Oracle hosted way of running CI against the oracle database</li> <li>We would need to opt into this by directing a CI action against this</li> <li>Emma: Is this related to the Oracle partnership inquiry? <ul> <li>Frank: Will follow up on this</li> </ul> </li> <li>Natalia: Can someone ask what the next steps are, what are they looking for from us? <ul> <li>They have implemented a github action that we could review</li> <li>We want a PR that runs the tests against their DBs</li> <li>Could use the magic Jenkins comment, or have a GitHub actions test workflow</li> <li>Tim: Send a message to open a PR / ticket to create to proceed this forward.</li> </ul> </li> <li>Emma: Is this something that we’ll be able to rely on? What level of support would it offer? <ul> <li>We could use this as a supplemental approach</li> </ul> </li> <li>Requirements are listed as: <ul> <li>Review technical eligibility by analyzing the current GitHub Actions workflow(s)</li> <li>Proceed with Oracle Test Pilot onboarding by providing required OCI resources</li> <li>Tim to reach out to get a sense of poster availability to make a PR</li> </ul> </li> </ul> <h2 id="redistributing-licenses-when-injecting-community-packages">Redistributing licenses when injecting community packages</h2> <ul> <li>When working on show_urls command, <a href="https://github.com/django/django/pull/21307">https://github.com/django/django/pull/21307</a></li> <li>We are doing more merging of 3rd party libraries into main / advocating that this is the path forward for features</li> <li>We have other licenses hanging out in the source code</li> <li>Emma: When merging 3rd party library features, we could ask maintainers opinion <ul> <li>If the maintainer is involved it’s easier to do</li> <li>If the maintainer isn’t it’s trickier</li> </ul> </li> <li>Frank: When merging 3rd party packages in, we could ask them to BSD3 it, so it’s easier for us to merge in</li> <li>On code organization <ul> <li>Could have a license file that directs to the various areas</li> <li>Could have a license at the top of each file or related to it</li> </ul> </li> <li>Seems agreement on social direction of asking maintainers to switch to BSD3 and/or formally agree to switch licenses. / Highlight that this is going to be a problem <ul> <li>Would need changes to new features repo README / process</li> <li>Follow up with Adam’s cookiecutter and Django Commons best practices</li> </ul> </li> <li>We should credit the authors/maintainers in docs</li> </ul> <h2 id="advertising-on-djangoprojectcom">Advertising on djangoproject.com</h2> <ul> <li>Carlton: We should improve the corporate sponsorship story first</li> <li>Showing advertisements would remove corporate sponsorship benefits</li> </ul> <h2 id="pycon-us-recap">PyCon US Recap</h2> <ul> <li>It was a good time</li> <li>Django and the DSF was mentioned in several talks</li> <li>The security of GitHub Actions was referenced</li> <li>We had several contributors to Django at sprints, mostly first-time contributors</li> </ul>

2026-05-04T00:00:00+00:00https://django.github.io/steering-council/meetings/2026/2026-05-04-steering-council-with-fellows/

<h2 id="agenda">Agenda</h2> <ul> <li>Logical properties and values in CSS</li> <li>Accessibility team leeway on code improvements</li> <li>DEP 20: Annual Release Process (<a href="https://github.com/django/deps/pull/109">link</a>)</li> <li>DEP 19: New technical governance (<a href="https://github.com/django/deps/pull/107">link</a>)</li> <li>DEP 18: Email providers (<a href="https://github.com/django/deps/pull/105">link</a>)</li> <li>Google Summer of Code</li> </ul> <h2 id="action-items">Action items</h2> <ul> <li>Emma: Draft blog post on 6.x Features: Rob is the only one who answered positively <ul> <li>Paste - plan publish - communicate with other authors on slack - Emma</li> <li>Share on #marketing channel in Slack</li> </ul> </li> <li>Sovereign Tech Fund <ul> <li>Emma: Get one or more project(s) ready (maybe Admin or at least list of places to start)</li> <li>Plan another meeting with Lexi once the above is done</li> </ul> </li> <li>Tim: Technical Governance document</li> <li>Tim: Teams Charters <ul> <li>Security - Transitioning last open items to team discussions</li> <li>Translations Team - Need to reach out to Claude</li> </ul> </li> <li>Carlton: Annual release DEP</li> <li>Review DEP 18 by end of week</li> </ul> <h2 id="logical-properties-and-values-in-css">Logical properties and values in CSS</h2> <ul> <li><a href="https://github.com/django/new-features/issues/148">New features</a>, requested by Accessibility team</li> <li>Regarding gritQL <ul> <li>Was there a discussion on this, why this in particular? <ul> <li>Can ask on new-features to ask for clarification on justification</li> </ul> </li> </ul> </li> <li>Seems like a positive <ul> <li>Concerns around backwards compatibility where we change the definitions of styles (Customisations) <ul> <li>Would require heads up and ideally we don’t do this, but the admin is an exception to the backwards compatibility policy</li> </ul> </li> <li>It’ll be helpful to mention this early on in a blog post that this is happening, who will be impacted, what expect things.</li> </ul> </li> </ul> <h2 id="accessibility-team-leeway-on-code-improvements">Accessibility team leeway on code improvements</h2> <ul> <li>They are discussing linting rules and the GritQL rules, but are spending time on “how do we do this from a process” perspective. Feels like we’re letting processes get in the way of people doing positive work.</li> <li>Natalia wants to assure accountability. That there will be support there.</li> <li>The team doesn’t have the capacity to be a required aspect of the whole contribution process. The team does not want to be a blocker, which was information that came from within the accessibility team.</li> <li>This is part of the volunteer nature. Sarah brings up the ‘wave’ nature of this. People surge in involvement, and then disappear, which is natural in volunteering. It can be a problem if Accessibility team review is required or strongly desired.</li> </ul> <h2 id="dep-20-annual-release-process">DEP 20: Annual release process</h2> <ul> <li>Discussion has been both positive and constructive</li> <li>A few decision points to settle. How many versions of Python to support: <ul> <li>Green only vs Plus last yellow Python support <ul> <li>Carlton: I genuinely don’t know which way is best here. Leaned to Plus Last Yellow because of e.g. Linux distributions.</li> <li>There is the <a href="https://launchpad.net/~deadsnakes">deadsnakes PPA for ubuntu</a> which provides all versions of python as .deb packages</li> <li>General sentiment is that “Green Only (whilst appealing) is too aggressive”.</li> </ul> </li> <li>Version numbering <ul> <li>We WON’T all agree on this (everyone has a favourite)</li> <li>But we CAN all live with any option we choose.</li> <li>“What colour?”</li> <li>YYYY vs YY v N <ul> <li>CalVer or Like-SemVar</li> </ul> </li> <li>Discussion wasn’t conclusive, as predicted ☺️</li> </ul> </li> </ul> </li> </ul> <h2 id="dep-19-new-technical-governance">DEP 19: New technical governance</h2> <ul> <li>Document structure: Do we need to move the final place to this into the docs as the source of truth to allow incremental updates? <ul> <li><a href="https://github.com/django/deps/pull/107#discussion_r3104952597">https://github.com/django/deps/pull/107#discussion_r3104952597</a></li> <li><a href="https://docs.djangoproject.com/en/6.0/internals/organization">https://docs.djangoproject.com/en/6.0/internals/organization</a></li> <li>Right now, docs would work well. <ul> <li><a href="https://docs.djangoproject.com/en/6.0/internals/organization/#:~:text=governance%20of%20other%20technical%20teams%20within%20the%20Django">https://docs.djangoproject.com/en/6.0/internals/organization/#:~:text=governance%20of%20other%20technical%20teams%20within%20the%20Django</a></li> </ul> </li> </ul> </li> <li>Transparency in decision making process <ul> <li><a href="https://github.com/django/deps/pull/107#discussion_r3142528926">https://github.com/django/deps/pull/107#discussion_r3142528926</a></li> </ul> </li> </ul> <h2 id="dep-18-email-providers">DEP 18: Email providers</h2> <ul> <li>The PR is ready to merge</li> <li>Natalia: Mike has been doing stellar work</li> </ul> <h2 id="google-summer-of-code">Google Summer of Code</h2> <ul> <li>All four project proposals were accepted!</li> </ul>

2026-04-20T00:00:00+00:00https://django.github.io/steering-council/meetings/2026/2026-04-20-steering-council/

<h2 id="agenda">Agenda</h2> <ul> <li>Action items review</li> <li>New features - Djangonaut Space review</li> <li>Performance Working Group</li> </ul> <h2 id="action-items">Action items</h2> <ul> <li>Emma: Draft blog post on 6.x Features: Rob is the only one who answered positively <ul> <li>Paste - plan publish - communicate with other authors on slack - Emma</li> <li>Share on #marketing channel in Slack</li> </ul> </li> <li>Sovereign Tech Fund <ul> <li>Emma: Get one or more project(s) ready (maybe Admin or at least list of places to start)</li> <li>Plan another meeting with Lexi once the above is done</li> </ul> </li> <li>Tim: Technical Governance document <ul> <li>Collecting feedback at <a href="https://github.com/django/deps/pull/107">https://github.com/django/deps/pull/107</a></li> </ul> </li> <li>Tim: Teams Charters <ul> <li>Security - Transitioning last open items to team discussions</li> <li>Translations - Need to reach out to Claude</li> </ul> </li> <li>Carlton: Annual release DEP <ul> <li>Working on it, should target for a month</li> </ul> </li> </ul> <h2 id="action-item-review">Action Item Review</h2> <ul> <li>Tom raised a concern about dropping the core team designation without mention</li> <li>This was allowed in DEP 10, but doesn’t appear to be awarded out</li> <li>Should this go in DEP 19 or not?</li> <li>The board previously looked into titles, awards.</li> <li>Who would identify people? <ul> <li>Could be automatically identified from GitHub and Trac</li> <li>Quarterly review- perhaps conferring with the fellows as a double check quarterly</li> </ul> </li> <li>Tim: Relay this with the rest of the SC.</li> </ul> <h2 id="new-features---djangonaut-space-review">New Features - Djangonaut Space review</h2> <ul> <li>A Q&amp;A with past Djangonauts to help identify next steps for agreed upon new features</li> <li>The goal would be to get people moving forward on the feature ideas and bringing these people further into the fold as regular contributors. <ul> <li>This likely would serve as a trial for a broader Django event</li> </ul> </li> </ul> <h2 id="performance-working-group">Performance Working Group</h2> <ul> <li><a href="https://github.com/django/dsf-working-groups/pull/74/">https://github.com/django/dsf-working-groups/pull/74/</a></li> <li>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</li> <li>Frank: There’s probably room for liaisons in the “contact when needed” realm</li> <li>Tom: This seems useful, but more in the SC area.</li> </ul>