The Django Project is managed by a team of volunteers pursuing three goals:
\nDriving the development of the Django Web Framework,
Fostering the ecosystem of Django-related software,
Leading the Django community in accordance with the values described in the\nDjango Code of Conduct.
The Django Project isn't a legal entity. The Django Software Foundation, a\nnon-profit organization, handles financial and legal matters related to the\nDjango Project. Other than that, the Django Software Foundation lets the\nDjango Project manage the development of the Django framework, its ecosystem\nand its community.
\nThe Django core team makes the decisions, nominates its new members, and\nelects its technical board. While it holds decision power in theory, it aims\nat using it as rarely as possible in practice. Rough consensus should be the\nnorm and formal voting an exception.
\nThe core team is the group of trusted volunteers who manage the Django\nProject. They assume many roles required to achieve the project's goals,\nespecially those that require a high level of trust. They make the decisions\nthat shape the future of the project.
\nCore team members are expected to act as role models for the community and\ncustodians of the project, on behalf of the community and all those who rely\non Django.
\nThey will intervene, where necessary, in online discussions or at official\nDjango events on the rare occasions that a situation arises that requires\nintervention.
\nThey have authority over the Django Project infrastructure, including the\nDjango Project website itself, the Django GitHub organization and\nrepositories, the Trac bug tracker, the mailing lists, IRC channels, etc.
\nCore team members may participate in formal votes, typically to nominate new\nteam members and to elect the technical board.
\nSome contributions don't require commit access. Depending on the reasons why a\ncontributor joins the team, they may or may not have commit permissions to the\nDjango code repository.
\nHowever, should the need arise, any team member may ask for commit access by\nwriting to the core team's mailing list. Access will be granted unless the\nperson withdraws their request or the technical board vetoes the proposal.
\nCore team members who have commit access are referred to as "committers" or\n"core developers".
\nOther permissions, such as access to the servers, are granted to those who\nneed them through the same process.
\nThe core team finds its origins with the four people who created Django. It has grown to a few dozen\npeople by co-opting volunteers who demonstrate:
\na good grasp of the philosophy of the Django Project
a solid track record of being constructive and helpful
significant contributions to the project's goals, in any form
willingness to dedicate some time to improving Django
As the project matures, contributions go way beyond code. Here's an incomplete\nlist of areas where contributions may be considered for joining the core team,\nin no particular order:
\nWorking on community management and outreach
Providing support on the mailing-lists and on IRC
Triaging tickets
Writing patches (code, docs, or tests)
Reviewing patches (code, docs, or tests)
Participating in design decisions
Providing expertise in a particular domain (security, i18n, etc.)
Managing the continuous integration infrastructure
Managing the servers (website, tracker, documentation, etc.)
Maintaining related projects (djangoproject.com site, ex-contrib apps, etc.)
Creating visual designs
Very few areas are reserved to core team members:
\nReviewing security reports
Merging patches (code, docs, or tests)
Packaging releases
Core team membership acknowledges sustained and valuable efforts that align\nwell with the philosophy and the goals of the Django Project.
\nIt is granted by a four fifths majority of votes cast in a core team vote and\nno veto by the technical board.
\nCore team members are always looking for promising contributors, teaching them\nhow the project is managed, and submitting their names to the core team's vote\nwhen they're ready. If you would like to join the core team, you can contact a\ncore team member privately or ask for guidance on the Django Core\nMentorship mailing-list.
\nThere's no time limit on core team membership. However, in order to provide\nthe general public with a reasonable idea of how many people maintain Django,\ncore team members who have stopped contributing are encouraged to declare\nthemselves as "past team members". Those who haven't made any non-trivial\ncontribution in two years may be asked to move themselves to this category,\nand moved there if they don't respond. Past team members lose their privileges\nsuch as voting rights and commit access.
\nThe technical board is a group of experienced and active committers who steer\ntechnical choices. Their main concern is to maintain the quality and stability\nof the Django Web Framework.
\nThe technical board holds two prerogatives:
\nMaking major technical decisions when no consensus is found otherwise. This\nhappens on the django-developers mailing-list.
Veto a grant of commit access or remove commit access. This happens on the\ndjango-core mailing-list.
In both cases, the technical board is a last resort. In these matters, it\nfulfills a similar function to the former Benevolent Dictators For Life.
\nWhen the board wants to exercise one of these prerogatives, it must hold a\nprivate, simple majority vote on the resolution. The quorum is the full\ncommittee — each member must cast a vote or abstain explicitly. Then the board\ncommunicates the result, and if possible the reasons, on the appropriate\nmailing-list. There's no appeal for such decisions.
\nIn addition, at its discretion, the technical board may act in an advisory\ncapacity on non-technical decisions.
\nThe technical board is an elected group of five committers. They're expected\nto be experienced but there's no formal seniority requirement. Its current\ncomposition is published here.
\nA new board is elected after each feature release of Django. The election\nprocess is managed by a returns officer nominated by the outgoing technical\nboard. The election process works as follows:
\nCandidates advertise their application for the technical board to the team.
\nThey must be committers already. There's no term limit for technical board\nmembers.
\nEach team member can vote for zero to five people among the candidates.\nCandidates are ranked by the total number of votes they received.
\nIn case of a tie, the person who joined the core team earlier wins.
\nBoth the application and the voting period last between one and two weeks, at\nthe outgoing board's discretion.
\nChanges to this document require a four fifths majority of votes cast in a\ncore team vote and no veto by the technical board.
\n