<div dir="ltr"><div>What about Rocket chat instead of Slack? It is open source.</div><div><a href="https://github.com/RocketChat/Rocket.Chat">https://github.com/RocketChat/Rocket.Chat</a></div><div><br></div><div>Monty, what kind of evaluation would you guys need? I might be able to help.<br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Aug 1, 2018 at 9:54 AM, Monty Taylor <span dir="ltr"><<a href="mailto:mordred@inaugust.com" target="_blank">mordred@inaugust.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On 08/01/2018 07:44 AM, Doug Hellmann wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Excerpts from Andrey Kurilin's message of 2018-08-01 15:21:37 +0300:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
ср, 1 авг. 2018 г. в 14:11, Dmitry Tantsur <<a href="mailto:dtantsur@redhat.com" target="_blank">dtantsur@redhat.com</a>>:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 08/01/2018 12:49 PM, Andrey Kurilin wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hey Ian and stackers!<br>
<br>
ср, 1 авг. 2018 г. в 8:45, Ian Wienand <<a href="mailto:iwienand@redhat.com" target="_blank">iwienand@redhat.com</a><br>
<mailto:<a href="mailto:iwienand@redhat.com" target="_blank">iwienand@redhat.com</a>>>:<br>
<br>
Hello,<br>
<br>
It seems freenode is currently receiving a lot of unsolicited traffic<br>
across all channels. The freenode team are aware [1] and doing their<br>
best.<br>
<br>
There are not really a lot of options. We can set "+r" on channels<br>
which means only nickserv registered users can join channels. We<br>
</blockquote>
have<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
traditionally avoided this, because it is yet one more barrier to<br>
communication when many are already unfamiliar with IRC access.<br>
However, having channels filled with irrelevant messages is also not<br>
very accessible.<br>
<br>
This is temporarily enabled in #openstack-infra for the time being,<br>
</blockquote>
so<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
we can co-ordinate without interruption.<br>
<br>
Thankfully AFAIK we have not needed an abuse policy on this before;<br>
but I guess we are the point we need some sort of coordinated<br>
response.<br>
<br>
I'd suggest to start, people with an interest in a channel can<br>
</blockquote>
request<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
+r from an IRC admin in #openstack-infra and we track it at [2]<br>
<br>
Longer term ... suggestions welcome? :)<br>
<br>
<br>
Move to Slack? We can provide auto-sending to emails invitations for<br>
</blockquote>
joining by<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
clicking the button on some page at <a href="http://openstack.org" rel="noreferrer" target="_blank">openstack.org</a> <<a href="http://openstack.org" rel="noreferrer" target="_blank">http://openstack.org</a>>.<br>
</blockquote>
It<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
will not add more berrier for new contributors and, at the same time,<br>
</blockquote>
this way<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
will give some base filtering by emails at least.<br>
</blockquote>
<br>
A few potential barriers with slack or similar solutions: lack of FOSS<br>
desktop<br>
clients (correct me if I'm wrong),<br>
</blockquote>
<br>
<br>
The second link from google search gives an opensource client written in<br>
python <a href="https://github.com/raelgc/scudcloud" rel="noreferrer" target="_blank">https://github.com/raelgc/scud<wbr>cloud</a> . Also, there is something which<br>
is written in golang.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
complete lack of any console clients (ditto),<br>
<br>
</blockquote>
<br>
Again, google gives several ones as first results -<br>
<a href="https://github.com/evanyeung/terminal-slack" rel="noreferrer" target="_blank">https://github.com/evanyeung/t<wbr>erminal-slack</a><br>
<a href="https://github.com/erroneousboat/slack-term" rel="noreferrer" target="_blank">https://github.com/erroneousbo<wbr>at/slack-term</a><br>
<br>
serious limits on free (as in beer) tariff plans.<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
</blockquote>
I can make an assumption that for marketing reasons, Slack Inc can propose<br>
extended Free plan.<br>
But anyway, even with default one the only thing which can limit us is<br>
`10,000 searchable messages` which is bigger than 0 (freenode doesn't store<br>
messages).<br>
<br>
<br>
Why I like slack? because a lot of people are familar with it (a lot of<br>
companies use it as like some opensource communities, like k8s )<br>
<br>
PS: I realize that OpenStack Community will never go away from Freenode and<br>
IRC, but I do not want to stay silent.<br>
</blockquote>
<br>
We are unlikely to select slack because the platform itself is<br>
proprietary, even if there are OSS clients. That said, there have<br>
been some discussions about platforms such as Matrix, which is<br>
similar to slack and also OSS.<br>
<br>
I think the main thing that is blocking any such move right now is<br>
the fact that we're lacking someone with time to evaluate the tool<br>
to see what it would take for us to run it. If you're interested in<br>
this, maybe you can work with the infrastructure team to plan and<br>
implement that evaluation?<br>
</blockquote>
<br></div></div>
In Vancouver I signed up to work on this - but so far it has been lower in priority than other tasks. I'll circle around with people today and see what we think about relative priorities.<br>
<br>
That said - Doug's invitation is quite valid - help would be welcome and I'd be happy to connect with someone who has time to help with this.<div class="HOEnZb"><div class="h5"><br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">Rafael Weingärtner</div></div>
</div>