New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Discord #345

Merged
merged 9 commits into from Aug 28, 2018

Conversation

@MelSumner
Contributor

MelSumner commented Jul 11, 2018

Rendered

MelSumner added some commits Jul 11, 2018

@rtablada

I think that there's some good stuff and in general the outlines of onboarding and channel organization are 👍 to me.

There's some unknown questions and drawbacks that I commented.

Show outdated Hide outdated text/0000-discord.md Outdated
Show outdated Hide outdated text/0000-discord.md Outdated
@robclancy

This comment has been minimized.

Show comment
Hide comment
@robclancy

robclancy Jul 11, 2018

Thank god! Wish other communities would do this so I can actually stay in there.

robclancy commented Jul 11, 2018

Thank god! Wish other communities would do this so I can actually stay in there.

@elwayman02

This comment has been minimized.

Show comment
Hide comment
@elwayman02

elwayman02 Jul 11, 2018

I wrote a comparison of a bunch of chat platforms from the perspective of open-source communities, which was heavily referenced for the Reactiflux move to Discord. This is a few years dated now (particularly in terms of Discord features that were missing then but now exist), but still relevant:

http://jhawk.co/team-chat-comparison
http://jhawk.co/team-chat-features

elwayman02 commented Jul 11, 2018

I wrote a comparison of a bunch of chat platforms from the perspective of open-source communities, which was heavily referenced for the Reactiflux move to Discord. This is a few years dated now (particularly in terms of Discord features that were missing then but now exist), but still relevant:

http://jhawk.co/team-chat-comparison
http://jhawk.co/team-chat-features

@happycollision

This comment has been minimized.

Show comment
Hide comment
@happycollision

happycollision Jul 11, 2018

Perhaps the welcome topic can explain that there is currently a Slack that is being transitioned from.

It would also be nice if it explained the difference between the purpose of the Discord and the Discourse instances. I know I am confused about where I should go for something.

happycollision commented Jul 11, 2018

Perhaps the welcome topic can explain that there is currently a Slack that is being transitioned from.

It would also be nice if it explained the difference between the purpose of the Discord and the Discourse instances. I know I am confused about where I should go for something.

Show outdated Hide outdated text/0000-discord.md Outdated
@kennethlarsen

This comment has been minimized.

Show comment
Hide comment
@kennethlarsen

kennethlarsen Jul 12, 2018

Member

Just a question from a Discord noob: Will there be any issues in terms of lack of integrations? Slack seems to support most API integrations pretty well (as well as built-in reminders for meetings etc).

Member

kennethlarsen commented Jul 12, 2018

Just a question from a Discord noob: Will there be any issues in terms of lack of integrations? Slack seems to support most API integrations pretty well (as well as built-in reminders for meetings etc).

Because we use Slack's free plan, the entire instance is limited to 10,000 messages in history at any time. Because of this hard cap, the amount of time messages persist continues to shrink as the community grows.
It's hard to quantify exactly how painful this limitation is, as it means that new community members can't search for the answer to a question that was likely answered in the past. We can never go back to reference how or when a decision was made, which can mean decision-making feels less transparent that it should be.

This comment has been minimized.

@st-h

st-h Jul 12, 2018

I think one key point is that it is quite difficult to mix real time messaging with a well sorted journal like long term storage. In my experience it gets very difficult to distil usable information from real time chats - especially by hand via a search function (this is from OSS projects hosted on free slack with message limit in place, so this might get worse the more messages are stored). But that has been brought up multiple times in the past and if we keep discussing on that level, we probably will never find a better solution.

@st-h

st-h Jul 12, 2018

I think one key point is that it is quite difficult to mix real time messaging with a well sorted journal like long term storage. In my experience it gets very difficult to distil usable information from real time chats - especially by hand via a search function (this is from OSS projects hosted on free slack with message limit in place, so this might get worse the more messages are stored). But that has been brought up multiple times in the past and if we keep discussing on that level, we probably will never find a better solution.

### Performance
The architecture of the Slack native application relies on running a separate web application per Slack instance the user is signed into. For users who need to be in multiple Slack instances, this can add up to a significant tax on computer resources, particularly as the application starts up.

This comment has been minimized.

@st-h

st-h Jul 12, 2018

I personally don't think this is a good point to make up a decision. Slack has become very frequently used on OSS projects. For instance I only use 1 slack instance, which has multiple workspaces for different OSS projects. If now one OSS projects decides to no longer use slack, this puts a burden on everyone who is contributing to multiple OSS projects, as they now need to use multiple clients. There will inevitably always be a group of people who will have a performance gain from the decision made here and people who will have a disadvantage.

@st-h

st-h Jul 12, 2018

I personally don't think this is a good point to make up a decision. Slack has become very frequently used on OSS projects. For instance I only use 1 slack instance, which has multiple workspaces for different OSS projects. If now one OSS projects decides to no longer use slack, this puts a burden on everyone who is contributing to multiple OSS projects, as they now need to use multiple clients. There will inevitably always be a group of people who will have a performance gain from the decision made here and people who will have a disadvantage.

This comment has been minimized.

@rtablada

rtablada Jul 12, 2018

I think there needs to be clarification of the word “instance”. Slack workspaces or orgs are implemented as completely separate processes meaning the more slack orgs you belong to the less performant it becomes.

