Project: rkt (Runtime / Container Runtime)
File: CONTRIBUTING.md

rkt is and accepts contributions via GitHub pull requests. This document outlines some of the conventions on development workflow, commit message formatting, contact points and other resources to make it easier to get your contribution accepted. By contributing to this project you agree to the Developer Certificate of Origin (DCO). This document was created by the Linux Kernel community and is a simple statement that you, as a contributor, have the legal right to make the contribution. See the file for details. The project has a mailing list and two discussion channels in IRC: Email: IRC: # on freenode.org, for general discussion IRC: # on freenode.org, for development discussion Please avoid emailing maintainers found in the MAINTAINERS file directly. They are very busy and read the mailing lists. Fork the repository on GitHub Read for build and for test instructions Play with the project, submit bugs, submit patches! This is a rough outline of what a contributor's workflow looks like: Create a topic branch from where you want to base your work (usually master). Make commits of logical units. Make sure your commit messages are in the proper format (see below). Push your changes to a topic branch in your fork of the repository. Make sure the pass, and add any new tests as appropriate. Submit a pull request to the original repository. Submit a comment with the sole content "@reviewer PTAL" (please take a look) in GitHub and replace "@reviewer" with the correct recipient. When addressing pull request review comments add new commits to the existing pull request or, if the added commits are about the same size as the previous commits, squash them into the existing commits. Once your PR is labelled as "reviewed/lgtm" squash the addressed commits in one commit. If your PR addresses multiple subsystems reorganize your PR and create multiple commits per subsystem. Your contribution is ready to be

Thanks for your contributions! Go style in the rkt project essentially just means following the upstream conventions: - It's recommended to set a save hook in your editor of choice that runs `goimports` against your code. Project docs should follow the [Documentation style and formatting guide](https://github.com/coreos/docs/tree/master/STYLE.md). Thank you for documenting! We follow a rough convention for commit messages that is designed to answer two questions: what changed and why. The subject line should feature the what and the body of the commit should describe the why. ``` scripts: add the test-cluster command this uses tmux to setup a test cluster that you can easily kill and start for debugging. Fixes #38 ``` The format can be described more formally as follows: ``` <subsystem>: <what changed> <BLANK LINE> <why this change was made> <BLANK LINE> <footer> ``` The first line is the subject and should be no longer than 70 characters, the second line is always blank, and other lines should be wrapped at 80 characters. This allows the message to be easier to read on GitHub as well as in various git tools. The pull request title and the first paragraph of the pull request description is being used to generate the changelog of the next release. The convention follows the same rules as for commit messages. The PR title reflects the what and the first paragraph of the PR description reflects the why. In most cases one can reuse the commit title as the PR title and the commit messages as the PR description for the PR. If your PR includes more commits spanning multiple subsystems one should change the PR title and the first paragraph of the PR description to reflect a summary of all changes involved. A large PR must be split into multiple commits, each with clear commit messages. Intermediate commits should compile and pass tests. Exceptions to non-compilable must have a valid reason, i.e. dependency bumps. Do not add entries in the changelog yourself. They will be overwritten when creating a new release.