Django community recently adopted proposal for a new governance model Django project DEP 10.
Simply put, Django previous governance model is not reasonable, to hinder the continued development and growth of the Django community. Official website blog reports, beginning Django project sponsor ( Adrian Holovaty and Kaplan-Moss Jacob ) can grant permission to others to commit, and by 2014, the number of core committer team has a lot in leadership positions after the two founders resigned, retains the basic structure of a core committer team, the team may add code to Django according to their own choice. At the same time we created a new group: the five committer composed of "technical committee" created by the core committer election, and as the final decision maker.
But in fact, almost all now add code to Django by Django Software Foundation (DSF, Django Software Foundation) paid contractors Django Fellows merger, or consolidation by a few active users. All versions of Django now released by the Fellows.
That core committer on the project team in almost no direct participation in the relevant processes Django, and almost all the technical decisions regarding the development of Django is not between committer discussion and decision, but anyone can participate in the public forum decisions by consensus.
This situation affects the participation of the developer community, but also affect the long-term healthy development of the Django project, so the community has been talking about reform. By now the DEP 10, some of the changes currently being implemented as follows:
The core committer before the team disbanded, commit rights associated members will also be deleted. Is currently creating a new role "Merger", he could commit, but can only merge from others pr. Merge can not determine initiative to add content to Django, nor any special decision-making privileges.
There will also create a "Releaser" role, he can access the release of Django and implement the relevant mechanisms, such as increasing the version number in the key file.
On the other hand, in case of need, the Technical Committee will retain the ultimate decision-making body, and will also be responsible to investigate future technology directions Django ideas and suggestions, and to determine the release schedule.
However, the membership of the Technical Committee will no longer be limited to the committer, the Technical Committee is no longer produced by the committer election. Those who had contributed to the Django technical people are eligible to run for members of the technical committee, individual members selected by the Django Software Foundation. Potential candidates for election to expand from the previous approximately 50 (committer) to the current nearly 200.
In addition, the term "Django Core Developer" (Django core developers) was renamed the honorary title, awarded by the DSF had a significant, long-term impact on Django's personal history.
More specific information you can view the original blog and DEP 10 original documents: