nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joe Skora <jsk...@gmail.com>
Subject Re: Github mails
Date Wed, 29 Jun 2016 12:06:17 GMT
+1

On Tue, Jun 28, 2016 at 12:37 PM, Joe Witt <joe.witt@gmail.com> wrote:

> Sean,
>
> Make sense and I believe it aligns with Lars original intent and
> suggestion.
>
> I've captured these items here
> https://issues.apache.org/jira/browse/NIFI-2137
>
> But in summary will carry out the following tasks pending any further
> recommendations that might alter that.
>
> 1) Request INFRA to create issues@nifi.a.o
> 2) Request INFRA to send all Github notifications to issues@nifi.a.o
> 3) Request INFRA to send all JIRA notifications to issues@nifi.a.o
> 4) Document on webpage for mailing lists the purpose of each mailing
> list (dev, commits, issues, users)
> 5) Document on webpage for mailing lists a link to
> https://lists.apache.org/list.html?nifi.apache.org
>
> Thanks
> Joe
>
> On Tue, Jun 28, 2016 at 8:17 AM, Sean Busbey <busbey@apache.org> wrote:
> > My usual concern with sending github notifications off of dev@ is that
> > not as many folks watch lists that are defined as a dumping ground for
> > automated messages (like a commits@ or notifications@).
> >
> > However, I usually think of github notifications like JIRA
> > notifications. AFAICT we already send all of the JIRA traffic to
> > commits@, so it makes sense for folks who want that level of detail on
> > project implementation to have a single place to go.
> >
> > At the same time, it might be hard for a new person to realize all
> > these things are going to commits@. Maybe we could add a brief
> > description to our mailing list page[1] of when folks should look to
> > the different lists?
> >
> > There's enough project activity now on jira/github/commits that I'd be
> > in favor of splitting out things that aren't actually commits to a
> > notifications@ (or issues@ or whatever).
> >
> > Also, now that lists.apache is live, I think we should link to it as
> > the "user friendly" list UI rather than nabble[2]. Folks do need an
> > @apache email address to post through lists.apache, but I don't know
> > how much we value the "ease of posting" feature of nabble.
> >
> > [1]: http://nifi.apache.org/mailing_lists.html
> > [2]: https://lists.apache.org/list.html?dev@nifi.apache.org
> >
> > On Mon, Jun 27, 2016 at 2:31 AM, Lars Francke <lars.francke@gmail.com>
> wrote:
> >> Hi everyone,
> >>
> >> there's lots of mails from the Github integration in the dev@ mailing
> list.
> >> It's getting pretty overwhelming. Yes I've created a filter but everyone
> >> would need to do that. Other projects have opted to move these kind of
> >> things to a "issues" mailing list.
> >>
> >> What do you think about that?
> >>
> >> Cheers,
> >> Lars
>

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