Welcome to the SAKK project! We love feedback and contributions, and this guide outlines how one can contribute to SAKK.
One of the easiest ways to contribute is to start discussing open issues in the comments below them. Check out SAKK Issues section, react with emoji, and comment:
For example, you can find issues labeled with roadmap and let us know in the comments what you think about the proposed features, which of them you consider the most important and why.
If you've found something in the repo that can be improved, check issues to see if someone has already reported it. If it is something new, open a new issue and describe it in free form. We'll see it and discuss it with you in the comments.
If you're looking to start contributing to current tasks, check out issues labeled good first issues.
Ready to make a change? Fork SAKK repo, clone it, make your changes in a separate branch, push it to GitHub and open a PR. The process is pretty standard. You can use this PR contributing guide from SAKK's umbrella repository:
We are looking for feedback and participation in our Roadmap. Please share your thoughts, issues you currently struggle with while serving and managing Kubeflow on EKS at scale, and ideas on how SAKK can help your ML/DevOps teams to address them. Please discuss our Roadmap with us on Slack or under the issues tagged roadmap.
If you have any questions, comments, ideas, or need help, come to our Slack to discuss it:
We will be happy if you can share this repository or promote it in any other way - on GitHub, social networks, blog posts, etc. The easiest way is to press the watch, star, and fork buttons or share a link on Twitter, Facebook, LinkedIn. If you're writing a relevant blog post, include information about SAKK and share a link. If you're working on more elaborate forms of relevant content and want to share about SAKK, please contact us to discuss how we can help. We would be thrilled to amplify your voice.
By contributing to this project you agree to the Developer Certificate of Origin (DCO). This document was created by the Linux Kernel community and is a simple statement that you, as a contributor, have the legal right to make the contribution. No action from you is required, but it's recommended to read DCO for details before you start contributing code to SAKK.
SAKK uses Slack as a primary communication channel. Just click the badge, log into Slack, and write something on any of our channels. Contributors, existing and potential, can use the #contribute channel in our Slack.
At SAKK, we recognize the work, effort, and creativity of open-source contributors and strive to create an inclusive community environment based on treating every participant with respect. Please see our Code of Conduct and adhere to it in your communication: