Contributions are welcome, and they are greatly appreciated! Every little bit helps, and credit will always be given.
When contributing, please mimic the coding style/conventions used in this repo. If you add new classes or functions, please add the appropriate doc blocks with examples. Also, make sure the python linter and tests pass.
Ready to contribute? Here's how.
Report bugs at https://github.com/nerevu/riko/issues.
If you are reporting a bug, please include:
- Your operating system name and version.
- Any details about your local setup that might be helpful in troubleshooting.
- Detailed steps to reproduce the bug.
Look through the GitHub issues for anything tagged with bug
and hack away.
Look through the GitHub issues for anything tagged with feature
and hack away.
riko could always use more documentation, whether as part of the official docs, in docstrings, or even on the web in blog posts, articles, and such. Feel free to contribute any type of documentation.
The best way to send feedback is to file an issue at https://github.com/nerevu/riko/issues.
If you are proposing a feature:
- Explain in detail how it would work.
- To make it easier to implement, Keep the scope as narrow as possible.
- Remember that this is a volunteer-driven project, and that contributions are welcome :)
Ready to contribute? Here's how to set up riko
for local development.
- Fork the
riko
repo on GitHub and clone
git clone git@github.com:<your_username>/riko.git
cd riko
- Setup a new virtualenv with
virtualenvwrapper
mkvirtualenv --no-site-packages riko
Or, if you only have virtualenv
installed
virtualenv --no-site-packages ~/.venvs/riko
source ~/.venvs/riko/bin/activate
- Install required modules
Python3
pip install -r dev-requirements.txt
pip install -r optional-requirements.txt
pip install -r requirements.txt
Python2
pip install -r dev-requirements.txt
pip install -r optional-requirements.txt
pip install -r py2-requirements.txt
- Run setup develop script
python setup.py develop
- Create a branch for local development
git checkout -b name-of-your-bugfix-or-feature
- Make your changes and run linter and tests
manage lint
manage test
# or to run the full integration tests
tox
- Commit your changes and push your branch to GitHub
git add .
git commit -m "Your detailed description of your changes."
git push origin name-of-your-bugfix-or-feature
- Submit a pull request on the riko repo.
Before you submit a pull request, check that it meets these guidelines:
- The pull request includes tests.
- If the pull request adds functionality, the docs should be updated: Put your new functionality into a function with a docstring, and add the feature to the list in README.rst.