Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:120343
MIME-Version: 1.0
References: <CADK1yX+aYifoOTwPGnuL3=xDL_NYgFgvZmFAvBfOK333Ohxwrw@mail.gmail.com>
In-Reply-To: <CADK1yX+aYifoOTwPGnuL3=xDL_NYgFgvZmFAvBfOK333Ohxwrw@mail.gmail.com>
Date: Thu, 18 May 2023 17:08:43 +0100
Message-ID: <CAO__Xv7ts7ZsdeubAEcKTDhek0Q17i6GVCHQ1P5QdfPz+UnXdg@mail.gmail.com>
To: Deleu <deleugyn@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000066ed3305fbfa0595"
Subject: Re: [PHP-DEV] PHP Package for PHP
From: fenniclog@gmail.com (tag Knife)

--00000000000066ed3305fbfa0595
Content-Type: text/plain; charset="UTF-8"

>
> The work to get started seems to be about:
>
> 1- Getting an RFC to approve this idea itself
> 2- Getting a repository to host the PHP package code.
> 3- CI/CD
> 4- Release Management
> 5- Versioning Strategy
> 6- Package naming convention
> 7- Distribution strategy (single package vs multiple sub-packages)
> 8- PHP developers and community contributions
>
> Anything I'm missing? Thoughts?
>

I'm also wondering if we should be looking at including composer as a
default install of PHP.
I remember there being some discussions about it and generally a positive
outcome, but then nothing further being done.

We PHP would do follow this approach providing composer package manager as
default with every future php release, should be a requirement.

--00000000000066ed3305fbfa0595--