Chat automation and bridges
Chat automation and bridges
Do we have an communitication issue?
In recent times the four bigger messaging apps surpassed requests on the major social networks.
Drupal is also evolving more and more into services oriented systems, with API first initiatives, GraphQL and oAuth2 in restful environments.
If we look at the bigger picture then chat-apps can be seen as the new browsers, bots would be the new websites. This is the beginning of a new(er) internet.
Instant messaging is the place with the greatest risk for creating an unwelcoming environment for a new member of our community. We need to demonstrate that you can provide something an order of magnitude more welcoming than alternatives.
-Rachel Lawson in drupalchat.me-
After launching drupalchat in september 2017 and initiating the rocket_chat module, we’ve come a long way in adaptation and solving our current “chat island problem”, where each local community has its own slack and IRC is presumed dead.
This is crippling us as a community to collaborate and learn from our own history.
Now the challenge is up to us win converts if (and only if) we can create and maintain a welcoming atmosphere
This session will bridge technology, business and community around a week of sprinting at Drupal Developer Days
Meanwhile we got IoT, ChatOps and AI as separate phenomena make things more complicated or easy.
On the edge between business and DevOPS.
Chat, from time wasted to automated value.
As a community we bump into communication issues for we used to chat in irc, now there is many chat islands thatIs it possible to steer social and community effects.
ekes @ekes 2:57 PM
I don't like slack _because it's f'ing opaque_. The whole group that set it up are in a power position they want to keep too. Doesn't make it good.