ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Raul Kripalani <r...@evosent.com>
Subject Re: Collaboration process at Ignite
Date Tue, 11 Aug 2015 08:54:48 GMT
Good point, Cos.

If the goal is to back up the chats, Slack offers that feature but it's a
paid one for over 10,000 msgs. I'll ask them if they are willing to offer
the service for free to an ASF project. To my knowledge, the person who
contacted Slack from the community-dev thread didn't ask this question.

Option B is to generate and upload the transcripts to a server, and link
out from the Apache Ignite site. Then use Google Search to make them
searchable.

But in practice this is only helpful to end users who want to check out if
their question has already been asked. Devs will likely never resort to the
transcripts and will expect decisions and big changes to be discussed on
the MLs.

If, on the other hand, the goal is to broadcast the matters of the day for
everyone to stay updated on a daily basis, I agree with Cos. Unnecessary
noise.

Raúl.
On 10 Aug 2015 23:47, "Konstantin Boudnik" <cos@apache.org> wrote:

> On Mon, Aug 10, 2015 at 11:41PM, Raul Kripalani wrote:
> > On Mon, Aug 10, 2015 at 10:52 PM, Dmitriy Setrakyan <
> dsetrakyan@apache.org>
> > wrote:
> >
> > > Would be ideal
> > > if Slack chats could be sent to the dev list on a daily basis as a
> safety
> > > net.
>
> I imagine that it will just raise a noise level on the dev@ list and most
> ppl
> will have to filter it out. If you feel like having these chats recorded -
> consider creating a separate list for all. But really I think even that is
> excessive.
>
> > That would be great. There's Slack Digest [1] we can try. There are
> > integrations also with Zapier [2] and IFTTT [3], although I think none
> > offers daily digest emails. Worse comes to worst, we can build something
> > directly against the Slack channels.history API [4]. A little Camel
> > integration, off the top of my head ;-)
> >
> > [1] http://slackdigest.com/digest.html
> > [2] https://zapier.com/zapbook/slack/
> > [3] https://ifttt.com/slack
> > [4] https://api.slack.com/methods/channels.history
> >
> > *Raúl Kripalani*
> > Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
> > Integration specialist
> > http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
> > http://blog.raulkr.net | twitter: @raulvk
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message