OSS: How is Django
Maintained*?

11 September 2026
Python Leadership Roundtable
Alex Hatfield

* Not exhaustive — but pretty solid, and certainly the main bits.

  • Open source — code anyone can use and change
  • Django — a batteries-included Python web framework

Who maintains Django

Governance structure & roles

  • Steering Council — elected; rules on direction and significant changes
  • Mergers — appointed by the Steering Council; the only ones who commit to main
  • Fellows — paid contributors who triage, review and keep the lights on
  • Wider community

What maintains Django

ToolWhat it’s used for
Django websiteDocs, downloads, news and release notes (djangoproject.com)
Django Forum (Discourse)Discussion before decision (forum.djangoproject.com)
DiscordReal-time chat and help for new contributors
Security emailThe one private channel, for vulnerabilities
TracTickets and triage (code.djangoproject.com)
GitHubRepos, pull requests, code review, CI checks and feature ideas
TransifexWhere the community writes translations

How is Django maintained

Django contribution intake flow diagram
Drag to pan · scroll to zoom · +/−/0 keys · double-click to reset
100%

Over to the Room

  • Are there aspects of Django’s process worth borrowing for our own work — and anything from how we work that could improve Django’s contribution process?
  • Has anyone got experience contributing to other open source projects? How does it compare?
  • What is AI doing to open source?