We welcome any and all contributions to Kedro, at whatever level you can manage. For example, you could:
- Join the community
- Troubleshoot other users' questions or get answers to your own queries
- Report a bug
- Propose a new feature
- Review other contributors' PRs
- Contribute a bug fix or a new feature
- Contribute to the documentation
You can also suggest anything else that you think improves the community for us all!
The Kedro team pledges to foster and maintain a friendly community. We enforce a Code of Conduct to ensure every Kedroid is welcomed and treated with respect.
You can find the Kedro community on our Discord server, which is where we share news and announcements, and general chat. You're also welcome to post links here to any articles or videos about Kedro that you create, or find, such as how-tos, showcases, demos, blog posts or tutorials.
We occasionally post on the QuantumBlack blog and we curate a Github repo that lists content created by the Kedro community.
We encourage you to ask and answer technical questions on GitHub discussions.
We use GitHub issues to keep track of known bugs. We keep a close eye on them and update them when we have an internal fix in progress.
Before you report a new issue, do your best to ensure your problem hasn't already been reported. If it has, just leave a comment on the existing issue, rather than create a new one. If you have already checked the existing GitHub issues and are still convinced that you have found odd or erroneous behaviour then please file a new one.
If you have new ideas for Kedro functionality then please open a GitHub issue and describe the feature you would like to see, why you need it, and how it should work.
Check the Kedro repo to find open pull requests and contribute a review!
If you're interested in contributing fixes to code or documentation, first read our guidelines for contributing developers for an explanation of how to get set up and the process you'll follow.
Once you are ready to contribute, a good place to start is to take a look at the good first issues and help wanted issues on GitHub.
You can help us improve the Kedro documentation online. Send us feedback as a GitHub issue or start a documentation discussion on GitHub.
You are also welcome to make a raise a PR with a bug fix or addition to the documentation. First read the guide Contribute to the Kedro documentation.