Apache Ignite Developers - Legacy Mail Archive

Bots on dev list

Classic

List

Threaded

17 messages Options

Denis Mekhanikov

Bots on dev list

Igniters,

We have a lot of threads, created by bots on the dev list.
Currently messages are sent by JIRA, GitHub and MTCGA bots. Maybe, some
others too, but these are the most active.

Take a look at this page:
http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-Developers-f1i35.html
It's hard to find actual discussions in this mess. I'd like to see
something like what we have on the users list:
http://apache-ignite-users.70518.x6.nabble.com/

It doesn't seem necessary to me to mix discussions with this cryptic flow
of information.
Can we create a separate mailing list for bots?

Denis

Dmitrii Ryabov

Re: Bots on dev list

Modern mail services allow users to filter messages. You can easily filter
out bot messages.

2018-08-29 11:48 GMT+03:00 Denis Mekhanikov <[hidden email]>:

> Igniters,
>
> We have a lot of threads, created by bots on the dev list.
> Currently messages are sent by JIRA, GitHub and MTCGA bots. Maybe, some
> others too, but these are the most active.
>
> Take a look at this page:
> http://apache-ignite-developers.2346864.n4.nabble.
> com/Apache-Ignite-Developers-f1i35.html
> It's hard to find actual discussions in this mess. I'd like to see
> something like what we have on the users list:
> http://apache-ignite-users.70518.x6.nabble.com/
>
> It doesn't seem necessary to me to mix discussions with this cryptic flow
> of information.
> Can we create a separate mailing list for bots?
>
> Denis
>

Mmuzaf

Re: Bots on dev list

Denis,

I would like to keep a single entry point into the whole Ignite development
process project,
but maybe other Igniters have another opinion on this. As for me, it's a
more convenient way
for searching any activity on dev.list by single keyword (e.g. PRs, JIRAs,
topics).

As mentioned Dmitry, you can configure your mail agent for grouping or
moving bot messages into
the separate directory. These messages have predefined topic names and can
be easily filtered.

On Wed, 29 Aug 2018 at 12:26 Dmitrii Ryabov <[hidden email]> wrote:

> Modern mail services allow users to filter messages. You can easily filter
> out bot messages.
>
> 2018-08-29 11:48 GMT+03:00 Denis Mekhanikov <[hidden email]>:
>
> > Igniters,
> >
> > We have a lot of threads, created by bots on the dev list.
> > Currently messages are sent by JIRA, GitHub and MTCGA bots. Maybe, some
> > others too, but these are the most active.
> >
> > Take a look at this page:
> > http://apache-ignite-developers.2346864.n4.nabble.
> > com/Apache-Ignite-Developers-f1i35.html
> > It's hard to find actual discussions in this mess. I'd like to see
> > something like what we have on the users list:
> > http://apache-ignite-users.70518.x6.nabble.com/
> >
> > It doesn't seem necessary to me to mix discussions with this cryptic flow
> > of information.
> > Can we create a separate mailing list for bots?
> >
> > Denis
> >
>

--
--
Maxim Muzafarov

Alexey Goncharuk

Re: Bots on dev list

Denis,

I am against filtering out MTCGA messages from the dev-list because test
failures affect every developer in the community and may be caused by any
developer in the community. Usually such emails require immediate action
and it would be wrong to move them to a separate list.

I understand, though, your concern about the dev-list appearance on nabble.
I wonder if there is an option to create subfolders there so that certain
emails are put into a separate subfolders, like Dmitrii Ryabov mentioned
before.

--AG

ср, 29 авг. 2018 г. в 12:48, Maxim Muzafarov <[hidden email]>:

