Decide on community communication channels

[cornelius]

We need to decide which communication channels we want to use in the various parts of the community, especially when it includes people not part of the core team.

Part of that is deciding on if we want to prefer open source software over services which we couldn't run ourselves.

Consequences of the decision such as what needs to be setup need to be documented and follow up actions created.

A starting point could be to keep as much communication as possible on GitHub so that it's in one place and can be managed without moving between channels, and use Slack for chat for the beginning as it's the most advanced tool, it's used by a number of high-profile open source communities such as Kubernetes, and we already use it.

[scravy]

Personally I would be a huge fan of having a dedicated mailing list, one where also people like @gfanti and @amiller would be on.

Edit: Any anyone who subscribes obviously ;-)

[Gnappuraz]

Anything but please no IRC as main channel XD that thing should be dead!

[scravy]

Sometimes, just sometimes, I would prefer IRC over Slack; or any other open protocol over that proprietary-hipster-startup-sometimes-not-even-working-Slack.

Edit: Also I really like email.

[kostyantyn]

Opinion about real-time vs asynchronous conversions https://dave.cheney.net/2017/04/11/why-slack-is-inappropriate-for-open-source-communications

[kostyantyn]

Opinion about real-time vs asynchronous conversion channels https://dave.cheney.net/2017/04/11/why-slack-is-inappropriate-for-open-source-communications

[scravy]

@kostyantyn I agree with that so much. It is okay for internal communications, but that's it. Also the fact that it's proprietary and you have to pay to unlock your history is quite unfortunate for the purpose of open source.

[Gnappuraz]

@kostyantyn totally agree, I would not use Slack if not for internal communication. I don't think we necessarily need a synched communication channel, I think we can simply use some asynch one. It could be a forum like bitcointalk that is very organized and easily accessible by anybody, linkable and persistent (what I don't like of forums is that they give mods and admins full power to censor and ban users). Mailing lists are also good I think, but they require a bit of experience to be used and not mess up, so we could keep them for more technical topics. I don't like IRC simply because you have to rely on bots to have the history and there is no way to keep the conversation organized, if you check the bitcoin's one is all over the place, they discuss a bunch of different stuff, and you have ppl asking for completely different things in the same place... Is a bit of a mess imho.

[scravy]

matrix.org and riot.im?

[Gnappuraz]

matrix.org and riot.im?

Nice but I would stay away from any IM system. At the end is pretty much asynch anyway unless some of us really wants to be interrupted so often, and the fact ppl know they have to wait to get an answer make them think more before writing while with IM this would not be the case.

[scravy]

http://asyncmanifesto.org/

Mailing list, good enough :-P

[kostyantyn]

WDYS about Reddit? Do we actually want to create and manage the subreddit?

[scravy]

I for one am no huge fan of reddit. Never posted there. I would have liked to have clicked THE BUTTON, but I didn't.

[Gnappuraz]

I think reddit is mostly used nowadays for community management not real discussions... also looking at the reddit of other coins is quite a mess... Is more about coin value and shilling/investments than tech discussions...