Skip to content

Latest commit

 

History

History
44 lines (27 loc) · 3.04 KB

GOVERNANCE.md

File metadata and controls

44 lines (27 loc) · 3.04 KB

KubeArmor Governance

This document outlines governance for KubeArmor and its related projects unless specifically outlined.

Code of Conduct

In order to promote an open, inclusive, welcoming environment, KubeArmor has adopted a code of conduct. It is the expectation that all participants have reviewed this document.

Maintainers

Maintainers for KubeArmor demonstrate a long-standing commitment to the success, growth, and viability of KubeArmor, its subprojects and dependencies. Maintainers share a responsibility in the project's success and their responsibilities are not limited to code contribution but may also include administrative and outreach responsibilities. Maintainers are nominated and selected on an as-needed basis to reflect the growth of the project and the community at large from amongst the project's contributors and subject matter experts. Maintainers need not have write access to the repo. Maintainers are expected to:

  • Maintaining the mission, vision, values, and scope of the project
  • Assure that the KubeArmor project is of the highest quality, relevancy, and value to the community
  • Refining the governance as needed
  • Making project level decisions
  • Controlling access to KubeArmor assets such as source repositories, hosting, project calendars
  • Addressing Code of Conduct violations
  • Deciding what sub-groups are part of the KubeArmor project
  • Overseeing the resolution and disclosure of security issues

Becoming a Maintainer

On successful merge of a significant pull request from a Contributor any current maintainer can reach to the author behind the pull request and ask them if they are willing to become a KubeArmor maintainer. Once nominated, and the individual accepts, the existing Maintainers will vote and if a 2/3 majority is reached, that individual will become a Maintainer.

Contributor

Contributors are individuals that write, commit, and/or review code, documentation, or provide technical expertise to the KubeArmor project. Any individual that has the demonstrated expertise, interest and dedication to the success of the project may become a contributor.

How to Contribute

For specific guidance on practical contribution steps for KubeArmor or any of its related projects, please review the CONTRIBUTING.md outline.

DCO and Licenses

The following licenses and contributor agreements will be used for KubeArmor projects:

Credits

This policy was created with guidance from documentation provided by Containerd, CoreDNS and Helm