> Denis,
>
> I would like to keep a single entry point into the whole Ignite development
> process project,
> but maybe other Igniters have another opinion on this. As for me, it's a
> more convenient way
> for searching any activity on dev.list by single keyword (e.g. PRs, JIRAs,
> topics).
>
> As mentioned Dmitry, you can configure your mail agent for grouping or
> moving bot messages into
> the separate directory. These messages have predefined topic names and can
> be easily filtered.
>
> On Wed, 29 Aug 2018 at 12:26 Dmitrii Ryabov <[hidden email]> wrote:
>
> > Modern mail services allow users to filter messages. You can easily
> filter
> > out bot messages.
> >
> > 2018-08-29 11:48 GMT+03:00 Denis Mekhanikov <[hidden email]>:
> >
> > > Igniters,
> > >
> > > We have a lot of threads, created by bots on the dev list.
> > > Currently messages are sent by JIRA, GitHub and MTCGA bots. Maybe, some
> > > others too, but these are the most active.
> > >
> > > Take a look at this page:
> > > http://apache-ignite-developers.2346864.n4.nabble.
> > > com/Apache-Ignite-Developers-f1i35.html
> > > It's hard to find actual discussions in this mess. I'd like to see
> > > something like what we have on the users list:
> > > http://apache-ignite-users.70518.x6.nabble.com/
> > >
> > > It doesn't seem necessary to me to mix discussions with this cryptic
> flow
> > > of information.
> > > Can we create a separate mailing list for bots?
> > >
> > > Denis
> > >
> >
> --
> --
> Maxim Muzafarov
>

Denis Mekhanikov

Re: Bots on dev list

In reply to this post by Dmitrii Ryabov

Guys,

Yep, I use filters on my mail account. But the portal is impossible to use.
When you subscribe to the dev list for the first time, you don't have any
history on your email,
and the archive is polluted with messages, sent by bots.

Some view on Nabble, that doesn't contain any automatically generated
messages, would help here.

Denis

ср, 29 авг. 2018 г. в 12:26, Dmitrii Ryabov <[hidden email]>:

dsetrakyan

Re: Bots on dev list

Is anyone in the community using or was using Nabble for the dev list
communication? Personally, I am subscribed to the dev list and use filters
in my email client.

D.

On Wed, Aug 29, 2018 at 3:40 AM, Denis Mekhanikov <[hidden email]>
wrote:

> Guys,
>
> Yep, I use filters on my mail account. But the portal is impossible to use.
> When you subscribe to the dev list for the first time, you don't have any
> history on your email,
> and the archive is polluted with messages, sent by bots.
>
> Some view on Nabble, that doesn't contain any automatically generated
> messages, would help here.
>
> Denis
>
> ср, 29 авг. 2018 г. в 12:26, Dmitrii Ryabov <[hidden email]>:
>
> > Modern mail services allow users to filter messages. You can easily
> filter
> > out bot messages.
> >
> > 2018-08-29 11:48 GMT+03:00 Denis Mekhanikov <[hidden email]>:
> >
> > > Igniters,
> > >
> > > We have a lot of threads, created by bots on the dev list.
> > > Currently messages are sent by JIRA, GitHub and MTCGA bots. Maybe, some
> > > others too, but these are the most active.
> > >
> > > Take a look at this page:
> > > http://apache-ignite-developers.2346864.n4.nabble.
> > > com/Apache-Ignite-Developers-f1i35.html
> > > It's hard to find actual discussions in this mess. I'd like to see
> > > something like what we have on the users list:
> > > http://apache-ignite-users.70518.x6.nabble.com/
> > >
> > > It doesn't seem necessary to me to mix discussions with this cryptic
> flow
> > > of information.
> > > Can we create a separate mailing list for bots?
> > >
> > > Denis
> > >
> >
>

Denis Mekhanikov

Re: Bots on dev list

I guess, nobody uses it because it's flooded by bots.
It may be useful to lookup old threads for people, who are not subscribed
to the mailing list from the beginning of time.

Denis

чт, 30 авг. 2018 г. в 3:39, Dmitriy Setrakyan <[hidden email]>:

