Send patches to ryu-devel@lists.sourceforge.net. Please don't use 'pull request' on github. We expect you to send a patch in Linux kernel development style. If you are not familiar with it, please read the following document:
https://www.kernel.org/doc/Documentation/SubmittingPatches
Please check your changes with pep8 and run unittests to make sure that they don't break the existing features. The following command does both for you:
fujita@rose:~/git/ryu$ ./run_tests.sh
Of course, you are encouraged to add unittests when you add new features (it's not a must though).
pep8 As python is used, PEP8 is would be hopefully mandatory for http://www.python.org/dev/peps/pep-0008/
pylint Although pylint is useful for finding bugs, but pylint score not very important for now because we're still at early development stage.
Google python style guide is very helpful http://google-styleguide.googlecode.com/svn/trunk/pyguide.html
Guidelines derived from Guido's Recommendations
OpenStack Nova style guide https://github.com/openstack/nova/blob/master/HACKING.rst
JSON files Ryu source tree has JSON files under ryu/tests/unit/ofproto/json. They are used by unit tests. To make patches easier to read, they are normalized using tools/normalize_json.py. Please re-run the script before committing changes to these JSON files.
此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。