* Small typos and clarification in contributing guide
* cross-link contributing guide and issue/pr template
* drop GOPATH mention
* don't include merge commits in PRs
* make high review delays explicit
* explicitly ask for link to current PR in changelog template
* clarify docs changes
* use bug template as authoritative place'
* consolidate development information in 090_participating
Also move issue / PR creation relevant information into contributing.md.
* clarify meaning of assigning to a pull request
* link to minimum go version
* minor typos
* golanci-lint is always applied in full
* add micro summary
* more typo fixes
* always run golangci-lint
* Simplify issue/pr template
* Fix IRC webchat link
* Move security policy to SECURITY.md
* address review comments
The basics around how to format commits and PR settings are primarily
relevant when opening a PR for the first time. But for repeated
contributors it is tedious to always tick those checkboxes.
Co-authored-by: rawtaz <rawtaz@users.noreply.github.com>