github.com/robstrong/etcd@v0.4.4-0.20140620001034-fb32a999a6bb/CONTRIBUTING.md (about) 1 # How to contribute 2 3 etcd is Apache 2.0 licensed and accepts contributions via Github pull requests. This document outlines some of the conventions on commit message formatting, contact points for developers and other resources to make getting your contribution into etcd easier. 4 5 # Email and chat 6 7 - Email: [etcd-dev](https://groups.google.com/forum/?hl=en#!forum/etcd-dev) 8 - IRC: #[coreos](irc://irc.freenode.org:6667/#coreos) IRC channel on freenode.org 9 10 ## Getting started 11 12 - Fork the repository on GitHub 13 - Read the README.md for build instructions 14 15 ## Contribution flow 16 17 This is a rough outline of what a contributor's workflow looks like: 18 19 - Create a topic branch from where you want to base your work. This is usually master. 20 - Make commits of logical units. 21 - Make sure your commit messages are in the proper format (see below). 22 - Push your changes to a topic branch in your fork of the repository. 23 - Submit a pull request to coreos/etcd. 24 25 Thanks for your contributions! 26 27 ### Code style 28 29 The coding style suggested by the Golang community is used in etcd. See [style doc](https://code.google.com/p/go-wiki/wiki/Style) for details. 30 31 Please follow this style to make etcd easy to review, maintain and develop. 32 33 ### Format of the commit message 34 35 etcd follows a rough convention for commit messages borrowed from Angularjs. This is an example of a commit: 36 37 ``` 38 feat(scripts/test-cluster): add a cluster test command 39 40 this uses tmux to setup a test cluster that you can easily kill and 41 start for debugging. 42 ``` 43 44 The format can be more formally described as follows: 45 46 ``` 47 <type>(<scope>): <subject> 48 <BLANK LINE> 49 <body> 50 <BLANK LINE> 51 <footer> 52 ``` 53 54 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 55 in various git tools. 56 57 ### Subject line 58 59 The subject line contains a succinct description of the change. 60 61 ### Allowed <type>s 62 - feat (feature) 63 - fix (bug fix) 64 - docs (documentation) 65 - style (formatting, missing semi colons, …) 66 - refactor 67 - test (when adding missing tests) 68 - chore (maintain) 69 70 ### Allowed <scope>s 71 72 Scopes can be anything specifying the place of the commit change within the repository. For example, "store", "API", etc. 73 74 ### More details on commits 75 76 For more details see the [angularjs commit style guide](https://docs.google.com/a/coreos.com/document/d/1QrDFcIiPjSLDn3EL15IJygNPiHORgU1_OOAqWjiDU5Y/edit#).