roles.txt 1.2 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970
  1. =====
  2. Roles
  3. =====
  4. .. _technical-board-list:
  5. Technical board
  6. ===============
  7. The technical board for the 1.11 release cycle is:
  8. * James Bennett
  9. * Andrew Godwin
  10. * Russell Keith-Magee
  11. * Carl Meyer
  12. * Marc Tamlyn
  13. .. _committers:
  14. Committers
  15. ==========
  16. Most :ref:`core team <core-team>` members have commit access. They're called
  17. "committers" or "core developers".
  18. Being part of the core team is a pre-requisite for having commit access.
  19. .. _security-team-list:
  20. Security team
  21. =============
  22. The security team is responsible for :doc:`Django's security policies
  23. </internals/security>`. It handles private reports of security issues.
  24. The current security team members are:
  25. - Florian Apolloner
  26. - James Bennett
  27. - Tim Graham
  28. - Adrian Holovaty
  29. - Markus Holtermann
  30. - Paul McMillan
  31. - Carl Meyer
  32. .. _releasers-list:
  33. Releasers
  34. =========
  35. Releasers take care of :doc:`building Django releases
  36. </internals/howto-release-django>`.
  37. The current releasers are:
  38. - James Bennett
  39. - Jacob Kaplan-Moss
  40. - Tim Graham
  41. Ops team
  42. ========
  43. The ops team maintains Django's infrastructure like the Django Project server,
  44. Trac instance, and continuous integration infrastructure.
  45. - Florian Apolloner
  46. - Tim Graham
  47. - Markus Holtermann
  48. - Jannis Leidel
  49. - Tobias McNulty