Skip to content

Latest commit

 

History

History
35 lines (26 loc) · 1.93 KB

CONTRIBUTING.md

File metadata and controls

35 lines (26 loc) · 1.93 KB
Raw

Contributing to Headphones

For users

In case you read this because you are posting an issue, please take a minute and conside the things below. The issue tracker is not a support forum. It is primarily intended to submit bugs, improvements or feature requests. However, we are glad to help you, and make sure the problem is not caused by Headphones, but don't expect step-by-step answers.

  • Use the search function. Chances are that your problem is already discussed.
  • Visit the Troubleshooting wiki first.
  • Use proper formatting. Paste your logs in code blocks.
  • Close your issue if you resolved it.

For developers

If you think you can contribute code to the Headphones repository, do not hesitate to submit a pull request.

Branches

All pull requests should be based on the develop branch. When you want to develop a new feature, clone the repository with git clone origin/develop -b FEATURE_NAME. Use meaningful commit messages.

Code compatibility

The code should work with Python 2.6 and 2.7. Note that Headphones runs on different platforms, including Network Attached Storage devices such as Synology.

Re-use existing code. Do not hesitate to add logging in your code. You can the logger module headphones.logger.* for this. Web requests are invoked via headphones.request.* and derived ones. Use these methods to automatically add proper and meaningful error handling.

Code conventions

Altough Headphones did not adapt a code convention in the past, we try to follow the PEP8 conventions for future code. A short summary to remind you (copied from http://wiki.ros.org/PyStyleGuide):

  • 4 space indentation
  • 80 characters per line
  • package_name
  • ClassName
  • method_name
  • field_name
  • _private_something
  • self.__really_private_field
  • _global

Document your code!