Re: [REMINDER] Technical discussion on the mailing list

> > At the end of the day, it comes down to two questions: > > 1) Are there technical and project direction discussions happening off > list and not reflected back to the list? > > 2) If yes, are the concrete decisions being made as a result of the off > list discussions? > From an Apache

Re: [REMINDER] Technical discussion on the mailing list

Hi Daniel, Thanks for raising this. I think I was a major contributor to your frustration with the process by suggesting big changes to your IO PR. As others have said, ideally that process should have gone differently: 1) we should have had documentation on the best practices in developing IOs,

Re: [REMINDER] Technical discussion on the mailing list

At the end of the day, it comes down to two questions: 1) Are there technical and project direction discussions happening off list and not reflected back to the list? 2) If yes, are the concrete decisions being made as a result of the off list discussions? The answer to #1 is a definite yes.

Re: [REMINDER] Technical discussion on the mailing list

Great summary Davor, +1 with what you said. Regards JB On 10/06/2016 08:29 AM, Davor Bonaci wrote: Daniel, so glad you are starting to contribute to Beam! It was great talking with you in person back in May. Welcome! -- There are lots of different things mentioned here; I'll try to address

Re: [REMINDER] Technical discussion on the mailing list

Yes, but as said in another e-mail, even if it's a step forward, an argued and valuable proposal message is better IMHO. Regards JB On 10/06/2016 08:16 AM, Daniel Kulp wrote: On Oct 6, 2016, at 2:33 AM, Dan Halperin wrote: Anyway, I don’t really understand why

Re: [REMINDER] Technical discussion on the mailing list

Hi Dan, Even if enable the "full" Github integration is a step forward, I'm not sure it will help at the end. I'm afraid we (at least most of us ;)) won't read pull request comments on the mailing list because it would be way more verbose. So, I think there's more value to quickly explain

Re: [REMINDER] Technical discussion on the mailing list

Daniel, so glad you are starting to contribute to Beam! It was great talking with you in person back in May. Welcome! -- There are lots of different things mentioned here; I'll try to address them separately. The first use of AutoValue should have been discussed on the dev@ mailing list. I

Re: [REMINDER] Technical discussion on the mailing list

> On Oct 6, 2016, at 2:33 AM, Dan Halperin wrote: > > Anyway, I don’t really understand why the full github integration wasn’t >> setup for the beam PR’s so that the comments would come back to the lists >> as well (and JIRA, BTW). >> > > This part confuses me.

Re: [REMINDER] Technical discussion on the mailing list

How about sending just the notifications for creating new JIRA and opening PR to dev@ so that those that are interested can start watching? Thanks, Thomas On Wed, Oct 5, 2016 at 5:33 PM, Dan Halperin wrote: > On Wed, Oct 5, 2016 at 5:13 PM, Daniel Kulp

Re: [REMINDER] Technical discussion on the mailing list

On Wed, Oct 5, 2016 at 5:13 PM, Daniel Kulp wrote: > I just want to give a little more context to this…. I’ve been lurking on > this list for several months now reading everything that’s going on. From > Apache’s standpoint, that should be a “very good start” for getting to

Re: [REMINDER] Technical discussion on the mailing list

I just want to give a little more context to this…. I’ve been lurking on this list for several months now reading everything that’s going on. From Apache’s standpoint, that should be a “very good start” for getting to know what is happening in a project. On my last PR, Eugene commented

Re: [REMINDER] Technical discussion on the mailing list

This is a great idea. And it produces many easy starter tickets! :-) On Wed, Oct 5, 2016 at 4:51 AM Jean-Baptiste Onofré wrote: > Hi team, > > I would like to excuse myself to have forgotten to discuss and share with > you a technical point and generally speaking do a small

Re: [REMINDER] Technical discussion on the mailing list

+1 for AutoValue. On Wed, Oct 5, 2016 at 4:51 AM, Jean-Baptiste Onofré wrote: > So, any comment happening on a GitHub pull request, or discussion on > hangouts which can impact the project (generally speaking) has to happen on > the mailing list. > > It provides project

Re: [REMINDER] Technical discussion on the mailing list

+1 for the notice +1 for the usage of AutoValue On Wed, Oct 5, 2016 at 4:51 AM, Jean-Baptiste Onofré wrote: > Hi team, > > I would like to excuse myself to have forgotten to discuss and share with > you a technical point and generally speaking do a small reminder. > > When we