Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:130729
Feedback-ID: id5114917:Fastmail
Date: Fri, 01 May 2026 12:15:35 +0100
To: internals@lists.php.net
Subject: Re: [PHP-DEV] Re: [RFC] Remove the links to X.com from PHP.net
User-Agent: K-9 Mail for Android
In-Reply-To: <CALrFCSwr=aK649H2Om2=Vcrfz642JsiNBfCgDVY8U1Z27KDcNg@mail.gmail.com>
References: <CALrFCSwr=aK649H2Om2=Vcrfz642JsiNBfCgDVY8U1Z27KDcNg@mail.gmail.com>
Message-ID: <A144C00F-4781-4959-B57D-A4F3320E87FE@rwec.co.uk>
Precedence: list
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: imsop.php@rwec.co.uk ("Rowan Tommins [IMSoP]")

On 30 April 2026 16:55:00 BST, Roman Pronskiy <roman@pronskiy=2Ecom> wrote:
>The account is silent because one credential holder unilaterally
>stopped posting and has not transferred or shared access despite
>repeated requests=2E That is a governance failure, not a project
>decision=2E Removing the link in this context does not reflect a project
>consensus to abandon the platform =E2=80=94 it ratifies the outcome of on=
e
>person's unilateral action=2E


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 wh=
o should have access=2E

2) Based on that policy, demand access to the X account called "php_offici=
al" be transferred=2E

3) Based on that process, decide whether the X account should be shut down=
, and if so, what that should look like (e=2Eg=2E complete account deletion=
, or profile update to link to other active channels)=2E


Otherwise, we're just setting ourselves up for more problems in future: pe=
ople creating "official" accounts on other services, then abandoning them, =
or worse=2E


Regards,

Rowan Tommins
[IMSoP]