Anecdotally I find that discord takes much fewer resources than slack while in the background and about the same resources as one workspace when in the foreground.

@rtablada

rtablada Jul 12, 2018

I think there needs to be clarification of the word “instance”. Slack workspaces or orgs are implemented as completely separate processes meaning the more slack orgs you belong to the less performant it becomes.

Anecdotally I find that discord takes much fewer resources than slack while in the background and about the same resources as one workspace when in the foreground.

This comment has been minimized.

@rwjblue

rwjblue Jul 12, 2018

Member

I personally think this section should be removed or reworded, it specifically states that performance isn't different enough to be a factor in the decision but at the same time the sections presence (in an RFC motivating a move) clearly indicates that it is...

@rwjblue

rwjblue Jul 12, 2018

Member

I personally think this section should be removed or reworded, it specifically states that performance isn't different enough to be a factor in the decision but at the same time the sections presence (in an RFC motivating a move) clearly indicates that it is...

This comment has been minimized.

@robclancy

robclancy Jul 12, 2018

I am in like 10 discord servers and never have performance issues, some of them quite big. But with slack it just takes 1 tab to start creeping up resource usage. More than 1 slack and it is noticeable and why I can't idle in places I want to. I refuse to use so many resources for a damn chat application.

@robclancy

robclancy Jul 12, 2018

I am in like 10 discord servers and never have performance issues, some of them quite big. But with slack it just takes 1 tab to start creeping up resource usage. More than 1 slack and it is noticeable and why I can't idle in places I want to. I refuse to use so many resources for a damn chat application.

Show outdated Hide outdated text/0000-discord.md Outdated
@kellyselden

This comment has been minimized.

Show comment
Hide comment
@kellyselden

kellyselden Jul 12, 2018

Thank god! Wish other communities would do this so I can actually stay in there.

@robclancy I'm curious what about Slack prevented you from staying that Discord would solve?

kellyselden commented Jul 12, 2018

Thank god! Wish other communities would do this so I can actually stay in there.

@robclancy I'm curious what about Slack prevented you from staying that Discord would solve?

@lougreenwood

This comment has been minimized.

Show comment
Hide comment
@lougreenwood

lougreenwood Jul 12, 2018

Does locked mean read-only if the user does not have that role assigned, or does it mean any user without that role cannot join at all?

Personally, I think there's immense value in lurking in these type of high-level channels, especially as a way to understand the nuance and reasoning of how & why some feature is the way it is...

lougreenwood commented Jul 12, 2018

Does locked mean read-only if the user does not have that role assigned, or does it mean any user without that role cannot join at all?

Personally, I think there's immense value in lurking in these type of high-level channels, especially as a way to understand the nuance and reasoning of how & why some feature is the way it is...

@luxferresum

This comment has been minimized.

Show comment
Hide comment
@luxferresum

luxferresum Jul 12, 2018

Why discord?

Don't get me wrong, I have nothing against discord, but maybe it should be put under alternatives why not one of the many other options was chosen. For example mattermost or matrix.org which is completely open source and decentralized by design.

luxferresum commented Jul 12, 2018

Why discord?

Don't get me wrong, I have nothing against discord, but maybe it should be put under alternatives why not one of the many other options was chosen. For example mattermost or matrix.org which is completely open source and decentralized by design.

@rwwagner90

This comment has been minimized.

Show comment
Hide comment
@rwwagner90

rwwagner90 Jul 12, 2018

Member

Just my personal opinion, but all of my other companies and organizations are not likely to move away from Slack, so now I just will have to monitor two apps constantly. This is okay, just one more icon in my dock.

Member

rwwagner90 commented Jul 12, 2018

Just my personal opinion, but all of my other companies and organizations are not likely to move away from Slack, so now I just will have to monitor two apps constantly. This is okay, just one more icon in my dock.

@rwjblue

This comment has been minimized.

Show comment
Hide comment
@rwjblue

rwjblue Jul 12, 2018

Member

all of my other companies and organizations are not likely to move away from Slack, so now I just will have to monitor two apps constantly

Totally agree, this should be listed in the RFCs drawbacks section

Member

rwjblue commented Jul 12, 2018

all of my other companies and organizations are not likely to move away from Slack, so now I just will have to monitor two apps constantly

Totally agree, this should be listed in the RFCs drawbacks section

@rwjblue

This comment has been minimized.

Show comment
Hide comment
@rwjblue

rwjblue Jul 12, 2018

Member

Just a question from a Discord noob: Will there be any issues in terms of lack of integrations? Slack seems to support most API integrations pretty well (as well as built-in reminders for meetings etc).

Discord also has a very detailed API and many integrations already exist. One thing to note is that free Slack instances have limited numbers of integrations (IIRC the limit is 10, but I could be wrong), but Discord doesn't have this limitation.

tldr; I think moving to discord would increase our ability to have meaningful integrations...

Member

rwjblue commented Jul 12, 2018

Just a question from a Discord noob: Will there be any issues in terms of lack of integrations? Slack seems to support most API integrations pretty well (as well as built-in reminders for meetings etc).

