X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=catagits%2FCatalyst-Manual.git;a=blobdiff_plain;f=lib%2FCatalyst%2FManual%2FDevelopmentProcess.pod;h=a0183e6ec9fe7d414e5cded6b5013b8348b3f835;hp=f8883f9b70b7f817ecd1d8a218465eae3741044c;hb=5336f54651dd781138086b9081b85b6839452a76;hpb=ca7329b2517b19d1ccf9673fb8d48920092676b5 diff --git a/lib/Catalyst/Manual/DevelopmentProcess.pod b/lib/Catalyst/Manual/DevelopmentProcess.pod index f8883f9..a0183e6 100644 --- a/lib/Catalyst/Manual/DevelopmentProcess.pod +++ b/lib/Catalyst/Manual/DevelopmentProcess.pod @@ -2,8 +2,48 @@ 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 Discussing proposed bugfixes or improvements + +L 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 + +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". + +=head2 Repositories + +The Catalyst git repository can be found at: + + 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 Catalyst subversion repository can be found at: + + svn: http://dev.catalyst.perl.org/repos/Catalyst + browser: http://dev.catalyst.perl.org/svnweb/Catalyst + =head2 Schedule There is no dated release cycle for Catalyst. New releases will be made @@ -13,12 +53,12 @@ significant feature addition, is completed. =head2 Roadmap for features The Catalyst Roadmap is kept at -L +L =head2 Bug list -The TODO list with known bugs / deficiences is kept at -L +The TODO list with known bugs / deficiencies is kept at +L =head1 The Catalyst Core Team @@ -81,9 +121,9 @@ current members. 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. @@ -107,28 +147,33 @@ 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 +=head2 New Catalyst Extensions -The main philosophy behind Catalyst development can be summarized as: +As Catalyst is deliberately designed for extension, there is an ecosystem of +several hundred Catalyst extensions that can be found on CPAN. - Patches welcome! +See L 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. -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.... +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. -=head2 Repositories +This could save you duplicate work, and will help you produce a better +thought out and designed extension. -The Catalyst subversion repository can be found at: +=head1 AUTHORS - http://dev.catalyst.perl.org/repos/Catalyst +Catalyst Contributors, see Catalyst.pm -and the git repository can be found at FIXME +=head1 COPYRIGHT -=head2 New Catalyst extensions +This library is free software. You can redistribute it and/or modify it under +the same terms as Perl itself. -As Catalyst is deliberately designed for extension, there is an ecosystem of -several hundred Catalyst extensions which can be found on CPAN. +=cut -FIXME