> Is anyone in the community using or was using Nabble for the dev list
> communication? Personally, I am subscribed to the dev list and use filters
> in my email client.
>
> D.
>
> On Wed, Aug 29, 2018 at 3:40 AM, Denis Mekhanikov <[hidden email]>
> wrote:
>
> > Guys,
> >
> > Yep, I use filters on my mail account. But the portal is impossible to
> use.
> > When you subscribe to the dev list for the first time, you don't have any
> > history on your email,
> > and the archive is polluted with messages, sent by bots.
> >
> > Some view on Nabble, that doesn't contain any automatically generated
> > messages, would help here.
> >
> > Denis
> >
> > ср, 29 авг. 2018 г. в 12:26, Dmitrii Ryabov <[hidden email]>:
> >
> > > Modern mail services allow users to filter messages. You can easily
> > filter
> > > out bot messages.
> > >
> > > 2018-08-29 11:48 GMT+03:00 Denis Mekhanikov <[hidden email]>:
> > >
> > > > Igniters,
> > > >
> > > > We have a lot of threads, created by bots on the dev list.
> > > > Currently messages are sent by JIRA, GitHub and MTCGA bots. Maybe,
> some
> > > > others too, but these are the most active.
> > > >
> > > > Take a look at this page:
> > > > http://apache-ignite-developers.2346864.n4.nabble.
> > > > com/Apache-Ignite-Developers-f1i35.html
> > > > It's hard to find actual discussions in this mess. I'd like to see
> > > > something like what we have on the users list:
> > > > http://apache-ignite-users.70518.x6.nabble.com/
> > > >
> > > > It doesn't seem necessary to me to mix discussions with this cryptic
> > flow
> > > > of information.
> > > > Can we create a separate mailing list for bots?
> > > >
> > > > Denis
> > > >
> > >
> >
>

Vladimir Ozerov

Re: Bots on dev list

This is somewhat controversial question. Some people has filters, some
doesn't. And it s true that at the moment it is hard to find pieces of
human communication in tons of automated e-mails (JIRA, GitHub, TC bot).
If to put JIRA and GitHub aside (let's do not mix things), personally
content of TC bot looks not very good. I doubt that contributors known how
to react to it. If we want contributors to take actions on specific
problem, we should send emails directly to them, not to everyone.

For me good solution looks as follows:
1) Create separate channel for bot messages
2) "To" field should contain this channel and e-mails of specific people

Thoughts?

On Thu, Aug 30, 2018 at 10:41 AM Denis Mekhanikov <[hidden email]>
wrote:

> I guess, nobody uses it because it's flooded by bots.
> It may be useful to lookup old threads for people, who are not subscribed
> to the mailing list from the beginning of time.
>
> Denis
>
> чт, 30 авг. 2018 г. в 3:39, Dmitriy Setrakyan <[hidden email]>:
>
> > Is anyone in the community using or was using Nabble for the dev list
> > communication? Personally, I am subscribed to the dev list and use
> filters
> > in my email client.
> >
> > D.
> >
> > On Wed, Aug 29, 2018 at 3:40 AM, Denis Mekhanikov <[hidden email]
> >
> > wrote:
> >
> > > Guys,
> > >
> > > Yep, I use filters on my mail account. But the portal is impossible to
> > use.
> > > When you subscribe to the dev list for the first time, you don't have
> any
> > > history on your email,
> > > and the archive is polluted with messages, sent by bots.
> > >
> > > Some view on Nabble, that doesn't contain any automatically generated
> > > messages, would help here.
> > >
> > > Denis
> > >
> > > ср, 29 авг. 2018 г. в 12:26, Dmitrii Ryabov <[hidden email]>:
> > >
> > > > Modern mail services allow users to filter messages. You can easily
> > > filter
> > > > out bot messages.
> > > >
> > > > 2018-08-29 11:48 GMT+03:00 Denis Mekhanikov <[hidden email]>:
> > > >
> > > > > Igniters,
> > > > >
> > > > > We have a lot of threads, created by bots on the dev list.
> > > > > Currently messages are sent by JIRA, GitHub and MTCGA bots. Maybe,
> > some
> > > > > others too, but these are the most active.
> > > > >
> > > > > Take a look at this page:
> > > > > http://apache-ignite-developers.2346864.n4.nabble.
> > > > > com/Apache-Ignite-Developers-f1i35.html
> > > > > It's hard to find actual discussions in this mess. I'd like to see
> > > > > something like what we have on the users list:
> > > > > http://apache-ignite-users.70518.x6.nabble.com/
> > > > >
> > > > > It doesn't seem necessary to me to mix discussions with this
> cryptic
> > > flow
> > > > > of information.
> > > > > Can we create a separate mailing list for bots?
> > > > >
> > > > > Denis
> > > > >
> > > >
> > >
> >
>

Andrew Mashenkov

Re: Bots on dev list

Huge +1 for separate channel for bots and direct notification.

On Thu, Aug 30, 2018 at 12:20 PM Vladimir Ozerov <[hidden email]>
wrote:

