[catagits/Catalyst-Manual.git] / lib / Catalyst / Manual / DevelopmentProcess.pod

=head1 NAME

Catalyst::Manual::DevelopmentProcess - Administrative structure of the Catalyst Development Process

=head1 Catalyst development

=head2 Schedule

There is no dated release cycle for Catalyst. New releases will be made
when sufficient small fixes have accumalated, or an important bugfix, or
significant feature addition is completed.

=head2 Roadmanp for features

The Catalyst Roadmap is kept at
L<http://dev.catalyst.perl.org/repos/Catalyst/Catalyst-Runtime/5.80/trunk/lib/Roadmap.pod>

=head2 Bug list

The TODO list with known bugs / deficiences is kept at
L<http://dev.catalyst.perl.org/repos/Catalyst/Catalyst-Runtime/5.80/trunk/TODO>

=head1 The Catalyst Core Team

The intention of the Catalyst Core Team is to maintain and support the
Catalyst framework, in order for it to be a viable and stable framework
for developing web-based MVC applications. This includes both technical
decisions about the Catalyst core distribution, and public relations
relating to the Catalyst framework as a whole.

The current goals of the Catalyst core development team are
be stability, performance, and a paced addition of features, with a
focus on extensibility.

The core team are concerned with the 'core' Catalyst distributions
(i.e. L<Catalyst::Runtime>, L<Catalyst::Devel> and L<Catalyst::Manual>),
and also tries to encourage best practices for extension authors and
cooperation and shared vision within the Catalyst community.

=head2 Membership

The Catalyst Core Team consists of the developers that have full commit
privileges to the entire Catalyst source tree, who have made a significant
contribution to the core Catalyst distributions, and various extensions and
pugins.

In addition, the core team includes members that have non-technical
roles such as marketing, legal, or economic responsibilities.

Currently, the Core Team consists of the following people:

=over 4

=item Brian Cassidy

=item Andy Grundman

=item Christian Hansen

=item Yuval Kogman

=item Marcus Ramberg

=item Jonathan Rockway

=item Jesse Sheidlower

=item Matt S. Trout

=item Florian Ragwitz

=item Tomas Doran

=back

New members of the Core Team must be accepted by a 2/3 majority by the
current members.

=head2 Technical Decisions.

Any change to the Catalyst core which can not be conceived as a
correction of an error in the current feature set will need to be
accepted by at least 3 members of the Core Team before it can be
commited to the trunk (which is the basis for CPAN releases). Anyone
with access is at any time free to make a branch to develop a proof of
concept for a feature to be committed to trunk.

=head2 Organizational and Philosophical Decisions.

Any such decision should be decided by majority vote. Thus it should be
a goal of the organization that its membership number should at any time
be an odd number, to render it effective with regards to decision
making. The exceptions to this rule are changes to this charter and
additions to the membership of the Core Team, which require a 2/3
majority.

=head2 CPAN Releases

Planned releases to CPAN should be performed by the release manager, at
the time of writing Marcus Ramberg, or the deputy release manager, at
the time of writing Florian Ragwitz. In the case of critical error
correction, any member of the Core Team can perform a rescue release.

=head2 Public statements from the Core Team

The Core Team should strive to appear publicly as a group when answering
questions or other correspondence. In cases where this is not possible,
the same order as for CPAN Releases applies.

=head1 Contributing to Catalyst

The main philosophy behind Catalyst development can be surimsed as:

    Patches welcome!

Everyone is welcome (and will be encouraged) to contribute to Catalyst
in whatever capacity they're able to. People in #catalyst-dev will be
more than happy to talk newcomers through contributing their first patch,
or how best to go about their first CPAN extension module..

=head2 Repositories

The Catalyst subversion repository can be found at:

    http://dev.catalyst.perl.org/repos/Catalyst

and the git repository can be found at FIXME

=head2 New Catalyst extensions

As Catalyst is deliberately designed for extension, there is an ecosystem of
several hundred Catalyst extensions which can be found on CPAN.

FIXME
Commit	Line	Data
cb93c9d7	1	=head1 NAME
	2
	3	Catalyst::Manual::DevelopmentProcess - Administrative structure of the Catalyst Development Process
	4
e91e320b	5	=head1 Catalyst development
cb93c9d7	6
e91e320b	7	=head2 Schedule
	8
	9	There is no dated release cycle for Catalyst. New releases will be made
	10	when sufficient small fixes have accumalated, or an important bugfix, or
	11	significant feature addition is completed.
cb93c9d7	12
e91e320b	13	=head2 Roadmanp for features
	14
	15	The Catalyst Roadmap is kept at
