|
|
@@ -21,107 +21,6 @@ and its community.
|
|
|
.. _Django Code of Conduct: https://www.djangoproject.com/conduct/
|
|
|
.. _Django Software Foundation: https://www.djangoproject.com/foundation/
|
|
|
|
|
|
-The Django core team makes the decisions, nominates its new members, and
|
|
|
-elects its technical board. While it holds decision power in theory, it aims
|
|
|
-at using it as rarely as possible in practice. Rough consensus should be the
|
|
|
-norm and formal voting an exception.
|
|
|
-
|
|
|
-.. _core-team:
|
|
|
-
|
|
|
-Core team
|
|
|
-=========
|
|
|
-
|
|
|
-Role
|
|
|
-----
|
|
|
-
|
|
|
-The core team is the group of trusted volunteers who manage the Django
|
|
|
-Project. They assume many roles required to achieve the project's goals,
|
|
|
-especially those that require a high level of trust. They make the decisions
|
|
|
-that shape the future of the project.
|
|
|
-
|
|
|
-Core team members are expected to act as role models for the community and
|
|
|
-custodians of the project, on behalf of the community and all those who rely
|
|
|
-on Django.
|
|
|
-
|
|
|
-They will intervene, where necessary, in online discussions or at official
|
|
|
-Django events on the rare occasions that a situation arises that requires
|
|
|
-intervention.
|
|
|
-
|
|
|
-They have authority over the Django Project infrastructure, including the
|
|
|
-Django Project website itself, the Django GitHub organization and
|
|
|
-repositories, the Trac bug tracker, the mailing lists, IRC channels, etc.
|
|
|
-
|
|
|
-Prerogatives
|
|
|
-------------
|
|
|
-
|
|
|
-Core team members may participate in formal votes, typically to nominate new
|
|
|
-team members and to elect the technical board.
|
|
|
-
|
|
|
-Some contributions don't require commit access. Depending on the reasons why a
|
|
|
-contributor joins the team, they may or may not have commit permissions to the
|
|
|
-Django code repository.
|
|
|
-
|
|
|
-However, should the need arise, any team member may ask for commit access by
|
|
|
-writing to the core team's mailing list. Access will be granted unless the
|
|
|
-person withdraws their request or the technical board vetoes the proposal.
|
|
|
-
|
|
|
-Core team members who have commit access are referred to as "committers" or
|
|
|
-"core developers".
|
|
|
-
|
|
|
-Other permissions, such as access to the servers, are granted to those who
|
|
|
-need them through the same process.
|
|
|
-
|
|
|
-Membership
|
|
|
-----------
|
|
|
-
|
|
|
-`Django team members <https://www.djangoproject.com/foundation/teams/>`_
|
|
|
-demonstrate:
|
|
|
-
|
|
|
-- a 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
|
|
|
-list of areas where contributions may be considered for joining the core team,
|
|
|
-in no particular order:
|
|
|
-
|
|
|
-- Working 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:
|
|
|
-
|
|
|
-- Reviewing security reports
|
|
|
-- Merging patches (code, docs, or tests)
|
|
|
-- Packaging releases
|
|
|
-
|
|
|
-Core team membership acknowledges sustained and valuable efforts that align
|
|
|
-well with the philosophy and the goals of the Django Project.
|
|
|
-
|
|
|
-It is granted by a four fifths majority of votes cast in a core team vote and
|
|
|
-no veto by the technical board.
|
|
|
-
|
|
|
-Core team members are always looking for promising contributors, teaching them
|
|
|
-how the project is managed, and submitting their names to the core team's vote
|
|
|
-when they're ready.
|
|
|
-
|
|
|
-There's no time limit on core team membership. However, in order to provide
|
|
|
-the general public with a reasonable idea of how many people maintain Django,
|
|
|
-core team members who have stopped contributing are encouraged to declare
|
|
|
-themselves as "past team members". Those who haven't made any non-trivial
|
|
|
-contribution in two years may be asked to move themselves to this category,
|
|
|
-and moved there if they don't respond. Past team members lose their privileges
|
|
|
-such as voting rights and commit access.
|
|
|
-
|
|
|
.. _technical-board:
|
|
|
|
|
|
Technical board
|
Mariusz Felisiak