openwhisk-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bertrand Delacretaz <>
Subject Re: [DISCUSS] graduation from the incubator
Date Mon, 25 Mar 2019 10:28:35 GMT

On Tue, Mar 19, 2019 at 7:27 PM Matt Sicker <> wrote:
> ...My suggestion as to how to improve this wouldn't be the daily digest.
> My suggestion would be to ensure any development conversations that
> take place on Slack should be recreated on the mailing lists...

I agree with the intention, but having to "recreate" conversations can
be counter-productive, I'd rather say that any "important"
conversation needs to move out of Slack into a place which is fully
open (as in findable with a Google search), asynchronous and has a
persistent URL.

Git tickets or pull requests fit the bill for that IMO, but the
problem is that they are scattered among multiple Git repositories and
it's hard to follow them "from afar" while not missing important

To me, the essence of "if it didn't happen on the dev list it didn't
happen" is being able to follow the project without missing anything
important by just subscribing to this list. It doesn't mean everything
has to really happen here (which I understand would not be popular)
but everything important has to be reflected here, one way or another,
so as to raise people's attention.

The automated Slack digests are useful for archiving things here but
as Matt Sicker says not really usable to quickly skim things.

I think the following should help convince the Incubator that this
project is ready to graduate as far as Apache-style communications are

a) Guidelines (on probably)
on how to use Slack as opposed to more persistent and async channels.
That's basically "anything important needs to be fully open and
discoverable from the dev list, with a persistent URL", doesn't need
to be complicated but should reassure the Incubator that the project
is clear about this.

b) Weekly news on this list about what's going on generally and which
PRs and tickets one should look at to stay informed. Might be
automated or semi-automated but I suppose some redactional content
helps. As I suppose the "full-timers" on this project are all on
Slack, maybe a bot that collects /news items and sends them once a
week would make this easy?


View raw message