I added IRC link README.md, now it is easier to enter the IRC.
Add IRC link to README.md #8232
pull ghost wants to merge 2 commits into bitcoin:master from changing 2 files +1 −2-
ghost commented at 9:21 AM on June 21, 2016: none
-
Add Freenode Link 376b0f0d28
-
jonasschnelli commented at 9:38 AM on June 21, 2016: contributor
Not sure if we should add a webchat link. It could lead to users joining the dev channel when the have end user problems...
-
paveljanik commented at 9:41 AM on June 21, 2016: contributor
Concept NACK
No webchat links please.
-
laanwj commented at 9:44 AM on June 21, 2016: member
On one hand it is nice to make it easy to join the chat, on the other hand one of the reasons that we moved from
bitcoin-devtobitcoin-core-devis that the former was getting too noisy. The new IRC channel is for development-related talk only, not for questions or support or ancillary discussion about bitcoin or bitcoin core. End-users should join#bitcoinnot#bitcoin-core-dev.So tend to agree with @jonasschnelli's sentiment.
-
in README.md:None in 376b0f0d28 outdated
36 | @@ -37,7 +37,7 @@ The developer [mailing list](https://lists.linuxfoundation.org/mailman/listinfo/ 37 | should be used to discuss complicated or controversial changes before working 38 | on a patch set. 39 | 40 | -Developer IRC can be found on Freenode at #bitcoin-core-dev. 41 | +Developer IRC can be found on Freenode at [#bitcoin-core-dev](https://webchat.freenode.net/?channels=#bitcoin-core-dev).
MarcoFalke commented at 9:47 AM on June 21, 2016:I am not convinced we should mention the dev chat in the readme...
We already link to CONTRIBUTING.md just three lines above. Do you mind to move the
Developer IRC can be found on Freenode at #bitcoin-core-dev.to CONTRIBUTING.md ?
laanwj commented at 9:50 AM on June 21, 2016:Sounds good to me.
MarcoFalke added the label Docs and Output on Jun 21, 2016Move Developer IRC link to CONTRIBUTING.md 5f5d386246ghost commented at 1:44 PM on June 21, 2016: noneConcept NACK No webchat links please. @paveljanik NACK rejected
NACK means "I disagree this should be merged", and must be accompanied by sound technical justification. NACKs without accompanying reasoning may be disregarded;
You had to provide technical reasons. Mine is a document, so it is impossible to provide "technical" justification.
laanwj commented at 1:51 PM on June 21, 2016: memberWith the move to CONTRIBUTORS I think it's okay.
jonasschnelli commented at 2:07 PM on June 21, 2016: contributorNot sure about this change.... Moving the IRC channel away from the mailing list link and adding a webchat URL (IMO devs should not use webchats) looks after a step backward.
MarcoFalke commented at 2:23 PM on June 21, 2016: memberMeh, when it seems unlikely to get support, better leave it as is for now.
paveljanik commented at 5:45 PM on June 21, 2016: contributorI think that moving link to #bitcoin-dev-core to CONTRIBUTING.md is good. Let's keep it (without webchat link).
MarcoFalke commented at 5:55 PM on June 21, 2016: memberSo with the same reason we could move the mailing list to CONTRIBUTING.md?
Anyway, why is the
bitcoin-core-devmailing list mentioned nowhere?ghost commented at 8:41 AM on June 22, 2016: noneHow about moving it into a code block? Developer IRC can be found on Freenode at
#bitcoin-core-dev.laanwj commented at 2:21 PM on June 27, 2016: memberThis is seemingly too controversial for such a simple change. Also seems that the OP deleted their account. Closing.
laanwj closed this on Jun 27, 2016MarcoFalke locked this on Sep 8, 2021ContributorsLabels
This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-04-17 15:15 UTC
More mirrored repositories can be found on mirror.b10c.me