And let’s add https://issues.apache.org/jira/browse/CALCITE-4217 <https://issues.apache.org/jira/browse/CALCITE-4217> to the list of changes that Vladimir has committed despite my clear objections.
> On Sep 5, 2020, at 3:43 PM, Julian Hyde <jhyde.apa...@gmail.com> wrote: > > In the Apache Way, how do I say, ‘Please stop trying to fix this. It isn’t > broken.’ > > Vladimir has been trying to fix things that aren’t broken over the last week. > It has been driving me crazy. It has wasted a bunch of my time, answering his > questions, pointing out that the behavior is intended. And still he goes > ahead and changes stuff. > > For example, https://issues.apache.org/jira/browse/CALCITE-4226 > <https://issues.apache.org/jira/browse/CALCITE-4226>. It works fine. There > are no bugs. Yet he still commits a change. > > This change does not have consensus. The only person who weighed in (me) was > against it. He did not leave time for anyone to review. > > What should I do now - back out his change? > > I fear that it is going to continue. > https://issues.apache.org/jira/browse/CALCITE-4199 > <https://issues.apache.org/jira/browse/CALCITE-4199>, the parent task of this > whole initiative to add more nullability annotations, has a bunch of other > sub-tasks. Early on, I tried to middle ground, but expressed skepticism about > the whole endeavor: "I would support evolution and incremental improvements > to our annotations. … But I don't want our code to look radically different > in six months.” And yet he has forged ahead, logging countless other tasks > that I think are useless. And the moment I look away, he will commit them. > > I find Vladimir’s behavior utterly exhausting. It saps time that I could be > using for better purposes in this project and in my opinion doesn’t improve > the project one iota. > > Julian >
