You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pekko.apache.org by "Claude Warren, Jr" <cl...@aiven.io.INVALID> on 2022/11/03 08:25:30 UTC
[Proposal][Discuss] Create a commits email list
Currently the commits from git are getting added to the dev email list
creating a lot of noise.
This proposal is to create a commits@pekko.apache.org email list and have
all git messages go there.
Re: [Proposal][Discuss] Create a commits email list
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
+1
Easier to filter ;))
Regards
JB
On Thu, Nov 3, 2022 at 9:25 AM Claude Warren, Jr
<cl...@aiven.io.invalid> 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 commits@pekko.apache.org email list and have
> all git messages go there.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
For additional commands, e-mail: dev-help@pekko.apache.org
Re: [Proposal][Discuss] Create a commits email list
Posted by Jean-Luc Deprez <Je...@gmail.com>.
While effective, it doesn't feel quite right.
The dev list should be consumable, without needing to resort to that.
I fear it's also causing noise towards IPMC/mentors, which e.g. have not
responded to the package name discussion.
On Sat, Nov 5, 2022, 18:12 Sean Glover <se...@seanglover.com> wrote:
> In the meantime I'm using a gmail filter for this list: (
> to:dev@pekko.apache.org) -(from:git@apache.org)
>
> On Sat, Nov 5, 2022 at 6:13 AM Greg Methvin <gr...@apache.org> wrote:
>
> > 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 <fa...@gmail.com> 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/list.html?notifications@linkis.apache.org
> > >
> > > 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 <gr...@apache.org> 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 <fa...@gmail.com> 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
> > > > > <ma...@aiven.io.invalid> 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 <
> > > JeanLuc.Deprez@gmail.com
> > > > > >
> > > > > > 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 <fa...@gmail.com>
> > 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 <fanningpj@gmail.com
> >
> > > wrote:
> > > > > > > > >
> > > > > > > > >
> https://lists.apache.org/list.html?commits@pekko.apache.org
> > > has
> > > > > commit
> > > > > > > > > emails already
> > > > > > > > >
> > > > > > > > > Could someone provide an actual email that they don't want
> to
> > > > > appear
> > > > > > > > > on the
> > https://lists.apache.org/list.html?dev@pekko.apache.org
> > > > > mailing
> > > > > > > > > list?
> > > > > > > > >
> > > > > > > > > Is it the Github Pull Request messages that people are
> > unhappy
> > > > > about?
> > > > > > > > >
> > > > > > > > > On Thu, 3 Nov 2022 at 09:52, PJ Fanning <
> fanningpj@gmail.com
> > >
> > > > > 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
> > > > > > > > > > <cl...@aiven.io.invalid> wrote:
> > > > > > > > > > >
> > > > > > > > > > > Actually, I went back and looked, we already have a
> > > > > > > > commits@pekko.apache.org
> > > > > > > > > > > mailinglist, we just have to redirect to it.
> > > > > > > > > > >
> > > > > > > > > > > On Thu, Nov 3, 2022 at 8:38 AM Andreas Gabor <
> > > antex@apache.org
> > > > > >
> > > > > > > > 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
> > > github@pekko.apache.org
> > > > > > > > <mailto:
> > > > > > > > > > > > github@pekko.apache.org> seems more appropriate? (As
> > > it’s
> > > > > not
> > > > > > > just
> > > > > > > > > > > > commits)
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > > On 3. Nov 2022, at 09:32, Greg Methvin <
> > > gregm@apache.org>
> > > > > > > wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > > +1
> > > > > > > > > > > > >
> > > > > > > > > > > > > Let's keep the dev mailing list for real
> discussion.
> > > > > > > > > > > > >
> > > > > > > > > > > > > On Thu, Nov 3, 2022 at 1:25 AM Claude Warren, Jr
> > > > > > > > > > > > > <cl...@aiven.io.invalid> 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
> > commits@pekko.apache.org
> > > > > email
> > > > > > > > list and
> > > > > > > > > > > > have
> > > > > > > > > > > > >> all git messages go there.
> > > > > > > > > > > > >>
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > ---------------------------------------------------------------------
> > > > > > > > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> > > > > > > > For additional commands, e-mail: dev-help@pekko.apache.org
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > >
> > > > > > 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:* matthew.dedetrich@aiven.io
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> > > > > For additional commands, e-mail: dev-help@pekko.apache.org
> > > > >
> > > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> > > For additional commands, e-mail: dev-help@pekko.apache.org
> > >
> > >
> >
>
Re: [Proposal][Discuss] Create a commits email list
Posted by Sean Glover <se...@seanglover.com>.
In the meantime I'm using a gmail filter for this list: (
to:dev@pekko.apache.org) -(from:git@apache.org)
On Sat, Nov 5, 2022 at 6:13 AM Greg Methvin <gr...@apache.org> wrote:
> 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 <fa...@gmail.com> 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/list.html?notifications@linkis.apache.org
> >
> > 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 <gr...@apache.org> 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 <fa...@gmail.com> 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
> > > > <ma...@aiven.io.invalid> 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 <
> > JeanLuc.Deprez@gmail.com
> > > > >
> > > > > 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 <fa...@gmail.com>
> 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 <fa...@gmail.com>
> > wrote:
> > > > > > > >
> > > > > > > > https://lists.apache.org/list.html?commits@pekko.apache.org
> > has
> > > > commit
> > > > > > > > emails already
> > > > > > > >
> > > > > > > > Could someone provide an actual email that they don't want to
> > > > appear
> > > > > > > > on the
> https://lists.apache.org/list.html?dev@pekko.apache.org
> > > > mailing
> > > > > > > > list?
> > > > > > > >
> > > > > > > > Is it the Github Pull Request messages that people are
> unhappy
> > > > about?
> > > > > > > >
> > > > > > > > On Thu, 3 Nov 2022 at 09:52, PJ Fanning <fanningpj@gmail.com
> >
> > > > 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
> > > > > > > > > <cl...@aiven.io.invalid> wrote:
> > > > > > > > > >
> > > > > > > > > > Actually, I went back and looked, we already have a
> > > > > > > commits@pekko.apache.org
> > > > > > > > > > mailinglist, we just have to redirect to it.
> > > > > > > > > >
> > > > > > > > > > On Thu, Nov 3, 2022 at 8:38 AM Andreas Gabor <
> > antex@apache.org
> > > > >
> > > > > > > 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
> > github@pekko.apache.org
> > > > > > > <mailto:
> > > > > > > > > > > github@pekko.apache.org> seems more appropriate? (As
> > it’s
> > > > not
> > > > > > just
> > > > > > > > > > > commits)
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > > On 3. Nov 2022, at 09:32, Greg Methvin <
> > gregm@apache.org>
> > > > > > wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > +1
> > > > > > > > > > > >
> > > > > > > > > > > > Let's keep the dev mailing list for real discussion.
> > > > > > > > > > > >
> > > > > > > > > > > > On Thu, Nov 3, 2022 at 1:25 AM Claude Warren, Jr
> > > > > > > > > > > > <cl...@aiven.io.invalid> 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
> commits@pekko.apache.org
> > > > email
> > > > > > > list and
> > > > > > > > > > > have
> > > > > > > > > > > >> all git messages go there.
> > > > > > > > > > > >>
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > >
> > > > > > >
> > ---------------------------------------------------------------------
> > > > > > > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> > > > > > > For additional commands, e-mail: dev-help@pekko.apache.org
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > >
> > > > > 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:* matthew.dedetrich@aiven.io
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> > > > For additional commands, e-mail: dev-help@pekko.apache.org
> > > >
> > > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> > For additional commands, e-mail: dev-help@pekko.apache.org
> >
> >
>
Re: [Proposal][Discuss] Create a commits email list
Posted by Greg Methvin <gr...@apache.org>.
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 <fa...@gmail.com> 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/list.html?notifications@linkis.apache.org
>
> 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 <gr...@apache.org> 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 <fa...@gmail.com> 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
> > > <ma...@aiven.io.invalid> 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 <
> JeanLuc.Deprez@gmail.com
> > > >
> > > > 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 <fa...@gmail.com> 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 <fa...@gmail.com>
> wrote:
> > > > > > >
> > > > > > > https://lists.apache.org/list.html?commits@pekko.apache.org
> has
> > > commit
> > > > > > > emails already
> > > > > > >
> > > > > > > Could someone provide an actual email that they don't want to
> > > appear
> > > > > > > on the https://lists.apache.org/list.html?dev@pekko.apache.org
> > > mailing
> > > > > > > list?
> > > > > > >
> > > > > > > Is it the Github Pull Request messages that people are unhappy
> > > about?
> > > > > > >
> > > > > > > On Thu, 3 Nov 2022 at 09:52, PJ Fanning <fa...@gmail.com>
> > > 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
> > > > > > > > <cl...@aiven.io.invalid> wrote:
> > > > > > > > >
> > > > > > > > > Actually, I went back and looked, we already have a
> > > > > > commits@pekko.apache.org
> > > > > > > > > mailinglist, we just have to redirect to it.
> > > > > > > > >
> > > > > > > > > On Thu, Nov 3, 2022 at 8:38 AM Andreas Gabor <
> antex@apache.org
> > > >
> > > > > > 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
> github@pekko.apache.org
> > > > > > <mailto:
> > > > > > > > > > github@pekko.apache.org> seems more appropriate? (As
> it’s
> > > not
> > > > > just
> > > > > > > > > > commits)
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > > On 3. Nov 2022, at 09:32, Greg Methvin <
> gregm@apache.org>
> > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > +1
> > > > > > > > > > >
> > > > > > > > > > > Let's keep the dev mailing list for real discussion.
> > > > > > > > > > >
> > > > > > > > > > > On Thu, Nov 3, 2022 at 1:25 AM Claude Warren, Jr
> > > > > > > > > > > <cl...@aiven.io.invalid> 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 commits@pekko.apache.org
> > > email
> > > > > > list and
> > > > > > > > > > have
> > > > > > > > > > >> all git messages go there.
> > > > > > > > > > >>
> > > > > > > > > >
> > > > > > > > > >
> > > > > >
> > > > > >
> ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> > > > > > For additional commands, e-mail: dev-help@pekko.apache.org
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > >
> > > > 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:* matthew.dedetrich@aiven.io
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> > > For additional commands, e-mail: dev-help@pekko.apache.org
> > >
> > >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> For additional commands, e-mail: dev-help@pekko.apache.org
>
>
Re: [Proposal][Discuss] Create a commits email list
Posted by PJ Fanning <fa...@gmail.com>.
'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/list.html?notifications@linkis.apache.org
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 <gr...@apache.org> 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 <fa...@gmail.com> 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
> > <ma...@aiven.io.invalid> 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 <JeanLuc.Deprez@gmail.com
> > >
> > > 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 <fa...@gmail.com> 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 <fa...@gmail.com> wrote:
> > > > > >
> > > > > > https://lists.apache.org/list.html?commits@pekko.apache.org has
> > commit
> > > > > > emails already
> > > > > >
> > > > > > Could someone provide an actual email that they don't want to
> > appear
> > > > > > on the https://lists.apache.org/list.html?dev@pekko.apache.org
> > mailing
> > > > > > list?
> > > > > >
> > > > > > Is it the Github Pull Request messages that people are unhappy
> > about?
> > > > > >
> > > > > > On Thu, 3 Nov 2022 at 09:52, PJ Fanning <fa...@gmail.com>
> > 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
> > > > > > > <cl...@aiven.io.invalid> wrote:
> > > > > > > >
> > > > > > > > Actually, I went back and looked, we already have a
> > > > > commits@pekko.apache.org
> > > > > > > > mailinglist, we just have to redirect to it.
> > > > > > > >
> > > > > > > > On Thu, Nov 3, 2022 at 8:38 AM Andreas Gabor <antex@apache.org
> > >
> > > > > 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 github@pekko.apache.org
> > > > > <mailto:
> > > > > > > > > github@pekko.apache.org> seems more appropriate? (As it’s
> > not
> > > > just
> > > > > > > > > commits)
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > > On 3. Nov 2022, at 09:32, Greg Methvin <gr...@apache.org>
> > > > wrote:
> > > > > > > > > >
> > > > > > > > > > +1
> > > > > > > > > >
> > > > > > > > > > Let's keep the dev mailing list for real discussion.
> > > > > > > > > >
> > > > > > > > > > On Thu, Nov 3, 2022 at 1:25 AM Claude Warren, Jr
> > > > > > > > > > <cl...@aiven.io.invalid> 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 commits@pekko.apache.org
> > email
> > > > > list and
> > > > > > > > > have
> > > > > > > > > >> all git messages go there.
> > > > > > > > > >>
> > > > > > > > >
> > > > > > > > >
> > > > >
> > > > > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> > > > > For additional commands, e-mail: dev-help@pekko.apache.org
> > > > >
> > > > >
> > > >
> > >
> > >
> > > --
> > >
> > > 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:* matthew.dedetrich@aiven.io
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> > For additional commands, e-mail: dev-help@pekko.apache.org
> >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
For additional commands, e-mail: dev-help@pekko.apache.org
Re: [Proposal][Discuss] Create a commits email list
Posted by Greg Methvin <gr...@apache.org>.
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 <fa...@gmail.com> 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
> <ma...@aiven.io.invalid> 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 <JeanLuc.Deprez@gmail.com
> >
> > 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 <fa...@gmail.com> 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 <fa...@gmail.com> wrote:
> > > > >
> > > > > https://lists.apache.org/list.html?commits@pekko.apache.org has
> commit
> > > > > emails already
> > > > >
> > > > > Could someone provide an actual email that they don't want to
> appear
> > > > > on the https://lists.apache.org/list.html?dev@pekko.apache.org
> mailing
> > > > > list?
> > > > >
> > > > > Is it the Github Pull Request messages that people are unhappy
> about?
> > > > >
> > > > > On Thu, 3 Nov 2022 at 09:52, PJ Fanning <fa...@gmail.com>
> 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
> > > > > > <cl...@aiven.io.invalid> wrote:
> > > > > > >
> > > > > > > Actually, I went back and looked, we already have a
> > > > commits@pekko.apache.org
> > > > > > > mailinglist, we just have to redirect to it.
> > > > > > >
> > > > > > > On Thu, Nov 3, 2022 at 8:38 AM Andreas Gabor <antex@apache.org
> >
> > > > 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 github@pekko.apache.org
> > > > <mailto:
> > > > > > > > github@pekko.apache.org> seems more appropriate? (As it’s
> not
> > > just
> > > > > > > > commits)
> > > > > > > >
> > > > > > > >
> > > > > > > > > On 3. Nov 2022, at 09:32, Greg Methvin <gr...@apache.org>
> > > wrote:
> > > > > > > > >
> > > > > > > > > +1
> > > > > > > > >
> > > > > > > > > Let's keep the dev mailing list for real discussion.
> > > > > > > > >
> > > > > > > > > On Thu, Nov 3, 2022 at 1:25 AM Claude Warren, Jr
> > > > > > > > > <cl...@aiven.io.invalid> 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 commits@pekko.apache.org
> email
> > > > list and
> > > > > > > > have
> > > > > > > > >> all git messages go there.
> > > > > > > > >>
> > > > > > > >
> > > > > > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> > > > For additional commands, e-mail: dev-help@pekko.apache.org
> > > >
> > > >
> > >
> >
> >
> > --
> >
> > 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:* matthew.dedetrich@aiven.io
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> For additional commands, e-mail: dev-help@pekko.apache.org
>
>
Re: [Proposal][Discuss] Create a commits email list
Posted by PJ Fanning <fa...@gmail.com>.
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
<ma...@aiven.io.invalid> 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 <Je...@gmail.com>
> 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 <fa...@gmail.com> 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 <fa...@gmail.com> wrote:
> > > >
> > > > https://lists.apache.org/list.html?commits@pekko.apache.org has commit
> > > > emails already
> > > >
> > > > Could someone provide an actual email that they don't want to appear
> > > > on the https://lists.apache.org/list.html?dev@pekko.apache.org mailing
> > > > list?
> > > >
> > > > Is it the Github Pull Request messages that people are unhappy about?
> > > >
> > > > On Thu, 3 Nov 2022 at 09:52, PJ Fanning <fa...@gmail.com> 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
> > > > > <cl...@aiven.io.invalid> wrote:
> > > > > >
> > > > > > Actually, I went back and looked, we already have a
> > > commits@pekko.apache.org
> > > > > > mailinglist, we just have to redirect to it.
> > > > > >
> > > > > > On Thu, Nov 3, 2022 at 8:38 AM Andreas Gabor <an...@apache.org>
> > > 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 github@pekko.apache.org
> > > <mailto:
> > > > > > > github@pekko.apache.org> seems more appropriate? (As it’s not
> > just
> > > > > > > commits)
> > > > > > >
> > > > > > >
> > > > > > > > On 3. Nov 2022, at 09:32, Greg Methvin <gr...@apache.org>
> > wrote:
> > > > > > > >
> > > > > > > > +1
> > > > > > > >
> > > > > > > > Let's keep the dev mailing list for real discussion.
> > > > > > > >
> > > > > > > > On Thu, Nov 3, 2022 at 1:25 AM Claude Warren, Jr
> > > > > > > > <cl...@aiven.io.invalid> 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 commits@pekko.apache.org email
> > > list and
> > > > > > > have
> > > > > > > >> all git messages go there.
> > > > > > > >>
> > > > > > >
> > > > > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> > > For additional commands, e-mail: dev-help@pekko.apache.org
> > >
> > >
> >
>
>
> --
>
> 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:* matthew.dedetrich@aiven.io
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
For additional commands, e-mail: dev-help@pekko.apache.org
Re: [Proposal][Discuss] Create a commits email list
Posted by Matthew Benedict de Detrich <ma...@aiven.io.INVALID>.
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 <Je...@gmail.com>
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 <fa...@gmail.com> 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 <fa...@gmail.com> wrote:
> > >
> > > https://lists.apache.org/list.html?commits@pekko.apache.org has commit
> > > emails already
> > >
> > > Could someone provide an actual email that they don't want to appear
> > > on the https://lists.apache.org/list.html?dev@pekko.apache.org mailing
> > > list?
> > >
> > > Is it the Github Pull Request messages that people are unhappy about?
> > >
> > > On Thu, 3 Nov 2022 at 09:52, PJ Fanning <fa...@gmail.com> 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
> > > > <cl...@aiven.io.invalid> wrote:
> > > > >
> > > > > Actually, I went back and looked, we already have a
> > commits@pekko.apache.org
> > > > > mailinglist, we just have to redirect to it.
> > > > >
> > > > > On Thu, Nov 3, 2022 at 8:38 AM Andreas Gabor <an...@apache.org>
> > 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 github@pekko.apache.org
> > <mailto:
> > > > > > github@pekko.apache.org> seems more appropriate? (As it’s not
> just
> > > > > > commits)
> > > > > >
> > > > > >
> > > > > > > On 3. Nov 2022, at 09:32, Greg Methvin <gr...@apache.org>
> wrote:
> > > > > > >
> > > > > > > +1
> > > > > > >
> > > > > > > Let's keep the dev mailing list for real discussion.
> > > > > > >
> > > > > > > On Thu, Nov 3, 2022 at 1:25 AM Claude Warren, Jr
> > > > > > > <cl...@aiven.io.invalid> 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 commits@pekko.apache.org email
> > list and
> > > > > > have
> > > > > > >> all git messages go there.
> > > > > > >>
> > > > > >
> > > > > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> > For additional commands, e-mail: dev-help@pekko.apache.org
> >
> >
>
--
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:* matthew.dedetrich@aiven.io
Re: [Proposal][Discuss] Create a commits email list
Posted by Jean-Luc Deprez <Je...@gmail.com>.
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 <fa...@gmail.com> 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 <fa...@gmail.com> wrote:
> >
> > https://lists.apache.org/list.html?commits@pekko.apache.org has commit
> > emails already
> >
> > Could someone provide an actual email that they don't want to appear
> > on the https://lists.apache.org/list.html?dev@pekko.apache.org mailing
> > list?
> >
> > Is it the Github Pull Request messages that people are unhappy about?
> >
> > On Thu, 3 Nov 2022 at 09:52, PJ Fanning <fa...@gmail.com> 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
> > > <cl...@aiven.io.invalid> wrote:
> > > >
> > > > Actually, I went back and looked, we already have a
> commits@pekko.apache.org
> > > > mailinglist, we just have to redirect to it.
> > > >
> > > > On Thu, Nov 3, 2022 at 8:38 AM Andreas Gabor <an...@apache.org>
> 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 github@pekko.apache.org
> <mailto:
> > > > > github@pekko.apache.org> seems more appropriate? (As it’s not just
> > > > > commits)
> > > > >
> > > > >
> > > > > > On 3. Nov 2022, at 09:32, Greg Methvin <gr...@apache.org> wrote:
> > > > > >
> > > > > > +1
> > > > > >
> > > > > > Let's keep the dev mailing list for real discussion.
> > > > > >
> > > > > > On Thu, Nov 3, 2022 at 1:25 AM Claude Warren, Jr
> > > > > > <cl...@aiven.io.invalid> 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 commits@pekko.apache.org email
> list and
> > > > > have
> > > > > >> all git messages go there.
> > > > > >>
> > > > >
> > > > >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> For additional commands, e-mail: dev-help@pekko.apache.org
>
>
Re: [Proposal][Discuss] Create a commits email list
Posted by PJ Fanning <fa...@gmail.com>.
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 <fa...@gmail.com> wrote:
>
> https://lists.apache.org/list.html?commits@pekko.apache.org has commit
> emails already
>
> Could someone provide an actual email that they don't want to appear
> on the https://lists.apache.org/list.html?dev@pekko.apache.org mailing
> list?
>
> Is it the Github Pull Request messages that people are unhappy about?
>
> On Thu, 3 Nov 2022 at 09:52, PJ Fanning <fa...@gmail.com> 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
> > <cl...@aiven.io.invalid> wrote:
> > >
> > > Actually, I went back and looked, we already have a commits@pekko.apache.org
> > > mailinglist, we just have to redirect to it.
> > >
> > > On Thu, Nov 3, 2022 at 8:38 AM Andreas Gabor <an...@apache.org> 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 github@pekko.apache.org <mailto:
> > > > github@pekko.apache.org> seems more appropriate? (As it’s not just
> > > > commits)
> > > >
> > > >
> > > > > On 3. Nov 2022, at 09:32, Greg Methvin <gr...@apache.org> wrote:
> > > > >
> > > > > +1
> > > > >
> > > > > Let's keep the dev mailing list for real discussion.
> > > > >
> > > > > On Thu, Nov 3, 2022 at 1:25 AM Claude Warren, Jr
> > > > > <cl...@aiven.io.invalid> 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 commits@pekko.apache.org email list and
> > > > have
> > > > >> all git messages go there.
> > > > >>
> > > >
> > > >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
For additional commands, e-mail: dev-help@pekko.apache.org
Re: [Proposal][Discuss] Create a commits email list
Posted by PJ Fanning <fa...@gmail.com>.
https://lists.apache.org/list.html?commits@pekko.apache.org has commit
emails already
Could someone provide an actual email that they don't want to appear
on the https://lists.apache.org/list.html?dev@pekko.apache.org mailing
list?
Is it the Github Pull Request messages that people are unhappy about?
On Thu, 3 Nov 2022 at 09:52, PJ Fanning <fa...@gmail.com> 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
> <cl...@aiven.io.invalid> wrote:
> >
> > Actually, I went back and looked, we already have a commits@pekko.apache.org
> > mailinglist, we just have to redirect to it.
> >
> > On Thu, Nov 3, 2022 at 8:38 AM Andreas Gabor <an...@apache.org> 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 github@pekko.apache.org <mailto:
> > > github@pekko.apache.org> seems more appropriate? (As it’s not just
> > > commits)
> > >
> > >
> > > > On 3. Nov 2022, at 09:32, Greg Methvin <gr...@apache.org> wrote:
> > > >
> > > > +1
> > > >
> > > > Let's keep the dev mailing list for real discussion.
> > > >
> > > > On Thu, Nov 3, 2022 at 1:25 AM Claude Warren, Jr
> > > > <cl...@aiven.io.invalid> 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 commits@pekko.apache.org email list and
> > > have
> > > >> all git messages go there.
> > > >>
> > >
> > >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
For additional commands, e-mail: dev-help@pekko.apache.org
Re: [Proposal][Discuss] Create a commits email list
Posted by PJ Fanning <fa...@gmail.com>.
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
<cl...@aiven.io.invalid> wrote:
>
> Actually, I went back and looked, we already have a commits@pekko.apache.org
> mailinglist, we just have to redirect to it.
>
> On Thu, Nov 3, 2022 at 8:38 AM Andreas Gabor <an...@apache.org> 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 github@pekko.apache.org <mailto:
> > github@pekko.apache.org> seems more appropriate? (As it’s not just
> > commits)
> >
> >
> > > On 3. Nov 2022, at 09:32, Greg Methvin <gr...@apache.org> wrote:
> > >
> > > +1
> > >
> > > Let's keep the dev mailing list for real discussion.
> > >
> > > On Thu, Nov 3, 2022 at 1:25 AM Claude Warren, Jr
> > > <cl...@aiven.io.invalid> 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 commits@pekko.apache.org email list and
> > have
> > >> all git messages go there.
> > >>
> >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
For additional commands, e-mail: dev-help@pekko.apache.org
Re: [Proposal][Discuss] Create a commits email list
Posted by "Claude Warren, Jr" <cl...@aiven.io.INVALID>.
Actually, I went back and looked, we already have a commits@pekko.apache.org
mailinglist, we just have to redirect to it.
On Thu, Nov 3, 2022 at 8:38 AM Andreas Gabor <an...@apache.org> 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 github@pekko.apache.org <mailto:
> github@pekko.apache.org> seems more appropriate? (As it’s not just
> commits)
>
>
> > On 3. Nov 2022, at 09:32, Greg Methvin <gr...@apache.org> wrote:
> >
> > +1
> >
> > Let's keep the dev mailing list for real discussion.
> >
> > On Thu, Nov 3, 2022 at 1:25 AM Claude Warren, Jr
> > <cl...@aiven.io.invalid> 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 commits@pekko.apache.org email list and
> have
> >> all git messages go there.
> >>
>
>
Re: [Proposal][Discuss] Create a commits email list
Posted by Andreas Gabor <an...@apache.org>.
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 github@pekko.apache.org <ma...@pekko.apache.org> seems more appropriate? (As it’s not just commits)
> On 3. Nov 2022, at 09:32, Greg Methvin <gr...@apache.org> wrote:
>
> +1
>
> Let's keep the dev mailing list for real discussion.
>
> On Thu, Nov 3, 2022 at 1:25 AM Claude Warren, Jr
> <cl...@aiven.io.invalid> 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 commits@pekko.apache.org email list and have
>> all git messages go there.
>>
Re: [Proposal][Discuss] Create a commits email list
Posted by Greg Methvin <gr...@apache.org>.
+1
Let's keep the dev mailing list for real discussion.
On Thu, Nov 3, 2022 at 1:25 AM Claude Warren, Jr
<cl...@aiven.io.invalid> 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 commits@pekko.apache.org email list and have
> all git messages go there.
>
Re: [Proposal][Discuss] Create a commits email list
Posted by Matthew Benedict de Detrich <ma...@aiven.io.INVALID>.
Definite +1 from me, this is unneeded noise and we already have a commits mailing list (which I assume is for this purpose).
--
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: matthew.dedetrich@aiven.io
On 3. Nov 2022 at 09:26 +0100, Claude Warren, Jr <cl...@aiven.io.invalid>, 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 commits@pekko.apache.org email list and have
> all git messages go there.