Received and awesomely fast reply from INFRA. All of our github notifications do go to [email protected] today and there are a few you can control but they must all be the same. The things we see going to commits are because some of them cause comments to get entered into JIRA as well which in turn sends updates to [email protected]
"You can have them sent to wherever you like, it is configurable on git-wip where those emails go to. Notification types are typically: - new pull request - comment on PR - comment on specific code - PR closed " Based on Lars request and the +1 notes that followed I will assume consensus later today or tomorrow and file the request to have all github items go to [email protected]. If we'd like to further split those to issues later we can pursue that. Thanks Joe On Tue, Jun 28, 2016 at 7:25 AM, Joe Witt <[email protected]> wrote: > Here is an INFRA request so we can gather more info. > https://issues.apache.org/jira/browse/INFRA-12191 > > My intent would be to just have all github notfications go to > [email protected] rather than make another mailing list. > > We could also switch to having a pure issues mailing list which would > be for all JIRA filings and Github auto notifications and then ideally > commits would be just for code commits to SVN/Git but i'm not sure > that distinction is valuable. What does seem valuable is keeping dev > clear for true developer driven discussion. > > If others have an opinion they'd like to share on this please do. > > Thanks > Joe > > On Tue, Jun 28, 2016 at 2:18 AM, Lars Francke <[email protected]> wrote: >> Thank you! >> >> There is at least pull request and issue stuff going to dev@ which would be >> better suited in a different list I think. >> >> On Tue, Jun 28, 2016 at 1:59 AM, Joe Witt <[email protected]> wrote: >> >>> Some GitHub things go to commits@nifi >>> >>> Will reach out to infra to learn more about our options. >>> >>> I was initially concerned about losing GitHub comments from dev but even >>> those seem inconsistent already. >>> >>> Will share what I learn so we can make a good decision. >>> On Jun 27, 2016 4:55 PM, "Jeff" <[email protected]> wrote: >>> >>> > I agree, there's a lot of GitHub "noise" on the dev list. >>> > >>> > +1 >>> > >>> > On Mon, Jun 27, 2016 at 5:58 PM Joe Witt <[email protected]> wrote: >>> > >>> > > Am on phone but the ones I see go to [email protected] >>> > > >>> > > Which ones are you referring to? >>> > > >>> > > Thanks >>> > > Joe >>> > > On Jun 27, 2016 11:45 AM, "Andy LoPresto" <[email protected]> >>> wrote: >>> > > >>> > > > +1. >>> > > > >>> > > > Andy LoPresto >>> > > > [email protected] >>> > > > *[email protected] <[email protected]>* >>> > > > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 >>> > > > >>> > > > On Jun 27, 2016, at 12: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 >>> > > > >>> > > > >>> > > > >>> > > >>> > >>>
