PHP Foundation 'under-funded' with one full-time staff member, director says
Amid critical security vulnerabilities and widespread use of PHP in everything from WordPress and government sites to large commercial platforms, the PHP Foundation is reportedly operating with only one full-time staff member and a shrinking budget of around $350,000. Commenters highlight the mismatch between PHP’s importance to the internet’s infrastructure and the limited funding it receives, debating whether the language should be better funded, put into long-term maintenance, or gradually sunset. The conversation widens into a critique of how open-source projects are chronically underfunded despite being essential, with proposals ranging from larger corporate contributions and government support to stronger fundraising and licensing strategies.
Funding situation of the PHP Foundation
- Public transaction logs show significant spending on contractor “work” and a shrinking balance of ~$350k.
- Reported to have only one full-time staff member (in a non-engineering role), plus multiple part-time contractors.
- Several commenters argue this is “not a lot” given the importance and scale of PHP, and that many more full‑time maintainers are needed.
- Some see this as part of a broader pattern of critical OSS infrastructure running “on fumes.”
Who uses PHP and how “serious” is it?
- Many well-known PHP-based platforms are cited: WordPress, Nextcloud, Wikipedia, pfSense UI, porn sites, social networks, CDNs, e‑commerce, government and public sector sites, and various enterprises.
- Some commenters deride PHP as “for the cheap and not very technical”; others counter that many profitable and mission‑critical organizations rely on it.
- PHP 8 and modern frameworks (especially Laravel and Symfony) are described as significantly more capable and pleasant than the old PHP 5 era.
- Laravel receives particular praise for documentation, ecosystem, tooling (Composer), and community.
Maintenance vs. sunsetting / migration
- One camp suggests PHP should be sunset or moved to “maintenance mode” if it can’t be properly funded.
- Others respond that mass migration of the global PHP footprint would be extremely costly and risky, and that all stacks have security vulnerabilities.
- Code migrations are described by some as “cheap” conceptually but, when examined (e.g., publicized rewrites in Rust), actually expensive, slow, and bug‑prone.
Funding models, incentives, and OSS politics
- Suggestions include:
- More corporate sponsorship, especially from large PHP-dependent companies.
- Government funding for critical OSS infrastructure.
- Endowment-style funds invested in broad indexes to pay maintainers indefinitely.
- Campaign-style fundraising similar to Wikipedia.
- Dual licensing with strong copyleft (GPL/AGPL) to support commercial funding.
- Debate over open source itself:
- Some see OSS as a “trojan horse” that devalues independent developers and concentrates power in a few large corporations.
- Others emphasize that FLOSS historically enabled many small and mid-sized businesses and still does.
- There is tension between the expectation of “free” software and later attempts to monetize or change licenses; some view post‑hoc moral pressure to fund projects as dishonest, others see it as a natural response to unexpected success and maintenance burden.
Contributor motivation and practical constraints
- Some contributors work on OSS out of genuine affinity for tools they use.
- Others say long workdays leave no energy for unpaid work; “non‑greedy” motives may exist but clash with economic reality.
- A few suggest integrating small contributions into work time, but this depends heavily on employer support.