Author: janne.t.harkonen
Date: Wed Jun 10 03:40:52 2009
New Revision: 2025
Modified:
wiki/ContributingCode.wiki
Log:
Edited wiki page through web user interface.
Modified: wiki/ContributingCode.wiki
==============================================================================
--- wiki/ContributingCode.wiki (original)
+++ wiki/ContributingCode.wiki Wed Jun 10 03:40:52 2009
@@ -3,8 +3,7 @@
= Code style =
-In general, we follow the [http://www.python.org/dev/peps/pep-0008/ Style
Guide
-for Python Code (PEP-8)] in all the code we write. Unless you have a very
good
+In general, we follow the [http://www.python.org/dev/peps/pep-0008/ Style
Guide for Python Code (PEP-8)] in all the code we write. Unless you have a
very good
reason not to, follow this. In some projects/modules there might be a
reason to
write code contradictory to PEP-8, but those exceptions should be clearly
documented.
@@ -17,8 +16,7 @@
* We leave two blank lines between public top level functions. However,
top-level function and associated helper function (whose name start with
`_`) are separated by one blank line.
Everyone interested in writing good Python code should read
-[http://python.net/~goodger/projects/pycon/2007/idiomatic/handout.html
-Idiomatic Python].
+[http://python.net/~goodger/projects/pycon/2007/idiomatic/handout.html
Idiomatic Python].
= Submitting patches =
@@ -56,6 +54,7 @@
Robot Framework itself and most of the related projects use Subversion as
their
version control system. The project pages have `Source` tab with additional
instructions for checkout.
+Patches should be submitted to the project's issue tracker, under relevant
= Testing =
@@ -72,4 +71,4 @@
To become a committer you need to send some number of quality patches
(tests
included!) that are relevant to the project. Additionally, you need to be
willing to adhere the coding guidelines (to the smallest detail) described
-above.
+above.
\ No newline at end of file