> This is somewhat controversial question. Some people has filters, some
> doesn't. And it s true that at the moment it is hard to find pieces of
> human communication in tons of automated e-mails (JIRA, GitHub, TC bot).
> If to put JIRA and GitHub aside (let's do not mix things), personally
> content of TC bot looks not very good. I doubt that contributors known how
> to react to it. If we want contributors to take actions on specific
> problem, we should send emails directly to them, not to everyone.
>
> For me good solution looks as follows:
> 1) Create separate channel for bot messages
> 2) "To" field should contain this channel and e-mails of specific people
>
> Thoughts?
>
> On Thu, Aug 30, 2018 at 10:41 AM Denis Mekhanikov <[hidden email]>
> wrote:
>
> > I guess, nobody uses it because it's flooded by bots.
> > It may be useful to lookup old threads for people, who are not subscribed
> > to the mailing list from the beginning of time.
> >
> > Denis
> >
> > чт, 30 авг. 2018 г. в 3:39, Dmitriy Setrakyan <[hidden email]>:
> >
> > > Is anyone in the community using or was using Nabble for the dev list
> > > communication? Personally, I am subscribed to the dev list and use
> > filters
> > > in my email client.
> > >
> > > D.
> > >
> > > On Wed, Aug 29, 2018 at 3:40 AM, Denis Mekhanikov <
> [hidden email]
> > >
> > > wrote:
> > >
> > > > Guys,
> > > >
> > > > Yep, I use filters on my mail account. But the portal is impossible
> to
> > > use.
> > > > When you subscribe to the dev list for the first time, you don't have
> > any
> > > > history on your email,
> > > > and the archive is polluted with messages, sent by bots.
> > > >
> > > > Some view on Nabble, that doesn't contain any automatically generated
> > > > messages, would help here.
> > > >
> > > > Denis
> > > >
> > > > ср, 29 авг. 2018 г. в 12:26, Dmitrii Ryabov <[hidden email]>:
> > > >
> > > > > Modern mail services allow users to filter messages. You can
> easily
> > > > filter
> > > > > out bot messages.
> > > > >
> > > > > 2018-08-29 11:48 GMT+03:00 Denis Mekhanikov <[hidden email]
> >:
> > > > >
> > > > > > Igniters,
> > > > > >
> > > > > > We have a lot of threads, created by bots on the dev list.
> > > > > > Currently messages are sent by JIRA, GitHub and MTCGA bots.
> Maybe,
> > > some
> > > > > > others too, but these are the most active.
> > > > > >
> > > > > > Take a look at this page:
> > > > > > http://apache-ignite-developers.2346864.n4.nabble.
> > > > > > com/Apache-Ignite-Developers-f1i35.html
> > > > > > It's hard to find actual discussions in this mess. I'd like to
> see
> > > > > > something like what we have on the users list:
> > > > > > http://apache-ignite-users.70518.x6.nabble.com/
> > > > > >
> > > > > > It doesn't seem necessary to me to mix discussions with this
> > cryptic
> > > > flow
> > > > > > of information.
> > > > > > Can we create a separate mailing list for bots?
> > > > > >
> > > > > > Denis
> > > > > >
> > > > >
> > > >
> > >
> >
>

--
Best regards,
Andrey V. Mashenkov

Dmitrii Ryabov

Re: Bots on dev list

In reply to this post by Vladimir Ozerov

Vladimir, your idea is good, but...
1. Who should be mentioned in messages like PR or JIRA ticket creation? As
I see, only these messages clutter up the nabble.
2. MTCGA messages should mention the commiter and authors of the "bad"
commit.
2. Comments and changes in PR, tickets, and reviews already are sent to the
users, who subscribed to them.

2018-08-30 12:19 GMT+03:00 Vladimir Ozerov <[hidden email]>:

Dmitrii Ryabov

Re: Bots on dev list

> 2. MTCGA messages should mention the commiter and authors of the "bad"
commit.
But this is not always possible.

2018-08-30 13:04 GMT+03:00 Dmitrii Ryabov <[hidden email]>:

