> On Mar 5, 2020, at 15:28, Stanislav Malyshev <smalys...@gmail.com> wrote: > > Hi! > >>>> If this version is approved, will the steward voluntarily deprecate >>>> version 3.0, and if not, and if 3.01 is approved, should 3.0 be >>>> involuntarily deprecated? >> >> >> The “steward” is the PHP Group. I know that Rasmus, Zeev, and Sascha are >> still active on this list, but I don’t know what the protocol is for making >> this decision. Would this need a simple RFC for the internals community to >> vote on? If that’s the route, I’m happy to put together a draft. > > I think it is already effectively "deprecated", as all current PHP > versions use 3.01. There was no formal announcement about it, I think, > but since this is the license that is used only for PHP engine and not > much else (and HHVM, which also uses 3.01) there wasn't much point about > explicitly stating it, but if it's necessary, I guess it'd make sense to > "deprecate" it, whatever that means.
IMO, this is just a formality. Since 3.01 has been in use for 14 years and PHP hasn’t used it since 2006, it is, as you say, effectively deprecated. We do have a number of PECL extensions not “owned” by the PHP Group that have applied the 3.01 license. In fact, PECL advocates for this here: https://pecl.php.net/account-request.php > We strongly encourage contributors to choose the PHP License 3.01 for their > extensions I also note at least one extension that continues to use the 3.0 license, and in fact, it appears they reverted from 3.01 to 3.0 in 2012 (I’m not sure why): https://github.com/websupport-sk/pecl-memcache/blob/NON_BLOCKING_IO_php7/LICENSE There is some concern at the OSI about these clauses, when the license is applied to any projects not owned by the PHP Group. I’ll keep everyone here posted and will let you know if these become more than passing concerns. 3. The name "PHP" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact gr...@php.net. 4. Products derived from this software may not be called "PHP", nor may "PHP" appear in their name, without prior written permission from gr...@php.net. You may indicate that your software works in conjunction with PHP by saying "Foo for PHP" instead of calling it "PHP Foo" or "phpfoo" Cheers, Ben
signature.asc
Description: Message signed with OpenPGP
