Tuesday 01 March 2011 10:07:20 pm
At the end of this tutorial, you should be able to contribute to eZ Publish Community Project, eZ Publish’s kernel developed by both eZ and the eZ Community. You will learn how to use git and github in the scope of this participation, and be given the bunch of best-practices to follow for smooth collaboration.
With the change to Git/ Github earlier this year, the 4.4 release and the future change to how we manage our eZ Publish Community Project (CP), now is a good time to learn how to get eZ Publish from Git and contribute on solving issues and innovating.
Collaborating on eZ Publish development is not really hard or too time-consuming if we take advantage of the tools that we have at hand, and Git + Github really shines here. First of all it’s a way for you to make sure the bug is fixed more quickly while at the same time making sure you are properly attributed for your work.
The Community Project symbolizes eZ’s core value of openness in making contribution to eZ Publish kernel happen. Time to roll your sleeves up and make eZ Publish a bit of your own.
This post is aimed at developers and technical users who want to be able to make changes to eZ Publish and share them with others, and in the end the change is bound to be integrated into the product.
If you’re just here to find out how to clone / “checkout” eZ Publish from Git, skip to “Cloning read only”, and optionally “Installing Git and setting up Github”.
Note: This document should be considered as a living document, parts of it can be moved to GitHub wiki at any point for easier maintenance and for updates as the community go forward. This is especially true for coding standards and commit conventions.