Groups | Search | Server Info | Login | Register


Groups > linux.debian.legal > #6204

Re: Updating the PHP license

From Ben Ramsey <ben@benramsey.com>
Newsgroups linux.debian.legal
Subject Re: Updating the PHP license
Date 2024-05-22 03:00 +0200
Message-ID <IGIuJ-eXrj-7@gated-at.bofh.it> (permalink)
References <IFyH8-eg75-3@gated-at.bofh.it> <IFRTr-erIf-11@gated-at.bofh.it> <IFURj-etr4-7@gated-at.bofh.it> <IGIuJ-eXrj-9@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

> On May 21, 2024, at 11:49, Richard Laager <rlaager@debian.org> wrote:
> 
> On 2024-05-19 14:53, Ben Ramsey wrote:
>> One of my goals with the RFC is to get rid of the idea of a “PHP License,” so it deprecates the PHP License and *replaces* it with the BSD 3-Clause License. I don’t want there to be a “PHP License, version 4.0.” I think that will continue to cause confusion in the community.
> 
> You (the copyright holders) could do both. That is, the PHP 4.0 license would be the same wording (other than the name) as BSD 3-Clause. That way, you trigger the "any subsequent version" clause, but then you also subsequently relicense PHP itself under BSD 3-Clause directly. This would indicate a clear intention that the PHP License is deprecated, while still getting the "any subsequent version" benefits for existing software.
> 
> Of course, this assumes that you WANT to trigger that option for third-party projects, which you may or may not. (I think you should want that, but it's not my code, so my opinion doesn't really matter.)


Honestly, I hadn’t considered this option before mailing this list, so I’m glad I mailed this list. :-)

After thinking it over, I do think we want to trigger this option for third-party projects, so that they have a clear path to upgrade the BSD 3-Clause license.

Cheers,
Ben

Back to linux.debian.legal | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

Updating the PHP license Ben Ramsey <ben@benramsey.com> - 2024-05-18 22:20 +0200
  Re: Updating the PHP license "Andrew M.A. Cater" <amacater@einval.com> - 2024-05-18 23:00 +0200
  Re: Updating the PHP license Francesco Poli <invernomuto@paranoici.org> - 2024-05-19 18:50 +0200
    Re: Updating the PHP license Ben Ramsey <ben@benramsey.com> - 2024-05-19 22:00 +0200
      Re: Updating the PHP license Francesco Poli <invernomuto@paranoici.org> - 2024-05-21 23:40 +0200
        Re: Updating the PHP license Ben Ramsey <ben@benramsey.com> - 2024-05-22 03:00 +0200
          Re: Updating the PHP license Francesco Poli <invernomuto@paranoici.org> - 2024-05-23 20:50 +0200
            Re: Updating the PHP license Ben Ramsey <ben@benramsey.com> - 2024-05-24 07:20 +0200
              Re: Updating the PHP license Francesco Poli <invernomuto@paranoici.org> - 2024-05-25 17:10 +0200
                Re: Updating the PHP license Ben Ramsey <ben@benramsey.com> - 2024-05-25 18:00 +0200
          Re: Updating the PHP license Ben Ramsey <ben@benramsey.com> - 2024-05-23 06:20 +0200
      Re: Updating the PHP license Ben Ramsey <ben@benramsey.com> - 2024-05-22 03:00 +0200
  Re: Updating the PHP license Ben Ramsey <ben@benramsey.com> - 2026-02-27 06:20 +0100
    Re: Updating the PHP license Francesco Poli <invernomuto@paranoici.org> - 2026-02-28 00:00 +0100

csiph-web