Re: [VOTE] include cleanup

From: Date: Mon, 27 Feb 2023 15:08:48 +0000
Subject: Re: [VOTE] include cleanup
References: 1 2 3 4 5 6 7 8 9 10  Groups: php.internals 
Request: Send a blank email to [email protected] to get a copy of this message

On 2/13/2023 4:13 AM, Arvids Godjuks wrote:
Good day dear Internals! I've been following this thread/RFC from its inception to the current moment. I have watched the situation deteriorate and at this point, I have major concerns about the events that transpired, the motivations of some decisions and the apparent major lack of communication. But the worst thing, in my opinion, is that the mistakes that were made about a decade ago are happening in this thread: Cubstomping and alienating new contributors who are willing to take on major amounts of work and are willing to take on the long-term maintenance. This happened to me years ago and while I'm still here and reading the threads, I backed off from contributing any further.  Many weeks of getting up early to work on the code for an hour before I had to head to work thrown away without even any better reason than "long-term maintenance" without me sticking around to do so.
Just turned me off from the whole situation.
I'm not alone in these concerns, but those people can do their own messaging. What I do not understand the most is the apparent "Not in my backyard" attitude to this RFC that seems to be happening. Improving the codebase ALWAYS requires breaking things and to be absolutely frank, I do not see how "merging conflicts" can be a sound reason for refusing header file shuffling. Or, in this case, "breaking extensions". I mean, the fixes are simple - update the header files. The author of the RFC is willing to provide the documentation/comments so it is easy to do. PHP 5 => PHP 7 engine transition was a major multi-year endeavour that was multiple orders of magnitude harder and broader problem, but everyone stuck to it and it was done. This RFC is nowhere even close to that but offers long-term improvements to the project. I am concerned about the apparent unwillingness to take on code cleanup projects. Can everybody involved cool their heads for a week, come back and talk this one out and make a plan for how to make the improvements in a way that parties can agree it should be handled?


Thread (23 messages)

« previous php.internals (#119606) next »