Re: [RFC][Vote] Policy on third party code

I also voted against because I think it's silly to create these arbitrary rules on the various frameworks. "Not playing favorites" is literally as easy as saying "The people who volunteered their time to build X did so using Y because that's what they knew, it doesn't mean the PHP project favors them over another option". No one serious writes PHP code without a framework today, and the fact we go so far to keeping PHP "stand alone" I think hurts the project more than it helps because it gives a casual observer the idea that PHP development is just the PHP language, which simply is never the case for a serious project. On Nov 10 2024, at 4:41 pm, Pedro Magalhães <mail@pmmaga.net> wrote: > On Fri, Nov 8, 2024 at 11:35 PM Larry Garfield <larry@garfieldtech.com > (mailto:larry@garfieldtech.com)> wrote: > > > I have opened the vote on the proposed third-paty-code policy clarification. > > > > https://wiki.php.net/rfc/third-party-code > > The vote will end on 22 November. > > -- > > Larry Garfield > > larry@garfieldtech.com (mailto:larry@garfieldtech.com) > > > Hi Larry, > > I want to let you know the reason why I'm voting no. Sorry for not bringing this up during > the discussion phase but I honestly haven't seen it mentioned. > Throughout the policy text there are three mentions to: > "Any library or PSR published by the PHP-FIG" > > Given that the spirit of the policy is to avoid endorsements, it seems out of place to give an > external organization special grants. The rules for inclusion and exclusion are and should remain > objective and equal for all libraries. > > Regards, > Pedro > > >