Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:115518
Message-ID: <990928F4-DB39-4896-AD79-BB874568EB9B@newclarity.net>
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_EF148D81-094B-4200-8F4F-A1FB96AAC664"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
Date: Tue, 20 Jul 2021 06:01:49 -0400
In-Reply-To: <CAF+90c-SbCtbPdXduyJ+0V4DMdrGy0ywWp=VyiKojGbOoZRCxg@mail.gmail.com>
Cc: PHP Internals <internals@lists.php.net>
To: Nikita Popov <nikita.ppv@gmail.com>
References: <B639F35B-4E7B-4FD5-8416-4FCFA6854858@newclarity.net>
 <CAF+90c-SbCtbPdXduyJ+0V4DMdrGy0ywWp=VyiKojGbOoZRCxg@mail.gmail.com>
Subject: Re: [PHP-DEV] License for PHP 8.x?
From: mike@newclarity.net (Mike Schinkel)

--Apple-Mail=_EF148D81-094B-4200-8F4F-A1FB96AAC664
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

> On Jul 19, 2021, at 3:31 AM, Nikita Popov <nikita.ppv@gmail.com> =
wrote:
>=20
> On Mon, Jul 19, 2021 at 5:56 AM Mike Schinkel <mike@newclarity.net =
<mailto:mike@newclarity.net>> wrote:
> I was just checking to see what the license was for PHP and this =
page[1] states:
>=20
>         "PHP 4, PHP 5 and PHP 7 are distributed under the PHP License =
v3.01, copyright (c) the PHP Group."
>=20
> Can I assume that PHP 8 is also distributed under the PHP License =
v3.01 and that this page on PHP.net <http://php.net/ <http://php.net/>> =
has just not yet been updated to reflect the existence of PHP 8?
>=20
> Yes, see https://github.com/php/php-src/blob/master/LICENSE =
<https://github.com/php/php-src/blob/master/LICENSE>. The page should be =
updated to say something like "PHP 4 and newer".

Thanks for the quick reply.

Maybe this would be a good first contribution for me?  How could I go =
about updating that page?

> =20
> -Mike
> P.S. Relatedly, if someone wants to publish code in a GitHub repo with =
intent to try to have it included in PHP what license should be used?  =
Would BSD-3 be appropriate?
>=20
> While both MIT and BSD are compatible, it's generally preferred to =
license it under the PHP license. This allows free code movement within =
php-src.

Doh!  Sorry, I had a bit of a brain fart. =20

When creating a repo GitHub allows us to select a LICENSE but does not =
include the PHP license as an option, and I was fixated on the list they =
presented. But obviously it is as simple as copying the PHP license into =
the repo after it is created, even though GitHub doesn't provide as a =
default option.  :-)

-Mike=

--Apple-Mail=_EF148D81-094B-4200-8F4F-A1FB96AAC664--