Galicaster Code Contributions

{section}
{column:width=50%}

h5. *RECOMMENDATIONS:*

# {color:#222222}All contributions must be forked from the "master" branch.{color}
# {color:#222222}Frequently pull changes made at the master branch, to keep your feature branch in synch. Features or bug fixes that don't merge cleanly will be rejected.{color}
# {color:#222222}Send us a pull request when your feature or bug fix is ready. Please do not group several bug fixes or features in the same request (where possible){color}
# {color:#222222}Use descriptive commit messages and include a reference to the relevant issue, if any (e.g. "Fixed so-and-so bug, issue #15").{color}

h5. {color:#222222}{*}NICE TO HAVE:*{color}

# {color:#222222}Add unit tests to the features developed.{color}
# {color:#222222}Check your code quality before sending the pull request. You may use tools such as pep8 or pychecker.{color}

{column:width=50%}

{center}

*We are using Git this way:*

!Galicaster.gitflow-model v02b.jpg|border=1,width=500!

Inspired on Vicent Driessen [Git branching model|http://nvie.com/posts/a-successful-git-branching-model/]
{center}
{column}{section}