> Vladimir, your idea is good, but...
> 1. Who should be mentioned in messages like PR or JIRA ticket creation? As
> I see, only these messages clutter up the nabble.
> 2. MTCGA messages should mention the commiter and authors of the "bad"
> commit.
> 2. Comments and changes in PR, tickets, and reviews already are sent to
> the users, who subscribed to them.
>
> 2018-08-30 12:19 GMT+03:00 Vladimir Ozerov <[hidden email]>:
>
>> This is somewhat controversial question. Some people has filters, some
>> doesn't. And it s true that at the moment it is hard to find pieces of
>> human communication in tons of automated e-mails (JIRA, GitHub, TC bot).
>> If to put JIRA and GitHub aside (let's do not mix things), personally
>> content of TC bot looks not very good. I doubt that contributors known how
>> to react to it. If we want contributors to take actions on specific
>> problem, we should send emails directly to them, not to everyone.
>>
>> For me good solution looks as follows:
>> 1) Create separate channel for bot messages
>> 2) "To" field should contain this channel and e-mails of specific people
>>
>> Thoughts?
>>
>> On Thu, Aug 30, 2018 at 10:41 AM Denis Mekhanikov <[hidden email]>
>> wrote:
>>
>> > I guess, nobody uses it because it's flooded by bots.
>> > It may be useful to lookup old threads for people, who are not
>> subscribed
>> > to the mailing list from the beginning of time.
>> >
>> > Denis
>> >
>> > чт, 30 авг. 2018 г. в 3:39, Dmitriy Setrakyan <[hidden email]>:
>> >
>> > > Is anyone in the community using or was using Nabble for the dev list
>> > > communication? Personally, I am subscribed to the dev list and use
>> > filters
>> > > in my email client.
>> > >
>> > > D.
>> > >
>> > > On Wed, Aug 29, 2018 at 3:40 AM, Denis Mekhanikov <
>> [hidden email]
>> > >
>> > > wrote:
>> > >
>> > > > Guys,
>> > > >
>> > > > Yep, I use filters on my mail account. But the portal is impossible
>> to
>> > > use.
>> > > > When you subscribe to the dev list for the first time, you don't
>> have
>> > any
>> > > > history on your email,
>> > > > and the archive is polluted with messages, sent by bots.
>> > > >
>> > > > Some view on Nabble, that doesn't contain any automatically
>> generated
>> > > > messages, would help here.
>> > > >
>> > > > Denis
>> > > >
>> > > > ср, 29 авг. 2018 г. в 12:26, Dmitrii Ryabov <[hidden email]
>> >:
>> > > >
>> > > > > Modern mail services allow users to filter messages. You can
>> easily
>> > > > filter
>> > > > > out bot messages.
>> > > > >
>> > > > > 2018-08-29 11:48 GMT+03:00 Denis Mekhanikov <
>> [hidden email]>:
>> > > > >
>> > > > > > Igniters,
>> > > > > >
>> > > > > > We have a lot of threads, created by bots on the dev list.
>> > > > > > Currently messages are sent by JIRA, GitHub and MTCGA bots.
>> Maybe,
>> > > some
>> > > > > > others too, but these are the most active.
>> > > > > >
>> > > > > > Take a look at this page:
>> > > > > > http://apache-ignite-developers.2346864.n4.nabble.
>> > > > > > com/Apache-Ignite-Developers-f1i35.html
>> > > > > > It's hard to find actual discussions in this mess. I'd like to
>> see
>> > > > > > something like what we have on the users list:
>> > > > > > http://apache-ignite-users.70518.x6.nabble.com/
>> > > > > >
>> > > > > > It doesn't seem necessary to me to mix discussions with this
>> > cryptic
>> > > > flow
>> > > > > > of information.
>> > > > > > Can we create a separate mailing list for bots?
>> > > > > >
>> > > > > > Denis
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>>
>
>

Dmitriy Pavlov

Re: Bots on dev list

Hi everyone,

I think email from the bot is something exceptional. In this case author
and committer already ignored test failures. So dev list is the last hope
that someone can come and fix the failure.

Other emails come from human actions, so I'm happy that so many actions
occur in the community. I never name it pollution.

Other Apache projects forward every comment in every PR to dev lists. So
Ignite notifications are rare.

Sincerely
Dmitriy Pavlov

чт, 30 авг. 2018 г., 13:06 Dmitrii Ryabov <[hidden email]>:

