[sword-devel] Possibility of using Slack

[Daniel Bennett]

 Totally understand. Slack is not a great solution in that case.

How about Gitter? It’s basically a modern IRC.

To get on this list, I had to personally reach out to Troy, because the
email list was (and is) blocking new people from joining. Not exactly
public and open.

Also, the Freenode channel doesn’t preserve message history. And, the last
two times I asked for help, no one responded. Gitter preserves all message
history, which is good.

Anything that can reduce barriers to people giving and receiving help would
be nice!

On Jun 28, 2018 at 3:53 PM, Greg Hellings <greg.hellings at gmail.com> wrote:


It sounds like that's the exact opposite of what we want. We want the
communication to be public and open, not private and closed.

Also: what service spent much of yesterday offline? Hint: not Freenode,
which is where we currently have our developer chat.

--Greg

On Thu, Jun 28, 2018 at 2:31 PM Daniel Bennett <danbenn at umich.edu> wrote:

> Hi everyone,
>
> Just wanted to float the possibility of creating a Slack group for sword
> development?
>
> If you haven’t seen Slack, it’s a group messaging service, which gives you
> control over notifications.
>
> It’s private, secure, and requires minimal personal information.
>
> Hit reply and let me (or the group) know your thoughts!
>
> Here’s a screenshot below:
> [image: Image result for slack screenshots]
> _______________________________________________
> sword-devel mailing list: sword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


_______________________________________________
sword-devel mailing list: sword-devel at crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.crosswire.org/pipermail/sword-devel/attachments/20180628/970bb7da/attachment.html>