From dev-return-3435-archive-asf-public=cust-asf.ponee.io@openwhisk.apache.org Mon Mar 25 10:28:50 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id E979218064C for ; Mon, 25 Mar 2019 11:28:49 +0100 (CET) Received: (qmail 80071 invoked by uid 500); 25 Mar 2019 10:28:48 -0000 Mailing-List: contact dev-help@openwhisk.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@openwhisk.apache.org Delivered-To: mailing list dev@openwhisk.apache.org Received: (qmail 80056 invoked by uid 99); 25 Mar 2019 10:28:48 -0000 Received: from mail-relay.apache.org (HELO mailrelay2-lw-us.apache.org) (207.244.88.137) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Mar 2019 10:28:48 +0000 Received: from mail-lj1-f179.google.com (mail-lj1-f179.google.com [209.85.208.179]) by mailrelay2-lw-us.apache.org (ASF Mail Server at mailrelay2-lw-us.apache.org) with ESMTPSA id 0F01623F7 for ; Mon, 25 Mar 2019 10:28:48 +0000 (UTC) Received: by mail-lj1-f179.google.com with SMTP id f23so7319069ljc.0 for ; Mon, 25 Mar 2019 03:28:47 -0700 (PDT) X-Gm-Message-State: APjAAAXyTut2X+tiFb/Qu1rsyUl5nYW93ymZ19I5iWhSCJYJ15+OT8on nHWlylrSnWdObTHXKXsNwgH/WrBTkOU4H486apQ= X-Google-Smtp-Source: APXvYqzo8Zh6I1/GbM+x3E0sTP4ZOPhMwuCwiBLgq71TZ/QXcCZX5y4MLBOljBLlduecSQGOEkDBqsoNNVZ+rkQ5TLA= X-Received: by 2002:a2e:22c4:: with SMTP id i187mr4018573lji.94.1553509726743; Mon, 25 Mar 2019 03:28:46 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Bertrand Delacretaz Date: Mon, 25 Mar 2019 11:28:35 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [DISCUSS] graduation from the incubator To: OpenWhisk Dev Content-Type: text/plain; charset="UTF-8" Hi, 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 things. 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 concerned: a) Guidelines (on http://openwhisk.apache.org/community.html 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? -Bertrand