Sure, "commits" for commit notifications and "notifications" for all other notifications sounds fine to me.
On Sat, Nov 5, 2022 at 2:29 AM PJ Fanning <[email protected]> wrote: > 'commits' is one of the standard mailing lists added for all projects. > I suggest we keep that for commit tracking. > > 'notifications' is a mailing list used by a lot of teams for Github > notifications - eg > https://lists.apache.org/[email protected] > > I'd prefer to use names for the mailing lists that match the names in > other projects. If 'notifications' sounds ok, I can request Infra team > to create that list and change the incubator-pekko repo to send Github > issue and PR notifications to that mailing list. > > On Fri, 4 Nov 2022 at 23:36, Greg Methvin <[email protected]> wrote: > > > > Can we just move all the github notifications to the commits@ mailing > list > > (and maybe rename it to github@ or something)? It seems like most of us > > prefer to get the notifications directly from GitHub, so I don't think > > there's much value in splitting them out into separate mailing lists, > > especially since you can just set up mail filters on that list to get > just > > the notifications you want. > > > > > > On Fri, Nov 4, 2022 at 13:03 PJ Fanning <[email protected]> wrote: > > > > > We probably need more mailing lists. If we had an 'issues' list and a > > > 'pullrequests' list then we could keep these emails off the dev list. > > > > > > People could choose to ignore or just dip into the lower priority > > > lists using https://lists.apache.org/ > > > > > > On Fri, 4 Nov 2022 at 19:45, Matthew Benedict de Detrich > > > <[email protected]> wrote: > > > > > > > > Yeah I am also not sure what value this brings considering that > Github > > > > pretty much sends you the exact same notifications, I am at the > point of > > > > putting it into a filter so it goes to ignore. > > > > > > > > On Fri, Nov 4, 2022 at 7:42 PM Jean-Luc Deprez < > [email protected] > > > > > > > > wrote: > > > > > > > > > Anybody else feeling a little swamped with the gitbox notifications > > > still > > > > > going to dev? > > > > > > > > > > Especially because it seems like the goal was to work GH centric, > but > > > if > > > > > you watch in GH + the mailing list, it's a good way to go > completely > > > > > bonkers. > > > > > > > > > > I've also attempted to switch to digest for commits list, but I > can't > > > say I > > > > > have received anything yet, so I wonder with what frequency that > > > happens. > > > > > > > > > > > > > > > > > > > > On Thu, Nov 3, 2022, 10:31 PJ Fanning <[email protected]> wrote: > > > > > > > > > > > I've updated the notifications config on the incubator-pekko git > > > repo. > > > > > > > > > > > > The new config should mean that PR status events (new PR, closed > PR) > > > > > > still go to the dev mailing list. > > > > > > > > > > > > Comments on PRs will be notified to the commits mailing list. > > > > > > > > > > > > In theory, we could get extra mailing lists created. This would > allow > > > > > > for the notifications to be more finely controlled. The downside > is > > > > > > that more mailing lists need to be followed, etc. > > > > > > > > > > > > For now, I think the 3 mailing lists we have is enough. > > > > > > > > > > > > On Thu, 3 Nov 2022 at 10:14, PJ Fanning <[email protected]> > wrote: > > > > > > > > > > > > > > https://lists.apache.org/[email protected] > has > > > commit > > > > > > > emails already > > > > > > > > > > > > > > Could someone provide an actual email that they don't want to > > > appear > > > > > > > on the https://lists.apache.org/[email protected] > > > mailing > > > > > > > list? > > > > > > > > > > > > > > Is it the Github Pull Request messages that people are unhappy > > > about? > > > > > > > > > > > > > > On Thu, 3 Nov 2022 at 09:52, PJ Fanning <[email protected]> > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features > > > > > > > > > > > > > > > > I've added .asf.yaml to all the pekko repos but didn't set > any > > > > > > > > 'notifications' settings. I could try setting one in the main > > > pekko > > > > > > > > repo for commits to see if I can get it right and later roll > out > > > to > > > > > > > > the other repos. > > > > > > > > > > > > > > > > On Thu, 3 Nov 2022 at 09:46, Claude Warren, Jr > > > > > > > > <[email protected]> wrote: > > > > > > > > > > > > > > > > > > Actually, I went back and looked, we already have a > > > > > > [email protected] > > > > > > > > > mailinglist, we just have to redirect to it. > > > > > > > > > > > > > > > > > > On Thu, Nov 3, 2022 at 8:38 AM Andreas Gabor < > [email protected] > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > I haven’t seen any commit related emails or do you mean > those > > > > > > > > > > notifications around PR activities like comments from > GitBox? > > > > > > > > > > > > > > > > > > > > "[GitHub] [incubator-pekko] mdedetrich commented on a > diff in > > > > > pull > > > > > > request > > > > > > > > > > #2: Update and apply scalafmt” > > > > > > > > > > > > > > > > > > > > If yes: I’m already filtering them out as I’m getting the > > > > > > notifications > > > > > > > > > > directly on GitHub but a separate email list would still > make > > > > > > sense. Even > > > > > > > > > > though a more generic address like > [email protected] > > > > > > <mailto: > > > > > > > > > > [email protected]> seems more appropriate? (As > it’s > > > not > > > > > just > > > > > > > > > > commits) > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On 3. Nov 2022, at 09:32, Greg Methvin < > [email protected]> > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > +1 > > > > > > > > > > > > > > > > > > > > > > Let's keep the dev mailing list for real discussion. > > > > > > > > > > > > > > > > > > > > > > On Thu, Nov 3, 2022 at 1:25 AM Claude Warren, Jr > > > > > > > > > > > <[email protected]> wrote: > > > > > > > > > > > > > > > > > > > > > >> Currently the commits from git are getting added to > the > > > dev > > > > > > email list > > > > > > > > > > >> creating a lot of noise. > > > > > > > > > > >> This proposal is to create a [email protected] > > > email > > > > > > list and > > > > > > > > > > have > > > > > > > > > > >> all git messages go there. > > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > To unsubscribe, e-mail: [email protected] > > > > > > For additional commands, e-mail: [email protected] > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > Matthew de Detrich > > > > > > > > *Aiven Deutschland GmbH* > > > > > > > > Immanuelkirchstraße 26, 10405 Berlin > > > > > > > > Amtsgericht Charlottenburg, HRB 209739 B > > > > > > > > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen > > > > > > > > *m:* +491603708037 > > > > > > > > *w:* aiven.io *e:* [email protected] > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
