From dev-return-43951-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Fri Jan 11 10:47:36 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 B1F8E180648 for ; Fri, 11 Jan 2019 10:47:35 +0100 (CET) Received: (qmail 73860 invoked by uid 500); 11 Jan 2019 09:47:34 -0000 Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list dev@ignite.apache.org Received: (qmail 73848 invoked by uid 99); 11 Jan 2019 09:47:34 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Jan 2019 09:47:34 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 96D59CD277 for ; Fri, 11 Jan 2019 09:47:33 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.284 X-Spam-Level: ** X-Spam-Status: No, score=2.284 tagged_above=-999 required=6.31 tests=[SPF_HELO_PASS=-0.001, SPF_SOFTFAIL=0.972, URI_HEX=1.313] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id LmaK81ayJKN3 for ; Fri, 11 Jan 2019 09:47:31 +0000 (UTC) Received: from n4.nabble.com (n4.nabble.com [199.38.86.66]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 1839E60DA2 for ; Fri, 11 Jan 2019 09:47:31 +0000 (UTC) Received: from n4.nabble.com (localhost [127.0.0.1]) by n4.nabble.com (Postfix) with ESMTP id 4657946CB899 for ; Fri, 11 Jan 2019 03:47:30 -0600 (CST) Date: Fri, 11 Jan 2019 03:47:30 -0600 (CST) From: oignatenko To: dev@ignite.apache.org Message-ID: <1547200050286-0.post@n4.nabble.com> In-Reply-To: References: Subject: Re: Time to remove automated messages from the devlist? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi Denis, Mixing JIRA and human mails in one list seems to be inconvenient both for those interested in monitoring human and JIRA mails and from this perspective separate lists approach looks superior. Also, your mention of filtering made me wonder if "mixed" approach may have effect opposite to what you want, that is folks will just blindly filter out JIRA mails so that these will be effectively hidden from target audience. That said, your reasons for sending JIRA notifications to mailing list readers look important to me and that also makes me unhappy with approach of separate JIRA list. Trying to figure if there is a way to somehow resolve above contradiction I re-checked Apache mailing lists documentation for maybe they have something to address these matters somehow. From what I read it looks that we can try sort of combined solution, when JIRA notification feed to separate mailing list which in turn forwards daily digest to human list. [1] WDYT? regards, Oleg [1]: https://apache.org/foundation/mailinglists.html#digest-subscriptions Denis Magda-2 wrote > -1 for this action. > > JIRA notifications are sent on purpose to the dev list - someone came > across an issue and want to report it to the dev community. The community > has to be aware of this. That's the purpose of the community to improve > and > fix the project. It's just wrong to force to subscribe to 2 lists, people > won't do this, we're lazy by nature. Just use email filters, that's XXI > century but please don't separate discussions from issues reporting. > > -- > Denis > > > On Thu, Jan 10, 2019 at 3:55 AM Dmitriy Pavlov < > dpavlov@ > > wrote: > >> Hi Igniters, >> >> After removal of GitHub Comments from the list I have (a very subjective) >> feeling, that there became more human-human interaction, which is >> definitely more important that opportunity to control new JIRA tickets >> using the list. >> >> I suggest coming back to the idea of moving JIRA to a separate list. >> Please >> share your vision on this topic. Should it be > jira@.apache > or we >> should reuse > notifications@.apache >> >> Sincerely, >> Dmitriy Pavlov >> -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/