1Catalyst::Manual::DevelUospemrenCtoPnrtorciebsust(e3d)PCeartlalDyosctu:m:eMnatnautailo:n:DevelopmentProcess(3)
2
3
4

NAME

6       Catalyst::Manual::DevelopmentProcess - Administrative structure of the
7       Catalyst Development Process
8

Contributing to Catalyst

10       The main philosophy behind Catalyst development can be summarized as:
11
12           Patches welcome!
13
14       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

Catalyst development

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
26           http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst-dev
27
28       or on IRC:
29
30           irc://irc.perl.org/catalyst-dev
31           http://wiki.catalystframework.org/wiki/livegroups
32
33       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
36   Repositories
37       The Catalyst git repository can be found at:
38
39           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
43   Schedule
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,
46       or significant feature addition, is completed.
47

The Catalyst Core Team

49       The intention of the Catalyst Core Team is to maintain and support the
50       Catalyst framework, in order for it to be a viable and stable framework
51       for developing web-based MVC applications. This includes both technical
52       decisions about the Catalyst core distribution, and public relations
53       relating to the Catalyst framework as a whole.
54
55       The current goals of the Catalyst core development team are stability,
56       performance, and a properly paced addition of features, with a focus on
57       extensibility.
58
59       The core team is concerned with the 'core' Catalyst distributions (i.e.
60       Catalyst::Runtime, Catalyst::Devel and Catalyst::Manual), and also
61       tries to encourage best practices for extension authors, and
62       cooperation and shared vision within the Catalyst community.
63
64   Membership
65       The Catalyst Core Team consists of the developers who have full commit
66       privileges to the entire Catalyst source tree, and who have made a
67       significant contribution to the core Catalyst distributions, and
68       various extensions and plugins.
69
70       In addition, the core team includes members that have non-technical
71       roles, such as marketing, legal, or economic responsibilities.
72
73       Currently, the Core Team consists of the following people:
74
75       Brian Cassidy
76       Andy Grundman
77       Christian Hansen
78       Yuval Kogman
79       Marcus Ramberg
80       Jonathan Rockway
81       Jesse Sheidlower
82       Matt S. Trout
83       Florian Ragwitz
84       Tomas Doran
85
86       New members of the Core Team must be accepted by a 2/3 majority by the
87       current members.
88
89   Technical Decisions.
90       Any change to the Catalyst core which can not be conceived as a
91       correction of an error in the current feature set will need to be
92       accepted by at least 3 members of the Core Team before it can be
93       committed to master (which is the basis for CPAN releases). Anyone with
94       access is at any time free to make a branch to develop a proof of
95       concept for a feature to be committed to master.
96
97   Organizational and Philosophical Decisions.
98       Any organizational or philosophical decision should be decided by
99       majority vote. Thus it should be a goal of the organization that its
100       membership number should at any time be an odd number, to render it
101       effective with regards to decision making. The exceptions to this rule
102       are changes to this charter and additions to the membership of the Core
103       Team, which require a 2/3 majority.
104
105   CPAN Releases
106       Planned releases to CPAN should be performed by the release manager, at
107       the time of writing Marcus Ramberg, or the deputy release manager, at
108       the time of writing Florian Ragwitz. In the case of critical error
109       correction, any member of the Core Team can perform a rescue release.
110
111   Public statements from the Core Team
112       The Core Team should strive to appear publicly as a group when
113       answering questions or other correspondence. In cases where this is not
114       possible, the same order as for CPAN releases applies.
115
116   New Catalyst Extensions
117       As Catalyst is deliberately designed for extension, there is an
118       ecosystem of several hundred Catalyst extensions that can be found on
119       CPAN.
120
121       See Catalyst::Manual::ExtendingCatalyst for more information on how to
122       extend Catalyst in various ways and how to write CPANable components
123       for Catalyst which can be reused in many applications.
124
125       It is recommended to post a request for comments to the Catalyst
126       mailing list, or ask around in the #catalyst IRC channel before
127       starting to implement something, as another member of the community is
128       likely to have example or prototype code that you can reuse, and
129       members of the community and core team are happy to advise on the best
130       way to implement a generic solution to a particular problem.
131
132       This could save you duplicate work, and will help you produce a better
133       thought out and designed extension.
134

AUTHORS

136       Catalyst Contributors, see Catalyst.pm
137
139       This library is free software. You can redistribute it and/or modify it
140       under the same terms as Perl itself.
141
142
143
144perl v5.30.1                      2020-0C1a-t2a9lyst::Manual::DevelopmentProcess(3)
Impressum