> > 2. MTCGA messages should mention the commiter and authors of the "bad"
> commit.
> But this is not always possible.
>
> 2018-08-30 13:04 GMT+03:00 Dmitrii Ryabov <[hidden email]>:
>
> > Vladimir, your idea is good, but...
> > 1. Who should be mentioned in messages like PR or JIRA ticket creation?
> As
> > I see, only these messages clutter up the nabble.
> > 2. MTCGA messages should mention the commiter and authors of the "bad"
> > commit.
> > 2. Comments and changes in PR, tickets, and reviews already are sent to
> > the users, who subscribed to them.
> >
> > 2018-08-30 12:19 GMT+03:00 Vladimir Ozerov <[hidden email]>:
> >
> >> This is somewhat controversial question. Some people has filters, some
> >> doesn't. And it s true that at the moment it is hard to find pieces of
> >> human communication in tons of automated e-mails (JIRA, GitHub, TC bot).
> >> If to put JIRA and GitHub aside (let's do not mix things), personally
> >> content of TC bot looks not very good. I doubt that contributors known
> how
> >> to react to it. If we want contributors to take actions on specific
> >> problem, we should send emails directly to them, not to everyone.
> >>
> >> For me good solution looks as follows:
> >> 1) Create separate channel for bot messages
> >> 2) "To" field should contain this channel and e-mails of specific people
> >>
> >> Thoughts?
> >>
> >> On Thu, Aug 30, 2018 at 10:41 AM Denis Mekhanikov <
> [hidden email]>
> >> wrote:
> >>
> >> > I guess, nobody uses it because it's flooded by bots.
> >> > It may be useful to lookup old threads for people, who are not
> >> subscribed
> >> > to the mailing list from the beginning of time.
> >> >
> >> > Denis
> >> >
> >> > чт, 30 авг. 2018 г. в 3:39, Dmitriy Setrakyan <[hidden email]
> >:
> >> >
> >> > > Is anyone in the community using or was using Nabble for the dev
> list
> >> > > communication? Personally, I am subscribed to the dev list and use
> >> > filters
> >> > > in my email client.
> >> > >
> >> > > D.
> >> > >
> >> > > On Wed, Aug 29, 2018 at 3:40 AM, Denis Mekhanikov <
> >> [hidden email]
> >> > >
> >> > > wrote:
> >> > >
> >> > > > Guys,
> >> > > >
> >> > > > Yep, I use filters on my mail account. But the portal is
> impossible
> >> to
> >> > > use.
> >> > > > When you subscribe to the dev list for the first time, you don't
> >> have
> >> > any
> >> > > > history on your email,
> >> > > > and the archive is polluted with messages, sent by bots.
> >> > > >
> >> > > > Some view on Nabble, that doesn't contain any automatically
> >> generated
> >> > > > messages, would help here.
> >> > > >
> >> > > > Denis
> >> > > >
> >> > > > ср, 29 авг. 2018 г. в 12:26, Dmitrii Ryabov <
> [hidden email]
> >> >:
> >> > > >
> >> > > > > Modern mail services allow users to filter messages. You can
> >> easily
> >> > > > filter
> >> > > > > out bot messages.
> >> > > > >
> >> > > > > 2018-08-29 11:48 GMT+03:00 Denis Mekhanikov <
> >> [hidden email]>:
> >> > > > >
> >> > > > > > Igniters,
> >> > > > > >
> >> > > > > > We have a lot of threads, created by bots on the dev list.
> >> > > > > > Currently messages are sent by JIRA, GitHub and MTCGA bots.
> >> Maybe,
> >> > > some
> >> > > > > > others too, but these are the most active.
> >> > > > > >
> >> > > > > > Take a look at this page:
> >> > > > > > http://apache-ignite-developers.2346864.n4.nabble.
> >> > > > > > com/Apache-Ignite-Developers-f1i35.html
> >> > > > > > It's hard to find actual discussions in this mess. I'd like to
> >> see
> >> > > > > > something like what we have on the users list:
> >> > > > > > http://apache-ignite-users.70518.x6.nabble.com/
> >> > > > > >
> >> > > > > > It doesn't seem necessary to me to mix discussions with this
> >> > cryptic
> >> > > > flow
> >> > > > > > of information.
> >> > > > > > Can we create a separate mailing list for bots?
> >> > > > > >
> >> > > > > > Denis
> >> > > > > >
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
> >
> >
>

Alexey Kuznetsov

