Django 프로젝트는 세 가지 목표를 추구하는 자원 봉사 팀에 의해 관리됩니다:
\nDjango 웹 프레임워크의 개발을 주도하고,
Django 관련 소프트웨어 생태계를 육성하고,
`Django Code of Conduct`_에 명시된 가치에 따라 Django 커뮤니티를 선도합니다.
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.
\nMerger_는 pull request를 `Django Git 저장소`_에 병합하는 소수의 사람들입니다.
\nMerger는 다음과 같은 특혜를 가집니다:
\n`사소한 변경`_(`DEP process`_를 사용할 필요가 없을 정도로 작음)을 구성하는 모든 pull request를 병합합니다. pull request가 다음에 의해 승인되지 않은 병합자는 해당 Merger가 주로 작성한 변경 사항을 병합해서는 안됩니다.:
\n\n적절한 장소에서 사소한 변경에 대한 논의를 시작하고 논의가 진행되는 동안 다른 Merger에게 병합을 자제하도록 요청합니다.
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.
\nMerger가 Django Fellow이기도 해야 한다는 요구 사항은 아니지만 Django Software Foundation은 Merger의 역할을 지속 가능하게 만드는 방법으로 Fellow 직책의 자금을 사용할 수 있는 권한이 있습니다.
\nMerger의 역할에는 다음과 같은 제한 사항이 적용됩니다.:
\nA person must not simultaneously serve as a member of the steering council. If\na Merger is elected to the steering council, they shall cease to be a Merger\nimmediately upon taking up membership in the steering council.
Releaser와 Merger의 역할을 동시에 수행할 수 있습니다.
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:
\n적절한 토론 장소의 양호한 상태의 회원 또는 DSF의 Fellowship 위원회의 의견을 받는 Django Sofeware Foundation 이사회는 고려할 사람을 제안할 수 있습니다.
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.
\n그렇지 않으면, Merger는 다음과 같은 방법으로 자격이 박탈될 수 있습니다.:
\nBecoming disqualified due to election to the steering council.
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 number\nat a minimum of three, in order to spread the workload and avoid over-burdening\nor burning out any individual Releaser. There is no upper limit to the number\nof Releasers.
\nReleaser가 Django Fellow이기도 해야 한다는 요구 사항은 아니지만 Django Software Foundation은 Releaser의 역할을 지속 가능하게 만드는 방법으로 Fellow 직책의 자금을 사용할 수 있는 권한이 있습니다.
\nReleaser와 Merger의 역할을 동시에 수행할 수 있습니다.
\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:
\n적절한 토론 장소의 양호한 상태의 회원 또는 DSF의 Fellowship 위원회의 의견을 받는 Django Sofeware Foundation 이사회는 고려할 사람을 제안할 수 있습니다.
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.
\n그렇지 않으면, Releaser는 다음과 같은 방법으로 자격이 박탈될 수 있습니다.:
\nDjango Software Foundation의 행동 강령 위원회에서 취한 조치로 인해 자격이 박탈됩니다.
A vote of the steering council.
The steering council is a group of experienced contributors who:
\nDjango의 개발 및 릴리스 프로세스를 감독하고,
기능 개발 및 릴리스의 방향을 설정하는 데 도움을 주고,
select Mergers and Releasers, and
다른 의사 결정 프로세스가 실패할 때 최종 투표를 합니다.
주요 역할은 Django 웹 프레임워크의 품질과 안정성을 유지하는 것입니다.
\nThe steering council holds the following prerogatives:
\nDjango의 기술적 변경에 대한 질문에 대해 구속력 있는 결정을 내립니다.
특정 코드 조각을 Django로 병합하거나 특정 병합 또는 커밋의 되돌리기를 거부합니다.
Django의 향후 기술 방향에 대한 제안 및 아이디어 요청을 발표합니다.
merger와 releaser를 선택하고 자격을 박탈합니다.
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.
Django의 조직 수정에 참여(Changing 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.
Django 오픈 소스 프로젝트 내에서 다른 기술 팀을 담당하고 그에 따라 해당 팀을 관리합니다.
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 process\nworks as follows:
\nThe steering council directs one of its members to notify the Secretary of the\nDjango Software Foundation, in writing, of the triggering of the election,\nand the condition which triggered it. The Secretary post to the appropriate\nvenue – the Django Forum to announce the election and its timeline.
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:
\nDjango 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 members\nof the steering council, and the DSF Board. A valid determination of\nineligibility requires that all other members of the steering council and all\nmembers of the DSF Board vote who can vote on the issue (the affected person,\nif a DSF Board member, must not vote) vote “yes” on a motion that the person\nin question is ineligible.
Changes to this document require the use of the DEP process, with\nmodifications described in DEP 0010.
\n