ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From oignatenko <oignate...@gridgain.com>
Subject Re: Time to remove automated messages from the devlist?
Date Fri, 11 Jan 2019 09:47:30 GMT
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]


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 &lt;

> dpavlov@

> &gt; 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/

View raw message