Teams
Teams indicate who is actively contributing in certain areas.
Ops team
The ops team maintains Django’s infrastructure like the Django Project server, Trac instance, and continuous integration infrastructure.
- Florian Apolloner
- Markus Holtermann
- Tim Graham
- Tobias McNulty
Releasers
Releasers take care of building Django releases.
- Carlton Gibson
- Jacob Kaplan-Moss
- James Bennett
- Tim Graham
Security team
The security team is responsible for Django’s security policies. It handles private reports of security issues.
- Adrian Holovaty
- Aymeric Augustin
- Carl Meyer
- Carlton Gibson
- Claude Paroz
- Collin Anderson
- Florian Apolloner
- Jacob Kaplan-Moss
- James Bennett
- Jannis Leidel
- Marc Tamlyn
- Markus Holtermann
- Michael Manfre
- Paul McMillan
- Sasha Romijn
- Shai Berger
- Simon Charette
- Tim Graham
Technical advisory team
Veteran contributors to Django and/or its ecosystem who are currently less involved in day to day development of Django. They may be consulted about design decisions in their areas of expertise.
- Aymeric Augustin
- Carl Meyer
- Collin Anderson
- Julien Phalip
- Karen Tracey
- Luke Plant
- Michael Manfre
- Sasha Romijn
- Shai Berger
- Tobias McNulty
- Tom Christie
Technical board
The technical board for the 2.2 release cycle is:
- Adam Johnson
- Andrew Godwin
- Aymeric Augustin
- Carl Meyer
- James Bennett
Technical team
Veteran contributors to Django who are actively involved in its development. Activities may include ticket triage, patch authoring, and patch review.
- Adam Johnson
- Carlton Gibson
- Claude Paroz
- Josh Smeaton
- Loïc Bistuer
- Marc Tamlyn
- Mariusz Felisiak
- Markus Holtermann
- Sergey Fedoseev
- Simon Charette
- Tim Graham
