You are browsing the Symfony 4 documentation, which changes significantly from Symfony 3.x. If your app doesn't use Symfony 4 yet, browse the Symfony 3.4 documentation.
Symfony Core Team
Symfony Core Team¶
The Symfony Core team is the group of developers that determine the direction and evolution of the Symfony project. Their votes rule if the features and patches proposed by the community are approved or rejected.
All the Symfony Core members are long-time contributors with solid technical expertise and they have demonstrated a strong commitment to drive the project forward.
This document states the rules that govern the Symfony core team. These rules are effective upon publication of this document and all Symfony Core members must adhere to said rules and protocol.
Symfony Core members are divided into 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 Team
- Merge pull requests for the component or components on which they have been granted privileges.
- Deciders Team
- Decide to merge or reject a pull request.
In addition, there are other groups created to manage specific topics:
- Manage the whole security process (triaging reported vulnerabilities, fixing the reported issues, coordinating the release of security fixes, etc.)
- Manage the whole symfony-docs repository.
Active Core Members¶
- Project Leader:
- Fabien Potencier (fabpot).
- Mergers Team (
- 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 Cache, Debug, Process, PropertyAccess, VarDumper components, PhpUnitBridge and the DebugBundle;
- Christophe Coevoet (stof) can merge into all components, bridges and bundles;
- Kévin Dunglas (dunglas) can merge into the PropertyInfo and the Serializer component;
- Jakub Zalas (jakzal) can merge into the DomCrawler and Intl components;
- Christian Flothmann (xabbuh) can merge into the Yaml component;
- Javier Eguiluz (javiereguiluz) can merge into the WebProfilerBundle;
- Grégoire Pineau (lyrixx) can merge into the Workflow component;
- Ryan Weaver (weaverryan) can merge into the Security component and the SecurityBundle;
- Robin Chalas (chalasr) can merge into the Console and Security components and the SecurityBundle;
- Maxime Steinhausser (ogizanagi) can merge into Config, Console, Form, Serializer, DependencyInjection, and HttpKernel components;
- Tobias Nyholm (Nyholm) manages the official and contrib recipes repositories;
- Samuel Rozé (sroze) can merge into the Messenger component.
- Deciders Team (
- Security Team (
- Documentation Team (
Former Core Members¶
They are no longer part of the core team, but we are very grateful for all their Symfony contributions:
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¶
-1votes must always be justified by technical and objective reasons;
+1votes do not require justification, unless there is at least one
- 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:
- It is a minor change ;
- Enough time was given for peer reviews (at least 2 days for "regular" pull requests, and 4 days for pull requests with "a significant impact");
- At least the component's Merger or two other Core members voted
+1and no Core member voted
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.
The Project Leader is also the release manager for every Symfony version.
This work, including the code samples, is licensed under a Creative Commons BY-SA 3.0 license.