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