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.
\nMergers are a small set of people who merge pull requests to the Django Git\nrepository.
\nMergers hold the following prerogatives:
\nMerging any pull request which constitutes a minor change (small enough\nnot to require the use of the DEP process). A Merger must not merge a\nchange primarily authored by that Merger, unless the pull request has been\napproved by:
\nanother Merger,
a steering council member,
a member of the triage & review team, or
a member of the security team.
Initiating discussion of a minor change in the appropriate venue, and request\nthat other Mergers refrain from merging it while discussion proceeds.
Requesting a vote of the steering council regarding any minor change if, in\nthe Merger’s opinion, discussion has failed to reach a consensus.
Requesting a vote of the steering council when a major change (significant\nenough to require the use of the DEP process) reaches one of its\nimplementation milestones and is intended to merge.
The steering council selects Mergers as necessary to maintain their number\nat a minimum of three, in order to spread the workload and avoid over-burdening\nor burning out any individual Merger. There is no upper limit to the number of\nMergers.
\nIt’s not a requirement that a Merger is also a Django Fellow, but the Django\nSoftware Foundation has the power to use funding of Fellow positions as a way\nto make the role of Merger sustainable.
\nThe following restrictions apply to the role of Merger:
\nA person must not simultaneously serve as a member of the steering council.\nIf a Merger is elected to the steering council, they shall cease to be a\nMerger immediately upon taking up membership in the steering council.
A person may serve in the roles of Releaser and Merger simultaneously.
The selection process, when a vacancy occurs or when the steering council deems\nit necessary to select additional persons for such a role, occur as follows:
\nAny member in good standing of an appropriate discussion venue, or the Django\nSoftware Foundation board acting with the input of the DSF’s Fellowship\ncommittee, may suggest a person for consideration.
The steering council considers the suggestions put forth, and then any member\nof the steering council formally nominates a candidate for the role.
The steering council votes on nominees.
Mergers may resign their role at any time, but should endeavor to provide some\nadvance notice in order to allow the selection of a replacement. Termination of\nthe contract of a Django Fellow by the Django Software Foundation temporarily\nsuspends that person’s Merger role until such time as the steering council can\nvote on their nomination.
\nOtherwise, a Merger may be removed by:
\nBecoming disqualified due to election to the steering council.
Becoming disqualified due to actions taken by the Code of Conduct committee\nof the Django Software Foundation.
A vote of the steering council.
Releasers are a small set of people who have the authority to upload packaged\nreleases of Django to the Python Package Index and to the\ndjangoproject.com website.
\nReleasers build Django releases and\nupload them to the Python Package Index and to the\ndjangoproject.com website.
\nThe steering council selects Releasers as necessary to maintain their\nnumber at a minimum of three, in order to spread the workload and avoid\nover-burdening or burning out any individual Releaser. There is no upper limit\nto the number of Releasers.
\nIt’s not a requirement that a Releaser is also a Django Fellow, but the Django\nSoftware Foundation has the power to use funding of Fellow positions as a way\nto make the role of Releaser sustainable.
\nA person may serve in the roles of Releaser and Merger simultaneously.
\nThe selection process, when a vacancy occurs or when the steering council deems\nit necessary to select additional persons for such a role, occur as follows:
\nAny member in good standing of an appropriate discussion venue, or the Django\nSoftware Foundation board acting with the input of the DSF’s Fellowship\ncommittee, may suggest a person for consideration.
The steering council considers the suggestions put forth, and then any member\nof the steering council formally nominates a candidate for the role.
The steering council votes on nominees.
Releasers may resign their role at any time, but should endeavor to provide\nsome advance notice in order to allow the selection of a replacement.\nTermination of the contract of a Django Fellow by the Django Software\nFoundation temporarily suspends that person’s Releaser role until such time as\nthe steering council can vote on their nomination.
\nOtherwise, a Releaser may be removed by:
\nBecoming disqualified due to actions taken by the Code of Conduct committee\nof the Django Software Foundation.
A vote of the steering council.
The steering council is a group of experienced contributors who:
\nprovide oversight of Django’s development and release process,
assist in setting the direction of feature development and releases,
select Mergers and Releasers, and
have a tie-breaking vote when other decision-making processes fail.
Their main concern is to maintain the quality and stability of the Django Web\nFramework.
\nThe steering council holds the following prerogatives:
\nMaking a binding decision regarding any question of a technical change to\nDjango.
Vetoing the merging of any particular piece of code into Django or ordering\nthe reversion of any particular merge or commit.
Announcing calls for proposals and ideas for the future technical direction\nof Django.
Selecting and removing mergers and releasers.
Participating in the removal of members of the steering council, when deemed\nappropriate.
Calling elections of the steering council outside of those which are\nautomatically triggered, at times when the steering council deems an election\nis appropriate.
Participating in modifying Django’s governance (see\nChanging the organization).
Declining to vote on a matter the steering council feels is unripe for a\nbinding decision, or which the steering council feels is outside the scope of\nits powers.
Taking charge of the governance of other technical teams within the Django\nopen-source project, and governing those teams accordingly.
The steering council is an elected group of five experienced contributors\nwho demonstrate:
\nA history of substantive contributions to Django or the Django ecosystem.\nThis history must begin at least 18 months prior to the individual’s\ncandidacy for the Steering Council, and include substantive contributions in\nat least two of these bullet points:
\nCode contributions to Django projects or major third-party packages in the\nDjango ecosystem
Reviewing pull requests and/or triaging Django project tickets
Documentation, tutorials or blog posts
Discussions about Django on the Django Forum
Running Django-related events or user groups
A history of engagement with the direction and future of Django. This does\nnot need to be recent, but candidates who have not engaged in the past three\nyears must still demonstrate an understanding of Django’s changes and\ndirection within those three years.
A new council is elected after each release cycle of Django. The election\nprocess works as follows:
\nThe steering council directs one of its members to notify the Secretary of\nthe Django Software Foundation, in writing, of the triggering of the\nelection, and the condition which triggered it. The Secretary post to the\nappropriate venue – the Django Forum to announce the election and its\ntimeline.
As soon as the election is announced, the DSF Board begin a period of\nvoter registration. All individual members of the DSF are automatically\nregistered and need not explicitly register. All other persons who believe\nthemselves eligible to vote, but who have not yet registered to vote, may\nmake an application to the DSF Board for voting privileges. The voter\nregistration form and roll of voters is maintained by the DSF Board. The DSF\nBoard may challenge and reject the registration of voters it believes are\nregistering in bad faith or who it believes have falsified their\nqualifications or are otherwise unqualified.
Registration of voters close one week after the announcement of the\nelection. At that point, registration of candidates begin. Any qualified\nperson may register as a candidate. The candidate registration form and\nroster of candidates are maintained by the DSF Board, and candidates must\nprovide evidence of their qualifications as part of registration. The DSF\nBoard may challenge and reject the registration of candidates it believes do\nnot meet the qualifications of members of the Steering Council, or who it\nbelieves are registering in bad faith.
Registration of candidates close one week after it has opened. One week\nafter registration of candidates closes, the Secretary of the DSF publishes\nthe roster of candidates to the Django Forum, and the election begins.\nThe DSF Board provides a voting form accessible to registered voters, and is\nthe custodian of the votes.
Voting is by secret ballot containing the roster of candidates, and any\nrelevant materials regarding the candidates, in a randomized order. Each\nvoter may vote for up to five candidates on the ballot.
The election conclude one week after it begins. The DSF Board then tally the\nvotes and produce a summary, including the total number of votes cast and\nthe number received by each candidate. This summary is ratified by a\nmajority vote of the DSF Board, then posted by the Secretary of the DSF to\nthe Django Forum. The five candidates with the highest vote totals\nimmediately become the new steering council.
A member of the steering council may be removed by:
\nBecoming disqualified due to actions taken by the Code of Conduct committee\nof the Django Software Foundation.
Determining that they did not possess the qualifications of a member of the\nsteering council. This determination must be made jointly by the other\nmembers of the steering council, and the DSF Board. A valid determination\nof ineligibility requires that all other members of the steering council and\nall members of the DSF Board vote who can vote on the issue (the affected\nperson, if a DSF Board member, must not vote) vote “yes” on a motion that the\nperson in question is ineligible.
Changes to this document require the use of the DEP process, with\nmodifications described in DEP 0010.
\n