Skip to content

Latest commit

 

History

History
48 lines (33 loc) · 4.02 KB

contributing.md

File metadata and controls

48 lines (33 loc) · 4.02 KB
Raw

Contributing

This project welcomes contributions and suggestions.

What do I need to know to help?

Akri utilizes a variety of technologies, and different background knowledge is more or less useful depending on what you are interested in contributing.

  • Some understanding of Kubernetes and Helm is needed to deploy and use Akri.
  • The Akri Controller and Agent are written in the Rust programming language.
  • All of Akri's components run on Linux, so you will need to set up an Ubuntu VM if you do not already have a Linux environment.
  • Sample brokers and end applications can be written in any language and are individually containerized.
  • We use Docker to build our containers.

How do I get started developing?

Contributions can be made by forking the repository and creating a pull request. Ideally, every pull request should have a corresponding issue that it is resolving. Each pull request will kick off a set of CI builds to validate that:

  • the code adheres to standard Rust formatting (cargo fmt)
  • the code builds properly (cargo build)
  • the code is free of common mistakes (cargo clippy)
  • the Akri tests all pass (cargo test)
  • the inline documentation builds (cargo doc)

See the Development documentation for more information on how to set up your environment and build Akri components locally.

Versioning

We follow the SymVer versioning strategy: [MAJOR].[MINOR].[PATCH]. Our current version can be found in ./version.txt.

  • For non-breaking bug fixes and small code changes, [PATCH] should be incremented. This can be accomplished by running version.sh -u -p
  • For non-breaking feature changes, [MINOR] should be incremented. This can be accomplished by running version.sh -u -n
  • For major and/or breaking changes, [MAJOR] should be incremented. This can be accomplished by running version.sh -u -m

To ensure that all product versioning is consistent, our CI builds will execute version.sh -c to check all known instances of version in our YAML, TOML, and code. This will also check to make sure that version.txt has been changed. If a pull request is needed where the version should not be changed, include [SAME VERSION] in the pull request title.

PR title flags

Akri's workflows check for three flags in the titles of PRs in order to decide whether to execute certain checks.

The version check workflow will run, ensuring you have increased the version number, unless you (A) only change a a file that is on an ignored path of the workflow, such as all *.md files OR (B) specify the [SAME VERSION] flag. Use this flag if your change will trigger the workflow and the version should not be changed by your PR. The flag will cause the check to automatically succeed.

Akri has some intermediate containers that decrease the build time of the more frequently built final containers. These intermediate builds are long running and should only be run when absolutely needed. If your PR triggers a workflow to build them, you will see the workflow fail and get a message that requests that you add a tag to your PR to either allow them to build ([ALLOW INTERMEDIATE BUILDS]) or ([IGNORE INTERMEDIATE BUILDS]).

Please add any appropriate flags to the end of your PR title.

CLA

Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

Code of Conduct

Participation in the Akri community is governed by the Code of Conduct.