3 Catalyst::Manual::DevelopmentProcess - Administrative structure of the Catalyst Development Process
5 =head1 Contributing to Catalyst
7 The main philosophy behind Catalyst development can be summarized as:
11 Everyone is welcome (and will be encouraged) to contribute to Catalyst
12 in whatever capacity they're able to. People in #catalyst-dev will be
13 more than happy to talk newcomers through contributing their first patch,
14 or how best to go about their first CPAN extension module....
16 =head1 Catalyst development
18 =head2 Discussing proposed bugfixes or improvements
20 L<http://wiki.catalystframework.org/wiki/#Community> has information about how
21 to get in touch with the Catalyst "community". In particular, you would
22 want to discuss a proposed change on the mailing list:
24 http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst-dev
28 irc://irc.perl.org/catalyst-dev
29 http://wiki.catalystframework.org/wiki/livegroups
31 Usually, the core team will be more than happy for you to contribute, and
32 will talk you through how to submit a patch, or get a "commit bit".
36 The Catalyst git repository can be found at:
38 read: git://git.shadowcat.co.uk/catagits/PROJECTNAME
39 write: catagits@git.shadowcat.co.uk:PROJECTNAME
40 browser: https://git.shadowcat.co.uk/gitweb/gitweb.cgi
44 There is no dated release cycle for Catalyst. New releases will be made
45 when sufficient small fixes have accumulated; or an important bugfix, or
46 significant feature addition, is completed.
48 =head1 The Catalyst Core Team
50 The intention of the Catalyst Core Team is to maintain and support the
51 Catalyst framework, in order for it to be a viable and stable framework
52 for developing web-based MVC applications. This includes both technical
53 decisions about the Catalyst core distribution, and public relations
54 relating to the Catalyst framework as a whole.
56 The current goals of the Catalyst core development team are stability,
57 performance, and a properly paced addition of features, with a focus on
60 The core team is concerned with the 'core' Catalyst distributions
61 (i.e. L<Catalyst::Runtime>, L<Catalyst::Devel> and L<Catalyst::Manual>),
62 and also tries to encourage best practices for extension authors, and
63 cooperation and shared vision within the Catalyst community.
67 The Catalyst Core Team consists of the developers who have full commit
68 privileges to the entire Catalyst source tree, and who have made a significant
69 contribution to the core Catalyst distributions, and various extensions and
72 In addition, the core team includes members that have non-technical
73 roles, such as marketing, legal, or economic responsibilities.
75 Currently, the Core Team consists of the following people:
83 =item Christian Hansen
89 =item Jonathan Rockway
91 =item Jesse Sheidlower
101 New members of the Core Team must be accepted by a 2/3 majority by the
104 =head2 Technical Decisions.
106 Any change to the Catalyst core which can not be conceived as a
107 correction of an error in the current feature set will need to be
108 accepted by at least 3 members of the Core Team before it can be
109 committed to master (which is the basis for CPAN releases). Anyone
110 with access is at any time free to make a branch to develop a proof of
111 concept for a feature to be committed to master.
113 =head2 Organizational and Philosophical Decisions.
115 Any organizational or philosophical decision should be decided by
116 majority vote. Thus it should be a goal of the organization that its
117 membership number should at any time be an odd number, to render it
118 effective with regards to decision making. The exceptions to this rule
119 are changes to this charter and additions to the membership of the Core
120 Team, which require a 2/3 majority.
124 Planned releases to CPAN should be performed by the release manager, at
125 the time of writing Marcus Ramberg, or the deputy release manager, at
126 the time of writing Florian Ragwitz. In the case of critical error
127 correction, any member of the Core Team can perform a rescue release.
129 =head2 Public statements from the Core Team
131 The Core Team should strive to appear publicly as a group when answering
132 questions or other correspondence. In cases where this is not possible,
133 the same order as for CPAN releases applies.
135 =head2 New Catalyst Extensions
137 As Catalyst is deliberately designed for extension, there is an ecosystem of
138 several hundred Catalyst extensions that can be found on CPAN.
140 See L<Catalyst::Manual::ExtendingCatalyst> for more information on how
141 to extend Catalyst in various ways and how to write CPANable components
142 for Catalyst which can be reused in many applications.
144 It is recommended to post a request for comments to the Catalyst mailing
145 list, or ask around in the #catalyst IRC channel before starting to
146 implement something, as another member of the community is likely to
147 have example or prototype code that you can reuse, and members of the
148 community and core team are happy to advise on the best way to implement
149 a generic solution to a particular problem.
151 This could save you duplicate work, and will help you produce a better
152 thought out and designed extension.
156 Catalyst Contributors, see Catalyst.pm
160 This library is free software. You can redistribute it and/or modify it under
161 the same terms as Perl itself.