b1a08fe1	16	L<http://dev.catalyst.perl.org/repos/Catalyst/Catalyst-Runtime/5.80/trunk/lib/Roadmap.pod>
cb93c9d7	17
e91e320b	18	=head2 Bug list
	19
	20	The TODO list with known bugs / deficiences is kept at
	21	L<http://dev.catalyst.perl.org/repos/Catalyst/Catalyst-Runtime/5.80/trunk/TODO>
cb93c9d7	22
e91e320b	23	=head1 The Catalyst Core Team
cb93c9d7	24
	25	The intention of the Catalyst Core Team is to maintain and support the
	26	Catalyst framework, in order for it to be a viable and stable framework
	27	for developing web-based MVC applications. This includes both technical
	28	decisions about the Catalyst core distribution, and public relations
	29	relating to the Catalyst framework as a whole.
	30
e91e320b	31	The current goals of the Catalyst core development team are
	32	be stability, performance, and a paced addition of features, with a
	33	focus on extensibility.
	34
	35	The core team are concerned with the 'core' Catalyst distributions
	36	(i.e. L<Catalyst::Runtime>, L<Catalyst::Devel> and L<Catalyst::Manual>),
	37	and also tries to encourage best practices for extension authors and
	38	cooperation and shared vision within the Catalyst community.
cb93c9d7	39
	40	=head2 Membership
	41
	42	The Catalyst Core Team consists of the developers that have full commit
e91e320b	43	privileges to the entire Catalyst source tree, who have made a significant
	44	contribution to the core Catalyst distributions, and various extensions and
	45	pugins.
cb93c9d7	46
e91e320b	47	In addition, the core team includes members that have non-technical
cb93c9d7	48	roles such as marketing, legal, or economic responsibilities.
cb93c9d7	49
7d36d4ac	50	Currently, the Core Team consists of the following people:
cb93c9d7	51
	52	=over 4
	53
7d36d4ac	54	=item Brian Cassidy
7d36d4ac	55
cb93c9d7	56	=item Andy Grundman
	57
	58	=item Christian Hansen
	59
7d36d4ac	60	=item Yuval Kogman
cb93c9d7	61
	62	=item Marcus Ramberg
	63
7d36d4ac	64	=item Jonathan Rockway
7d36d4ac	65
cb93c9d7	66	=item Jesse Sheidlower
	67
	68	=item Matt S. Trout
	69
b1a08fe1	70	=item Florian Ragwitz
	71
	72	=item Tomas Doran
	73
cb93c9d7	74	=back
	75
	76	New members of the Core Team must be accepted by a 2/3 majority by the
	77	current members.
	78
	79	=head2 Technical Decisions.
	80
	81	Any change to the Catalyst core which can not be conceived as a
	82	correction of an error in the current feature set will need to be
	83	accepted by at least 3 members of the Core Team before it can be
	84	commited to the trunk (which is the basis for CPAN releases). Anyone
	85	with access is at any time free to make a branch to develop a proof of
	86	concept for a feature to be committed to trunk.
	87
	88	=head2 Organizational and Philosophical Decisions.
	89
	90	Any such decision should be decided by majority vote. Thus it should be
	91	a goal of the organization that its membership number should at any time
	92	be an odd number, to render it effective with regards to decision
	93	making. The exceptions to this rule are changes to this charter and
	94	additions to the membership of the Core Team, which require a 2/3
	95	majority.
	96
	97	=head2 CPAN Releases
	98
	99	Planned releases to CPAN should be performed by the release manager, at
	100	the time of writing Marcus Ramberg, or the deputy release manager, at
b1a08fe1	101	the time of writing Florian Ragwitz. In the case of critical error
cb93c9d7	102	correction, any member of the Core Team can perform a rescue release.
	103
	104	=head2 Public statements from the Core Team
	105
	106	The Core Team should strive to appear publicly as a group when answering
	107	questions or other correspondence. In cases where this is not possible,
	108	the same order as for CPAN Releases applies.
	109
e91e320b	110	=head1 Contributing to Catalyst
	111
	112	The main philosophy behind Catalyst development can be surimsed as:
	113
	114	Patches welcome!
	115
	116	Everyone is welcome (and will be encouraged) to contribute to Catalyst
	117	in whatever capacity they're able to. People in #catalyst-dev will be
	118	more than happy to talk newcomers through contributing their first patch,
	119	or how best to go about their first CPAN extension module..
	120
	121	=head2 Repositories
	122
	123	The Catalyst subversion repository can be found at:
	124
	125	http://dev.catalyst.perl.org/repos/Catalyst
	126
	127	and the git repository can be found at FIXME
	128
	129	=head2 New Catalyst extensions
	130
	131	As Catalyst is deliberately designed for extension, there is an ecosystem of
	132	several hundred Catalyst extensions which can be found on CPAN.
cb93c9d7	133
e91e320b	134	FIXME