Re: Bots on dev list

Dmitriy,

How about to change e-mail subject
from *[MTCGA]: new failures in builds [nnnnn] needs to be handled*
to *[MTCGA]: new failures in builds needs to be handled* ?

If subject will be the same it will not produce lots of threads on dev list
and it will be a single thread.
What do you think?

--
Alexey Kuznetsov

Dmitriy Pavlov

Re: Bots on dev list

Hi Alexey,

Thank you for that brilliant idea. Build ID was added intentionally to
separate topics. But for timeout failures, it creates odd topics.

I would like to suggest a modification of the idea: What if we will include
a suite name instead of build ID. It will keep the context of suite
failures and fixes in one topic. E.g. recent problematic suite: Zookeeper
will originate 1 or 2 topics, and human reply to it will be kept together
with suite failure context. Please share your vision.

Sincerely.
Dmitriy Pavlov

пт, 7 сент. 2018 г. в 8:25, Alexey Kuznetsov <[hidden email]>:

> Dmitriy,
>
> How about to change e-mail subject
> from *[MTCGA]: new failures in builds [nnnnn] needs to be handled*
> to *[MTCGA]: new failures in builds needs to be handled* ?
>
> If subject will be the same it will not produce lots of threads on dev list
> and it will be a single thread.
> What do you think?
>
> --
> Alexey Kuznetsov
>

Alexey Kuznetsov

Re: Bots on dev list

Dmitriy,

I like your idea to add suite name.

On Mon, Sep 10, 2018 at 5:42 PM Dmitriy Pavlov <[hidden email]>
wrote:

> Hi Alexey,
>
> Thank you for that brilliant idea. Build ID was added intentionally to
> separate topics. But for timeout failures, it creates odd topics.
>
> I would like to suggest a modification of the idea: What if we will include
> a suite name instead of build ID. It will keep the context of suite
> failures and fixes in one topic. E.g. recent problematic suite: Zookeeper
> will originate 1 or 2 topics, and human reply to it will be kept together
> with suite failure context. Please share your vision.
>
> Sincerely.
> Dmitriy Pavlov
>
> пт, 7 сент. 2018 г. в 8:25, Alexey Kuznetsov <[hidden email]>:
>
> > Dmitriy,
> >
> > How about to change e-mail subject
> > from *[MTCGA]: new failures in builds [nnnnn] needs to be handled*
> > to *[MTCGA]: new failures in builds needs to be handled* ?
> >
> > If subject will be the same it will not produce lots of threads on dev
> list
> > and it will be a single thread.
> > What do you think?
> >
> > --
> > Alexey Kuznetsov
> >
>

--
Alexey Kuznetsov

Vladimir Ozerov

Re: Bots on dev list

Folks,

If there will be a single thread for all failures, nobody will read it.
Simply because it will be always "unread", with tons of messages, where it
would be impossible to find a failure I am responsible for.
Several threads - on per suite - makes situation a bit better, but still
nobody will read it. What is worse, there will be a lot of fat threads atop
of all other threads, so e.g. the very first page of GMail will always be
filled with failure messages.

In order to make things comfortable and efficient, we should strive to make
messages as specific as possible, instead of grouping unrelated failures
into one thread. IMO we can solve the problem as follows:
1) Move bot messages to separate mailing list
2) Add personal contributor email addresses to that messages for easy
filtering
3) If needed - add *aggregate* email, sent once a day (or several days) to
dev list with all the issues.

This way, we first reach contributor directly. Then we send reminder to the
dev list, without flooding.

Thoughts?

On Mon, Sep 10, 2018 at 5:11 PM Alexey Kuznetsov <[hidden email]>
wrote:

