Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129833
Precedence: list
MIME-Version: 1.0
References: <CAMW7n8B9XHzF5ND21-hNYtw26EnE+0b+W0Nv=wb_ayMmu4CbKw@mail.gmail.com>
 <CAMW7n8C1m08+pKKYBGkMnNZmGmu-_kkxS-r_SCuRupBY+RHe5A@mail.gmail.com>
 <CANCsWvfXWDjdmKFFQvV0Ger6yNVSfOhQqnbyTr7bEQHSjmXyLg@mail.gmail.com>
 <79CDB2CC-E397-436E-B5A2-10DA1E451A97@rwec.co.uk> <CAMW7n8BJcC-X-sA0NB_oQLfzry+331TfO1uhvNDGZcoSxe7bFQ@mail.gmail.com>
 <D427F18D-CDEC-4DDE-8169-71F8156F2E48@rwec.co.uk> <CAMW7n8DHhfDKciJxRuvFFS-X6ojVE9D00frTCSV65HYAfNEmFw@mail.gmail.com>
In-Reply-To: <CAMW7n8DHhfDKciJxRuvFFS-X6ojVE9D00frTCSV65HYAfNEmFw@mail.gmail.com>
Date: Wed, 21 Jan 2026 23:18:37 +0100
Message-ID: <CAEKnhAEAOXWweZvwpkM9925Pf2Obz=8UoRtkhXDrQwsZdKE5cQ@mail.gmail.com>
Subject: Re: [PHP-DEV] Re: [RFC] True Async RFC 1.7
To: Edmond Dantes <edmond.ht@gmail.com>
Cc: "Rowan Tommins [IMSoP]" <imsop.php@rwec.co.uk>, internals@lists.php.net
Content-Type: multipart/alternative; boundary="000000000000ed6d740648ed4e65"
From: bukka@php.net (Jakub Zelenka)

--000000000000ed6d740648ed4e65
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed, Jan 21, 2026 at 8:15=E2=80=AFPM Edmond Dantes <edmond.ht@gmail.com>=
 wrote:

> > Unless I missed something, there was never a discussion of what a
> Working Group should look like, what its aims were, how it would report
> back to the mailing list, etc.
>
> Yes, we don=E2=80=99t have a working group like that. And I=E2=80=99m afr=
aid I don=E2=80=99t
> know how it could come into existence.
> I don=E2=80=99t have the authority to create "such" a group, and I=E2=80=
=99m not aware
> of who does.
>

Technically it could be done through the policy RFC like anything
governance related. The issue is that this would be a significant change to
our decision making and it might be potentially difficult to find an
agreement. Also it requires extra time from people involved which might not
be easy as well..

Kind regards,

Jakub

--000000000000ed6d740648ed4e65
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Wed, Jan 21, 2026 at 8:15=E2=80=AFPM E=
dmond Dantes &lt;<a href=3D"mailto:edmond.ht@gmail.com">edmond.ht@gmail.com=
</a>&gt; wrote:</div><div class=3D"gmail_quote gmail_quote_container"><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:=
1px solid rgb(204,204,204);padding-left:1ex">&gt; Unless I missed something=
, there was never a discussion of what a Working Group should look like, wh=
at its aims were, how it would report back to the mailing list, etc.<br>
<br>
Yes, we don=E2=80=99t have a working group like that. And I=E2=80=99m afrai=
d I don=E2=80=99t<br>
know how it could come into existence.<br>
I don=E2=80=99t have the authority to create &quot;such&quot; a group, and =
I=E2=80=99m not aware<br>
of who does.<br></blockquote><div><br></div><div>Technically it could be do=
ne through the policy RFC like anything governance related. The issue is th=
at this would be a significant change to our decision making and it might b=
e potentially difficult to find an agreement. Also it requires extra time f=
rom people involved which might not be easy as well..</div><div><br></div><=
div>Kind regards,</div><div><br></div><div>Jakub</div></div></div>

--000000000000ed6d740648ed4e65--