tonygentilcore
commented
7 years ago From @aza on August 16, 2016 22:13
Seems like it's a nice feature to have to slipperize Slack teams adopting Other, as well as useful for us.
Feel like we will feel the pull for deeper integrations as we use. On Mon, Aug 15, 2016 at 9:38 AM Tony Gentilcore notifications@github.com wrote:
We could pretty easily write a Slack bot that posts all messages in a slack channel to an other channel. The idea is that we could do this for channels that have bots like #alerts and then we get access to a large number of existing slack bots for free (e.g. travis, sentry, jenkins, etc).
But I'm on the fence about whether this is actually a good idea. It'd help us move away from slack faster, for sure. But on the other hand, it'd limit our thinking about what kind of integrations w/ travis, sentry, etc we could implement atop other chat that aren't implementable as a slack bot.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/other-xyz/other.js/issues/34, or mute the thread https://github.com/notifications/unsubscribe-auth/AAE1iAA37zEpG4_yhoNHsAKpIhzWAN_Aks5qgJYMgaJpZM4Jki3X .
From @tonygentilcore on August 24, 2016 21:18
From @tonygentilcore on August 15, 2016 16:38
We could pretty easily write a Slack bot that posts all messages in a slack channel to an other channel. The idea is that we could do this for channels that have bots like #alerts and then we get access to a large number of existing slack bots for free (e.g. travis, sentry, jenkins, etc).
But I'm on the fence about whether this is actually a good idea. It'd help us move away from slack faster, for sure. But on the other hand, it'd limit our thinking about what kind of integrations w/ travis, sentry, etc we could implement atop other chat that aren't implementable as a slack bot.
Copied from original issue: other-xyz/other.js#34
Copied from original issue: other-xyz/time-cone#79