Catalyst::Manual::DevelopmentProcess - Administrative structure of the Catalyst Development Process The main current goals of the Catalyst core development team continue to be stability, performance, and a more paced addition of features, with a focus on extensibility. Extensive improvements to the documentation are also expected in the short term. The Catalyst Roadmap at <http://dev.catalyst.perl.org/roadmap> will remain as is, and continues to reflect the specific priorities and schedule for future releases.

Intention
The intention of the Catalyst Core Team is to maintain and support the Catalyst framework, in order for it to be a viable and stable framework for developing web-based MVC applications. This includes both technical decisions about the Catalyst core distribution, and public relations relating to the Catalyst framework as a whole. The main priority for development is stability for the users of the framework, while improving usability and extensibility, as well as improving documentation and ease of deployment.

Membership
The Catalyst Core Team consists of the developers that have full commit privileges to the entire Catalyst source tree. In addition, the core team may accept members that have non-technical roles such as marketing, legal, or economic responsibilities. At the time of conception, the Core Team consists of the following people: New members of the Core Team must be accepted by a 2/3 majority by the current members.

Technical Decisions.
Any change to the Catalyst core which can not be conceived as a correction of an error in the current feature set will need to be accepted by at least 3 members of the Core Team before it can be commited to the trunk (which is the basis for CPAN releases). Anyone with access is at any time free to make a branch to develop a proof of concept for a feature to be committed to trunk.

Organizational and Philosophical Decisions.
Any such decision should be decided by majority vote. Thus it should be a goal of the organization that its membership number should at any time be an odd number, to render it effective with regards to decision making. The exceptions to this rule are changes to this charter and additions to the membership of the Core Team, which require a 2/3 majority.

CPAN Releases
Planned releases to CPAN should be performed by the release manager, at the time of writing Marcus Ramberg, or the deputy release manager, at the time of writing Andy Grundman. In the case of critical error correction, any member of the Core Team can perform a rescue release.

Public statements from the Core Team
The Core Team should strive to appear publicly as a group when answering questions or other correspondence. In cases where this is not possible, the same order as for CPAN Releases applies.