Translating & Localizing eZ Publish using GIT

Conclusion

This tutorial gives the necessary technical insight on how to use GIT/github to participate to the Localization effort of eZ Publish. If using this tool poses a problem to you, you still have the opportunity to drop the work done to community@ez.no, making sure your valuable Localization contributions are not missed.

Happy localization everyone !

Resources

If you have questions when it comes to git, first place to look should probably be Github’s FAQ, as it explains things straight forward and also covers Github-related questions. But for a GIT specific article, be sure to check out one from A list Apart on the subject which also mentions the most important additional GIT resources like Git ready, Pro Git and the official documentation. If you are a cheat-sheet addict, check this out : http://help.github.com/git-cheat-sheets.

Feel free to use the forums ( http://share.ez.no/forums/translation ), or comments under this tutorial to ask for & share tips & tricks on the usage of GIT/github.

This tutorial is available for offline reading in PDF format : Translating and Localizing eZ Publish using GIT - PDF Version

About the authors : Nicolas Pastorino & Andre Rømcke

Written by :

• Nicolas Pastorino
• Andre Rømcke

Reviewed by Bertrand Dunogier.

License choice

http://creativecommons.org/licenses/by-sa/3.0

Appendix : GIT/Github jargon

Git terms:

• Clone: Clones a whole repository, giving you access to all it’s branches and tags locally in one folder (but you’ll need to use checkout to select one at a time).
• Commit: Like in svn, but only done locally. Allows you to commit offline and do several small commits to simplify reviews
• Push: Push your local commits to a remote repository
• Pull: Like svn up, pulls in changes from a remote repository
• origin: The origin remote server, this refers to the origin remote GIT server you cloned a repository from, and has nothing to do with forks.
• upstream: And open source term for a third party project your code relies on, in GIT often used for the original project, the one you forked in case of Github. aka ezystems/ezpublish when dealing with eZ Publish.

Github terms:

• Fork: Like a copy of a repository with some knowledge of original repository and compare / status features. To be able to easily share changes you do, as opposed to keeping your changes locally on custom branches or setting up your own GIT server that contains your changes.
• Pull request: A Github feature, makes it possible to notify the original repository committers about your branch and ask him to integrate your work in (make sure you comply with CLA / coding standards before you do)