Re: Learning from this week

Strike that, the title in the other email is negative and I agree we should go past it. If people are talked out, then let me give my perspective. It’s great hearing from Andy, Romain, Gurkan, Jon G, Jon F, and Mark. You are all contributing to the strength of the community. We do have more

Re: Learning from this week

Happy to discuss over in that thread, but there are still some points we missed and need to learn from before we move on. I’ll follow up. -- David Blevins http://twitter.com/dblevins http://www.tomitribe.com > On Jul 2, 2017, at 1:32 AM, Romain Manni-Bucau wrote: > >

Re: Learning from this week

+1 Only the ones who don't work make no failures ;) Let's learn from it and move on. LieGrue, strub > Am 02.07.2017 um 10:32 schrieb Romain Manni-Bucau : > > We already got this discussion on the thread you mentionned David and think > we ended up by recognizing some

Re: Learning from this week

We already got this discussion on the thread you mentionned David and think we ended up by recognizing some errors but only good wills from all parties. We also got from that some process enhancements I think we would need to write down when any of us would have time. So not sure we need another

Re: Learning from this week

I think it would be fair to give Andy and Romain the first responses. - Andy, do you see anything you may have said or did in your exchange with Romain that you feel is not the Apache way? - Romain, do you see anything you may have said or did in your exchange with Andy that you feel is not

Learning from this week

I’ve gone through the commit@ and dev@ archives to piece together exactly what happened on the 27th. This type of conflict is disappointing and not the Apache Way. We need to shine a spotlight on and learn from these types of exchanges. We have some homework to do. Everyone read this