Contributing to Philo

So you want to contribute to Philo? That’s great! Here’s some ways you can get started:

• Report bugs and request features using the issue tracker at the project site.
• Contribute code using git. You can fork philo’s repository either on GitHub or Gitorious. If you are contributing to Philo, you will need to submit a Contributor License Agreement.
• Join the discussion on IRC at irc://irc.oftc.net/#philo if you have any questions or suggestions or just want to chat about the project. You can also keep in touch using the project mailing lists: philo@ithinksw.org and philo-devel@ithinksw.org.

Branches and Code Style

We use A successful Git branching model with the blessed repository. To make things easier, you probably should too. This means that you should work on and against the develop branch in most cases, and leave it to the release manager to create the commits on the master branch if and when necessary. When pulling changes into the blessed repository at your request, the release manager will usually merge them into the develop branch unless you explicitly note they be treated otherwise.

Philo adheres to PEP8 for its code style, with two exceptions: tabs are used rather than spaces, and lines are not truncated at 79 characters.

Licensing and Legal

In order for the release manager to merge your changes into the blessed repository, you will need to have already submitted a signed CLA. Our CLAs are based on the Apache Software Foundation’s CLAs, which is the same source as the Django Project’s CLAs. You might, therefore, find the Django Project’s CLA FAQ. helpful.

If you are an individual not doing work for an employer, then you can simply submit the Individual CLA.

If you are doing work for an employer, they will need to submit the Corporate CLA and you will need to submit the Individual CLA Individual CLA as well.

Both documents include information on how to submit them.