<div dir="auto"><div>What you say makes sense, Dev.<div dir="auto"><br></div><div dir="auto">By the way, who does one contact to get an invite for an account to <a href="https://icannatlarge.slack.com/" style="font-family:sans-serif">https://icannatlarge.slack.<wbr>com/</a>?</div><div dir="auto"><br><div data-smartmail="gmail_signature" dir="auto">Regards,<br><br>Justine Chew<br>-----</div></div><br><div class="gmail_extra"><br><div class="gmail_quote">On Mar 14, 2017 12:54 AM, "Dev Anand Teelucksingh" <<a href="mailto:devtee@gmail.com">devtee@gmail.com</a>> wrote:<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dear All,<br>
<br>
I've been thinking (and tinkering) about group chat.<br>
<br>
I'm suggesting that the At-Large Community use the free tier Slack<br>
version that we have at <a href="https://icannatlarge.slack.com/" rel="noreferrer" target="_blank">https://icannatlarge.slack.<wbr>com/</a><br>
<br>
Key reasons why:<br>
<br>
- Its very unlikely that ICANN will offer support (server resources,<br>
tech support) in the short term to deploy a self hosted solution like<br>
mattermost or Rocket.chat for ICANN At-Large Community. ICANN may be<br>
considering group chat solutions but given Slack export capabilities,<br>
it can be quite likely that<br>
- The challenge of a volunteer to deploy an open source solution for a<br>
large number of users using their resources without payment and<br>
support it to configure or fix things is too much and runs the risk of<br>
a volunteer unable to fulfil such a task after valiantly starting and<br>
the self hosted version goes down.<br>
- from an end user perspective, Slack works. It has the key features<br>
we want in group chat - threaded conversations, mobile apps, ability<br>
to create public channels, private rooms, and direct messages, search<br>
across channels.<br>
- the free tier offers 10 integrations - I've integrated Twitter,<br>
Skype, a translation tool, and an archive tool bot and was able to do<br>
this using the browser. Just like any other cloud service.<br>
<br>
here's a screenshot of the Slack channels<br>
<a href="https://www.dropbox.com/s/xgka1gpxnhpwv24/ttf-icann58-slack-channels.png" rel="noreferrer" target="_blank">https://www.dropbox.com/s/<wbr>xgka1gpxnhpwv24/ttf-icann58-<wbr>slack-channels.png</a><br>
<br>
The approach I've done is to create channels for interests and wgs<br>
that didn't neatly fit the interests - I've used the Key Policy<br>
issues of the At-Large Community<br>
<a href="https://www.dropbox.com/s/f1f81kugty0hulh/Policy-Issues-of-Interest-to-ICANN-At-Large.png" rel="noreferrer" target="_blank">https://www.dropbox.com/s/<wbr>f1f81kugty0hulh/Policy-Issues-<wbr>of-Interest-to-ICANN-At-Large.<wbr>png</a><br>
(this screenshot was from the O&E Community Onboarding presentations<br>
<a href="https://community.icann.org/display/atlarge/At-Large+Community+Onboarding" rel="noreferrer" target="_blank">https://community.icann.org/<wbr>display/atlarge/At-Large+<wbr>Community+Onboarding</a>)<br>
<br>
- Slack content can be exported on a regular basis as a backup and<br>
also for importing in any future group chat solution that could be<br>
deployed/supported by ICANN<br>
- I've also installed and configured this service which creates a<br>
public archive of the Slack room -<br>
<a href="http://icannatlarge.slackarchive.io/" rel="noreferrer" target="_blank">http://icannatlarge.<wbr>slackarchive.io/</a> so we can make our conversations<br>
public facing<br>
We can link to the conversations in a channel, for eg<br>
<a href="http://icannatlarge.slackarchive.io/technologytaskforce" rel="noreferrer" target="_blank">http://icannatlarge.<wbr>slackarchive.io/<wbr>technologytaskforce</a> or<br>
<a href="http://icannatlarge.slackarchive.io/idn/page-1" rel="noreferrer" target="_blank">http://icannatlarge.<wbr>slackarchive.io/idn/page-1</a> to a specific message.<br>
And in theory, I think it means that the search limit can be overcome.<br>
<br>
Thoughts? The TTF session is Wednesday<br>
<font color="#888888"><br>
Dev Anand<br>
</font><div class="elided-text"><br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
On Fri, Mar 10, 2017 at 2:59 AM, Chris Gift <<a href="mailto:chris.gift@icann.org">chris.gift@icann.org</a>> wrote:<br>
> Dev<br>
><br>
> Thanks for this. It’s great stuff. I would also look at visibility, archiving, and data access – all core to our transparency and accountability mandates.<br>
><br>
> Chris Gift<br>
><br>
> On 3/9/17, 6:45 AM, "<a href="mailto:ttf-bounces@atlarge-lists.icann.org">ttf-bounces@atlarge-lists.<wbr>icann.org</a> on behalf of Dev Anand Teelucksingh" <<a href="mailto:ttf-bounces@atlarge-lists.icann.org">ttf-bounces@atlarge-lists.<wbr>icann.org</a> on behalf of <a href="mailto:devtee@gmail.com">devtee@gmail.com</a>> wrote:<br>
><br>
> ;-) which is what happens when I try to have too many drafts onscreen.<br>
><br>
> As I was saying, I do need feedback on what this group wants regarding<br>
> group chat applications<br>
><br>
> Some of my thoughts<br>
><br>
> - we use Skype for At-Large chat<br>
> However there are disadvantages of using Skype<br>
> - chat history is not preserved - a lot of At-Large discussions over<br>
> the years have already been lost as persons upgrade their machines<br>
> - conversations on various topics happens in one group so as multiple<br>
> persons chime in at different times, potential conversations/insights<br>
> on a particular topic/issue are lost in the one stream.<br>
> - no ability to search messages across all skype groups - one has to<br>
> remember what skype group a potential message was in to find it<br>
><br>
> QUESTION : Any other disadvantages to note?<br>
><br>
> - there are a myriad of group chat applications - Slack, Hipchat,<br>
> Rocket.chat, Mattermost<br>
><br>
> - all share common features<br>
> - creating public rooms or channels for groups and/or topics<br>
> - creating private groups not visible to persons outside of such groups<br>
> - mobile apps to get push notifications and to respond to<br>
> messages via mobile more effectively<br>
> - ability to search across all channels and rooms<br>
> - can be administered by staff to create/archive/delete rooms/channels<br>
> - staff/admins have more control to add/remove/invite persons<br>
> - allows for extensions/integrations so that different services<br>
> can be integrated (eg Twitter notifications to a channel, email to a<br>
> channel)<br>
><br>
> QUESTION: Any other core features to note?<br>
><br>
> Based on these core features, Group chat offers significant benefits than Skype<br>
> - potential for At-large community members to be added by Staff and<br>
> added to channels of their interest<br>
> - potential to reduce email overload<br>
> - ability to find messages and conversations when they have time and<br>
> new found interest to learn/participate more<br>
><br>
> QUESTION: Any other core benefits?<br>
><br>
> QUESTION - Are there any specific feature that makes a specific group<br>
> chat stand out in terms of which one should be picked?<br>
><br>
> QUESTION - What do we want to recommend for ALAC/ICANN as next steps?<br>
><br>
> Looking forward to comments<br>
><br>
> Dev Anand<br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
> On Thu, Mar 9, 2017 at 10:02 AM, Dev Anand Teelucksingh<br>
> <<a href="mailto:devtee@gmail.com">devtee@gmail.com</a>> wrote:<br>
> > Dear All,<br>
> ><br>
> > Here's the slides for the TTF session at ICANN58<br>
> > <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_presentation_d_1uAxM-5Fi9hUBV2ZtqsGe3nKk8C0CDkJDDrtUfLV8XjOwE_edit-3Fusp-3Dsharing&d=DwICAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=zS0x8pK8z0FnanGSXbXvoRVfpJzE1Xmo0ZZP9Gl3-rw&m=gFod0ez7zYcG_fvtwhex4-dIzXSyKaKPlrG2TPx7ij8&s=L3HxyXbLbVub6rdDAJkf8TTemqvxJRv8GSSluEytMYE&e=" rel="noreferrer" target="_blank">https://urldefense.proofpoint.<wbr>com/v2/url?u=https-3A__docs.<wbr>google.com_presentation_d_<wbr>1uAxM-<wbr>5Fi9hUBV2ZtqsGe3nKk8C0CDkJDDrt<wbr>UfLV8XjOwE_edit-3Fusp-<wbr>3Dsharing&d=DwICAg&c=<wbr>FmY1u3PJp6wrcrwll3mSVzgfkbPSS6<wbr>sJms7xcl4I5cM&r=<wbr>zS0x8pK8z0FnanGSXbXvoRVfpJzE1X<wbr>mo0ZZP9Gl3-rw&m=gFod0ez7zYcG_<wbr>fvtwhex4-<wbr>dIzXSyKaKPlrG2TPx7ij8&s=<wbr>L3HxyXbLbVub6rdDAJkf8TTemqvxJR<wbr>v8GSSluEytMYE&e=</a><br>
> > (editing link, no Google login required)<br>
> ><br>
> > Still have work on Policy tracking and how At-Large should use group<br>
> > chat applications<br>
> ><br>
> > Whilst I put together the policy tracking slides, I do need feedback<br>
> > on what this group wants<br>
> > regarding group chat applications<br>
> ><br>
> > Some of my thoughts<br>
> ><br>
> > - there are a myriad of group chat applications - Slack, Hipchat,<br>
> > Rocket.chat, Mattermost<br>
> > - all share common features<br>
> > - creating public rooms or channels for groups and/or topics<br>
> > - creating private groups not visible to persons outside of such groups<br>
> > -<br>
> ><br>
> ><br>
> > - Group chat applications have signf<br>
> ><br>
> > Re: Group chat applications,<br>
> ______________________________<wbr>_________________<br>
> ttf mailing list<br>
> <a href="mailto:ttf@atlarge-lists.icann.org">ttf@atlarge-lists.icann.org</a><br>
> <a href="https://mm.icann.org/mailman/listinfo/ttf" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/ttf</a><br>
><br>
><br>
______________________________<wbr>_________________<br>
ttf mailing list<br>
<a href="mailto:ttf@atlarge-lists.icann.org">ttf@atlarge-lists.icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/ttf" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/ttf</a><br>
</div></blockquote></div><br></div></div></div>