R4R: Contributing Guidelines advocate early discussion b4 coding

[rigelrozanski]

Based on this PR #1792 which was opened before adequate discussion had taken place, unfortunately the contributing docs didn't indicate a procedure which includes discussion in an issue before coding

• Updated all relevant documentation (docs/)
• [n/a] Updated all relevant code comments
• [n/a] Wrote tests
• [n/a] Added entries in PENDING.md
• [n/a] Updated cmd/gaia and examples/

---

For Admin Use:

• Added appropriate labels to PR (ex. wip, ready-for-review, docs)
• Reviewers Assigned
• Squashed all commits, uses message "Merge pull request #XYZ: [title]" (coding standards)

[ValarDragon]

The numbered list is a great idea as well! It's way easier to follow that.

[ValarDragon]

extra and

[rigelrozanski]

addressed

[codecov]

Codecov Report

Merging #1796 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop    #1796   +/-   ##
========================================
  Coverage    63.46%   63.46%           
========================================
  Files          117      117           
  Lines         6914     6914           
========================================
  Hits          4388     4388           
  Misses        2270     2270           
  Partials       256      256

[cwgoes]

This looks good, but it's starting to get rather long - maybe worth adding a "tl;dr" summary?

[rigelrozanski]

Thinking about this more... it might be best to do something like delete all the other sections besides the first section and include links to those sections in the first sections (this sections would likely go into tendermint/coding)