Hey Matt, To be clear, I’m asking for input on a name amongst those choices.
Also, we shouldn’t be archiving emails so we forget about them. The point is the conversation for the project should happen here and if it’s dev relevant conversation then it should be something that those that don’t have the advantage of operating at GitHub and believing that’s the home for the project still have a chance to participate by sending mails and participating in the conversation for the project, here. That said, I think there’s a simple solution: 1) stand up new list (we can use the mlreq program here, once we agree on the name) https://infra.apache.org/officers/mlreq/ 2) file INFRA JIRA ticket and have ASF GitHub bot send communication to list from #1 Make sense? Agree? Cheers, Chris ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Chris Mattmann, Ph.D. Chief Architect Instrument Software and Science Data Systems Section (398) NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 168-519, Mailstop: 168-527 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Director, Information Retrieval and Data Science Group (IRDS) Adjunct Associate Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA WWW: http://irds.usc.edu/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ On 5/26/16, 11:23 AM, "Matt Post" <p...@cs.jhu.edu> wrote: >Chris, to be clear, are you asking for input on a name, or suggesting creating >all three lists? > >The main issue I'm concerned with is that comments on Github generate three >emails: > >- Github sends an email to dev >- If the comment is on a pull that matches a JIRA issue, the ASF Github bot >sends an email to me >- It also sends the same email to dev > >I think we should just (a) tell Github to stop posting to dev and (b) tell the >ASF Github bot to send everything to commits. We could create a new list, but >there's some complexity in maintaining lists themselves, and it seems that >commits would be a good place to bury things and forget about them. > >Would that satisfy the archiving goals? Who can do this? I don't seem to have >Github permission on incubator-joshua to do (a), and I don't know how to do >(b). > >matt > > > > >> On May 26, 2016, at 11:34 AM, kellen sunderland >> <kellen.sunderl...@gmail.com> wrote: >> >> I'd +1 as well. Your breakdown looks good to me Chris. >> >> On Thu, May 26, 2016 at 4:12 PM, Mattmann, Chris A (3980) < >> chris.a.mattm...@jpl.nasa.gov> wrote: >> >>> +1 to a separate list for GitHub stuff. Many communities (Kudu, >>> Spark, etc.) end up doing this. >>> >>> How about: >>> >>> revi...@joshua.incubator.apache.org >>> git...@joshua.incubator.apache.org >>> iss...@joshua.incubator.apache.org >>> >>> Any of those? >>> >>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >>> Chris Mattmann, Ph.D. >>> Chief Architect >>> Instrument Software and Science Data Systems Section (398) >>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA >>> Office: 168-519, Mailstop: 168-527 >>> Email: chris.a.mattm...@nasa.gov >>> WWW: http://sunset.usc.edu/~mattmann/ >>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >>> Director, Information Retrieval and Data Science Group (IRDS) >>> Adjunct Associate Professor, Computer Science Department >>> University of Southern California, Los Angeles, CA 90089 USA >>> WWW: http://irds.usc.edu/ >>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> On 5/26/16, 6:00 AM, "Matt Post" <p...@cs.jhu.edu> wrote: >>> >>>> I agree it's good to have Github stuff archived on Apache-owned domains, >>> I just think that the list gets overwhelmed with garbage that most people >>> are just deleting. I mean, I like the idea of skimming through commits, but >>> today I am waking up to over 100 emails, and I have to pick out the >>> auto-generated emails that I don't have time to read from the important >>> ones. If most people are just saving things to a separate folder, that they >>> are never going to read, isn't it better to turn off those auto-emails? >>>> >>>> Why not use a separate list like git@ or archive@ for such posts? Then >>> it's there for people to search, but no one has to wade through it. >>>> >>>> >>>> >>>> >>>>> On May 26, 2016, at 12:45 AM, Lewis John Mcgibbney < >>> lewis.mcgibb...@gmail.com> wrote: >>>>> >>>>> Hi Matt, >>>>> >>>>> As Henry said. Either we get them going to a different list or else you >>>>> subscribe to dev-dig...@joshua.incubator.apache.org (subscribe through >>>>> dev-digest-subscr...@joshua.incubator.apache.org)? >>>>> Which do you prefer? >>>>> Quick reasoning as to why Github convo is shadowed on the Apache lists. >>> If >>>>> Github ever goes away, then we loose all of the conversation. We >>> archive it >>>>> @Apache so we cover our communities. >>>>> Thanks >>>>> >>>>> >>>>> On Wed, May 25, 2016 at 2:11 PM, < >>>>> dev-digest-h...@joshua.incubator.apache.org> wrote: >>>>> >>>>>> >>>>>> From: Matt Post <p...@cs.jhu.edu> >>>>>> To: dev@joshua.incubator.apache.org >>>>>> Cc: >>>>>> Date: Wed, 25 May 2016 15:48:24 -0400 >>>>>> Subject: too many emails >>>>>> Does someone know how to turn off the mailing of all github comments to >>>>>> dev? >>>>>> >>>>>> The way I see it, we all have to be on dev, so it should be for people, >>>>>> not robots. I am getting every comment about three times. >>>>>> >>>>>> I would just do it but I don't know how. >>>>>> >>>>>> >>>> >>> >