Discord also has a very detailed API and many integrations already exist. One thing to note is that free Slack instances have limited numbers of integrations (IIRC the limit is 10, but I could be wrong), but Discord doesn't have this limitation.

tldr; I think moving to discord would increase our ability to have meaningful integrations...

Show outdated Hide outdated text/0000-discord.md Outdated
@robclancy

This comment has been minimized.

Show comment
Hide comment
@robclancy

robclancy Jul 12, 2018

@kellyselden terrible performance. Slack with multiple orgs just not being good in general, one account per org for example. I use tabs for slack and it's just not worth it. Whereas I have many discord servers I idle in and performance isn't different between 1 or 20. I also use the same account and can switch between servers with an instant click. I find the UX far better as well for communities.

We use slack at work (like everyone) which it is focused on, but it isn't suited for communities at all. Hell you need to use a third part service just so people can join...

robclancy commented Jul 12, 2018

@kellyselden terrible performance. Slack with multiple orgs just not being good in general, one account per org for example. I use tabs for slack and it's just not worth it. Whereas I have many discord servers I idle in and performance isn't different between 1 or 20. I also use the same account and can switch between servers with an instant click. I find the UX far better as well for communities.

We use slack at work (like everyone) which it is focused on, but it isn't suited for communities at all. Hell you need to use a third part service just so people can join...

MelSumner added some commits Jul 12, 2018

Update 0000-discord.md
Added some more clarification based on comments to the RFC.
Update 0000-discord.md
Updated to include integrations/API section
@MelSumner

This comment has been minimized.

Show comment
Hide comment
@MelSumner

MelSumner Jul 12, 2018

Contributor

all of my other companies and organizations are not likely to move away from Slack, so now I just will have to monitor two apps constantly

Totally agree, this should be listed in the RFCs drawbacks section

This is a situation that many folks already find themselves in, which is why I didn't include it.

Contributor

MelSumner commented Jul 12, 2018

all of my other companies and organizations are not likely to move away from Slack, so now I just will have to monitor two apps constantly

Totally agree, this should be listed in the RFCs drawbacks section

This is a situation that many folks already find themselves in, which is why I didn't include it.

@MelSumner

This comment has been minimized.

Show comment
Hide comment
@MelSumner

MelSumner Jul 12, 2018

Contributor

Just a question from a Discord noob: Will there be any issues in terms of lack of integrations? Slack seems to support most API integrations pretty well (as well as built-in reminders for meetings etc).

@kennethlarsen Discord is awesome at this. I added an integrations/API section to the RFC.

Contributor

MelSumner commented Jul 12, 2018

Just a question from a Discord noob: Will there be any issues in terms of lack of integrations? Slack seems to support most API integrations pretty well (as well as built-in reminders for meetings etc).

@kennethlarsen Discord is awesome at this. I added an integrations/API section to the RFC.

@walter

This comment has been minimized.

Show comment
Hide comment
@walter

walter Jul 12, 2018

I'm curious how Riot.im compares to Discord. If a move is being proposed, I wonder if it's a better long term choice.

walter commented Jul 12, 2018

I'm curious how Riot.im compares to Discord. If a move is being proposed, I wonder if it's a better long term choice.

@sotojuan

This comment has been minimized.

Show comment
Hide comment
@sotojuan

sotojuan Jul 13, 2018

I think Discord is a great choice right now, but it is a VC-backed company that is eventually going to have to answer to investors. I really doubt their Nitro plan is profitable enough... my worry is that they will start restricting free features at some point.

sotojuan commented Jul 13, 2018

I think Discord is a great choice right now, but it is a VC-backed company that is eventually going to have to answer to investors. I really doubt their Nitro plan is profitable enough... my worry is that they will start restricting free features at some point.

@NullVoxPopuli

This comment has been minimized.

Show comment
Hide comment
@NullVoxPopuli

NullVoxPopuli Jul 13, 2018

I just want to point out how much memory slack uses...

Here are before and after screenshots of memory usage. (4 slacks open)

before: (4 open)
image

after: (closed all 4)
image

(only 1GB is actually pretty good for slack -- there must have been a memory leak that was fixed or something)

Looking in the chrome task manager:

image
image

The memory seems to be based on the number of channels within each slack.

So, for Discord,
image

but, on discord, I'm in 7 different groups, each with a few to many many channels.. so.. resource-wise, discord is a clear winner.

NullVoxPopuli commented Jul 13, 2018

I just want to point out how much memory slack uses...

Here are before and after screenshots of memory usage. (4 slacks open)

before: (4 open)
image

after: (closed all 4)
image

(only 1GB is actually pretty good for slack -- there must have been a memory leak that was fixed or something)

Looking in the chrome task manager:

image
image

The memory seems to be based on the number of channels within each slack.

So, for Discord,
image

but, on discord, I'm in 7 different groups, each with a few to many many channels.. so.. resource-wise, discord is a clear winner.

@st-h

This comment has been minimized.

Show comment
Hide comment
@st-h

st-h Jul 13, 2018

@NullVoxPopuli interesting. but what OS?

