Github mails
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
Re: Github mails
+1. Andy LoPresto alopre...@apache.org alopresto.apa...@gmail.com PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > On Jun 27, 2016, at 12:31 AM, Lars Francke 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 signature.asc Description: Message signed with OpenPGP using GPGMail
Re: Github mails
Am on phone but the ones I see go to commits@nifi.a.o Which ones are you referring to? Thanks Joe On Jun 27, 2016 11:45 AM, "Andy LoPresto" wrote: > +1. > > Andy LoPresto > alopre...@apache.org > *alopresto.apa...@gmail.com * > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > > On Jun 27, 2016, at 12:31 AM, Lars Francke 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 > > >
Re: Github mails
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 wrote: > Am on phone but the ones I see go to commits@nifi.a.o > > Which ones are you referring to? > > Thanks > Joe > On Jun 27, 2016 11:45 AM, "Andy LoPresto" wrote: > > > +1. > > > > Andy LoPresto > > alopre...@apache.org > > *alopresto.apa...@gmail.com * > > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > > > > On Jun 27, 2016, at 12:31 AM, Lars Francke > 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 > > > > > > >
Re: Github mails
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" 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 wrote: > > > Am on phone but the ones I see go to commits@nifi.a.o > > > > Which ones are you referring to? > > > > Thanks > > Joe > > On Jun 27, 2016 11:45 AM, "Andy LoPresto" wrote: > > > > > +1. > > > > > > Andy LoPresto > > > alopre...@apache.org > > > *alopresto.apa...@gmail.com * > > > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > > > > > > On Jun 27, 2016, at 12:31 AM, Lars Francke > > 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 > > > > > > > > > > > >
Re: Github mails
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 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" 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 wrote: > > > > > Am on phone but the ones I see go to commits@nifi.a.o > > > > > > Which ones are you referring to? > > > > > > Thanks > > > Joe > > > On Jun 27, 2016 11:45 AM, "Andy LoPresto" > wrote: > > > > > > > +1. > > > > > > > > Andy LoPresto > > > > alopre...@apache.org > > > > *alopresto.apa...@gmail.com * > > > > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > > > > > > > > On Jun 27, 2016, at 12:31 AM, Lars Francke > > > 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 > > > > > > > > > > > > > > > > > >
Re: Github mails
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 comm...@nifi.apache.org 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 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 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" 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 wrote: >> > >> > > Am on phone but the ones I see go to commits@nifi.a.o >> > > >> > > Which ones are you referring to? >> > > >> > > Thanks >> > > Joe >> > > On Jun 27, 2016 11:45 AM, "Andy LoPresto" >> wrote: >> > > >> > > > +1. >> > > > >> > > > Andy LoPresto >> > > > alopre...@apache.org >> > > > *alopresto.apa...@gmail.com * >> > > > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 >> > > > >> > > > On Jun 27, 2016, at 12:31 AM, Lars Francke >> > > 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 >> > > > >> > > > >> > > > >> > > >> > >>
Re: Github mails
Received and awesomely fast reply from INFRA. All of our github notifications do go to dev@nifi.a.o 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 commits@nifi.a.o "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 commits@nifi.a.o. 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 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 > comm...@nifi.apache.org 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 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 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" 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 wrote: >>> > >>> > > Am on phone but the ones I see go to commits@nifi.a.o >>> > > >>> > > Which ones are you referring to? >>> > > >>> > > Thanks >>> > > Joe >>> > > On Jun 27, 2016 11:45 AM, "Andy LoPresto" >>> wrote: >>> > > >>> > > > +1. >>> > > > >>> > > > Andy LoPresto >>> > > > alopre...@apache.org >>> > > > *alopresto.apa...@gmail.com * >>> > > > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 >>> > > > >>> > > > On Jun 27, 2016, at 12:31 AM, Lars Francke >>> > > 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 >>> > > > >>> > > > >>> > > > >>> > > >>> > >>>
Re: Github mails
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 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
Re: Github mails
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 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 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
Re: Github mails
+1 On Tue, Jun 28, 2016 at 12:37 PM, Joe Witt 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 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 > 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 >
Re: Github mails
Ok team I put in a request for 'issues@nifi.a.o' 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 wrote: > +1 > > On Tue, Jun 28, 2016 at 12:37 PM, Joe Witt 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 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 >> 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 >>
Re: Github mails
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 wrote: > Ok team I put in a request for 'issues@nifi.a.o' 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 wrote: > > +1 > > > > On Tue, Jun 28, 2016 at 12:37 PM, Joe Witt 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 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 > > >> 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 > >> >
Re: Github mails
no problem at all. the changes should be in effect now. http://mail-archives.apache.org/mod_mbox/nifi-issues/201607.mbox/browser On Tue, Jul 5, 2016 at 2:29 AM, Lars Francke wrote: > 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 wrote: > >> Ok team I put in a request for 'issues@nifi.a.o' 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 wrote: >> > +1 >> > >> > On Tue, Jun 28, 2016 at 12:37 PM, Joe Witt 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 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 > > >> >> 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 >> >> >>
