First of all, thank you for choosing to contribute to our project. This short guide will describe the required coding conventions, as well as the built-in tests that we use in our project. Following these guidelines will help us merge your pull request into our code base in a fast as smooth manner.
Please send us a GitHub Pull Request with a clear list of what you've done. Make sure to include a clear log message for your commits, describing the modifications / additions to the code base, and their implications.
In order to help us close the bug as quickly as possible, please follow these steps:
- Make sure there isn't an open issue that already addresses this bug
- If there isn't, open a new issue and attach as many informative details as you can:
- Architecture & compilation flags in which the bug occurs
- Trace + logs, describing the bug / exception
- As many details as you can in order to help us reproduce and fix this issue
- If you already have a fix, please submit it as a pull request, and include the bug details in it's description
Start reading our code and we believe you'll get the hang of it. The important notes are:
- Every function should be documented in a manner that is consistent with the current documentation standard
- Each indentation level should be 4 spaces in width (spaces, not tabs)
- We believe that comments improve the readability, make sure that your code is documented enough to be understood by other developers
Scout uses the following tools to enforce coding conventions and to help eliminate common python bugs:
Testing can be done from the project's home directory:
- Testing for pydocstyle:
Scout> python tests.py - Testing for flake8:
Scout> flake8 src
We believe that the only way that Open Source tools will help the infosec community in the long term, is to maintain these tools and to make sure they are developed according to the community standards. Each contribution brings as one step further to this goal.
Thanks :)