celix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexander Broekhuis <a.broekh...@gmail.com>
Subject Re: Send GitHub notifications to new notifications@ list (instead of dev@)
Date Wed, 06 May 2020 06:06:59 GMT
Hi Roy,

Thanks for the reply!

If we can do something about the duplicates, that would be great. I don't
see much added value in both a github AND a gitbox email for the same
stuff...


Op zo 3 mei 2020 om 13:00 schreef Roy Lenferink <rlenferink@apache.org>:

> Hi Alexander,
>
> Thanks for the answer, great input! Answers inline.
>
> On 2020/04/29 21:17:01, Alexander Broekhuis <a.broekhuis@gmail.com>
> wrote:
> > Not saying that I like all the mails to dev, but those mails do contain
> the
> > only discussions we have nowadays (Issues at github and comments on Pull
> > Requests).
> > So I also do see some value in the current way. Is there a way to filter
> > out those mails and keep them coming to dev@?
>
> The only thing we can differ between is issues and pull requests. Indeed
> as a lot of
> communication happens on both issues and pull requests it doesn't make
> sense to differ
> between the two.
>
> We could differ between the celix & celix-site repository [1][2], e.g.
> celix sending all GitHub activity to
> dev@ and celix-site sending notifications to notifications@. But since
> celix-site doesn't have that
> much pull request/issue activity IMO it doesn't really make sense to have
> a separate list for that.
>
> >
> > For this reason for me a -0. We should not forget that the primary way of
> > communication (and decision making and archiving) is the mailinglist [1].
> >
> > Arguably, 'notifications' is also a mailing list, but I'm not sure if we
> do
> > right to the community with that...
>
> My viewpoint was a committer one. In which the duplicate messages can be
> time-consuming
> sometimes. But I definitely agree that I won't help the community if we
> move the activity to a
> separate mailing list. We can leave stuff as it is right now and can
> always re-consider when the
> community and mailing list activity increases.
>
> Maybe I should just spend some time to setup my mail filters :)
>
> [1] https://gitbox.apache.org/schemes.cgi?celix
> [2] https://gitbox.apache.org/schemes.cgi?celix-site
>
> >
> > [1]: http://theapacheway.com/on-list/
> >
> > Op wo 29 apr. 2020 om 21:11 schreef Pepijn Noltes <
> pepijnnoltes@gmail.com>:
> >
> > > Hi Roy,
> > >
> > > Sounds good, +1.
> > >
> > > On Wed, Apr 29, 2020 at 6:58 PM Roy Lenferink <rlenferink@apache.org>
> > > wrote:
> > > >
> > > > Hi all,
> > > >
> > > > Currently all GitHub activity is sent to our dev@ list. I'd like to
> > > propose to change this to a new
> > > > notifications@celix.apache.org list.
> > > >
> > > > This way Celix contributors/watchers on our dev list won't be
> 'spammed'
> > > with all the ongoing GitHub
> > > > traffic and for the people who still want to receive the GitHub
> > > notifications it is opt-in to a separate
> > > > mailing list. It will also be easier to find actual (development
> > > related) discussions when browsing
> > > > through the dev@celix.a.o messages on lists.apache.org [1]. Also,
> when
> > > already watching the GitHub
> > > > repository notifications will be sent twice: once from GitHub, once
> from
> > > the dev list.
> > > >
> > > > Lazy consensus will apply: no objections within the next 72 hours and
> > > I'll request the mailing list.
> > > > Changing the notification scheme is self-serve via the .asf.yaml [2]
> > > >
> > > > Best regards,
> > > > Roy
> > > >
> > > > [1] https://lists.apache.org/list.html?dev@celix.apache.org
> > > > [2] https://s.apache.org/asfyaml-notify
> > >
> >
> >
> > --
> > Met vriendelijke groet,
> >
> > Alexander Broekhuis
> >
>


-- 
Met vriendelijke groet,

Alexander Broekhuis

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message