发布于 2015-08-27 16:39:03 | 182 次阅读 | 评论: 0 | 来源: 网络整理
This document states the rules that govern the Symfony Core group. These rules
are effective upon publication of this document and all Symfony Core members
must adhere to said rules and protocol.
Core Organization
Symfony Core members are divided into three groups. Each member can only belong
to one group at a time. The privileges granted to a group are automatically
granted to all higher priority groups.
The Symfony Core groups, in descending order of priority, are as follows:
- Project Leader
- Elects members in any other group;
- Merges pull requests in all Symfony repositories.
- Mergers
- Merge pull requests for the component or components on which they have been
granted privileges.
- Deciders
- Decide to merge or reject a pull request.
Active Core Members
- Project Leader:
- Mergers (
@symfony/mergers
on GitHub):
- Bernhard Schussek (webmozart) can merge into the Form,
Validator, Icu, Intl, Locale, OptionsResolver and PropertyAccess
components;
- Tobias Schultze (Tobion) can merge into the Routing,
OptionsResolver and PropertyAccess components;
- Romain Neutron (romainneutron) can merge into the
Process component;
- Nicolas Grekas (nicolas-grekas) can merge into the Debug
component, the VarDumper component and the DebugBundle;
- Christophe Coevoet (stof) can merge into the BrowserKit,
Config, Console, DependencyInjection, DomCrawler, EventDispatcher,
HttpFoundation, HttpKernel, Serializer, Stopwatch, DoctrineBridge,
MonologBridge, and TwigBridge components;
- Kévin Dunglas (dunglas) can merge into the Serializer
component;
- Abdellatif AitBoudad (aitboudad) can merge into the Translation
component;
- Jakub Zalas (jakzal) can merge into the DomCrawler component.
- Deciders (
@symfony/deciders
on GitHub):
Core Membership Application
At present, new Symfony Core membership applications are not accepted.
Core Membership Revocation
A Symfony Core membership can be revoked for any of the following reasons:
- Refusal to follow the rules and policies stated in this document;
- Lack of activity for the past six months;
- Willful negligence or intent to harm the Symfony project;
- Upon decision of the Project Leader.
Should new Symfony Core memberships be accepted in the future, revoked
members must wait at least 12 months before re-applying.
Code Development Rules
Symfony project development is based on pull requests proposed by any member
of the Symfony community. Pull request acceptance or rejection is decided based
on the votes cast by the Symfony Core members.
Pull Request Voting Policy
-1
votes must always be justified by technical and objective reasons;
+1
votes do not require justification, unless there is at least one
-1
vote;
- Core members can change their votes as many times as they desire
during the course of a pull request discussion;
- Core members are not allowed to vote on their own pull requests.
Pull Request Merging Policy
A pull request can be merged if:
- Enough time was given for peer reviews (a few minutes for typos or minor
changes, at least 2 days for “regular” pull requests, and 4 days for pull
requests with “a significant impact”);
- It is a minor change , regardless of the number of votes;
- At least the component’s Merger or two other Core members voted
+1
and no Core member voted -1
.
Pull Request Merging Process
All code must be committed to the repository through pull requests, except for
minor changes which can be committed directly to the repository.
Mergers must always use the command-line gh
tool provided by the
Project Leader to merge the pull requests.
Release Policy
The Project Leader is also the release manager for every Symfony version.
Symfony Core Rules and Protocol Amendments
The rules described in this document may be amended at anytime at the
discretion of the Project Leader.