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 the general Development Guidelines and Patch Submission.
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.
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.
