Contribution
This guide has been written to help anyone interested in contributing to the development of Catmandu. Please read this guide before contributing to Catmandu or related projects, to avoid wasted effort and maximizing the chances of your contributions being used.
There are many ways to contribute to the project. Catmandu is a young yet active project and any kind of help is very much appreciated!
You don't have to start by hacking the code, spreading the word is very valuable as well!
If you have a blog, just feel free to speak about Catmandu.
Of course, it doesn't have to be limited to blogs or Twitter. Feel free to spread the word in whatever way you consider fit and drop us a line on the Catmandu user mailing list noted below.
Also, if you're using and enjoying Catmandu, rating us on cpanratings.perl.org, explaining what you like about Catmandu is another very valuable contribution that helps other new users find us!
Subscribing to the mailing list and providing assistance to new users is incredibly valuable.
- Mailing list:
librecat-dev@mail.librecat.org - Subscribe or view archives here: http://mail.librecat.org/mailman/listinfo/librecat-dev
We value documentation very much, but it's difficult to keep it up-to-date. If you find a typo or an error in the documentation please do let us know - ideally by submitting a patch (pull request) with your fix or suggestion (see "Patch Submission").
To contribute to Catmandu's core code, see "Patch Submission" below. You can also extend the functionality by new Importers, Exporters, Stores, Fix packages, Validators, Binds, or Plugins. Have a look at the list of missing modules for existing ideas and resources for new Catmandu modules. Feel also free to add new ideas and links there.
This section lists high-level recommendations for developing Catmandu, for more detailed guidelines, see the Coding guidelines.
Catmandu should be able to install for all Perl versions since 5.10.1, on any platform for which Perl exists. We focus mainly on GNU/Linux (any distribution).
You should avoid regressions as much as possible and keep backwards compatibility in mind when refactoring. Stable releases should not break functionality and new releases should provide an upgrade path and upgrade tips such as warning the user about deprecated functionality.
We can measure our quality using the CPAN testers platform: http://www.cpantesters.org.
A good way to help the project is to find a failing build log on the CPAN testers: http://www.cpantesters.org/distro/D/Catmandu.html
If you find a failing test report or another kind of bug, feel free to report it as a GitHub issue: http://github.com/LibreCat/Catmandu/issues. Please make sure the bug you're reporting does not yet exist.
- See development setup for guidelines how to set up a development environment for contributing to the Catmandu core.
- See Patch submission (GitHub workflow)
The official website is here: http://librecat.org/
A mailing list is available here: librecat-dev@mail.librecat.org
The official repository is hosted on GitHub at http://github.com:LibreCat/Catmandu.
Official developers have write access to this repository, contributors are invited to fork the dev branch (!) and submit a pull request, as described at patch submission.
This guide was based on Dancer2::Development.