> Dmitriy,
>
> I like your idea to add suite name.
>
> On Mon, Sep 10, 2018 at 5:42 PM Dmitriy Pavlov <[hidden email]>
> wrote:
>
> > Hi Alexey,
> >
> > Thank you for that brilliant idea. Build ID was added intentionally to
> > separate topics. But for timeout failures, it creates odd topics.
> >
> > I would like to suggest a modification of the idea: What if we will
> include
> > a suite name instead of build ID. It will keep the context of suite
> > failures and fixes in one topic. E.g. recent problematic suite: Zookeeper
> > will originate 1 or 2 topics, and human reply to it will be kept together
> > with suite failure context. Please share your vision.
> >
> > Sincerely.
> > Dmitriy Pavlov
> >
> > пт, 7 сент. 2018 г. в 8:25, Alexey Kuznetsov <[hidden email]>:
> >
> > > Dmitriy,
> > >
> > > How about to change e-mail subject
> > > from *[MTCGA]: new failures in builds [nnnnn] needs to be handled*
> > > to *[MTCGA]: new failures in builds needs to be handled* ?
> > >
> > > If subject will be the same it will not produce lots of threads on dev
> > list
> > > and it will be a single thread.
> > > What do you think?
> > >
> > > --
> > > Alexey Kuznetsov
> > >
> >
>
>
> --
> Alexey Kuznetsov
>

Dmitriy Pavlov

Re: Bots on dev list

Hi Vladimir,

In general, I agree with these ideas, but it will be a lot of work to be
done to make personal notification even possible. We need to match each TC
and GitHub, GitHub account with email, this could become huge manual work.
We need to develop personal notifications code. Would you like to make a
contribution to these changes?

So I found more realistic to
A. group by suite and/or
B. implement some digest-like notification (to avoid mass emails).
C. Fix this strange bug with several notifications about one suite timeout
(I will do my absolute best to find out why it happens).

About point 1 I'm not sure I agree because
1. Nobody will read a separate list,
2. and it not possible to discuss failure with the rest of the community.
Please note that healthy practice is that someone will reply to failure
thread and email one more time when failure is fixed.

So I suggest concentrating on avoiding of failing a test, so the bot will
be silent :).

Sincerely,
Dmitriy Pavlov

пн, 10 сент. 2018 г. в 18:34, Vladimir Ozerov <[hidden email]>:

> Folks,
>
> If there will be a single thread for all failures, nobody will read it.
> Simply because it will be always "unread", with tons of messages, where it
> would be impossible to find a failure I am responsible for.
> Several threads - on per suite - makes situation a bit better, but still
> nobody will read it. What is worse, there will be a lot of fat threads atop
> of all other threads, so e.g. the very first page of GMail will always be
> filled with failure messages.
>
> In order to make things comfortable and efficient, we should strive to make
> messages as specific as possible, instead of grouping unrelated failures
> into one thread. IMO we can solve the problem as follows:
> 1) Move bot messages to separate mailing list
> 2) Add personal contributor email addresses to that messages for easy
> filtering
> 3) If needed - add *aggregate* email, sent once a day (or several days) to
> dev list with all the issues.
>
> This way, we first reach contributor directly. Then we send reminder to the
> dev list, without flooding.
>
> Thoughts?
>
>
> On Mon, Sep 10, 2018 at 5:11 PM Alexey Kuznetsov <[hidden email]>
> wrote:
>
> > Dmitriy,
> >
> > I like your idea to add suite name.
> >
> > On Mon, Sep 10, 2018 at 5:42 PM Dmitriy Pavlov <[hidden email]>
> > wrote:
> >
> > > Hi Alexey,
> > >
> > > Thank you for that brilliant idea. Build ID was added intentionally to
> > > separate topics. But for timeout failures, it creates odd topics.
> > >
> > > I would like to suggest a modification of the idea: What if we will
> > include
> > > a suite name instead of build ID. It will keep the context of suite
> > > failures and fixes in one topic. E.g. recent problematic suite:
> Zookeeper
> > > will originate 1 or 2 topics, and human reply to it will be kept
> together
> > > with suite failure context. Please share your vision.
> > >
> > > Sincerely.
> > > Dmitriy Pavlov
> > >
> > > пт, 7 сент. 2018 г. в 8:25, Alexey Kuznetsov <[hidden email]>:
> > >
> > > > Dmitriy,
> > > >
> > > > How about to change e-mail subject
> > > > from *[MTCGA]: new failures in builds [nnnnn] needs to be handled*
> > > > to *[MTCGA]: new failures in builds needs to be handled* ?
> > > >
> > > > If subject will be the same it will not produce lots of threads on
> dev
> > > list
> > > > and it will be a single thread.
> > > > What do you think?
> > > >
> > > > --
> > > > Alexey Kuznetsov
> > > >
> > >
> >
> >
> > --
> > Alexey Kuznetsov
> >
>