Re: [RFC] Policy on 3rd party code

From: Date: Fri, 04 Oct 2024 11:22:43 +0000
Subject: Re: [RFC] Policy on 3rd party code
References: 1  Groups: php.internals 
Request: Send a blank email to internals+get-125743@lists.php.net to get a copy of this message
On Wed, 2 Oct 2024, Larry Garfield wrote: > Since Jim's RFC proposal was criticized for being too vague, I hereby > offer a somewhat more prescriptive policy proposal on using 3rd party > code. (With JIm's blessing.) It's still more heuristics than rules, > but I think that's the right approach generally. It also includes a > voting mechanism to resolve edge cases when they come up. > > I'm sure we'll bikeshed it to death, but please keep an open mind > about the concept in the first place. PHP is more than just php-src, > and that's a good thing. We need to catch up with that reality, while > at the same time maintaining a reasonable neutrality about projects > Internals doesn't manage directly. > > https://wiki.php.net/rfc/third-party-code > > *Puts on trusty flame-retardant suit* | The following packages are explicitly approved for use by this RFC, as | they meet all of the criteria above. | | - Xdebug That's not strictly true, as it doesn't have an "Approved License". It's a nitpick, but Xdebug has "The Xdebug License" (https://github.com/xdebug/xdebug/blob/master/LICENSE), which is the PHP License 3.01, but with s/PHP/Xdebug. I've been wanting to change that for ages, but it requires approval from all contributors, and that's not going to happen easily. cheers, Derick -- https://derickrethans.nl | https://xdebug.org | https://dram.io Author of Xdebug. Like it? Consider supporting me: https://xdebug.org/support mastodon: @derickr@phpc.social @xdebug@phpc.social

« previous php.internals (#125743) next »