Hi, On Fri, May 1, 2026 at 2:18 PM Rowan Tommins [IMSoP] <[email protected]> wrote:
> On 30 April 2026 16:55:00 BST, Roman Pronskiy <[email protected]> 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 — it ratifies the outcome of one > >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.
