Sorry for late reply. Unfortunately it's the best we can currently get from this bot. Seems there aren't too many Slack-to-email options out there.
On Thu, May 25, 2017, 19:20 Ran Ziv <r...@gigaspaces.com> wrote: > Thank you for weighing in Matej. Glad to hear you're okay with the slack > digests. > > Arthur, have you had the chance to see if the bot's format can be adjusted > to be, um, somewhat prettier..? > > On Tue, May 23, 2017 at 6:58 PM, Matej Artač <matej.ar...@xlab.si> wrote: > > > Hello Ran, > > > > I as an observer am quite fine with having digests or transcripts from > > Slack appear in the mailing list. > > > > As far as I understand, Slack is reserved to people with Apache ID, so > > getting the conversation onto the mailing list would be good. > > > > Best regards, > > Matej > > > > > > Ran Ziv je 21.5.2017 ob 14:03 napisal: > > > > Matej, John etc. - The issue we keep coming back to, and the reason we > try > >> to avoid emails, is that discussions on emails are simply much slower > than > >> ones on Slack. > >> > >> John, regarding summarizing slack conversations on the mailing list > >> manually - that's possible, but then I feel like we might be getting the > >> worst of both worlds - someone would have to spend the time summarizing > >> the > >> conversation, plus it would not be as complete as it would have been had > >> it > >> been copied in its entirety (or, alternatively, have taken place > entirely > >> over the mailing list). I personally think the bot - assuming we can > >> improve its format somewhat - is actually more useful in that regard, > even > >> when excluding the work one would have to do to summarize the > >> conversation. > >> > >> Arthur (and also Tal, who suggested it on Slack) - I'm very much against > >> moving specifically the daily updates to the mailing list, keeping > >> everything else on Slack. IMO it makes sense to do it exactly the other > >> way > >> around. The updates are about things which are in progress, and are much > >> less relevant to the mailing list than actual discussions and > >> announcements > >> over completed features etc. > >> > >> > >> We need to find the right balance between the overhead the mailing list > >> incurs and the need to have everything logged on the list - and IMO the > >> bot > >> is the best solution at this time. > >> However, John, if you think otherwise, even after taking into > >> consideration > >> what I've mentioned above, then let us know what other flow you suggest > >> exactly, and we'll follow that instead. > >> > >> > >> Ran > >> > >> > >> > >> > >> On Tue, May 16, 2017 at 8:04 AM, Matej Artač <matej.ar...@xlab.si> > wrote: > >> > >> Dear all, > >>> > >>> I like this proposal. I am an outsider who is interested in the > >>> activities > >>> and progress of your project. It would be really great for me if this > >>> mailing list would contain what John suggests. I think it would greatly > >>> improve visibility into your project and likely provide a grounds for > >>> some > >>> additional discussion and comments from a larger community. > >>> > >>> Best regards, > >>> Matej > >>> > >>> > >>> John D. Ament je 15.5.2017 ob 16:12 napisal: > >>> > >>> No, and that's sort of the issue at hand here. I've requested these > >>> > >>>> mailing list changes because the dev@ traffic is typically github or > >>>> JIRA > >>>> chatter. We have no on list discussions. I'm basically trying to > force > >>>> you guys to actually talk to one another via email, since our other > >>>> attempts have not worked out well. > >>>> > >>>> I would expect that Slack discussions are summarized here by those > >>>> participating in them. Not automatically. > >>>> > >>>> John > >>>> > >>>> On Tue, May 9, 2017 at 10:00 PM Arthur Berezin <art...@gigaspaces.com > > > >>>> wrote: > >>>> > >>>> I missed the Slack chat, but sounds good +1. Is there an easy way to > >>>> get a > >>>> > >>>>> digest of the slack chat over dev mailing list? > >>>>> > >>>>> On Tue, May 9, 2017, 21:43 John D. Ament <johndam...@apache.org> > >>>>> wrote: > >>>>> > >>>>> All, > >>>>> > >>>>>> Based on a brief chat on Slack, I'm going to go ahead and create two > >>>>>> new > >>>>>> mailing lists: > >>>>>> > >>>>>> - commits@ > >>>>>> - issues@ > >>>>>> > >>>>>> The reason being, the dev list is designed for developer > discussions, > >>>>>> but > >>>>>> most of the banter is on JIRA issues or GitHub PRs/commits. To > >>>>>> > >>>>>> effectively > >>>>> > >>>>> measure the community openness we need to separate the types. > >>>>>> > >>>>>> All changes in a JIRA issue will be sent to issues@ and all commits > >>>>>> will > >>>>>> go > >>>>>> to commits@. > >>>>>> > >>>>>> John > >>>>>> > >>>>>> > >>>>>> -- > >>> Senior researcher > >>> XLAB d.o.o. > >>> Pot za Brdom 100 > >>> SI-1000 Ljubljana > >>> Slovenia > >>> > >>> DICE project team leader and WP5 leader: http://www.dice-h2020.eu > >>> Member, OASIS TOSCA Standard Technical Committee > >>> > >>> URL: http://www.xlab.si/rd/ > >>> Live chat: visit http://www.xlab.si/ and click Live chat > >>> Google Drive, hangouts: matej.artac...@gmail.com > >>> Office phone: +386 1 244 77 53 > >>> > >>> > >>> > > -- > > Senior researcher > > XLAB d.o.o. > > Pot za Brdom 100 > > SI-1000 Ljubljana > > Slovenia > > > > DICE project team leader and WP5 leader: http://www.dice-h2020.eu > > Member, OASIS TOSCA Standard Technical Committee > > > > URL: http://www.xlab.si/rd/ > > Live chat: visit http://www.xlab.si/ and click Live chat > > Google Drive, hangouts: matej.artac...@gmail.com > > Office phone: +386 1 244 77 53 > > > > >
