aboutsummaryrefslogtreecommitdiff
path: root/CONTRIBUTING.md
diff options
context:
space:
mode:
authorJim Posen <jimpo@coinbase.com>2018-03-22 12:56:17 -0700
committerJim Posen <jimpo@coinbase.com>2018-03-22 12:58:57 -0700
commit30d1a0ae37964f71812ac016275510faadbf41f3 (patch)
treeb41b8c12fd07909f2fabb3617dce23a8d8e1f1aa /CONTRIBUTING.md
parentf686002a8eba820a40ac2f34a6e8f57b2b5cc54c (diff)
Docs: Improve documentation on standard communication channels
More information about connection on IRC will hopefully help new contributors.
Diffstat (limited to 'CONTRIBUTING.md')
-rw-r--r--CONTRIBUTING.md18
1 files changed, 18 insertions, 0 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 8381bd2448..ea475f8cfb 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -15,6 +15,24 @@ merging pull requests as well as a "lead maintainer" who is responsible for the
release cycle, overall merging, moderation and appointment of maintainers.
+Communication Channels
+----------------------
+
+Most communication about Bitcoin Core development happens on IRC, in the
+#bitcoin-core-dev channel on Freenode. The easiest way to participate on IRC is
+with the web client, [webchat.freenode.net](https://webchat.freenode.net/). Chat
+history logs can be found
+on [botbot.me](https://botbot.me/freenode/bitcoin-core-dev/).
+
+Discussion about code base improvements happens in GitHub issues and on pull
+requests.
+
+The developer
+[mailing list](https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev)
+should be used to discuss complicated or controversial changes before working on
+a patch set.
+
+
Contributor Workflow
--------------------