Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:119903
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.400.51.1.1\))
Date: Tue, 11 Apr 2023 10:40:31 +0100
References: <aa9f0f66-f772-3fc4-4f66-2245930ab089@helionweb.de>
 <CAPyj-LAughwkC=nQjU=K56rMmCjPdmq42DPPr7Q0v0dtkieLzA@mail.gmail.com>
 <CADK1yXKWbwiUAmWpoOdCF459fzq3w47SpwBvJ_6-nXTnfzkjhQ@mail.gmail.com>
 <8abbed60-5569-4eca-ad12-957877feed9b@app.fastmail.com>
 <CADK1yXJj1=gfNLgUX69yED_pa5zJLJomyQ9M0K57zavu1fTikw@mail.gmail.com>
 <efa92c34-7296-44f0-b120-635a3590f8cb@app.fastmail.com>
 <CADK1yXKrxuBpScE7oWNo-dVPGi1p7wHCKRe28JhknBZxQy_B5g@mail.gmail.com>
 <CABigaAVZJgHSW5P735F=-NmjNQS=CVGtwRXbQS+HGG4_gfGP8g@mail.gmail.com>
 <CADyq6sJNtAJAZui7KcKzYj0S65mZpbniVTrcpCd4PmRCF=TkRA@mail.gmail.com>
 <A3F0C7DD-34F0-4C4E-AFE1-88CBF203C386@sewell.info>
To: php internals <internals@lists.php.net>
In-Reply-To: <A3F0C7DD-34F0-4C4E-AFE1-88CBF203C386@sewell.info>
Message-ID: <0A4FDAA0-F63E-461B-8286-C526B85A30EB@sewell.info>
Subject: Re: [PHP-DEV] Future stability of PHP?
From: php@sewell.info (Matthew Sewell)

Just to follow up on that, and going totally off topic, I was reading =
about thanks.dev the other day.

One of our concerns is that we can easily give money to top level =
projects or things we consciously add but how do you give it to all the =
dependencies and the thanks.dev approach seems a good idea (I have a =
separate problem in that our projects are rarely on GitHub or GitLab) =
but does anybody who would actually benefit from it have any thoughts on =
whether it would be good for them or not?

> On 11 Apr 2023, at 10:09, Matthew Sewell <php@sewell.info> wrote:
>=20
> What's meaningful in this sense?
>=20
> I have a budget for supporting open source projects (back to my money =
v time point) and a percentage of that is for the PHP Foundation. I'd =
happily pay LTS fees we pay elsewhere (even sometimes as a safety net) =
to the Foundation but believe that the money we give to projects is just =
that, a donation that the project can use as it sees fit, rather than =
the purchasing of a service as we do commercially.
>=20
> Best wishes,
>=20
> Matt
>=20
>> On 11 Apr 2023, at 09:56, Marco Pivetta <ocramius@gmail.com> wrote:
>>=20
>> I'm also curious to hear whether any participants in this thread =
do/did
>> support the PHP foundation in any tangible way :D
>>=20
>> If you treat it like an LTS provider, perhaps it's time to pay up the =
LTS
>> support fees?
>>=20
>> Marco Pivetta
>>=20
>> https://mastodon.social/@ocramius
>>=20
>> https://ocramius.github.io/
>>=20
>>=20
>> On Tue, 11 Apr 2023 at 10:40, Alex Wells <autaut03@gmail.com> wrote:
>>=20
>>> On Tue, Apr 11, 2023 at 6:10=E2=80=AFAM Deleu <deleugyn@gmail.com> =
wrote:
>>>=20
>>>> I don't want to use those weird stuff, but I'm
>>>> doing the best I can to replace every single line of old code that =
has
>>> been
>>>> written in an era that "best practices for PHP development" were =
not what
>>>> you and I know today.
>>>>=20
>>>=20
>>> I still do not understand why you're expecting the whole PHP project =
to put
>>> in enormous efforts to keep the backwards compatibility and solve =
your
>>> problems (temporarily) instead of you doing so. What's stopping you =
from
>>> using the last supported PHP version by that codebase and fixing or, =
worst
>>> case scenario, rewriting it if you wish, while on that (non latest) =
PHP
>>> version? What causes the desperation to update to the latest PHP? Is =
it new
>>> features or security fixes, or both?
>>>=20
>=20