Expand CatalystAndMoose somewhat, re-arrange the DevelopmentProcess docs some more...

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

diff --git a/lib/Catalyst/Manual/DevelopmentProcess.pod b/lib/Catalyst/Manual/DevelopmentProcess.pod
index 36d04b1..df23c76 100644 (file)
--- a/lib/Catalyst/Manual/DevelopmentProcess.pod
+++ b/lib/Catalyst/Manual/DevelopmentProcess.pod
@@ -2,21 +2,25 @@
 
 Catalyst::Manual::DevelopmentProcess - Administrative structure of the Catalyst Development Process
 
-=head1 Aims of the Catalyst Core Team
+=head1 Catalyst development
 
-The main current goals of the Catalyst core development team continue to
-be stability, performance, and a more paced addition of features, with a
-focus on extensibility.
+=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.
 
-The Catalyst Roadmap at
+=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>
-will remain as is,
-and continues to reflect the specific priorities and schedule for future
-releases.
 
-=head1 Charter for the Catalyst Core Team
+=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>
 
-=head2 Intention
+=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
@@ -24,16 +28,23 @@ 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 main priority for development is stability for the users of the
-framework, while improving usability and extensibility, as well as
-improving documentation and ease of deployment.
+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.
+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 may accept members that have non-technical
+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:
@@ -96,4 +107,28 @@ 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