Contribution Guidelines

    This section has information on how to contribute to Nebraska. It assumes you have cloned this repository (or your own Github fork).

    Any contributions to the project are accepted under the terms of the project’s license ( AGPL v3 ).

    Code of Conduct

    Please refer to the Kinvolk Code of Conduct .

    Development practices

    The Nebraska project follows the Kinvolk Contribution Guidelines which promotes good and consistent contribution practises across Kinvolk’s projects. Before start contributing, and in addition to this section, please read those guidelines.

    Filing an issue or feature request

    Please use the project’s issue tracker for filing any bugs you find or features you think are useful.

    Complex contributions

    If you have a complex contribution in mind (meaning changes in the architecture or a lot of LOC changed), it is advisable to first file a Github issue and discuss the implementation with the project’s maintainers.

    Coding style

    The coding style for backend and frontend should be consistent. For helping and verifying that, we have go and js linters.

    The backend linter runs automatically when using the make backend command. For linting the frontend, use make frontend-lint.

    The linters are also run in the CI system, so any PRs you create will be tested for compliance with the coding style.

    To speed up a review from the project’s maintainers, please make sure that the CI checks are passing for your PR.

    Commit guidelines

    For the general guidelines on making PRs/commits easier to review, please check out Kinvolk’s contribution guidelines on git .