Stryker: discord for stryker

[kmdrGroch]

We can make some discord for easier comunication with each other. Channels like: development for each stryker, website, and help: for live help.

[simondel]

The most important thing for me is to reduce the amount of input channels. Right now we have:

• GitHub
• Gitter
• Twitter
• Private email
• Work email
• Work Slack (between devs and users/fans inside our company)
• WhatsApp (directly between devs)

[kmdrGroch]

roger that @simondel. Closing then :)

[simondel]

That doesn't mean that this is not a good idea :) I just would not like to have everything that we have now _and_ also have Discord.

Do you think Discord could replace some input channels that we have right now?

[nicojs]

We could also move our slack to the public.

Problem with slack and discord is that they are volatile. So if we help someone or make some decisions, it is quickly forgotten.

[nicojs]

In contrast to those solutions, we could point people to stack overflow for questions. There already is one question out there: https://stackoverflow.com/questions/44023041/stryker-mutation-tesing-with-es6-files

The upside is that it is very public. It directly helps others. By far the best place for questions I think. @simondel what do you think?

[simondel]

Also sounds good @nicojs, however right now we often need multiple comments to resolve a question/problem. Stack Overflow doesn't really work for this use case in my opinion.

[nicojs]

True. But those questions can easily be answered with: "please open an issue". Once the issue is resolved we can update the answer / create a new answer.

That would help document the questions and provide help for people on places they already know.

[nicojs]

This is where comments are used for in stack overflow all the time. I also think that people can judge this for themselves. If it is a technical error they see, they'll probably report it as a bug. If it is a functional warning/error they don't understand, they'll open a question.

In short:

• I think people can make the distinction
• If someone makes a wrong assumption, no problemo, we can point him to the correct one

In any case, I think it is worth a try, don't you?

[kmdrGroch]

And after problem is solved we can add it to FAQ :3

[legopiraat]

I've been thinking about this a lot as well, I agree with Simon that there are many input channels for Stryker. Maybe we should move from our internal slack and work email to an overall StrykerDevTeam gitter channel so we can eliminate 2 input channels? Not sure how the company will react to this.

[simondel]

We're closing this issue for now.