1Catalyst::Manual::DevelUospemrenCtoPnrtorciebsust(e3d)PCeartlalDyosctu:m:eMnatnautailo:n:DevelopmentProcess(3)
2
6 Catalyst::Manual::DevelopmentProcess - Administrative structure of the
7 Catalyst Development Process
8
10 The main philosophy behind Catalyst development can be summarized as:
11 Patches welcome!
13 Everyone is welcome (and will be encouraged) to contribute to Catalyst
15 in whatever capacity they're able to. People in #catalyst-dev will be
16 more than happy to talk newcomers through contributing their first
17 patch, or how best to go about their first CPAN extension module....
18
20 Discussing proposed bugfixes or improvements
21 <http://dev.catalystframework.org/wiki/#Community> has information
22 about how to get in touch with the Catalyst "community". In
23 particular, you would want to discuss a proposed change on the mailing
24 list:
25 http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst-dev
27 or on IRC:
29 irc://irc.perl.org/catalyst-dev
31 http://dev.catalystframework.org/wiki/livegroups
32 Usually, the core team will be more than happy for you to contribute,
34 and will talk you through how to submit a patch, or get a "commit bit".
35 Repositories
37 The Catalyst subversion repository can be found at:
38 svn: http://dev.catalyst.perl.org/repos/Catalyst
40 browser: http://dev.catalyst.perl.org/svnweb/Catalyst
41 and the git repository can be found at:
43 read: git://git.shadowcat.co.uk/catagits/PROJECTNAME
45 write: catagits@git.shadowcat.co.uk:PROJECTNAME
46 browser: https://git.shadowcat.co.uk/gitweb/gitweb.cgi
47 Schedule
49 There is no dated release cycle for Catalyst. New releases will be made
50 when sufficient small fixes have accumulated; or an important bugfix,
51 or significant feature addition, is completed.
52 Roadmap for features
54 The Catalyst Roadmap is kept at
55 http://dev.catalyst.perl.org/repos/Catalyst/Catalyst-Runtime/5.80/trunk/lib/Roadmap.pod
56 <http://dev.catalyst.perl.org/repos/Catalyst/Catalyst-
57 Runtime/5.80/trunk/lib/Roadmap.pod>
58 Bug list
60 The TODO list with known bugs / deficiences is kept at
61 http://dev.catalyst.perl.org/repos/Catalyst/Catalyst-Runtime/5.80/trunk/TODO
62 <http://dev.catalyst.perl.org/repos/Catalyst/Catalyst-
63 Runtime/5.80/trunk/TODO>
64
66 The intention of the Catalyst Core Team is to maintain and support the
67 Catalyst framework, in order for it to be a viable and stable framework
68 for developing web-based MVC applications. This includes both technical
69 decisions about the Catalyst core distribution, and public relations
70 relating to the Catalyst framework as a whole.
71 The current goals of the Catalyst core development team are stability,
73 performance, and a properly paced addition of features, with a focus on
74 extensibility.
75 The core team is concerned with the 'core' Catalyst distributions (i.e.
77 Catalyst::Runtime, Catalyst::Devel and Catalyst::Manual), and also
78 tries to encourage best practices for extension authors, and
79 cooperation and shared vision within the Catalyst community.
80 Membership
82 The Catalyst Core Team consists of the developers who have full commit
83 privileges to the entire Catalyst source tree, and who have made a
84 significant contribution to the core Catalyst distributions, and
85 various extensions and plugins.
86 In addition, the core team includes members that have non-technical
88 roles, such as marketing, legal, or economic responsibilities.
89 Currently, the Core Team consists of the following people:
91 Brian Cassidy
93 Andy Grundman
94 Christian Hansen
95 Yuval Kogman
96 Marcus Ramberg
97 Jonathan Rockway
98 Jesse Sheidlower
99 Matt S. Trout
100 Florian Ragwitz
101 Tomas Doran
102 New members of the Core Team must be accepted by a 2/3 majority by the
104 current members.
105 Technical Decisions.
107 Any change to the Catalyst core which can not be conceived as a
108 correction of an error in the current feature set will need to be
109 accepted by at least 3 members of the Core Team before it can be
110 commited to the trunk (which is the basis for CPAN releases). Anyone
111 with access is at any time free to make a branch to develop a proof of
112 concept for a feature to be committed to trunk.
113 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.
121 CPAN Releases
123 Planned releases to CPAN should be performed by the release manager, at
124 the time of writing Marcus Ramberg, or the deputy release manager, at
125 the time of writing Florian Ragwitz. In the case of critical error
126 correction, any member of the Core Team can perform a rescue release.
127 Public statements from the Core Team
129 The Core Team should strive to appear publicly as a group when
130 answering questions or other correspondence. In cases where this is not
131 possible, the same order as for CPAN releases applies.
132 New Catalyst Extensions
134 As Catalyst is deliberately designed for extension, there is an
135 ecosystem of several hundred Catalyst extensions that can be found on
136 CPAN.
137 See Catalyst::Manual::ExtendingCatalyst for more information on how to
139 extend Catalyst in various ways and how to write CPANable components
140 for Catalyst which can be reused in many applications.
141 It is recommended to post a request for comments to the Catalyst
143 mailing list, or ask around in the #catalyst IRC channel before
144 starting to implement something, as another member of the community is
145 likely to have example or prototype code that you can reuse, and
146 members of the community and core team are happy to advise on the best
147 way to implement a generic solution to a particular problem.
148 This could save you duplicate work, and will help you produce a better
150 thought out and designed extension.
151
153 Catalyst Contributors, see Catalyst.pm
154
156 This library is free software. You can redistribute it and/or modify it
157 under the same terms as Perl itself.
158perl v5.12.0 2009-1C2a-t2a8lyst::Manual::DevelopmentProcess(3)