Docs: Improve documentation on standard communication channels
More information about connection on IRC will hopefully help new contributors.
This commit is contained in:
parent
f686002a8e
commit
30d1a0ae37
2 changed files with 18 additions and 6 deletions
|
@ -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
|
||||
--------------------
|
||||
|
||||
|
|
|
@ -33,12 +33,6 @@ regularly to indicate new official, stable release versions of Bitcoin Core.
|
|||
|
||||
The contribution workflow is described in [CONTRIBUTING.md](CONTRIBUTING.md).
|
||||
|
||||
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.
|
||||
|
||||
Developer IRC can be found on Freenode at #bitcoin-core-dev.
|
||||
|
||||
Testing
|
||||
-------
|
||||
|
||||
|
|
Loading…
Reference in a new issue