Contribute

First of all, new developers are welcome to participate. :-)
You can access the Cherokee source code using the following methods:

How to contribute

Before we can incorporate significant contributions, certain legal requirements must be met. Basically you have to make a copyright assignment to the project main developer. Translations and small changes can be accepted without a copyright disclaimer or a copyright assignment.

The project is Free Software licensed under the GPL, this is just a legal issue, but anyway please read the license documentation, prior to contributing anything.

The copyright assignment can be done by submitting the Cherokee Contributor Agreement v1.0, avialable in several formats:

Translations

You will need the cherokee.pot language template, which can be downloaded, extracted from the tarball or generated with autogen.sh if you are using our latest trunk. In this case you will find it as /po/admin/cherokee.pot.

Once you have the ".pot" file you will be able to generate the required .po files for your new language contribution.

The easiest way is to use poEdit, which is a cross-platform gettext catalogs editor.

You can also work with the currently existing .po files to improve or extend our present translations. You can begin making the changes you wish by using a plain text editor or the above mentioned application.

Report Bugs

You might find that something does not work as it should. If so, please file a bug report using our Bug report system or the mail list.

If not using the latest version, chances are that the bug has been found and fixed in the meantime. We would appreciate if you could take the time to upgrade to the latest version (or even the latest SVN snapshot) and verify your bug, but this is not required for reporting.

Mailing list

If something goes wrong, or if you have a question, a suggestion, or are simply interested in Cherokee developement, you can join the Cherokee public mailing list.

Development Mailing lists

There are a couple of mailing list for developers. Both of them are used to send automatic generated messages from the code repository and the bug tracking system. They are useful for developers who want to be updated with the last changes and problems:

Experiments

We are trying hard to innovate. Check out our latest experiments!

Bounty hunting

Bounty hunting is a way of having fun and earning money while working on a Free Software project.

This initiative provides a number of tasks we would like to get done for future releases. Each task has an associated prize. If you implement any of them, you will earn the bounty. Isn't it a wonderful way to have fun and earn money at the same time?

This is an initiative we are going to keep running on the Cherokee project. As long as your contributions help to improve the project's quality and its diffusion, we will try to pay you back!

Be tuned, we will keep publishing new bounties.

Image

Task list

TaskDescriptionBountyFunder
Define it! The best bounty hunting task of all! Think of a cool feature we would love to add to Cherokee, propose it on the mail list, and if it makes sense for us, we will make a new task entry with your proposal. We have money waiting for it! up to you DynDNS

Bounty process

Contact

If you have further questions about this Bounty Hunting, or you want to support the project with new tasks, I encourage you to contact alvaro@alobbs.com

Supporters

This bounty hunting is supported by some of our partners. They are happy with Cherokee and this is their way of supporting the project.
Thank you!!