[Neos] [TEAM] Slack for November sprint

[Jacob Floyd]

On Oct 31, 2014 9:50 AM, "Jigal van Hemert" <jigal.van.hemert at typo3.org>
wrote:
> Pros
> - Real names visible
Good point

> - it is not meant for permanent discussions/decisions which really need
to be done in mailing lists

I hadn't considered that it wasn't supposed to be permanent. I hear
Snapchat is good for ephemeral conversation too. I don't use Snapchat and I
always log my IM conversations so that I can refer back to things I have
written or explained. That is very useful later when I try to incorporate
those things in documentation.

So I need something that stores everything I say which is only when I'm
online. Connect could be helpful, but, for me, is not as important as being
amble to remember what I say, and what people say when they respond to my
questions.

> - works across platforms (notifications on mobile when not logged in on
web interface)

I haven't tried the mobile app yet. Does it use a lot of ram? I already
have so many things (ie productivity apps) on my phone that the social apps
feel like they just slow things down.

> - channels inside a team, currently used for various areas of interest

Good point

> - easy possibility to create bots (there is one created to get info from
gerrit and forge); several plugins available e.g. for displaying problems
from CI tools

Bots are fabulous

> - no irritating "<userx> has left freenode (Remote host closed the
connection)"

That would be a welcome change

> - no extra software needed (runs in browser) like IRC clients

On my desktop, that's a negative for me. I like having all my IM go through
pidgin where I can log everything that I see when I'm online. (See above
for why.) Is there a slack plugin for pidgin? I hate that Google hangouts
runs in the browser. Skype insists on using their asp which waists some of
my ram instead of working in the consolidated IM interface that pidgin
provides. If I can't use the same interface to log in to both yahoo, irc,
and whatever else I have to use to communicate/instant message, then I
don't really want to use it.

If I'm using someone else's computer or I'm traveling with my chromebook, a
browser based solution works well. But on my gentoo Linux laptop (where I
do all of my programming and most of my documentation work), browser based
is a con for me.

> Cons
> - no connection with t3o user base; invite only
> - limited history
> - yet another site to register with and open
> - no public access to discussions