On Thu, 4 Jun 2026 at 05:55, Jim Winstead <[email protected]> wrote: > > On Mon, May 18, 2026, at 11:07 AM, Jim Winstead wrote: > > Hi, > > I just opened voting for the "Remove the links to X.com from PHP.net" RFC. > > The RFC: https://wiki.php.net/rfc/remove-link-to-x-from-php-net > The PR: https://github.com/php/web-php/pull/1879 > The discussion thread:https://news-web.php.net/php.internals/130610 > > Voting runs until 2026-06-03 17:00:00 UTC. There is just one vote to cast. > > Thanks. > > Jim > > > Hi, > > The vote failed to achieve a 2/3 majority of "Yes" votes, so the link to > defunct account on the website owned by the transphobic white supremacist > will remain on the homepage of PHP.net. > > Thanks to everyone who voted. > > Jim >
I have voted No not because I am against removing the link to x.com from php.net, but because I am against the RFC. If we lost access to the account, create a new one or if we have nobody to post these announcements, remove the link from php.net. There is no need for an RFC. From what it seems to me, x.com is still online, and some people are using it, so it should not be about who owns that platform but rather whether the PHP team has the need and capacity to post anything there. I think social media exposure is good, but not strictly necessary. Together with the x.com link there are links to fosstodon.org and linkedin.com. The latest post on X was about PHP 8.3, but the other sites have more recent activity. So unless someone decides to start posting on x.com again, the link should be considered dead and removed from the site, regardless of the outcome of this RFC. In a similar vein, we don't have links to Facebook or TikTok because, as I assume, nobody is posting announcements there. Maybe there should be a social media person who is in charge of an account on all of these social media sites and will post regularly. But having a link to an account with no activity is of no use to anyone.
