-
Pick an issue to work on. For first-time contributors, the best would be to pick an issue tagged good-first-issue.
-
If you feel adventurous and would like to take a challenging issue, we would love to have you contribute on issues tagged help-wanted.
-
There is a Contribution Guide that explains how to create a fork and raise PR on GitHub.
-
If the issue involves code changes you need to install development env using this Development Guide.
Contributions are not necessarily in the form of code changes. KubeArmor community can benefit from contributions such as:
-
Users are welcome to contribute policy-templates for their workloads. The workloads have to be generic enough such that it benefits the wider community. E.g., if someone brings up a system policy restricting access to nginx process that would be useful in multiple scenarios and for the wider community then come up with a policy-template that is specific to your proprietary application.
-
Blogs
a. Explain The use of KubeArmor-Client's features (KVMService, Event Auditor, Visibility, etc)
b. Describe How to use KubeArmor-Client to protect your workload with specific use-cases you may have. Please do not shy away from getting as technical as you can.
c. Put your topic of interest
-
Feedback to the community
Just helping advance any discussion on KubeArmor Slack, Community meetings, office hours will make a big difference.
-
Talking about KubeArmor-Client in meetups
We would certainly encourage users or devs of KubeArmor to talk about it in open/closed forums. The community can help with logistics such as compiling/feedback on slide-decks, technical diagrams, etc.