Merge PR #102: Remove clog config

.clog.yaml

@@ -1,10 +0,0 @@
-sections:
-  breaking: Breaking Changes
-  features: Features
-  improvements: Improvements
-  bugfixes: Bugfixes
-
-tags:
-  - gaiad
-  - gaiacli
-  - rest

CHANGELOG.md

@@ -9,6 +9,17 @@ The latest version comes first.
 The release date of each version is displayed.
 Mention whether you follow Semantic Versioning.
 
+Usage:
+
+Change log entries are to be added to the Unreleased section under the
+appropriate stanza (see below). Each entry should ideally include a tag and
+the Github issue reference in the following format:
+
+* (<tag>) \#<issue-number> message
+
+The issue numbers will later be link-ified during the release process so you do
+not have to worry about including a link manually, but you can if you wish.
+
 Types of changes (Stanzas):
 
 "Features" for new features.
@@ -24,7 +35,7 @@ Ref: https://keepachangelog.com/en/1.0.0/
 
 ## [Unreleased]
 
-## [1.0.0] - 2019-08-13
+## [v1.0.0] - 2019-08-13
 
 ### Bug Fixes
 
@@ -82,4 +93,4 @@ Ref: https://keepachangelog.com/en/1.0.0/
 <!-- Release links -->
 
 [Unreleased]: https://github.com/cosmos/gaia/compare/v1.0.0...HEAD
-[1.0.0]: https://github.com/cosmos/gaia/releases/tag/v1.0.0
+[v1.0.0]: https://github.com/cosmos/gaia/releases/tag/v1.0.0

CONTRIBUTING.md

@@ -21,24 +21,27 @@ Contributing to this repo can mean many things such as participated in
 discussion or proposing code changes. To ensure a smooth workflow for all
 contributors, the general procedure for contributing has been established:
 
-  1. either [open](https://github.com/cosmos/gaia/issues/new/choose) or
-     [find](https://github.com/cosmos/gaia/issues) an issue you'd like to help with,
-  2. participate in thoughtful discussion on that issue,
-  3. if you would then like to contribute code:
-     1. if a the issue is a proposal, ensure that the proposal has been accepted,
-     2. ensure that nobody else has already begun working on this issue, if they have
-       make sure to contact them to collaborate,
-     3. if nobody has been assigned the issue and you would like to work on it
-       make a comment on the issue to inform the community of your intentions
-       to begin work,
-     4. follow standard github best practices: fork the repo, branch from the
-       top of `master`, make some commits, and submit a PR to `master`,
-         - for core developers working within the Gaia repo, 
-	 to ensure a clear ownership of branches, branches must be named with the convention `yourname/{issue-}feature-name`.  
-     5. submit your PR early and make sure it's opened as a `Draft`, even if it's
-        incomplete, this indicates to the community you're working on something and
-        allows them to provide comments early in the development process. When the code
-        is complete it should be marked as ready-for-review using Github's `Mark Ready` feature.
+1. Either [open](https://github.com/cosmos/gaia/issues/new/choose) or
+   [find](https://github.com/cosmos/gaia/issues) an issue you'd like to help with
+2. Participate in thoughtful discussion on that issue
+3. If you would like to contribute:
+   1. If a the issue is a proposal, ensure that the proposal has been accepted
+   2. Ensure that nobody else has already begun working on this issue, if they have
+      make sure to contact them to collaborate
+   3. If nobody has been assigned the issue and you would like to work on it
+      make a comment on the issue to inform the community of your intentions
+      to begin work
+   4. Follow standard Github best practices: fork the repo, branch from the
+      HEAD of `master`, make some commits, and submit a PR to `master`
+      - For core developers working within the cosmos-sdk repo, to ensure a clear
+      ownership of branches, branches must be named with the convention
+      `{moniker}/{issue#}-branch-name`
+   5. Be sure to submit the PR in `Draft` mode submit your PR early, even if
+      it's incomplete as this indicates to the community you're working on
+      something and allows them to provide comments early in the development process
+   6. When the code is complete it can be marked `Ready for Review`
+   7. Be sure to include a relevant change log entry in the `Unreleased` section
+      of `CHANGELOG.md` (see file for log format)
 
 Note that for very small or blatantly obvious problems (such as typos) it is
 not required to an open issue to submit a PR, but be aware that for more complex