We would love for you to contribute to this project and help make it even better than it is today! As a contributor, here are the guidelines we would like you to follow:
Help us keep this community open and inclusive.
Our code of conduct is located here.
Come talk to us about OPAL, or authorization in general - we would love to hear from you ❤️
You can:
- Raise questions in our Github discussions
- Report issues and ask for features in Github issues
- Follow us on Twitter to get the latest OPAL updates
- Join our Slack community to chat about authorization, open-source, realtime communication, tech or anything else! We are super available on slack ;)
If you are using our project, please consider giving us a ⭐️
If you find a bug in the source code, you can help us by submitting an issue or even better, you can submit a Pull Request with a fix.
You can request a new feature by submitting an issue to our GitHub Repository.
Issues are submitted to our Github issues.
Before you submit an issue, please search the issue tracker, maybe an issue for your problem already exists and the discussion might inform you of workarounds readily available.
We want to fix all the issues as soon as possible, but before fixing a bug we need to reproduce and confirm it. In order to reproduce bugs, we require that you provide:
- Full logs of opal server and opal client
- Your configuration for OPAL server and OPAL client
- i.e: docker compose, Kubernetes YAMLs, environment variables, etc.
- you should redact any secrets/tokens/api keys in your config
PRs are submitted here.
- Pull requests are welcome! (please make sure to include passing tests and docs)
- Prior to submitting a PR - open an issue on GitHub, or make sure your PR addresses an existing issue well.