Re: [DISCUSS] comm...@daffodil.apache.org

2019-10-24 Thread Steve Lawrence
day, October 21, 2019 10:16 AM >> To: dev@daffodil.apache.org >> Subject: Re: [DISCUSS] comm...@daffodil.apache.org >> >> Seems perfectly reasonable to me. All the PRs and comments definitely >> get a bit overwhelming and can hide actual discussions. We already have >>

Re: [DISCUSS] comm...@daffodil.apache.org

2019-10-24 Thread Steve Lawrence
gt; +1 from me. > > From: Steve Lawrence > Sent: Monday, October 21, 2019 10:16 AM > To: dev@daffodil.apache.org > Subject: Re: [DISCUSS] comm...@daffodil.apache.org > > Seems perfectly reasonable to me. All the PRs and comments definitely > get a bit overwhelming and can hide a

Re: [DISCUSS] comm...@daffodil.apache.org

2019-10-21 Thread Beckerle, Mike
Reserving dev for topical discussions from developers seems wise. Robot-created emails should always be separable. +1 from me. From: Steve Lawrence Sent: Monday, October 21, 2019 10:16 AM To: dev@daffodil.apache.org Subject: Re: [DISCUSS] comm

Re: [DISCUSS] comm...@daffodil.apache.org

2019-10-21 Thread Steve Lawrence
Seems perfectly reasonable to me. All the PRs and comments definitely get a bit overwhelming and can hide actual discussions. We already have a commits@ list but only commits go there. Makes sense to send all other commit related stuff there as well. +1 from me On 10/21/19 7:13 AM, Julian Feinau

[DISCUSS] comm...@daffodil.apache.org

2019-10-21 Thread Julian Feinauer
Hi folks, I follow the Daffodil ML since a while now but I already recognized that its extremly “noisy” with tons of reports about commits, PRs, Comments and so on. At PLC4X we added an additional list commits@... Where we send all those things (and where PMC and Committers should be subscribed)