2.8 KiB
This is a Jazzband project. By contributing you agree to abide by the Contributor Code of Conduct and follow the guidelines.
Contributing
We love your input! We want to make contributing to this project as easy and transparent as possible, whether it's:
- Reporting a bug
- Discussing the current state of the code
- Submitting a fix
- Proposing new features
- Becoming a maintainer
Dependencies
We use poetry to manage the dependencies.
To install them you would need to run install command:
poetry install
To activate your virtualenv run poetry shell.
Tests
We use pytest and flake8 for quality control.
To run all tests:
pytest
We develop with Github
We use github to host code, to track issues and feature requests, as well as accept pull requests.
We use Github Flow, so all code changes from community happen through pull requests
Pull requests are the best way to propose changes to the codebase (we use Github Flow). We actively welcome your pull requests:
- Fork the repo and create your branch from
master. - If you've added code that should be tested, add tests.
- If you've changed APIs, update the documentation.
- Ensure the test suite passes.
- Make sure your code lints.
- Describe the pull request using this template.
Any contributions you make will be under the GNU Lesser General Public License v3.0
In short, when you submit code changes, your submissions are understood to be under the same LGPLv3 that covers the project. Feel free to contact the maintainers if that's a concern.
Report bugs using Github's issues
We use GitHub issues to track public bugs. Report a bug by opening a new issue. Use this template to describe your reports.
Use a consistent coding style
We use Black and (working towards) wemake-python-styleguide for code and Google-style reStructuredText for doc-strings.
This document was adapted from the open-source contribution guidelines for [Facebook's Draft](
a9316a723f/CONTRIBUTING.md).