Yes, it should be available at issues@. We were requested to note this
email down so it does not get forgotten. Would somebody mind documenting it?

-Marco

Am 14.02.2018 6:52 nachm. schrieb "Pedro Larroy" <
pedro.larroy.li...@gmail.com>:

> Is there a new alias to subscribe to get the Jira notifications?
>
> On Wed, Feb 7, 2018 at 7:10 PM, Marco de Abreu
> <marco.g.ab...@googlemail.com> wrote:
> > Ticket is available at
> > https://issues.apache.org/jira/plugins/servlet/mobile#issue/INFRA-15997
> >
> > -Marco
> >
> > Am 07.02.2018 7:09 nachm. schrieb "Suneel Marthi" <smar...@apache.org>:
> >
> >> Most projects have their Jira setup to go to commits@<crappy-project>.
> >> apache.org
> >>
> >> file an infra ticket to make that change for MxNet
> >>
> >> On Wed, Feb 7, 2018 at 12:17 PM, Hen <bay...@apache.org> wrote:
> >>
> >> > The typical approach is to have them sent to a notifications list
> (along
> >> > with CI etc).
> >> >
> >> > Normally that still redirects to dev iirc.
> >> >
> >> > On Wed, Feb 7, 2018 at 03:24 kellen sunderland <
> >> > kellen.sunderl...@gmail.com>
> >> > wrote:
> >> >
> >> > > +1
> >> > >
> >> > > On Feb 7, 2018 2:49 AM, "Marco de Abreu" <
> marco.g.ab...@googlemail.com
> >> >
> >> > > wrote:
> >> > >
> >> > > > Lol, at least Link this thread please to show that the community
> >> > actually
> >> > > > wants this.
> >> > > >
> >> > > > -Marco
> >> > > >
> >> > > > Am 06.02.2018 5:29 nachm. schrieb "Chris Olivier" <
> >> > cjolivie...@gmail.com
> >> > > >:
> >> > > >
> >> > > > > I opened a ticket anyway.  Meh.
> >> > > > >
> >> > > > > On Tue, Feb 6, 2018 at 5:05 PM, Marco de Abreu <
> >> > > > > marco.g.ab...@googlemail.com
> >> > > > > > wrote:
> >> > > > >
> >> > > > > > Haha, we need to have a discussion here first before we can
> make
> >> > the
> >> > > > > > change. I'd like the opinion of the community on this one.
> >> > > > > >
> >> > > > > > -Marco
> >> > > > > >
> >> > > > > > On Tue, Feb 6, 2018 at 5:04 PM, Chris Olivier <
> >> > cjolivie...@gmail.com
> >> > > >
> >> > > > > > wrote:
> >> > > > > >
> >> > > > > > > Please feel free to submit a ticket to Infra to get the
> emails
> >> > > > > disabled.
> >> > > > > > >
> >> > > > > > > Oh yeah...  If we do that, they send us nasty emails...
> >> > > > > > >
> >> > > > > > > Waiting for Sebastian to file a ticket (I pinged on Slack).
> >> > > > > > >
> >> > > > > > >
> >> > > > > > > On Tue, Feb 6, 2018 at 5:00 PM, Marco de Abreu <
> >> > > > > > > marco.g.ab...@googlemail.com
> >> > > > > > > > wrote:
> >> > > > > > >
> >> > > > > > > > Hello,
> >> > > > > > > >
> >> > > > > > > > while I highly appreciate the usage of JIRA within MXNet,
> I
> >> > guess
> >> > > > > that
> >> > > > > > > I'm
> >> > > > > > > > not the only one bothered by the high number of JIRA
> >> > > notifications
> >> > > > on
> >> > > > > > > dev@
> >> > > > > > > > .
> >> > > > > > > > While everybody has the chance to create a filter for
> these
> >> > > > message,
> >> > > > > > I'm
> >> > > > > > > > afraid that new developers and people viewing the archive
> are
> >> > > > getting
> >> > > > > > > > pretty frustrated as actual conversations are pushed to
> the
> >> > side
> >> > > by
> >> > > > > all
> >> > > > > > > the
> >> > > > > > > > communication happening on the JIRA tickets (see [1]).
> >> > Therefor,
> >> > > > I'd
> >> > > > > > > > propose one of the following solutions:
> >> > > > > > > >
> >> > > > > > > > 1. Disable JIRA notifications to dev@ entirely, leading
> to
> >> > only
> >> > > > the
> >> > > > > > > people
> >> > > > > > > > subscribed to a ticket being notified directly.
> >> > > > > > > > 2. Create a separate email list for JIRA in the same way
> as
> >> > [2].
> >> > > > > > > >
> >> > > > > > > > Best regards,
> >> > > > > > > > Marco
> >> > > > > > > >
> >> > > > > > > > [1]: https://lists.apache.org/list.
> html?d...@mxnet.apache.org
> >> > > > > > > > [2]: https://lists.apache.org/list.
> >> > html?comm...@mxnet.apache.org
> >> > > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
>

Reply via email to