Commit | Line | Data |
cb93c9d7 |
1 | =head1 NAME |
2 | |
3 | Catalyst::Manual::DevelopmentProcess - Administrative structure of the Catalyst Development Process |
4 | |
5 | =head1 Aims of the Catalyst Core Team |
6 | |
7 | The main current goals of the Catalyst core development team continue to |
8 | be stability, performance, and a more paced addition of features, with a |
9 | focus on extensibility. Extensive improvements to the documentation are |
10 | also expected in the short term. |
11 | |
12 | The Catalyst Roadmap at L<http://dev.catalyst.perl.org/roadmap> will |
13 | remain as is, and continues to reflect the specific priorities and |
14 | schedule for future releases. |
15 | |
16 | =head1 Charter for the Catalyst Core Team |
17 | |
18 | =head2 Intention |
19 | |
20 | The intention of the Catalyst Core Team is to maintain and support the |
21 | Catalyst framework, in order for it to be a viable and stable framework |
22 | for developing web-based MVC applications. This includes both technical |
23 | decisions about the Catalyst core distribution, and public relations |
24 | relating to the Catalyst framework as a whole. |
25 | |
26 | The main priority for development is stability for the users of the |
27 | framework, while improving usability and extensibility, as well as |
28 | improving documentation and ease of deployment. |
29 | |
30 | =head2 Membership |
31 | |
32 | The Catalyst Core Team consists of the developers that have full commit |
33 | privileges to the entire Catalyst source tree. |
34 | |
35 | In addition, the core team may accept members that have non-technical |
36 | roles such as marketing, legal, or economic responsibilities. |
37 | |
7d36d4ac |
38 | Currently, the Core Team consists of the following people: |
cb93c9d7 |
39 | |
40 | =over 4 |
41 | |
7d36d4ac |
42 | =item Brian Cassidy |
43 | |
cb93c9d7 |
44 | =item Andy Grundman |
45 | |
46 | =item Christian Hansen |
47 | |
7d36d4ac |
48 | =item Yuval Kogman |
cb93c9d7 |
49 | |
50 | =item Marcus Ramberg |
51 | |
7d36d4ac |
52 | =item Jonathan Rockway |
53 | |
cb93c9d7 |
54 | =item Jesse Sheidlower |
55 | |
56 | =item Matt S. Trout |
57 | |
cb93c9d7 |
58 | =back |
59 | |
60 | New members of the Core Team must be accepted by a 2/3 majority by the |
61 | current members. |
62 | |
63 | =head2 Technical Decisions. |
64 | |
65 | Any change to the Catalyst core which can not be conceived as a |
66 | correction of an error in the current feature set will need to be |
67 | accepted by at least 3 members of the Core Team before it can be |
68 | commited to the trunk (which is the basis for CPAN releases). Anyone |
69 | with access is at any time free to make a branch to develop a proof of |
70 | concept for a feature to be committed to trunk. |
71 | |
72 | =head2 Organizational and Philosophical Decisions. |
73 | |
74 | Any such decision should be decided by majority vote. Thus it should be |
75 | a goal of the organization that its membership number should at any time |
76 | be an odd number, to render it effective with regards to decision |
77 | making. The exceptions to this rule are changes to this charter and |
78 | additions to the membership of the Core Team, which require a 2/3 |
79 | majority. |
80 | |
81 | =head2 CPAN Releases |
82 | |
83 | Planned releases to CPAN should be performed by the release manager, at |
84 | the time of writing Marcus Ramberg, or the deputy release manager, at |
85 | the time of writing Andy Grundman. In the case of critical error |
86 | correction, any member of the Core Team can perform a rescue release. |
87 | |
88 | =head2 Public statements from the Core Team |
89 | |
90 | The Core Team should strive to appear publicly as a group when answering |
91 | questions or other correspondence. In cases where this is not possible, |
92 | the same order as for CPAN Releases applies. |
93 | |
94 | |