Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:130730
Precedence: list
MIME-Version: 1.0
References: <CALrFCSwr=aK649H2Om2=Vcrfz642JsiNBfCgDVY8U1Z27KDcNg@mail.gmail.com>
 <A144C00F-4781-4959-B57D-A4F3320E87FE@rwec.co.uk>
In-Reply-To: <A144C00F-4781-4959-B57D-A4F3320E87FE@rwec.co.uk>
Date: Fri, 1 May 2026 14:56:41 +0300
Message-ID: <CAPhkiZxXUi5m-_DzH42tt_2Hdio9H06uL89vHNabWnuq7ns=1A@mail.gmail.com>
Subject: Re: [PHP-DEV] Re: [RFC] Remove the links to X.com from PHP.net
To: "Rowan Tommins [IMSoP]" <imsop.php@rwec.co.uk>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary="000000000000dad3be0650c0461c"
From: narf@devilix.net (Andrey Andreev)

--000000000000dad3be0650c0461c
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi,

On Fri, May 1, 2026 at 2:18=E2=80=AFPM Rowan Tommins [IMSoP] <imsop.php@rwe=
c.co.uk>
wrote:

> On 30 April 2026 16:55:00 BST, Roman Pronskiy <roman@pronskiy.com> wrote:
> >The account is silent because one credential holder unilaterally
> >stopped posting and has not transferred or shared access despite
> >repeated requests. That is a governance failure, not a project
> >decision. Removing the link in this context does not reflect a project
> >consensus to abandon the platform =E2=80=94 it ratifies the outcome of o=
ne
> >person's unilateral action.
>
>
> I agree with Roman here: even if there was unanimous agreement that the X
> account should be shut down, we would need to proceed in stages:
>
> 1) Agree how official PHP social media accounts should be governed, and
> who should have access.
>
> 2) Based on that policy, demand access to the X account called
> "php_official" be transferred.
>
> 3) Based on that process, decide whether the X account should be shut
> down, and if so, what that should look like (e.g. complete account
> deletion, or profile update to link to other active channels).
>
>
> Otherwise, we're just setting ourselves up for more problems in future:
> people creating "official" accounts on other services, then abandoning
> them, or worse.
>
>
I'm all for addressing the long-term governance issue, and I don't think
anyone else has objected to that.

However, I don't understand why unlinking this X account from php.net
should wait for all of the bureaucracy to play out first. The account has
been inactive (or at least hasn't posted anything) for over a decade it
seems, and is currently a liability. To me it's a no-brainer to remove the
link now, and only add it back if/when the situation is resolved.

Cheers,
Andrey.

--000000000000dad3be0650c0461c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div>Hi,</div><br><div class=3D"gmail_quo=
te"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, May 1, 2026 at 2:18=E2=80=
=AFPM Rowan Tommins [IMSoP] &lt;<a href=3D"mailto:imsop.php@rwec.co.uk" tar=
get=3D"_blank">imsop.php@rwec.co.uk</a>&gt; wrote:<br></div><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex">On 30 April 2026 16:55:00 BST, Roman Pro=
nskiy &lt;<a href=3D"mailto:roman@pronskiy.com" target=3D"_blank">roman@pro=
nskiy.com</a>&gt; wrote:<br>
&gt;The account is silent because one credential holder unilaterally<br>
&gt;stopped posting and has not transferred or shared access despite<br>
&gt;repeated requests. That is a governance failure, not a project<br>
&gt;decision. Removing the link in this context does not reflect a project<=
br>
&gt;consensus to abandon the platform =E2=80=94 it ratifies the outcome of =
one<br>
&gt;person&#39;s unilateral action.<br>
<br>
<br>
I agree with Roman here: even if there was unanimous agreement that the X a=
ccount should be shut down, we would need to proceed in stages:<br>
<br>
1) Agree how official PHP social media accounts should be governed, and who=
 should have access.<br>
<br>
2) Based on that policy, demand access to the X account called &quot;php_of=
ficial&quot; be transferred.<br>
<br>
3) Based on that process, decide whether the X account should be shut down,=
 and if so, what that should look like (e.g. complete account deletion, or =
profile update to link to other active channels).<br>
<br>
<br>
Otherwise, we&#39;re just setting ourselves up for more problems in future:=
 people creating &quot;official&quot; accounts on other services, then aban=
doning them, or worse.<br><br></blockquote><div><br></div><div>I&#39;m all =
for addressing the long-term governance issue, and I don&#39;t think anyone=
 else has objected to that.</div><div><br></div><div>However, I don&#39;t u=
nderstand why unlinking this X account from <a href=3D"http://php.net">php.=
net</a> should wait for all of the bureaucracy to play out first. The accou=
nt has been inactive (or at least hasn&#39;t posted anything) for over a de=
cade it seems, and is currently a liability. To me it&#39;s a no-brainer to=
 remove the link now, and only add it back if/when the situation is resolve=
d.</div><div><br></div><div>Cheers,</div><div>Andrey.</div></div></div>
</div>

--000000000000dad3be0650c0461c--