Overview

To set a strong foundation, this section outlines how we, the community and members of Hanzo KMS, should approach the development and contribution process.

Hanzo KMS has two major code-bases. One for the platform code, and one for SDKs. The contribution process has some key differences between the two, so we've split the documentation into two sections:

We are building an inclusive community, and this means adhering to the Code of Conduct.

Bug reports help make Hanzo KMS a better experience for everyone. When you report a bug, a template will be created automatically containing information we'd like to know.

Before raising a new issue, please search existing ones to make sure you're not creating a duplicate.

You can start by browsing through our list of issues or adding your own that improves on the platform experience. Once you've decided on an issue, leave a comment and wait to get approved; this helps avoid multiple people working on the same issue.

If you're ever in doubt about whether or not a proposed feature aligns with Hanzo KMS as a whole, feel free to raise an issue about it and we'll get back to you promptly.

Anyone can contribute code to Hanzo KMS. To get started, check out the local development guide for the platform:

Most of Hanzo KMS's code is under the MIT license, though some paid feature restrictions are covered by a proprietary license.

Any third party components incorporated into our code are licensed under the original license provided by the applicable component owner.