Re: Asynchronous communications (was: Please review our project's draft...)

2018-12-19 Thread Carlos Santana
Thanks Bertrand ! Oh it looks like they use a simple script that some how they run daily and connects to Slack REST API to extract the last messages and then sends and email. This is a perfect use case for OpenWhisk because I really don’t want to setup a server to run a cron job :-) - Carlos

Re: Asynchronous communications (was: Please review our project's draft...)

2018-12-19 Thread Bertrand Delacretaz
Hi Carlos, On Tue, Dec 18, 2018 at 8:31 PM Carlos Santana wrote: > ...Can you find out how they set it up ?... I have asked - https://lists.apache.org/thread.html/a4d0071104ad69a68870c8c40f8dca0b889ebbd565d3c68b88492b4b@%3Cdev.pulsar.apache.org%3E -Bertrand

Re: Asynchronous communications (was: Please review our project's draft...)

2018-12-18 Thread Carlos Santana
Good find Bertrand +1 Sounds good to me, people can always filter out if they are not interested in the daily email and already engaged in Slack. But those that wanted can benefit also the search and archive would be good to have. Can you find out how they set it up ? Do they use slackdigest [

Re: Asynchronous communications (was: Please review our project's draft...)

2018-12-18 Thread Bertrand Delacretaz
Hi, On Wed, Jun 6, 2018 at 6:12 PM Rodric Rabbah wrote: > ...Chetan suggested looking into Slack workspace export... Coming back to this after a long time, looking at this month's Board reports (the joys of being there ;-) I stumbled on daily Slack digests that Apache Pulsar sends to their dev l

Re: Asynchronous communications (was: Please review our project's draft...)

2018-06-07 Thread Bertrand Delacretaz
On Wed, Jun 6, 2018 at 6:50 PM, David P Grove wrote: > ...I don't think Slack is as good at going really deep into the details (turns > into "walls of text" that are intimidating to catch up with when you come > to them later).,, I agree with that, that was my point earlier here as well. > ...Gi

Re: Asynchronous communications (was: Please review our project's draft...)

2018-06-06 Thread David P Grove
Bertrand Delacretaz wrote on 06/06/2018 11:06:01 AM: > > On Wed, Jun 6, 2018 at 4:42 PM, David P Grove wrote: > > ...As Rodric said, properly organized channels and the use of threads help > > quite a bit... > > Do you have a few Slack URLs of good examples of that? > > I'll look at them quick

Re: Asynchronous communications (was: Please review our project's draft...)

2018-06-06 Thread Rob Allen
> On 6 Jun 2018, at 15:30, Rodric Rabbah wrote: > > Re slack... good discipline on our part does make it easier to catch up > even after hundreds of messages are posted. We do try to organize > discussions using slack threads so that it is easier to follow a particular > topic. This doesn't alw

Re: Asynchronous communications (was: Please review our project's draft...)

2018-06-06 Thread Rodric Rabbah
Chetan suggested looking into Slack workspace export - It looks like we can export all the messages this way (since 1/20/2017 for public channels). A simple UI to polish the JSON and make it easier to read and search would be helpful. Here's an example of a recent thread of discussion: https://ope

Re: Asynchronous communications (was: Please review our project's draft...)

2018-06-06 Thread Bertrand Delacretaz
On Wed, Jun 6, 2018 at 4:42 PM, David P Grove wrote: > ...As Rodric said, properly organized channels and the use of threads help > quite a bit... Do you have a few Slack URLs of good examples of that? I'll look at them quickly, before they disappear ;-) -Bertrand

Re: Asynchronous communications (was: Please review our project's draft...)

2018-06-06 Thread David P Grove
Bertrand Delacretaz wrote on 06/06/2018 10:23:35 AM: > From: Bertrand Delacretaz > To: dev@openwhisk.apache.org > Date: 06/06/2018 10:31 AM > Subject: Re: Asynchronous communications (was: Please review our > project's draft...) > > Hi, > > On Wed, Jun 6

Re: Asynchronous communications (was: Please review our project's draft...)

2018-06-06 Thread Rodric Rabbah
Re slack... good discipline on our part does make it easier to catch up even after hundreds of messages are posted. We do try to organize discussions using slack threads so that it is easier to follow a particular topic. This doesn't always happen and as I noted, requires good habits. We have also

Re: Asynchronous communications (was: Please review our project's draft...)

2018-06-06 Thread Bertrand Delacretaz
Hi, On Wed, Jun 6, 2018 at 4:05 PM, David P Grove wrote: > ...Professionally, I'm on several Slack teams that are paid (unlimited > history) and I personally find it _much_ easier to catch up with and > understand multiple weeks of technical conversation in a properly focused > Slack channel than

Re: Asynchronous communications (was: Please review our project's draft...)

2018-06-06 Thread David P Grove
Bertrand Delacretaz wrote on 06/06/2018 09:32:09 AM: > > ...Would it be worth adding the growth of the > > Slack community? We're ~800 members and it is really active > > With my incubation mentor hat on: enthusiasm for the the project is > fantastic news, but Apache projects should do the

Asynchronous communications (was: Please review our project's draft...)

2018-06-06 Thread Bertrand Delacretaz
Someone wrote: > ...Would it be worth adding the growth of the > Slack community? We're ~800 members and it is really active With my incubation mentor hat on: enthusiasm for the the project is fantastic news, but Apache projects should do their business on asynchronous channels, and I don't c