Loading sub-menu...

Recomendations for Code Contributions

Version 1 by Vicente Goyanes
on feb 13, 2014 10:56.

compared with
Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (3)

View Page History
*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}Use descriptive commit messages and include a reference to the relevant issue, if any (e.g. "Fixed so-and-so bug, issue #15").{color}

{color:#222222}NICE TO HAVE:{color}
{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}