Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:103880
MIME-Version: 1.0
References: <CAF+90c9+g7k8Oq4ZtTm1mzkx0gwBJsu=2Yvto4rZeuqTusCeLQ@mail.gmail.com>
 <DM6PR02MB5594CCAE223187931678ED8CAC960@DM6PR02MB5594.namprd02.prod.outlook.com>
 <CAF+90c-fqmq=45TnvLR-rj5Lh=6-S+_-8-Z-ftPwhSjVKw3aEA@mail.gmail.com> <DM6PR02MB559447F56355973CC9A673E3AC960@DM6PR02MB5594.namprd02.prod.outlook.com>
In-Reply-To: <DM6PR02MB559447F56355973CC9A673E3AC960@DM6PR02MB5594.namprd02.prod.outlook.com>
Date: Tue, 29 Jan 2019 19:42:17 +0100
Message-ID: <CAF+90c-NwiP_-LP7Hw-+Mbv-ErjHVYOTsV0ScmWbkWHpBGNE7Q@mail.gmail.com>
To: Zeev Suraski <zeev@zend.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000004f866105809d283d"
Subject: Re: [PHP-DEV] Simplify license headers
From: nikita.ppv@gmail.com (Nikita Popov)

--0000000000004f866105809d283d
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, Jan 29, 2019 at 12:24 AM Zeev Suraski <zeev@zend.com> wrote:

>
>
> No, this case cannot be made. You are likely mixing up licensing and
> copyright here. Licensing (in the absence of a CLA) follows the
> inbound=3Doutbound principle, i.e., it is understood that inbound
> contributions are made under the same terms as the outbound license.
> However (in the absence of a copyright assignment agreement) each
> contributor retains copyright for their contributions.
>
>
>
> I'm certainly not confusing licensing and copyright, Nikita, and with due
> respect - you don't know what you're saying for a fact, neither does
> anybody really, as I'm not aware it's ever been tested in court.  We have
> purposely included the copyright notice on each and every file, and wheth=
er
> adding code to such files out of one's free will constitutes written
> consent or not is at the very least debatable (and potentially has
> different answers depending on the jurisdiction).
>
>
>
> And while this may not bother you personally, this discussion comes up
> every single year when the inevitable year increment PRs start rolling in=
.
> The most recent one for 2019 is https://github.com/php/php-src/pull/3730,
> which triggered this mail. I am rather predisposed against commits that
> touch a large part of the codebase to make a change that is not just whol=
ly
> unnecessary, but also legally extremely dubious.
>
>
>
> If the yearly sed annoyance is the true source of the issue then let's go
> with one of the proposals made on that thread =E2=80=93 i.e. use "-presen=
t" or just
> "(c) The PHP Group" without years.
>

Okay, let's change it to "(c) The PHP Group" then. While that doesn't make
it right, it does remove my main annoyance.

Nikita

--0000000000004f866105809d283d--