I started a new thread to discuss moving GitHub discussion
notifications to the commits@ mailing list here:
https://lists.apache.org/thread/ny8cz9fj4lwk752m4nylpzdg35lwfn6v.

I should have continued on this thread, sorry for breaking it out.

- Michael

On Fri, Dec 16, 2022 at 1:12 AM tison <wander4...@gmail.com> wrote:
>
> And I can support the statement that either open-ended discussions or
> questions traffics are currently most on users@ bias.
>
> Best,
> tison.
>
>
> tison <wander4...@gmail.com> 于2022年12月16日周五 15:11写道:
>
> > Hi Michael,
> >
> > For my personal mailbox, on Gmail, I have a filter 'to:(
> > dev@pulsar.apache.org) subject:GitHub' and then all related emails are
> > filtered out. It can produce false positives but not hurt so far.
> >
> > Best,
> > tison.
> >
> >
> > Michael Marshall <mmarsh...@apache.org> 于2022年12月16日周五 14:35写道:
> >
> >> Do we provide users any guidelines for when to open an issue vs start
> >> a discussion? If we cannot control the discussion notifications to
> >> this list, I think we should prefer issues for now. The extra
> >> notifications are making it challenging for me to keep up with this
> >> list.
> >>
> >> In my opinion, open ended discussions belong on the users@ or dev@
> >> list. I thought we adopted discussions as a way for users to ask
> >> questions about ambiguous topics, especially because some users are on
> >> github but are not on our users@ mailing list.
> >>
> >> Thanks,
> >> Michael
> >>
> >> On Tue, Dec 13, 2022 at 7:48 PM tison <wander4...@gmail.com> wrote:
> >> >
> >> > > can we set it not to sync
> >> >
> >> > It seems the current .asf.yaml and it's underneath tech doesn't support
> >> > such fine-grained control.
> >> >
> >> > I ever talk to the author about configuring in category level but it's
> >> > still unsupported yet also.
> >> >
> >> > The source code, IIRC, is hosted at
> >> > https://github.com/apache/infrastructure-github-discussions-notifier
> >> >
> >> > Best,
> >> > tison.
> >> >
> >> >
> >> > Yu <li...@apache.org> 于2022年12月12日周一 17:34写道:
> >> >
> >> > > Hi tison,
> >> > >
> >> > > Thanks for clearing up various issues and PRs!
> >> > >
> >> > > One quick question:
> >> > > For the "Discussion posts" converted from "Issues", can we set it not
> >> to
> >> > > sync to dev@pulsar.apache.org (since they do not have new
> >> discussions and
> >> > > comments)?
> >> > >
> >> > > Thank you!
> >> > >
> >> > >
> >> > > On Mon, Dec 12, 2022 at 10:30 AM Zili Chen <ti...@apache.org> wrote:
> >> > >
> >> > > > In the Kvrocks community, we meet the same problem and redirect the
> >> mails
> >> > > > to issues@[1].
> >> > > >
> >> > > > Although, three points here:
> >> > > >
> >> > > > 1. Follow the ASF policy all effective discussions should happen on
> >> the
> >> > > > mailing list, while to issues@ should be also "on the list".
> >> > > > 2. For personal mailbox, you can set up a filter.
> >> > > > 3. For https://lists.apache.org/ searching, you may use `-GITBOX'
> >> but it
> >> > > > can filter unexpected mails.
> >> > > >
> >> > > > Best,
> >> > > > tison.
> >> > > >
> >> > > > [1] https://github.com/apache/incubator-kvrocks/pull/1023
> >> > > >
> >> > > > On 2022/12/09 11:45:44 Girish Sharma wrote:
> >> > > > > Hello Pulsar community,
> >> > > > >
> >> > > > > I recently joined this ML. I have been keenly following the RC,
> >> Voting
> >> > > > and
> >> > > > > PIP related email threads so far. I only have one question - is
> >> there a
> >> > > > way
> >> > > > > to disable the emails from GitBox about github discussions?
> >> Mainly for
> >> > > > the
> >> > > > > following reasons:
> >> > > > >
> >> > > > >    1. The GitHub discussions emails from GitBox do not thread
> >> properly
> >> > > as
> >> > > > >    the subject of the email contains unique text like "XYZ
> >> commented on
> >> > > > thread
> >> > > > >    <constant part>"
> >> > > > >    2. There is already a way to subscribe to github discussions
> >> via
> >> > > > GitHub
> >> > > > >    UI so these emails are duplicated.
> >> > > > >
> >> > > > > Regards
> >> > > > > --
> >> > > > > Girish Sharma
> >> > > > >
> >> > > >
> >> > >
> >>
> >

Reply via email to