Hi Ilya, > I have added you to "Contributors 1" role. Everybody in this role will still > get those "issue created" e-mail.
Thank you for that! Should not we mention this tweak with "Contributors 1" role somewhere in advanced how-to-contribute page? 2021-04-26 12:28 GMT+03:00, Ilya Kasnacheev <ilya.kasnach...@gmail.com>: > Hello! > > I have added you to "Contributors 1" role. Everybody in this role will > still get those "issue created" e-mail. > > Feel free in asking me to enlist. > > Regards, > -- > Ilya Kasnacheev > > > чт, 22 апр. 2021 г. в 18:16, Ivan Pavlukhin <vololo...@gmail.com>: > >> > All issues notifications are also sent to iss...@ignite.apache.org so >> one can subscribe to this list in order to track the created tickets. >> >> Does not sound as useful advice. Issues list [1] looks like real >> scrapyard, I doubt that it can be usable for anyone in current flavor. >> Can we send only "Created" notifications there? >> >> [1] https://lists.apache.org/list.html?iss...@ignite.apache.org >> >> 2021-04-21 18:30 GMT+03:00, Ilya Kasnacheev <ilya.kasnach...@gmail.com>: >> > Hello! >> > >> > INFRA ticket created: https://issues.apache.org/jira/browse/INFRA-21762 >> > >> > I have asked to keep sending the created issue notifications for >> > "Contributors 1" role, which is empty at present. So if you wish to >> > keep >> > getting those e-mails, please add yourself to this role or tell me to >> > do >> so >> > for you. >> > >> > Regards, >> > -- >> > Ilya Kasnacheev >> > >> > >> > ср, 21 апр. 2021 г. в 17:59, Alexey Goncharuk < >> alexey.goncha...@gmail.com>: >> > >> >> I support the idea. All issues notifications are also sent to >> >> iss...@ignite.apache.org so one can subscribe to this list in order to >> >> track the created tickets. The notifications trash the devlist archive >> UI >> >> and make it extremely difficult to navigate. >> >> >> >> вт, 20 апр. 2021 г. в 18:35, Ilya Kasnacheev >> >> <ilya.kasnach...@gmail.com >> >: >> >> >> >> > Hello, Maxim! >> >> > >> >> > You are free to revert any commit which has led to any new stable >> >> > test >> >> > failure, or new flaky test that was non-flaky before. >> >> > >> >> > Just revert the change and reopen the ticket. >> >> > >> >> > The problem here is that it's very hard to detect on the spot, most >> >> > of >> >> > MTCGA e-mails are false positives and even if they are not, it is >> >> > not >> >> > relevant for most of developers. >> >> > >> >> > WDYT? I'm also still waiting for more input. >> >> > >> >> > Regards, >> >> > -- >> >> > Ilya Kasnacheev >> >> > >> >> > >> >> > ср, 14 апр. 2021 г. в 21:26, Maxim Muzafarov <mmu...@apache.org>: >> >> > >> >> > > +1 for new JIRA issues >> >> > > -1 for MTCGA notifications >> >> > > >> >> > > Why we should hide errors from the dev-list? Who should take care >> >> > > of >> >> > > issues reported by MTCGA.Bot in this case? >> >> > > We must apply stricter rules for such issues: a commit leading to >> >> > > an >> >> > > error must be reverted. >> >> > > >> >> > > On Wed, 14 Apr 2021 at 20:00, Denis Mekhanikov >> >> > > <dmekhani...@gmail.com> >> >> > > wrote: >> >> > > > >> >> > > > Huge +1 to this. >> >> > > > >> >> > > > I've already brought up this topic in the past: >> >> > > > >> >> > > >> >> > >> >> >> http://apache-ignite-developers.2346864.n4.nabble.com/Bots-on-dev-list-td34406.html >> >> > > > I hope some day newcomers won't need to set up their email >> >> > > > filters >> >> when >> >> > > > they come to the developers list. >> >> > > > >> >> > > > Denis >> >> > > > >> >> > > > ср, 14 апр. 2021 г. в 18:07, Atri Sharma <a...@apache.org>: >> >> > > > >> >> > > > > +1 to move issues to the issues list. >> >> > > > > >> >> > > > > For MTCGA, maybe build@? >> >> > > > > >> >> > > > > On Wed, Apr 14, 2021 at 8:35 PM Ilya Kasnacheev >> >> > > > > <il...@apache.org> >> >> > > wrote: >> >> > > > > > >> >> > > > > > Hello! >> >> > > > > > >> >> > > > > > We have a discussion on how to ensure best engagement in >> >> > > > > > dev@ >> >> > list, >> >> > > and >> >> > > > > it >> >> > > > > > seems that Issue Created emails from IGNITE project consume >> >> > > > > > a >> >> > > > > > lot >> >> > of >> >> > > > > screen >> >> > > > > > space, it's hard to spot genuine discussions in >> >> > > > > > https://lists.apache.org/list.html?dev@ignite.apache.org for >> >> > > example. >> >> > > > > > >> >> > > > > > We already have issues@ mailing list. I propose that we stop >> >> > > sending any >> >> > > > > > JIRA emails to dev@. If anyone wishes to get just Created >> >> emails, >> >> > > they >> >> > > > > can >> >> > > > > > subscribe to these messages in their JIRA account settings. >> >> > > > > > I >> >> > imagine >> >> > > > > most >> >> > > > > > of you already filter these messages out, so you may need to >> >> adjust >> >> > > your >> >> > > > > > filters slightly. >> >> > > > > > >> >> > > > > > A distant second is MTCGA messages, which are also >> >> > > > > > autogenerated >> >> > and >> >> > > not >> >> > > > > > informative for most readers of the channel, since they are >> >> > > > > > at >> >> best >> >> > > > > > targeted at a single committer and at worst flaky. >> >> > > > > > >> >> > > > > > Where could we move those? What is your opinion here, on >> >> > > > > > both >> >> > issues? >> >> > > > > > >> >> > > > > > Regards, >> >> > > > > >> >> > > > > -- >> >> > > > > Regards, >> >> > > > > >> >> > > > > Atri >> >> > > > > Apache Concerted >> >> > > > > >> >> > > >> >> > >> >> >> > >> >> >> -- >> >> Best regards, >> Ivan Pavlukhin >> > -- Best regards, Ivan Pavlukhin
