PHP has official accounts on Twitter/X, Mastodon and LinkedIn, but no rules for how they're run. This RFC from Roman Pronskiy adds a formal policy covering who holds the credentials, who decides what gets posted, and how accounts are added or retired. The policy text lives in a pull request to php/policies, and passing the RFC adopts it.

Why it's needed

Right now, individual people hold the logins, with no way to hand them over if someone steps away. There's also no set process for requesting a post.

The RFC uses the Twitter/X account as an example. It has about 109,000 followers and has been silent since June 4, 2024. That wasn't a project decision. The person with the login stopped posting, and requests to share access or set up automated posts went nowhere. The RFC doesn't say what should happen to that account. It sets up a process so decisions like that are made on purpose.

What the policy sets up

  • The Infrastructure Team holds the credentials. At least three people hold each account's login, and their names are public.
  • A new Social Media Team decides what gets posted. It's open to volunteers from the PHP community, its member list is public, and new members are announced on the internals mailing list first.
  • The PHP Foundation is optional. The Social Media Team can delegate some work, like marketing, to the Foundation and take it back at any time. The Foundation never gets the credentials.
  • Some posts are off limits. No politics unrelated to PHP, no ads for things unrelated to PHP, no personal opinions presented as the project's view, and no personal disputes.
  • No silent shutdowns. Every listed account keeps posting, even if only automated posts. The only way to stop is a written retirement process that's announced in advance.

The Social Media Team writes its own day-to-day guidelines and can change them by pull request without an RFC. Changing the main policy takes an RFC with a two-thirds majority.

What it means for you

This doesn't touch PHP code. It only covers the project's official accounts, and you can still post about PHP on your own. People who hold logins today will be asked to hand them to the Infrastructure Team.

Where it stands

The RFC is under discussion. It was first drafted on April 30, 2026, and is on version 1.6. The plan is a single yes or no vote needing two-thirds, but no vote has been set up yet.