I see your point. But right now it's really very hard to follow any discussions because the gitbox bot spams the list like crazy.
I know it's not only a CXF problem, but there is one more thing which I noticed in projects which co-went to github. Previously we had mailing list + Jira. But with gitbox integration all the information is all over the place mailing list + jira + PRs + github tickets + other github repos + + That makes it really hard to read up. Again: not a CXF issue, we need to tackle this on a general infra level. LieGrue, strub > Am 26.04.2018 um 00:21 schrieb Daniel Kulp <[email protected]>: > > > We have a notifications@ list, but that is for build notification (Jenkins) > which is very different than discussions on PR’s. > > If GitBox would allow the Open/Close to go to commits@ and the comments to > remain on dev@, I could be open to that idea. > > Dan > > > >> On Apr 25, 2018, at 4:56 PM, John D. Ament <[email protected]> wrote: >> >> Lots of projects have been struggling with this. Many podlings have been >> creating notifications@ to reduce the dev list clutter. Those interested >> can subscribe there. >> >> On Wed, Apr 25, 2018, 4:51 PM Daniel Kulp <[email protected]> wrote: >> >>> >>> I disagree…. Comments on PR’s should go to dev so the developers can see >>> what is happening with the discussions. >>> >>> Dan >>> >>> >>> >>>> On Apr 25, 2018, at 4:14 PM, Mark Struberg <[email protected]> >>> wrote: >>>> >>>> GitBox should imo get directed to [email protected] >>>> >>>> Would make it much easier to see what's going on. >>>> >>>> txs and LieGrue, >>>> strub >>> >>> -- >>> Daniel Kulp >>> [email protected] - http://dankulp.com/blog >>> Talend Community Coder - http://coders.talend.com >>> >>> > > -- > Daniel Kulp > [email protected] - http://dankulp.com/blog > Talend Community Coder - http://coders.talend.com >
