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. The ops team is sufficiently staffed at this time. Membership is by invitation. As needed, the team may make a call for help on the django-developers mailing list.
- Carlton Gibson
- Florian Apolloner
- Mariusz Felisiak
- Markus Holtermann
- Tobias McNulty
Releasers
Releasers take care of building Django releases.
- Carlton Gibson
- Jacob Kaplan-Moss
- James Bennett
- Mariusz Felisiak
Security team
The security team is responsible for Django’s security policies. It handles private reports of security issues. The security team is sufficiently staffed at this time. Membership is by invitation. As needed, the team may make a call for applicants on the django-developers mailing list.
- Adrian Holovaty
- Aymeric Augustin
- Carlton Gibson
- Claude Paroz
- Collin Anderson
- Florian Apolloner
- Jacob Kaplan-Moss
- James Bennett
- Jannis Leidel
- Mariusz Felisiak
- Markus Holtermann
- Michael Manfre
- Paul McMillan
- Shai Berger
- Simon Charette
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
- Josh Smeaton
- Julien Phalip
- Karen Tracey
- Loïc Bistuer
- Luke Plant
- Michael Manfre
- Shai Berger
- Tobias McNulty
- Tom Christie
Technical board
The technical board for the 3.2 release cycle is:
- Adam Johnson
- Andrew Godwin
- James Bennett
- Markus Holtermann
- Tom Forbes
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
- Mariusz Felisiak
- Markus Holtermann
- Simon Charette