However, I still don't think the performance of a (single) client makes a good point for switching the whole messaging ecosystem. Just a few reasons:

  • performance may vary depending on the OS used, so this will not be very easy to compare accurately. let alone making an educated decision based on how much which OS is used
  • clients do evolve and change (sometimes in very short time). The performance issues we are debating about might be gone sooner than we switch the whole ecosystem
  • alternative clients might get published (I don't know wether slacks api allows this though)
  • ...

Personally, I would drop performance completely and focus on the key points. If these are strong enough, performance will not be an issue unless the new client is much worse than what we have now.

st-h commented Jul 13, 2018

@NullVoxPopuli interesting. but what OS?

However, I still don't think the performance of a (single) client makes a good point for switching the whole messaging ecosystem. Just a few reasons:

  • performance may vary depending on the OS used, so this will not be very easy to compare accurately. let alone making an educated decision based on how much which OS is used
  • clients do evolve and change (sometimes in very short time). The performance issues we are debating about might be gone sooner than we switch the whole ecosystem
  • alternative clients might get published (I don't know wether slacks api allows this though)
  • ...

Personally, I would drop performance completely and focus on the key points. If these are strong enough, performance will not be an issue unless the new client is much worse than what we have now.

@elwayman02

This comment has been minimized.

Show comment
Hide comment
@elwayman02

elwayman02 Jul 13, 2018

elwayman02 commented Jul 13, 2018

@rwjblue

This comment has been minimized.

Show comment
Hide comment
@rwjblue

rwjblue Jul 13, 2018

Member

Personally, I would drop performance completely and focus on the key points. If these are strong enough, performance will not be an issue unless the new client is much worse than what we have now.

Agree. I do think Discords perf to be better than Slacks, but its just so far removed from being a factor in the decision that I think it muddies the discussion here...

Member

rwjblue commented Jul 13, 2018

Personally, I would drop performance completely and focus on the key points. If these are strong enough, performance will not be an issue unless the new client is much worse than what we have now.

Agree. I do think Discords perf to be better than Slacks, but its just so far removed from being a factor in the decision that I think it muddies the discussion here...

@NullVoxPopuli

This comment has been minimized.

Show comment
Hide comment
@NullVoxPopuli

NullVoxPopuli Jul 13, 2018

@st-h

@NullVoxPopuli interesting. but what OS?

Linux / Ubuntu 18.04

But I know my coworkers complain about slack resource usage on both Mac and Windows. :-\

NullVoxPopuli commented Jul 13, 2018

@st-h

@NullVoxPopuli interesting. but what OS?

Linux / Ubuntu 18.04

But I know my coworkers complain about slack resource usage on both Mac and Windows. :-\

@MelSumner

This comment has been minimized.

Show comment
Hide comment
@MelSumner

MelSumner Aug 15, 2018

Contributor

Gently encouraging folks who are joining the conversation now, to please read through the RFC and the comments if possible- I’m seeing a few repeat comments that I know we have explored/responsed to. Thank you so much! 👍

Contributor

MelSumner commented Aug 15, 2018

Gently encouraging folks who are joining the conversation now, to please read through the RFC and the comments if possible- I’m seeing a few repeat comments that I know we have explored/responsed to. Thank you so much! 👍

@st-h

This comment has been minimized.

Show comment
Hide comment
@st-h

st-h Aug 15, 2018

@lougreenwood sorry if that came across other than I intended. My intention was mainly to point out that we don't achieve much if we keep discussing items that are mainly subjective and to bring attention to what in my understanding have been the core issues behind this RFC. I was also trying to point out possible alternative implementations which could gain more value on the long run. However, maybe I misinterpreted the RFC... I don't know by now. This wasn't meant to provide an argument against using discord. I think improvement is good, yet it may take a toll we don't really know. Still we could get some data about that by launching a short survey for instance, but I guess by now it's better to just move on. Maybe an RFC even isn't the best option to discuss a topic which has such a direct impact on the community. And yes, I shouldn't have tried to intervene that dreadful conversation - that did not go well at all. There surely is something to take away from that :)

st-h commented Aug 15, 2018

@lougreenwood sorry if that came across other than I intended. My intention was mainly to point out that we don't achieve much if we keep discussing items that are mainly subjective and to bring attention to what in my understanding have been the core issues behind this RFC. I was also trying to point out possible alternative implementations which could gain more value on the long run. However, maybe I misinterpreted the RFC... I don't know by now. This wasn't meant to provide an argument against using discord. I think improvement is good, yet it may take a toll we don't really know. Still we could get some data about that by launching a short survey for instance, but I guess by now it's better to just move on. Maybe an RFC even isn't the best option to discuss a topic which has such a direct impact on the community. And yes, I shouldn't have tried to intervene that dreadful conversation - that did not go well at all. There surely is something to take away from that :)

@Caltor

This comment has been minimized.

Show comment
Hide comment
@Caltor

Caltor Aug 16, 2018

I (probably like lots of Developers) already use Slack in work so adding Discord is going to be a royal pain and I probably just won't bother tbh. The Ember community is already diluted and confused enough as it is without adding another option.

Caltor commented Aug 16, 2018

I (probably like lots of Developers) already use Slack in work so adding Discord is going to be a royal pain and I probably just won't bother tbh. The Ember community is already diluted and confused enough as it is without adding another option.

@RuslanZavacky

This comment has been minimized.

Show comment
Hide comment
@RuslanZavacky

RuslanZavacky Aug 16, 2018

I am not generally concerned about this move and I trust Ember team that evaluation was done properly. I do use Discord for times when I have to talk to my friends when occasionally playing games and I don't have any cons against Discord. When in game land, some time ago, we've done a similar switch from Skype to Discord and I would say the main factor was performance, you don't want your voice app to have 100% of one of your CPU in the important moments.. :)

Saying that "this is another app to check"... it's not a good argument. Discord has a mobile app, you can have proper notifications and check it when it suits you. Ember is not a game, to be hooked into - it should have focused on help and growth for you and the community.

Ask yourself - how many chat apps you use to communicate with your friends and family? I have Hangouts, Skype, Facebook Messenger, Viber, Whatsapp, Messenger. Some people also send messages on Instagram. Is it inconvenient? Yes. But I don't get hundreds of messages each hour in each of this sources - so it's not a big problem.

Adding Discord to that, is not gonna be an issue as well. And when you fight against it - are you sure you fight because of legitimate reasons, or because you don't like change?

One thing though, even if this is an RFC - it would be so much nicer, to already have the ability to join the Ember server and slowly dive in into the new experience.

RuslanZavacky commented Aug 16, 2018

I am not generally concerned about this move and I trust Ember team that evaluation was done properly. I do use Discord for times when I have to talk to my friends when occasionally playing games and I don't have any cons against Discord. When in game land, some time ago, we've done a similar switch from Skype to Discord and I would say the main factor was performance, you don't want your voice app to have 100% of one of your CPU in the important moments.. :)

Saying that "this is another app to check"... it's not a good argument. Discord has a mobile app, you can have proper notifications and check it when it suits you. Ember is not a game, to be hooked into - it should have focused on help and growth for you and the community.

Ask yourself - how many chat apps you use to communicate with your friends and family? I have Hangouts, Skype, Facebook Messenger, Viber, Whatsapp, Messenger. Some people also send messages on Instagram. Is it inconvenient? Yes. But I don't get hundreds of messages each hour in each of this sources - so it's not a big problem.

Adding Discord to that, is not gonna be an issue as well. And when you fight against it - are you sure you fight because of legitimate reasons, or because you don't like change?

One thing though, even if this is an RFC - it would be so much nicer, to already have the ability to join the Ember server and slowly dive in into the new experience.

@robclancy

This comment has been minimized.

Show comment
Hide comment
@robclancy

robclancy Aug 16, 2018

@Caltor I (probably like a lot of people who use a computer) already use Discord and with current Ember slack it is a royal pain to run another instance of slack with another account just to ask a question. The Ember community barely exists on slack so moving them to discord won't be much of a change and using a community focused app can only encourage growth. Much less confusing for someone to click a single link to join a discord server than to have to make a whole new slack account.

robclancy commented Aug 16, 2018

@Caltor I (probably like a lot of people who use a computer) already use Discord and with current Ember slack it is a royal pain to run another instance of slack with another account just to ask a question. The Ember community barely exists on slack so moving them to discord won't be much of a change and using a community focused app can only encourage growth. Much less confusing for someone to click a single link to join a discord server than to have to make a whole new slack account.

@robclancy

This comment has been minimized.

Show comment
Hide comment
@robclancy

robclancy Aug 16, 2018

@RuslanZavacky 3 days ago @wifelette said there are ~5 days before this is closed and the move is done. So I think this weekend or early next week we can join.

robclancy commented Aug 16, 2018

@RuslanZavacky 3 days ago @wifelette said there are ~5 days before this is closed and the move is done. So I think this weekend or early next week we can join.

@cibernox

This comment has been minimized.

Show comment
Hide comment
@cibernox

cibernox Aug 16, 2018

Contributor

I tend to favour Slack because it's what I use in my day to day job. However, I don't want to say No until I try how discourse feels.

What concerns me the most is, given how widespread slack is today, if putting the official ember chat room in place outside the usual toolchain most devs have will hurt adoption or engagement, both of the chat and of the framework itself.

I take that if the move proves to be wrong we are always on time to go back to Slack, right?

Maybe this has been asked before, I haven't read the entire issue, but is there any kind of metric we can use to know if people's engagement drops significantly? Not having one would concern me, as we wouldn't know if we are making a bad move.

Contributor

cibernox commented Aug 16, 2018

I tend to favour Slack because it's what I use in my day to day job. However, I don't want to say No until I try how discourse feels.

What concerns me the most is, given how widespread slack is today, if putting the official ember chat room in place outside the usual toolchain most devs have will hurt adoption or engagement, both of the chat and of the framework itself.

I take that if the move proves to be wrong we are always on time to go back to Slack, right?

Maybe this has been asked before, I haven't read the entire issue, but is there any kind of metric we can use to know if people's engagement drops significantly? Not having one would concern me, as we wouldn't know if we are making a bad move.

@ebryn

This comment has been minimized.

Show comment
Hide comment
@ebryn

ebryn Aug 17, 2018

Member

Does anyone else feel like there should be something like a Community RFC that supersedes the Discord RFC?

I'm personally very much on the fence about the Discord switch and the community has been having conversations about how we should be using Slack / Discourse, whether Spectrum.Chat is a better alternative, etc. that feels very relevant and may change the way we perceive the need for switching to Discord

https://discuss.emberjs.com/t/should-ember-better-define-its-use-of-slack/14474

https://embercommunity.slack.com/archives/C045YSXTK/p1534092148000056

I 🤔 if the lack of Slack history would be as big of an issue as it is today if we more formally organized community activity: start using Discourse more regularly, being better about using StackOverflow for Q&A, and Github for discussions around development

Member

ebryn commented Aug 17, 2018

Does anyone else feel like there should be something like a Community RFC that supersedes the Discord RFC?

I'm personally very much on the fence about the Discord switch and the community has been having conversations about how we should be using Slack / Discourse, whether Spectrum.Chat is a better alternative, etc. that feels very relevant and may change the way we perceive the need for switching to Discord

https://discuss.emberjs.com/t/should-ember-better-define-its-use-of-slack/14474

https://embercommunity.slack.com/archives/C045YSXTK/p1534092148000056

I 🤔 if the lack of Slack history would be as big of an issue as it is today if we more formally organized community activity: start using Discourse more regularly, being better about using StackOverflow for Q&A, and Github for discussions around development

@NullVoxPopuli

This comment has been minimized.

Show comment
Hide comment
@NullVoxPopuli

NullVoxPopuli Aug 17, 2018

what if we added a bot to slack that automatically captured and indexed all the conversations?

NullVoxPopuli commented Aug 17, 2018

what if we added a bot to slack that automatically captured and indexed all the conversations?

@robclancy

This comment has been minimized.

Show comment
Hide comment
@robclancy

robclancy Aug 17, 2018

I have yet to see any real reasons to use anything else over discord. All I have seen is anecdotal statements about what people already use.

robclancy commented Aug 17, 2018

I have yet to see any real reasons to use anything else over discord. All I have seen is anecdotal statements about what people already use.

@lolmaus

This comment has been minimized.

Show comment
Hide comment
@lolmaus

lolmaus Aug 17, 2018

@NullVoxPopuli what if we added a bot to slack that automatically captured and indexed all the conversations?

Won't work with private messages.

Every month Slack forces me into frustration and shame from seeing a person in a list of private dialogues and not being able to recall who that is and what you were discussing.

Double shame when a person asks you smth like "Any luck?" and you have to reapond with "Who are you?"

lolmaus commented Aug 17, 2018

@NullVoxPopuli what if we added a bot to slack that automatically captured and indexed all the conversations?

Won't work with private messages.

Every month Slack forces me into frustration and shame from seeing a person in a list of private dialogues and not being able to recall who that is and what you were discussing.

Double shame when a person asks you smth like "Any luck?" and you have to reapond with "Who are you?"

@kategengler

This comment has been minimized.

Show comment
Hide comment
@kategengler

kategengler Aug 17, 2018

Member

As I said earlier, I believe we are actively trying to push longer discussions and repeat questions into Discourse (Forums).

I do think there's a need for real-time chat in addition to that, though, for at least a few use-cases:

  • Coordinating work (meeting links, splitting up tasks, quick questions to get unblocked, swarming on work (probably also coordinated with a Quest issue or the like)
  • Live discussion of ideas (that may later become Discourse posts, RFCs, addons, etc...)
  • Help; while it would be great to say this should entirely happen on StackOverflow or the Forums, that is unrealistic. When asking for help, I don't often know exactly what to ask or what information is relevant. When giving help, I'm more likely to quickly ask a followup in a chat than I am to engage on a Forum post that I then I have to check for updates. We should be pushing the outcomes of common questions to something like the forums.
  • Social/Community (Things like watercooler/random or local channels)

For me, Discord has just one thing over Slack, and that is history.
For me, History solves a few important problems:

  • The conversation about how to implement a feature that vanishes before you have time to go back (maybe even just a day or two later) and create issues or an RFC out of the discussion.
  • The zombie notifications for mentions or DMs that I can no longer access because I left the computer for a few days.
  • The aforementioned lack of context around DMs. There are many people in our community and it can be hard to remember who works on what.
  • The inability to look back and find how a question was answered to repeat it or push the answer to the forums or the Guides.
Member

kategengler commented Aug 17, 2018

As I said earlier, I believe we are actively trying to push longer discussions and repeat questions into Discourse (Forums).

I do think there's a need for real-time chat in addition to that, though, for at least a few use-cases:

  • Coordinating work (meeting links, splitting up tasks, quick questions to get unblocked, swarming on work (probably also coordinated with a Quest issue or the like)
  • Live discussion of ideas (that may later become Discourse posts, RFCs, addons, etc...)
  • Help; while it would be great to say this should entirely happen on StackOverflow or the Forums, that is unrealistic. When asking for help, I don't often know exactly what to ask or what information is relevant. When giving help, I'm more likely to quickly ask a followup in a chat than I am to engage on a Forum post that I then I have to check for updates. We should be pushing the outcomes of common questions to something like the forums.
  • Social/Community (Things like watercooler/random or local channels)

For me, Discord has just one thing over Slack, and that is history.
For me, History solves a few important problems:

  • The conversation about how to implement a feature that vanishes before you have time to go back (maybe even just a day or two later) and create issues or an RFC out of the discussion.
  • The zombie notifications for mentions or DMs that I can no longer access because I left the computer for a few days.
  • The aforementioned lack of context around DMs. There are many people in our community and it can be hard to remember who works on what.
  • The inability to look back and find how a question was answered to repeat it or push the answer to the forums or the Guides.
@tomdale

This comment has been minimized.

Show comment
Hide comment
@tomdale

tomdale Aug 28, 2018

Member

Thank you everyone for the spirited discussion! Given that the conversation has died down, now is the right time to make a call on this RFC.

After several long discussions based on the concerns raised above, we still think Discord is the right next step and intend to merge this RFC. We do this with the awareness that this is not the preferred outcome for many people.

Ultimately, we believe that the harm caused by Slack's lack of history outweighs its many benefits. While migrating the community to Discord is a difficult and annoying task, it has a one-time cost. The cost of lost history (and key contributors not using Slack because of it) is one we continue to pay, and has knock-on effects in terms of transparency and our ability to bring in new contributors—the lifeblood of any open source project.

We should also reiterate our intent to move far more discussion from chat to our forums. Not only are forum threads more welcoming to global contributors, who may miss important chat topics in the backlog while they sleep, they are discoverable to search engines and linkable from things like StackOverflow answers.

We will be posting more detailed next steps soon, and invite folks to help us test out our new Discord instance and work out any bugs before we begin the migration in earnest.

Ember is its community, not its codebase. Preserving the health of this community is my number one priority. A sincere thank you to everyone who commented on this RFC, for or against. Decisions like this are not easy, but I believe this is the right thing to do for the long-term health of Ember.

If you have any suggestions for how we can smooth the migration process, please let us know. See you in Discord!

Member

tomdale commented Aug 28, 2018

Thank you everyone for the spirited discussion! Given that the conversation has died down, now is the right time to make a call on this RFC.

After several long discussions based on the concerns raised above, we still think Discord is the right next step and intend to merge this RFC. We do this with the awareness that this is not the preferred outcome for many people.

Ultimately, we believe that the harm caused by Slack's lack of history outweighs its many benefits. While migrating the community to Discord is a difficult and annoying task, it has a one-time cost. The cost of lost history (and key contributors not using Slack because of it) is one we continue to pay, and has knock-on effects in terms of transparency and our ability to bring in new contributors—the lifeblood of any open source project.

We should also reiterate our intent to move far more discussion from chat to our forums. Not only are forum threads more welcoming to global contributors, who may miss important chat topics in the backlog while they sleep, they are discoverable to search engines and linkable from things like StackOverflow answers.

We will be posting more detailed next steps soon, and invite folks to help us test out our new Discord instance and work out any bugs before we begin the migration in earnest.

Ember is its community, not its codebase. Preserving the health of this community is my number one priority. A sincere thank you to everyone who commented on this RFC, for or against. Decisions like this are not easy, but I believe this is the right thing to do for the long-term health of Ember.

If you have any suggestions for how we can smooth the migration process, please let us know. See you in Discord!

@tomdale tomdale merged commit 7be35ed into emberjs:master Aug 28, 2018

1 check passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details

tomdale added a commit that referenced this pull request Aug 28, 2018

@Caltor

This comment has been minimized.

Show comment
Hide comment
@Caltor

Caltor Aug 29, 2018

@tomdale Not the decision I personally favour but I appreciate someone has to make a decision. I don't know much about Discord but from what I have read about it (particularly on this discussion) it doesn't seem to be any better at recording and searching history? Also it seems to me that Discord is designed for gamers whereas Slack is aimed at Developers.

While there is a chat system available I think there will always be the temptation to use it rather than the forums. Would it be feasible to close down the chat altogether and do everything via the forums?

Caltor commented Aug 29, 2018

@tomdale Not the decision I personally favour but I appreciate someone has to make a decision. I don't know much about Discord but from what I have read about it (particularly on this discussion) it doesn't seem to be any better at recording and searching history? Also it seems to me that Discord is designed for gamers whereas Slack is aimed at Developers.

While there is a chat system available I think there will always be the temptation to use it rather than the forums. Would it be feasible to close down the chat altogether and do everything via the forums?

@NullVoxPopuli

This comment has been minimized.

Show comment
Hide comment
@NullVoxPopuli

NullVoxPopuli Aug 29, 2018

Not that I have any weight on this, but as an observer:

Also it seems to me that Discord is designed for gamers

and supporting open source https://discordapp.com/open-source

Check this out: https://blog.discordapp.com/open-source-and-discord-b7466080fbf2

whereas Slack is aimed at Developers.

Slack is aimed at businesses. I've asked slack a number of times to support things that would make devs and open source communities happy, and they don't care --- because it wouldn't make them money or whatever.

@Caltor you should really give Discord a go. imo it's worlds better than slack, and they're much more receptive to community feedback when it comes to the direction of the app.

https://feedback.discordapp.com/forums/326712-discord-dream-land

NullVoxPopuli commented Aug 29, 2018

Not that I have any weight on this, but as an observer:

Also it seems to me that Discord is designed for gamers

and supporting open source https://discordapp.com/open-source

Check this out: https://blog.discordapp.com/open-source-and-discord-b7466080fbf2

whereas Slack is aimed at Developers.

Slack is aimed at businesses. I've asked slack a number of times to support things that would make devs and open source communities happy, and they don't care --- because it wouldn't make them money or whatever.

@Caltor you should really give Discord a go. imo it's worlds better than slack, and they're much more receptive to community feedback when it comes to the direction of the app.

https://feedback.discordapp.com/forums/326712-discord-dream-land

@Caltor

This comment has been minimized.

Show comment
Hide comment
@Caltor

Caltor Aug 29, 2018

@NullVoxPopuli I'll check it out.

@tomdale ideas for smooth transition:

  1. Idiot's guide to getting started on Discord and connecting to Ember channel/server (?)
  2. Everytime someone posts a message on Slack they get an automatic message saying to use Discord instead. I think you might be able to do this with the Slackbot. Does Discord have a bot BTW?
  3. A searchable (web?) archive of previous Slack discussions
  4. Maybe some sort of link such as IFTTT or Microsoft Flow that would automatically post to Discord if someone posts on Slack? Not sure about this one...

Caltor commented Aug 29, 2018

@NullVoxPopuli I'll check it out.

@tomdale ideas for smooth transition:

  1. Idiot's guide to getting started on Discord and connecting to Ember channel/server (?)
  2. Everytime someone posts a message on Slack they get an automatic message saying to use Discord instead. I think you might be able to do this with the Slackbot. Does Discord have a bot BTW?
  3. A searchable (web?) archive of previous Slack discussions
  4. Maybe some sort of link such as IFTTT or Microsoft Flow that would automatically post to Discord if someone posts on Slack? Not sure about this one...
@Caltor

This comment has been minimized.

Show comment
Hide comment
@Caltor

Caltor Aug 29, 2018

So is there a server for EmberJS on Discord yet?

Caltor commented Aug 29, 2018

So is there a server for EmberJS on Discord yet?

@lolmaus

This comment has been minimized.

Show comment
Hide comment
@lolmaus

lolmaus Aug 29, 2018

So is there a server for EmberJS on Discord yet?

There is, but the team are keeping it private until they set everything up perfectly.

Unfortunately, invitation requests aren't considered yet, even from early adopting enthusiasts.

lolmaus commented Aug 29, 2018

So is there a server for EmberJS on Discord yet?

There is, but the team are keeping it private until they set everything up perfectly.

Unfortunately, invitation requests aren't considered yet, even from early adopting enthusiasts.

@Alonski

This comment has been minimized.

Show comment
Hide comment
@Alonski

Alonski Sep 3, 2018

Member

Just updating everyone who is following this. The transition has started and you are all welcome to move on over to Discord: https://discord.gg/zT3asNS 🎉

Member

Alonski commented Sep 3, 2018

Just updating everyone who is following this. The transition has started and you are all welcome to move on over to Discord: https://discord.gg/zT3asNS 🎉

@LemonAndroid

This comment has been minimized.

Show comment
Hide comment
@LemonAndroid

LemonAndroid Sep 3, 2018

@lolmaus
Gitter is not evolving?

LemonAndroid commented Sep 3, 2018

@lolmaus
Gitter is not evolving?

@lolmaus

This comment has been minimized.

Show comment
Hide comment
@lolmaus

lolmaus Sep 4, 2018

@LemonAndroid That's my impression. I'd be happy to learn otherwise, but so far I'm very disappointed with Gitter. It had a great potential.

lolmaus commented Sep 4, 2018

@LemonAndroid That's my impression. I'd be happy to learn otherwise, but so far I'm very disappointed with Gitter. It had a great potential.

@localpcguy

This comment has been minimized.

Show comment
Hide comment
@localpcguy

localpcguy Sep 4, 2018

I'm not sure this is the proper venue to discuss Glitter, maybe on Discord would be better? Nvrmind, I can't read

localpcguy commented Sep 4, 2018

I'm not sure this is the proper venue to discuss Glitter, maybe on Discord would be better? Nvrmind, I can't read

@LemonAndroid

This comment has been minimized.

Show comment
Hide comment
@LemonAndroid

LemonAndroid Sep 4, 2018

@localpcguy i was pointed to this thread here on discord :D.

LemonAndroid commented Sep 4, 2018

@localpcguy i was pointed to this thread here on discord :D.

@localpcguy

This comment has been minimized.

Show comment
Hide comment
@localpcguy

localpcguy Sep 4, 2018

Ah shoot - I read that as Glitter, not Gitter...carry on - and Glitter isn't even an Ember thing, was thinking of Glimmer, sheesh, need more coffee

localpcguy commented Sep 4, 2018

Ah shoot - I read that as Glitter, not Gitter...carry on - and Glitter isn't even an Ember thing, was thinking of Glimmer, sheesh, need more coffee

@lougreenwood

This comment has been minimized.

Show comment
Hide comment
@lougreenwood

lougreenwood Sep 7, 2018

Just wanted to say - Discord is feeling hella vibrant after a week! Nice work @MelSumner 🥇

lougreenwood commented Sep 7, 2018

Just wanted to say - Discord is feeling hella vibrant after a week! Nice work @MelSumner 🥇

@josemarluedke josemarluedke referenced this pull request Sep 13, 2018

Merged

be -> by #244

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment