Joe, thank you for following up on all of this and the others for chiming in!
Sorry for dumping this idea here and then not responding to the thread for a week so again thanks for this! On Sat, Jul 2, 2016 at 12:55 AM, Joe Witt <[email protected]> wrote: > Ok team I put in a request for '[email protected]' and updated > https://issues.apache.org/jira/browse/INFRA-12191# to reflect our > plans. Will now edit the website to document the purpose of each > list. > > Thanks > Joe > > On Wed, Jun 29, 2016 at 5:06 AM, Joe Skora <[email protected]> wrote: > > +1 > > > > On Tue, Jun 28, 2016 at 12:37 PM, Joe Witt <[email protected]> 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 [email protected] > >> 2) Request INFRA to send all Github notifications to [email protected] > >> 3) Request INFRA to send all JIRA notifications to [email protected] > >> 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 <[email protected]> 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/[email protected] > >> > > >> > On Mon, Jun 27, 2016 at 2:31 AM, Lars Francke <[email protected] > > > >> 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 > >> >
