Commit | Line | Data |
9b29b536 |
1 | =head1 Catalyst Development Process |
2 | |
3 | Below you will find information related to 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 |
155abf4b |
8 | be stability, performance, and a more paced addition of features, with a |
9b29b536 |
9 | focus on extensibility. Extensive improvements to the documentation are |
10 | also expected in the short term. |
11 | |
12 | The Catalyst Roadmap at http://dev.catalyst.perl.org/roadmap will remain |
13 | as is, and continues to reflect the specific priorities and schedule for |
14 | 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 |
155abf4b |
22 | for developing web-based MVC applications. This includes both technical |
9b29b536 |
23 | decisions about the Catalyst core distribution, and public relations |
155abf4b |
24 | relating to the Catalyst framework as a whole. |
9b29b536 |
25 | |
155abf4b |
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. |
9b29b536 |
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 | |
155abf4b |
35 | In addition, the core team may accept members that have non-technical |
36 | roles such as marketing, legal, or ecconomic responsibilities. |
9b29b536 |
37 | |
38 | |
39 | At the time of conception, the Core Team consists of the following people: |
40 | |
41 | =over 4 |
42 | |
43 | =item Andy Grundman |
44 | |
45 | =item Christian Hansen |
46 | |
47 | =item Brian Cassidy |
48 | |
49 | =item Marcus Ramberg |
50 | |
51 | =item Jesse Sheidlower |
52 | |
53 | =item Matt S. Trout |
54 | |
55 | =item Yuval Kogman |
56 | |
57 | =back |
58 | |
59 | New members of the Core Team must be accepted by a 2/3 majority by the |
60 | current members. |
61 | |
62 | =head2 Technical Decisions. |
63 | |
155abf4b |
64 | Any change to the Catalyst core which can not be conceived as a |
65 | correction of an error in the current feature set will need to be |
66 | accepted by at least 3 members of the Core Team before it can be |
67 | commited to the trunk (which is the basis for CPAN releases). Anyone |
68 | with access is at any time free to make a branch to develop a proof of |
69 | concept for a feature to be committed to trunk. |
9b29b536 |
70 | |
71 | =head2 Organizational and Philosophical Decisions. |
72 | |
155abf4b |
73 | Any such decision should be decided by majority vote. Thus it should be |
74 | a goal of the organization that its membership number should at any time |
75 | be an odd number, to render it effective with regards to decision |
76 | making. The exceptions to this rule are changes to this charter and |
77 | additions to the membership of the Core Team, which require a 2/3 |
78 | majority. |
9b29b536 |
79 | |
80 | =head2 CPAN Releases |
81 | |
155abf4b |
82 | Planned releases to CPAN should be performed by the release manager, at |
4a001870 |
83 | the time of writing Marcus Ramberg, or the deputy release manager, at |
155abf4b |
84 | the time of writing Andy Grundman. In the case of critical error |
85 | correction, any member of the Core Team can perform a rescue release. |
9b29b536 |
86 | |
87 | =head2 Public statements from the Core Team |
88 | |
89 | The Core Team should strive to appear publicly as a group when answering |
155abf4b |
90 | questions or other correspondence. In cases where this is not possible, |
91 | the same order as for CPAN Releases applies. |
9b29b536 |
92 | |
93 | |