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://wiki.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://wiki.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 git repository can be found at:
38 read: git://git.shadowcat.co.uk/catagits/PROJECTNAME
40 write: catagits@git.shadowcat.co.uk:PROJECTNAME
41 browser: https://git.shadowcat.co.uk/gitweb/gitweb.cgi
42 The Catalyst subversion repository can be found at:
44 svn: http://dev.catalyst.perl.org/repos/Catalyst
46 browser: http://dev.catalyst.perl.org/svnweb/Catalyst
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://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=catagits/Catalyst-Runtime.git;a=blob_plain;f=lib/Catalyst/ROADMAP.pod;hb=master>
56 Bug list
58 The TODO list with known bugs / deficiencies is kept at
59 <http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=catagits/Catalyst-Runtime.git;a=blob_plain;f=TODO;hb=master>
60
62 The intention of the Catalyst Core Team is to maintain and support the
63 Catalyst framework, in order for it to be a viable and stable framework
64 for developing web-based MVC applications. This includes both technical
65 decisions about the Catalyst core distribution, and public relations
66 relating to the Catalyst framework as a whole.
67 The current goals of the Catalyst core development team are stability,
69 performance, and a properly paced addition of features, with a focus on
70 extensibility.
71 The core team is concerned with the 'core' Catalyst distributions (i.e.
73 Catalyst::Runtime, Catalyst::Devel and Catalyst::Manual), and also
74 tries to encourage best practices for extension authors, and
75 cooperation and shared vision within the Catalyst community.
76 Membership
78 The Catalyst Core Team consists of the developers who have full commit
79 privileges to the entire Catalyst source tree, and who have made a
80 significant contribution to the core Catalyst distributions, and
81 various extensions and plugins.
82 In addition, the core team includes members that have non-technical
84 roles, such as marketing, legal, or economic responsibilities.
85 Currently, the Core Team consists of the following people:
87 Brian Cassidy
89 Andy Grundman
90 Christian Hansen
91 Yuval Kogman
92 Marcus Ramberg
93 Jonathan Rockway
94 Jesse Sheidlower
95 Matt S. Trout
96 Florian Ragwitz
97 Tomas Doran
98 New members of the Core Team must be accepted by a 2/3 majority by the
100 current members.
101 Technical Decisions.
103 Any change to the Catalyst core which can not be conceived as a
104 correction of an error in the current feature set will need to be
105 accepted by at least 3 members of the Core Team before it can be
106 committed to master (which is the basis for CPAN releases). Anyone with
107 access is at any time free to make a branch to develop a proof of
108 concept for a feature to be committed to master.
109 Organizational and Philosophical Decisions.
111 Any organizational or philosophical decision should be decided by
112 majority vote. Thus it should be a goal of the organization that its
113 membership number should at any time be an odd number, to render it
114 effective with regards to decision making. The exceptions to this rule
115 are changes to this charter and additions to the membership of the Core
116 Team, which require a 2/3 majority.
117 CPAN Releases
119 Planned releases to CPAN should be performed by the release manager, at
120 the time of writing Marcus Ramberg, or the deputy release manager, at
121 the time of writing Florian Ragwitz. In the case of critical error
122 correction, any member of the Core Team can perform a rescue release.
123 Public statements from the Core Team
125 The Core Team should strive to appear publicly as a group when
126 answering questions or other correspondence. In cases where this is not
127 possible, the same order as for CPAN releases applies.
128 New Catalyst Extensions
130 As Catalyst is deliberately designed for extension, there is an
131 ecosystem of several hundred Catalyst extensions that can be found on
132 CPAN.
133 See Catalyst::Manual::ExtendingCatalyst for more information on how to
135 extend Catalyst in various ways and how to write CPANable components
136 for Catalyst which can be reused in many applications.
137 It is recommended to post a request for comments to the Catalyst
139 mailing list, or ask around in the #catalyst IRC channel before
140 starting to implement something, as another member of the community is
141 likely to have example or prototype code that you can reuse, and
142 members of the community and core team are happy to advise on the best
143 way to implement a generic solution to a particular problem.
144 This could save you duplicate work, and will help you produce a better
146 thought out and designed extension.
147
149 Catalyst Contributors, see Catalyst.pm
150
152 This library is free software. You can redistribute it and/or modify it
153 under the same terms as Perl itself.
154perl v5.28.0 2014-1C2a-t1a3lyst::Manual::DevelopmentProcess(3)