We warmly welcome and actively support anyone willing to contribute to Tine 2.0!

Contribution can be made in many ways and most of the time our forum would be the best place to ask, suggest, brainstorm, find a combatant, etc. If you encounter a bug, please help us to raise the quality and enter it into our bug-tracker.

What should you need to know if you want to actively contribute code to Tine 2.0?

First of all Tine 2.0 is free software. You can basically do with Tine 2.0 whatever you like. But most of the time you would want anything you write to go upstream so it will be included into the next Tine 2.0 releases.

And this is, what we want too. We have decided to make Tine 2.0 free software for people to fix bugs, add features and write own modules.

So this is what we require for anything going upstream:

1. Please download and sign our Contributor License Agreement (CLA).

After signing and sending us the CLA, you are given full GIT access.

2. Checkout the tine 2.0 master.

3. Use our bug-tracker

Please have a look if your specific problem or feature is already listed there. We also recommend adding your own tasks tasks to the tracker as well.

4. Check the Zend Framework coding standard.

5. Do some coding!

Please note that any commit must be OKed from

• development (quality of code), and (if applicable)
• usability (quality of user experience)

So if you are brave, you just commit you patches and hope for the best. But it is much wiser for you to actively seek support from the core team early.

Again, the forum would be the place to do so:

• Tell us what you want to do.
• Ask for a code review early to understand, what we understand as quality of code.
• Show wireframes or early mock-ups to get feedback from the usabilty experts.
• You can even ask for usabilty experts to do the wireframing for you, so you "only" need to code and do not have to bother about quality of user experience.

Welcome and enjoy!