IMO we need to run a formal vote on this change, and then PMC chair can create (or reuse) a separate list for messages from Git repos.
ср, 14 нояб. 2018 г. в 16:08, Vladimir Ozerov <voze...@gridgain.com>: > Igniters, > > I would say that "set the filter" is not a solution. First, it is not > always possible technically. E.g. I use GMail and my dev-list emails are > already use a rule. I cannot extract generated emails from overall flow > with GMail capabilities. But the more important things - is why in the > first place someone needs to went through that generated nightmare? > > Git messages is a spam. Looks like everyone agrees with that. As far as > JIRA ticket creation - this is all about importance. When someone writes an > email to the devlist, this is likely to be important topic requiring > attention. When someone creates a ticket, most likely this either a bug, or > a piece of already discussed issue, or so. In other words - average devlist > user is likely to be interested in manual messages and is very unlikely to > be interested in "Ticket created" messages. Not important information > overshadows important. Let's continue disucssion this. > > As far as Git - what should be done to remove Git messages from the list? > > Vladimir. > > On Tue, Nov 6, 2018 at 6:49 PM Dmitriy Pavlov <dpavlov....@gmail.com> > wrote: > > > Petr, some manual digest, is probably not needed because Apache list > allows > > subscribing to digest. dev-digest-subsr...@ignite.apache.org if I > remember > > this correctly. > > > > вт, 6 нояб. 2018 г. в 18:28, Petr Ivanov <mr.wei...@gmail.com>: > > > > > Can be Jira notifications united in some kind of daily digest? > > > Maybe we can add special filter (new tasks / updates during last 24 > > hours) > > > with notification scheme? > > > > > > > > > > On 6 Nov 2018, at 18:15, Dmitriy Pavlov <dpavlov....@gmail.com> > wrote: > > > > > > > > I should mention I disagree to remove JIRA issues as the first step. > It > > > > helps everyone to understand what other people are going to do in the > > > > project. You always can comment if it is not the best approach, > find a > > > > duplicate issue, and you may suggest help. > > > > > > > > PR notification is more or less duplicates JIRA (as 1 JIRA 1..* PR), > so > > > it > > > > may be ok to move Git's messages to notificati...@ignite.apache.org > > > > <notificati...@ignite.apache.orgб> > > > > > > > > But we should keep JIRA and test failures. > > > > > > > > вт, 6 нояб. 2018 г. в 17:49, Alexey Kuznetsov <akuznet...@apache.org > >: > > > > > > > >> Hi! > > > >> > > > >> I have filter for e-mail from JIRA (very useful, I can quick search > > > issue > > > >> there without visiting JIRA). > > > >> > > > >> And I'm just deleting tons of e-mails from GitBox & about PRs. > > > >> > > > >> I don't know what for we need them? > > > >> > > > >> May by we try to move GitBox & PRs-related mails first and see how > it > > > goes? > > > >> > > > >> -- > > > >> Alexey Kuznetsov > > > >> > > > > > > > > >
