Hi Dominik,

I was writing about gitter just now :)

If searchability is an issue, then indeed we could consider the free plan
of gitter: https://billing.gitter.im


In any case, we should instruct users who paste code snippets at the
mailing list to use http://gist.github.com


On Sun, Aug 26, 2018 at 4:13 PM Dominik Wosiński <wos...@gmail.com> wrote:

>
>
> ---------- Forwarded message ---------
> From: Dominik Wosiński <wos...@gmail.com>
> Date: niedz., 26 sie 2018 o 15:12
> Subject: ODP: would you join a Slack workspace for Flink?
> To: Hequn Cheng <chenghe...@gmail.com>
>
>
> Hey,
> I have been facing this issue for multiple open source projects and
> discussions. Slack in my opinion has two main issues :
>
>              - the already mentioned issue with searching, through search
> engine
>
>              - Slack is still commercial application.
>
> The second issue is quite important, because for free version Slack gives
> 10k messages of history. I personally think that for Flink this would to
> loss all messages that are older than a week possibly. This is the big
> issue as it woul most certainly lead to asking the same questions over and
> over again. I’ve seen really big slack groups for some big projects where
> the history would last like 3-4 days and this is pure nightmare.
>
> The better solution would be to use gitter than Slack IMHO if there is
> need for such way of communication.
>
> Best Regards,
> Dominik.
>
>
>
> Wysłane z aplikacji Poczta
> <https://go.microsoft.com/fwlink/?LinkId=550986> dla Windows 10
>
>
>
> *Od: *Hequn Cheng <chenghe...@gmail.com>
> *Wysłano: *niedziela, 26 sierpnia 2018 14:37
> *Do: *Nicos Maris <nicos.ma...@gmail.com>
> *DW: *ches...@apache.org; user <user@flink.apache.org>
> *Temat: *Re: would you join a Slack workspace for Flink?
>
>
>
> Hi Nicos,
>
>
>
> Thanks for bring up this discussion. :-)
>
> Slack is a good way to communicate, but it seems not very fit for the open
> source field. The messages on Slack are mixed up and can not be searched
> through search engine.
>
>
>
> Best, Hequn
>
>
>
> On Sun, Aug 26, 2018 at 7:22 PM Nicos Maris <nicos.ma...@gmail.com> wrote:
>
> Chesnay can you take a look at the following PR?
>
>
>
> https://github.com/apache/flink-web/pull/120
>
>
>
> On Sun, Aug 26, 2018 at 1:09 PM Chesnay Schepler <ches...@apache.org>
> wrote:
>
> There have been previous discussions around using slack and they were
> rejected.
>
> Personally I would just remove the IRC channel; I'm not aware of any
> committer actually spending time there.
>
> On 25.08.2018 17:07, Nicos Maris wrote:
>
>
>
> Hi all,
>
>
>
>
>
> This mailing list is for user support and questions. If you would also use
> slack for user support and questions, then please vote at the following
> ticket. If you don't have an account at that jira, you can reply to this
> email with a "+1".
>
>
>
>
>
> [FLINK-10217 <https://issues.apache.org/jira/browse/FLINK-3862>] use
> Slack for user support and questions
>  Current status
>
> For user support and questions, users are instructed to subscribe to
> user@flink.apache.org but there are users like me who enjoy using also a
> chat channel. However, the instructions to do so are not clear and the IRC
> activity is low and it is definitely not indicative of the project's
> activity
> <https://issues.apache.org/jira/browse/FLINK-3862?focusedCommentId=16152376&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16152376>
> .
>
> The website <https://flink.apache.org/community.html> mentions that "If
> you want to talk with the Flink committers and users in a chat, there is an 
> IRC
> channel <https://flink.apache.org/community.html#irc>."
> Option 1: Use Slack
>
> An example of an Apache project that is using Slack
> <https://tedium.co/2017/10/17/irc-vs-slack-chat-history> is:
> http://mesos.apache.org/community
>
> I can assist on setting it up if at least one expert joins from the very
> beginning.
> Option 2: Keep using IRC and document it
>
> Add the missing section
> <https://github.com/apache/flink-web/blob/master/community.md#irc> at the
> website along with instructions for people who have never used IRC.
> Option 3: Use only the mailing list
>
> Use only user@flink.apache.org for user support and questions and do not
> mention IRC at the website.
>
>
>
>
>

Reply via email to