Thanks for your interest in contributing! These guidelines apply across the
Pryv organization unless a repository provides its own
CONTRIBUTING.md.
- Report bugs — open an issue on the relevant repository with clear steps to reproduce, expected vs. actual behaviour, and your environment.
- Suggest features — open an issue describing the use case and motivation.
- Submit code — fork, branch, and open a pull request (see below).
- Improve docs — documentation lives in dev-site (published at pryv.github.io).
- Fork the repository and create a branch from the default branch.
- Keep changes focused; one logical change per pull request.
- Follow the existing code style and run the project's linter and tests.
- Describe what changed and why in the PR description.
- Link any related issue.
Please do not open public issues for security vulnerabilities. See
SECURITY.md for responsible disclosure.
Most Pryv repositories are open-source (BSD-3-Clause or as stated in each repo's
LICENSE). By contributing, you agree your contributions are licensed under the
repository's license.
Be respectful and constructive. We want Pryv to be a welcoming community for everyone.