Catalyst::Manual::DevelopmentProcess - Administrative structure of the Catalyst Development Process
+=head1 Contributing to Catalyst
+
+The main philosophy behind Catalyst development can be summarized 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....
+
=head1 Catalyst development
-=head2 Schedule
+=head2 Discussing proposed bugfixes or improvements
-There is no dated release cycle for Catalyst. New releases will be made
-when sufficient small fixes have accumulated; or an important bugfix, or
-significant feature addition, is completed.
+L<http://wiki.catalystframework.org/wiki/#Community> has information about how
+to get in touch with the Catalyst "community". In particular, you would
+want to discuss a proposed change on the mailing list:
+
+ http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst-dev
+
+or on IRC:
+
+ irc://irc.perl.org/catalyst-dev
+ http://wiki.catalystframework.org/wiki/livegroups
-=head2 Roadmap for features
+Usually, the core team will be more than happy for you to contribute, and
+will talk you through how to submit a patch, or get a "commit bit".
-The Catalyst Roadmap is kept at
-L<http://dev.catalyst.perl.org/repos/Catalyst/Catalyst-Runtime/5.80/trunk/lib/Roadmap.pod>
+=head2 Repositories
+
+The Catalyst git repository can be found at:
-=head2 Bug list
+ read: git://git.shadowcat.co.uk/catagits/PROJECTNAME
+ write: catagits@git.shadowcat.co.uk:PROJECTNAME
+ browser: https://git.shadowcat.co.uk/gitweb/gitweb.cgi
-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 Schedule
+
+There is no dated release cycle for Catalyst. New releases will be made
+when sufficient small fixes have accumulated; or an important bugfix, or
+significant feature addition, is completed.
=head1 The Catalyst Core Team
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
+committed to master (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.
+concept for a feature to be committed to master.
=head2 Organizational and Philosophical Decisions.
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 summarized as:
+=head2 New Catalyst Extensions
- Patches welcome!
+As Catalyst is deliberately designed for extension, there is an ecosystem of
+several hundred Catalyst extensions that can be found on CPAN.
-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....
+See L<Catalyst::Manual::ExtendingCatalyst> for more information on how
+to extend Catalyst in various ways and how to write CPANable components
+for Catalyst which can be reused in many applications.
-=head2 Repositories
+It is recommended to post a request for comments to the Catalyst mailing
+list, or ask around in the #catalyst IRC channel before starting to
+implement something, as another member of the community is likely to
+have example or prototype code that you can reuse, and members of the
+community and core team are happy to advise on the best way to implement
+a generic solution to a particular problem.
-The Catalyst subversion repository can be found at:
+This could save you duplicate work, and will help you produce a better
+thought out and designed extension.
- http://dev.catalyst.perl.org/repos/Catalyst
+=head1 AUTHORS
-and the git repository can be found at FIXME
+Catalyst Contributors, see Catalyst.pm
-=head2 New Catalyst extensions
+=head1 COPYRIGHT
-As Catalyst is deliberately designed for extension, there is an ecosystem of
-several hundred Catalyst extensions which can be found on CPAN.
+This library is free software. You can redistribute it and/or modify it under
+the same terms as Perl itself.
-FIXME
+=cut
projects / catagits/Catalyst-Manual.git / blobdiff