Non-code Contribution Guide

You can pick up any of the following ways you’re interested to contribute.

If you’re using KubeVela, the easiest thing to contribute is to credit the community.
If you are interested, you can also write a kubevela.io blog to tell more about the use case.
You can also contribute to KubeVela Official Samples.

Before submitting a new issue, try to make sure someone hasn’t already reported the problem. Look through the existing issues for similar issues.

Report a bug by submitting a bug report. Make sure that you provide as much information as possible on how to reproduce the bug.

Follow the issue template and add additional information that will help us replicate the problem.

If you believe you’ve found a security vulnerability, please read our security policy for more details.

If you have an idea to improve KubeVela, submit an feature request.

If you don’t have the knowledge or time to code, consider helping with issue triage. The community will thank you for saving them time by spending some of yours.

Read more about the ways you can Triage issues.

If you have a question and you can’t find the answer in the documentation, the next step is to ask it on the github discussion.

It’s important to us to help these users, and we’d love your help. You can help other KubeVela users by answering their questions.

Contributing to the docs needs to learn some knowledge about how to make a pull request to Github, I think this won’t be hard if you follow the guide.

kubevela.io Developer Guide

For more ways to contribute, check out the Open Source Guides.

Last updated on Nov 1, 2022 by Tianxin Dong