[email protected] should have already existed but not attached to
the github to send notification. We need just to create issues@. But the
question is how to migrate current receivers of the commits and issues
(currently notifications are sent to dev@). If we redirect all the
notifications to the two empty mailing lists without auto migration, then
suddenly everybody will stop receiving those notifications and people will
have to manually add themselves to the two mailing lists.  I don't find a
way to clone and rename. Does anybody have idea on how to solve this
problem?

On Mon, Aug 21, 2023 at 11:55 PM Uwe L. Korn <[email protected]> wrote:

> +1
>
> On Tue, Aug 22, 2023, at 5:29 AM, Gang Wu wrote:
> > +1 on this.
> >
> > We may create the following mailing lists:
> > - [email protected] : notifications from JIRA issues.
> > - [email protected] : notifications from Github PRs and
> comments.
> >
> > This is what the Apache ORC community currently does. Can one of the PMCs
> > do this?
> > Probably we need a formal vote before proceeding.
> > https://infra.apache.org/mailing-list-moderation.html#new-mailing-list
> >
> > Best,
> > Gang
> >
> > On Tue, Aug 22, 2023 at 8:49 AM Xinli shang <[email protected]>
> wrote:
> >
> >> It is a good idea. Thank Antonie for the proposal.
> >>
> >> On Tue, Aug 22, 2023 at 2:03 AM Julien Le Dem
> <[email protected]
> >> >
> >> wrote:
> >>
> >> > +1
> >> >
> >> > On Mon, Aug 21, 2023 at 10:16 AM Antoine Pitrou <[email protected]>
> >> > wrote:
> >> >
> >> > >
> >> > > Hello,
> >> > >
> >> > > I would like to request that automated notifications (from GitHub,
> >> > > Jira... whatever) be sent to a separate mailing-list and GMane
> mirror.
> >> > > Currently, the endless stream of automated notifications in this
> >> > > mailing-list means that discussions between humans quickly get lost
> or
> >> > > even unnoticed by other people.
> >> > >
> >> > > For the record, we did this move in Apache Arrow and never came
> back.
> >> > >
> >> > > Thanks in advance
> >> > >
> >> > > Antoine.
> >> > >
> >> > >
> >> > >
> >> >
> >>
> >>
> >> --
> >> Xinli Shang
> >>
>


-- 
Xinli Shang

Reply via email to