We love your input! We want to make contributing to SwarmVault 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
We use GitHub to host code, to track issues and feature requests, as well as accept pull requests.
- Fork the repo and create your branch from
main
- 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
- Issue that pull request!
- Update the README.md with details of changes if applicable
- Update the requirements.txt if you add any dependencies
- The PR will be merged once you have the sign-off of two other developers
In short, when you submit code changes, your submissions are understood to be under the same GNU GPL v3 License that covers the project. Feel free to contact the maintainers if that's a concern.
We use GitHub issues to track public bugs. Report a bug by opening a new issue; it's that easy!
Great Bug Reports tend to have:
- A quick summary and/or background
- Steps to reproduce
- Be specific!
- Give sample code if you can
- What you expected would happen
- What actually happens
- Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)
- Use Black for Python code formatting
- 4 spaces for indentation rather than tabs
- You can try running
black .
for style unification
By contributing, you agree that your contributions will be licensed under its GNU GPL v3 License.
This document was adapted from the open-source contribution guidelines for Facebook's Draft.