From 9bad9a4ceee667dec6ea2cb59161dfe34b458560 Mon Sep 17 00:00:00 2001 From: Quentin Machu Date: Mon, 18 Jul 2016 18:51:08 +0200 Subject: [PATCH] Add initial license/contribution files --- AUTHORS | 2 + CONTRIBUTING.md | 62 +++++++++++++++ DCO | 36 +++++++++ LICENSE | 201 ++++++++++++++++++++++++++++++++++++++++++++++++ NOTICE | 5 ++ README.md | 8 ++ 6 files changed, 314 insertions(+) create mode 100644 AUTHORS create mode 100644 CONTRIBUTING.md create mode 100644 DCO create mode 100644 LICENSE create mode 100644 NOTICE create mode 100644 README.md diff --git a/AUTHORS b/AUTHORS new file mode 100644 index 0000000..cf49d87 --- /dev/null +++ b/AUTHORS @@ -0,0 +1,2 @@ +PiotrProkop +Quentin Machu diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 100644 index 0000000..a7668ca --- /dev/null +++ b/CONTRIBUTING.md @@ -0,0 +1,62 @@ +# How to Contribute + +This project is [Apache 2.0 licensed](LICENSE) and accept 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. + +# Certificate of Origin + +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 [DCO](DCO) file for details. + +## Getting Started + +- Fork the repository on GitHub +- Read the [README](README.md) for build and test instructions +- Play with the project, submit bugs, submit patches! + +## Contribution Flow + +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 tests pass, and add any new tests as appropriate. +- Submit a pull request to the original repository. + +Thanks for your contributions! + +### Format of the Commit Message + +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: + +``` +: + + + +