github.com/macb/etcd@v0.3.1-0.20140227003422-a60481c6b1a0/CONTRIBUTING.md (about) 1 # How to contribute 2 3 etcd is open source, Apache 2.0 licensed and accepts contributions via Github pull requests. 4 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. 5 6 # Email and chat 7 8 For simplicity etcd discussions happen on coreos-dev and in #coreos-dev. 9 As the community grows we will move to a dedicated mailing list and IRC channel. 10 11 - Email: [coreos-dev](https://groups.google.com/forum/#!forum/coreos-dev) 12 - IRC: #[coreos](irc://irc.freenode.org:6667/#coreos) IRC channel on freenode.org 13 14 ## Getting Started 15 16 - Fork the repository on GitHub 17 - Read the README.md for build instructions 18 19 ## Contribution flow 20 21 This is a rough outline of what a contributor's workflow looks like: 22 23 - Create a topic branch from where you want to base your work. This is usually master. 24 - Make commits of logical units. 25 - Make sure your commit messages are in the proper format, see below 26 - Push your changes to a topic branch in your fork of the repository. 27 - Submit a pull request to coreos/etcd 28 29 Thanks for you contributions! 30 31 ### Format of the commit message 32 33 etcd follow a rough convention for commit messages borrowed from Angularjs. 34 This is an example of a commit: 35 36 ``` 37 feat(scripts/test-cluster): add a cluster test command 38 39 this uses tmux to setup a test cluster that you can easily kill and 40 start for debugging. 41 ``` 42 43 To make it more formal it looks something like this: 44 45 ``` 46 <type>(<scope>): <subject> 47 <BLANK LINE> 48 <body> 49 <BLANK LINE> 50 <footer> 51 ``` 52 53 The first line is the subject and should not be longer than 70 characters, the second line is always blank and other lines should be wrapped at 80 characters. 54 This allows the message to be easier to read on github as well as in various git tools. 55 56 ### Subject line 57 58 The subject line contains succinct description of the change. 59 60 ### Allowed <type> 61 - feat (feature) 62 - fix (bug fix) 63 - docs (documentation) 64 - style (formatting, missing semi colons, …) 65 - refactor 66 - test (when adding missing tests) 67 - chore (maintain) 68 69 ### Allowed <scope> 70 71 Scopes could be anything specifying place of the commit change. For example store, api, etc. 72 73 ### More details on commits 74 75 For more details see the [angularjs commit style guide](https://docs.google.com/a/coreos.com/document/d/1QrDFcIiPjSLDn3EL15IJygNPiHORgU1_OOAqWjiDU5Y/edit#).