Growing PHP for the Future // PHPverse 2025  🔗 **Source:** [Growing PHP for the Future // PHPverse 2025](https://www.youtube.com/watch?v=zxTMzygBt7s) > [!note]+ Document Notes > tags: [#php, #open-source, #foundation, #community, #sustainability, #language-evolution, #ospo, #contributor-engagement, #phpverse2025] > - #php > - #open-source > - #foundation > - #community > - #sustainability > - #language-evolution > - #ospo > - #contributor-engagement > Author: Speakers (Roman, Gina, PHP Foundation) > Source: [Growing PHP for the Future // PHPverse 2025](https://www.youtube.com/watch?v=zxTMzygBt7s) > Reference: [YouTube Video](https://www.youtube.com/watch?v=zxTMzygBt7s) > date created: 2025-07-01 13:25 > > # Growing PHP for the Future: PHPverse 2025 > <!-- deep-read:sections start --> ## Table of Contents - [📝 Summary](#📝-summary) - [📖 Main Content](#📖-main-content) - [🗒️ Notes](#🗒️-notes) - [📖 References](#📖-references) - [🗣️ Paraphrase](#🗣️-paraphrase) - [📰 Newsletter](#📰-newsletter) - [✅ Action Items](#✅-action-items) - [🧪 Hypotheses](#🧪-hypotheses) - [📊 Methodology](#📊-methodology) - [❓ Questions](#❓-questions) - [🔮 Future Research](#🔮-future-research) - [💡 Implications](#💡-implications) - [🧠 Learning Styles Assessment](#🧠-learning-styles-assessment) - [📊 Accessibility Assessment](#📊-accessibility-assessment) - [🌍 DEIB Assessment](#🌍-deib-assessment) - [✅ Logical validity](#✅-logical-validity) - [🔍 DARVO Analysis Prompt](#🔍-darvo-analysis-prompt) - [🔍 SEO Evaluation](#🔍-seo-evaluation) - [🎯 Conclusion](#🎯-conclusion) --- ## 📝 Summary The session celebrates PHP's growth, examining the PHP Foundation's pivotal role in securing funding, driving strategic development, and stabilizing the language ecosystem. Key takeaways include PHP's resilience through technical and human crises, landmark achievements in funding and security, increasing community engagement, and a future-focused approach balancing new features with robust maintenance. The conversation highlights pathways for new contributors, underscores the Foundation’s impact, and teases ongoing modernization efforts and experimental features. --- ## 📖 Main Content ### 🗒️ Notes - **[00:06](https://www.youtube.com/watch?v=zxTMzygBt7s&t=6) Foundation Achievements & Community Impact** - The PHP Foundation now delivers on its original goals: sustainability, security, and community enablement. - Core developers and executive leadership actively foster ecosystem health. - Milestone: Roman’s promotion to PHP Storm product lead, reflecting industry alignment. - **[02:01](https://www.youtube.com/watch?v=zxTMzygBt7s&t=121) PHP’s Evolution and Resilience** - PHP’s 30-year journey is marked by major crises with each release, including total rewrites and failed projects (PHP 6). - The 2021 sustainability crisis (loss of paid developers) was addressed by creating the PHP Foundation. - **[07:04](https://www.youtube.com/watch?v=zxTMzygBt7s&t=424) Funding, Security, and Expansion** - German government investment allowed the Foundation to shift from maintenance to strategic initiatives. - Completed first major external security audit in a decade, public reporting for transparency. - Documentation and extension system (PEL) overhauled; ongoing improvements for cryptography and filesystem docs. - **[09:29](https://www.youtube.com/watch?v=zxTMzygBt7s&t=569) Community Growth & Recognition** - Maintenance and review activities by paid core developers enable broader community contribution. - Collaboration with the European Commission on the Cyber Resilience Act demonstrates PHP’s importance in global infrastructure. - **[14:33](https://www.youtube.com/watch?v=zxTMzygBt7s&t=873) Technical Innovation** - Performance: Tail core VM proof-of-concept brings up to 5.5% improvement for frameworks like Symfony. - New features: Pattern matching, server compatibility, JSON schema support, robust datetime API. - Composer integration and new extension installation tools (pi) make PHP more accessible. - **[20:24](https://www.youtube.com/watch?v=zxTMzygBt7s&t=1224) Community Contribution Pathways** - Multiple ways to help: documentation, translation, testing, code coverage, bug triage. - Foundation primarily needs employer sponsorship and sustained financial backing to fund key roles. - **[25:58](https://www.youtube.com/watch?v=zxTMzygBt7s&t=1558) Governance and Experimental Features** - Discussion around integrating more tools into PHP core (e.g., composer, symfony components). - New governance allows php.net to mention community projects and the Foundation. - Experimental features may use opt-in flags to gather real-world feedback before inclusion. - **[27:46](https://www.youtube.com/watch?v=zxTMzygBt7s&t=1666) Website Redesign and Analytics** - Open-source website redesign project with analytics to identify user needs. - Downloads page is a top priority for usability improvements. - Community feedback and design input encouraged, though aggregating opinions is a challenge. - **[31:35](https://www.youtube.com/watch?v=zxTMzygBt7s&t=1895) Foundation as Ecosystem Catalyst** - The Foundation turns financial support into core development, infrastructure, and community programs. - Main ask: advocate for employer sponsorship; technical contributions best directed toward PHP itself. - **[33:26](https://www.youtube.com/watch?v=zxTMzygBt7s&t=2006) Looking Forward** - Ongoing encouragement for open contribution, experimentation, and collaboration. - PHP remains modern, evolving, and community-driven. --- ## 📖 References - [YouTube: Growing PHP for the Future // PHPverse 2025](https://www.youtube.com/watch?v=zxTMzygBt7s) - [PHP Foundation](https://opencollective.com/phpfoundation) - [Cyber Resilience Act (EU)](https://digital-strategy.ec.europa.eu/en/policies/cyber-resilience-act) - [php.net](https://www.php.net/) --- ## 🗣️ Paraphrase 1. **On PHP’s Sustainability Crisis and the Foundation’s Formation:** > “Back in 2021, PHP faced a crisis not of technology but of sustainability—after Nikita left, there was only one paid developer. With no organization steering the project, JetBrains and other major industry players collaborated, pooling resources to create the PHP Foundation, ensuring funding, knowledge transfer, and reliable releases.” *Paraphrased:* In 2021, PHP encountered a major sustainability issue when, after Nikita’s departure, only a single paid developer remained. Without any organizational backing, JetBrains and key industry partners joined forces, pooling financial resources to launch the PHP Foundation. This step ensured steady funding, the sharing of expertise, and a return to reliable, on-schedule releases. 2. **On Encouraging Contributions:** > “You can help not just by donating but by contributing to documentation, translations, code testing, and bug triage. The PHP Foundation’s core mission is to turn financial support into funded developer time for critical work. For technical contributions, get involved with PHP itself; for financial help, encourage your employer to sponsor.” *Paraphrased:* Contributions go beyond monetary support—there’s always a need for people to work on documentation, translations, testing, and bug triage. The Foundation’s real impact is using financial backing to enable core developers to focus on essential work. If you want to help technically, contribute directly to PHP. If you can support financially, encourage your employer to become a sponsor. --- ## 📰 Newsletter **PHP Moves Forward: Foundation, Features, and You!** This month at PHPverse 2025, the PHP Foundation showed why it's the backbone of PHP’s evolution. From securing German government funding to pushing the first security audit in a decade, the Foundation’s impact is clear. Want to join the movement? Contributions aren’t just about code—documentation, translations, and bug reporting are all fair game! Key features on the horizon: a faster core VM, modernized extension management, and native JSON schema support. Community feedback is shaping everything, and the open-source website redesign needs your input. Employers: want PHP to keep thriving? Sponsor the Foundation and turn financial support into tangible improvements for everyone. The future’s bright, the roadmap’s public, and PHP’s best days are ahead. Relevant links: - [PHP Foundation](https://opencollective.com/phpfoundation) - [Cyber Resilience Act](https://digital-strategy.ec.europa.eu/en/policies/cyber-resilience-act) - [Contribute to PHP](https://www.php.net/get-involved.php) --- ## ✅ Action Items - **Advocate for Foundation Sponsorship:** Encourage GoDaddy and other large organizations to directly sponsor the PHP Foundation, supporting sustainable development. - **Promote Contributor Pathways:** Highlight documentation, translation, and bug triage as accessible entry points for new contributors—especially valuable for WordPress and broader open-source onboarding. - **Model Foundation Structure:** Use the PHP Foundation’s transition from crisis to sustainability as a case study for OSPO playbooks and open-source program office proposals. - **Align Messaging:** Emphasize transparency, funding, and clear governance structures as critical for healthy open-source ecosystems, reinforcing your focus on inclusive, sustainable communities. - **Integrate Modern PHP Developments:** Incorporate insights on new features (e.g., generics, JSON schema, performance improvements) into developer education and training content. - **Facilitate Website Contribution:** Organize design workshops or async feedback sessions to aggregate opinions on the php.net redesign—model community-driven change. --- ## 🧪 Hypotheses - **Sustainable Funding Increases Contributor Engagement:** If open-source projects like PHP adopt transparent, reliable funding models, community contributions and code quality will rise. - **External Audits Improve Ecosystem Security:** Regular, independent security audits will significantly reduce vulnerabilities in the PHP core and extensions. - **Employer Sponsorship Is a Primary Growth Lever:** Projects receiving direct organizational sponsorship will maintain more consistent, strategic development than those relying solely on volunteer effort. ### 📊 Methodology - **Mixed Methods:** Combine quantitative analysis (contribution rates, code quality metrics, frequency of security incidents) with qualitative interviews (maintainers, contributors, sponsors). - **Data Sources:** GitHub commit history, Open Collective funding reports, PHP Foundation meeting minutes, community surveys. - **Analysis Techniques:** Regression analysis for impact of funding on activity; thematic coding of qualitative feedback. ### ❓ Questions - What barriers remain for new contributors to join PHP core or documentation efforts? - How do funding models influence the priorities and pace of language development? - What experimental features would the community most value in PHP’s future releases? - How does PHP’s governance compare to other major open-source projects? ### 🔮 Future Research - Study long-term impacts of paid vs. volunteer maintenance on open-source sustainability. - Analyze outcomes from opt-in/experimental language features in other ecosystems. - Investigate the effectiveness of public-private partnerships (e.g., German government support) on project resilience. ### 💡 Implications - Advancing knowledge on funding models will help replicate PHP’s success across the OSS landscape. - Improved onboarding and documentation could make PHP—and similar projects—more welcoming and sustainable. - Cross-sector support (government + industry) may become essential for the digital commons’ security and reliability. --- ## 🧠 Learning Styles Assessment **Readability:** Conversational, advanced beginner to intermediate (B2-C1 CEFR). 1. **Visual Learners:** - **Present:** Slides, references to graphs, video format, mention of mockups. - **Improve:** Publish infographics of Foundation funding, contribution stats, and project timelines. 2. **Aural Learners:** - **Present:** Live session, available as video/audio. - **Improve:** Provide audio summaries or podcast versions; offer transcript with time-synced highlights. 3. **Verbal Learners:** - **Present:** Rich narrative, analogies (e.g., “kitchen sink”), explanations of governance. - **Improve:** Add more storytelling and user-case interviews. 4. **Physical Learners:** - **Present:** Not direct, but encourages hands-on code contribution. - **Improve:** Create interactive playgrounds for trying new PHP features or writing docs. 5. **Logical Learners:** - **Present:** Chronological recount of crises and responses, data-driven project updates. - **Improve:** Include step-by-step walkthroughs for getting involved and contribution flowcharts. 6. **Social Learners:** - **Present:** References to collaboration, open mailing lists, Discord, GitHub. - **Improve:** Highlight peer-learning opportunities, community mentorship programs. 7. **Solitary Learners:** - **Present:** Reflective tone, invites solo contributors, offers independent ways to help. - **Improve:** Add personal reflection prompts or solo contribution case studies. 8. **Naturalistic Learners:** - **Present:** Not addressed directly. - **Improve:** Use natural-world analogies (ecosystem health, sustainability). --- ## 📊 Accessibility Assessment - **Screen Reader Compatibility:** The session is primarily a spoken video; transcript available but may need better HTML structuring if published on a website. - **Improve:** Add semantic HTML to transcripts; alt text for all graphics in shared slides. - **Keyboard Navigation:** No barriers for the transcript, but website redesign should ensure all interactive elements are keyboard accessible. - **Contrast & Readability:** Not directly referenced; encourage PHP.net redesign to use high-contrast schemes and accessible fonts. - **Text Resizing:** Transcript is text-based and resizable. - **Improve:** Ensure all future documentation and websites use responsive, accessible layouts. --- ## 🌍 DEIB Assessment - **Cultural Relevance:** Panel includes multiple nationalities and emphasizes global collaboration; encourages non-English speakers to contribute to translations. - **Improve:** Provide more case studies/examples from underrepresented regions or marginalized groups. - **Inclusive Language:** Generally neutral and welcoming; no gendered or exclusionary terms noted. - **Improve:** Continue reviewing language for jargon or complexity, especially in onboarding materials. - **Neurodiversity Support:** Transcript could be chunked with clearer headers, bullet points, and shorter sentences to aid comprehension. - **Improve:** Break dense info into smaller, digestible parts, use more visuals for key points. - **Representation:** The session highlights multiple roles, but gender and other diversity markers not specified. - **Improve:** Feature more diverse voices in future panels and communications. - **Psychological Safety:** Warm, supportive, and community-focused tone. - **Improve:** Explicitly state community guidelines or code of conduct in public forums. --- ## ✅ Logical validity - **Sound Deductive Reasoning:** The causal relationship between funding, paid developer time, and improved language maintenance is consistently and logically presented. - *Strength:* Shows how direct investment leads to project stability. - **Strong Inductive Reasoning:** Infers that rising community contributions correlate with Foundation support—backed by data (e.g., contribution graphs). - **Balanced and Nuanced Views:** Acknowledges both challenges (e.g., burnout, conservative governance) and successes, avoiding one-sided optimism. - **Coherent Counterarguments:** Addresses hesitation about adding features/tooling to core, citing both technical debt risks and benefits. **Potential Fallacies:** - **Appeal to Tradition:** Slight tendency to favor “the way PHP has always done things” regarding governance; could be more open to structural experimentation. - **False Dilemma (Minimally):** Implied at times (“either fund via employers or we lose sustainability”), but counterbalanced by suggestions for volunteer efforts and documentation. **Tone of Voice:** Friendly, collaborative, pragmatic, with moments of humor (“kitchen sink”), never hostile or dismissive. --- ## 🔍 DARVO Analysis Prompt - **Deny:** No evidence of denial regarding challenges; speakers are transparent about PHP’s past crises and the need for funding. - **Attack:** No attacks on detractors, critics, or rival languages; focus is on constructive responses and solutions. - **Reverse Victim and Offender:** The panel does not claim to be a victim, nor does it attempt to invert criticism. - **Conclusion:** No DARVO tactics present. The tone is open, humble, and community-centered. --- ## 🔍 SEO Evaluation 1. **Keywords:** - Present throughout: “PHP Foundation”, “open source”, “contribution”, “funding”, “security audit”, “core developer”, “PHP language”. - Good keyword placement, though meta description is absent (since it’s a transcript). 2. **Meta Description:** - Not provided; recommend adding for improved searchability. 3. **Title Tag:** - Accurate, but could be shortened for optimal search display. 4. **Headers:** - Transcript lacks formal headers; summary should be chunked with H2/H3 for SEO. 5. **Content Length:** - Sufficient depth for high engagement and authority. 6. **Internal/External Links:** - Opportunities for both present (PHP.net, Foundation, etc.). 7. **URL Structure:** - YouTube URL is clean; would recommend similar on any related blog post. 8. **Image Optimization:** - Not applicable here; recommend alt text and optimized images for any slide decks/screenshots. 9. **Mobile Optimization:** - YouTube and Markdown summaries are mobile-friendly. 10. **User Engagement:** - Q&A, calls to action (“contribute, sponsor, get involved”). 11. **Schema Markup:** - Not in transcript; blog post version should use Article or Video schema. 12. **Social Sharing:** - Encourage addition of share buttons and Open Graph/Twitter tags for promotion. --- ## 🎯 Conclusion The PHP Foundation’s approach is a textbook example of how open-source communities can weather crises and thrive through strategic funding, transparent governance, and an inclusive spirit. With a renewed focus on onboarding, experimental features, and global collaboration, PHP’s future looks bright. Community members—whether coders, documentarians, or sponsors—are invited to contribute to PHP’s ongoing evolution. For OSPO leaders, educators, and advocates, the Foundation’s journey offers a compelling model for sustainable, scalable, and resilient open-source stewardship. --- <!-- deep-read:sections end --> [[3. Resources/Readwise/Full Document Contents/Articles/Growing PHP for the Future PHPverse 2025|Full Document Contents]] ## Highlights - and uh chipped in with money to create uh the PHP foundation a nonprofit organization that develops the PHP language. So the mission is to support advance and develop the language and our goals in back then we're quite humble actually to solve those three major problems. find money basically to establish a sustainable funding model, transparent budget. Um then pay developers, find those developers, build ([View Highlight](https://read.readwise.io/read/01jz3jd40nya9q3gpee4z98y8j)) - grow. That's the most important part. So that that means that the work that PHP foundation developers are doing with this maintenance reviewing requests and uh answering questions just ma enabling the community works. So we see it um with every year it grows and it's amazing. So what is it actually the um one thing I wanted to mention before I go to the impact is um uh thing that you might not know is that PHP foundation actually collaborates with the European ([View Highlight](https://read.readwise.io/read/01jz3jd41g2tx4hay0pjksf550)) - and PHP. So it's now officially supported by the PHP Foundation. It's already by this time part of the PHP uh GitHub organization. So we'll try to do more things with this in regards of marketing and um promotion and uh integration. And now I want to pass Mike to Gina who will tell you about some features that are under development. Yeah. Hello. So now it's my turn and I will talk about what some of us or most of us actually have been ([View Highlight](https://read.readwise.io/read/01jz3jd432hyrd7tkm4sqk0wqd)) - we want uh we um we got some inspiration from other languages and we'll uh we'll make sure it's uh welcoming for everyone. Okay. Well, that's good. I'll remember that for next year PHP verse when you're back and we can like discuss this the the progress. No one retrospective. Has the PHP website been updated? I think that's a it's a good one. Neils, did you have any uh any other question? I mean there are like a lot more ([View Highlight](https://read.readwise.io/read/01jz3jd48ke53pptkk0jn5jh1t)) - PHP core functionality on surrounding necessities. Um, and we don't need a lot of like hands-on help on the PHP foundation right now. There's a few things here and there sometimes too, but um, if you have contribution ability, contribute to PHP. Yeah, like do exactly what Gina said. Um, that's that's where we need help. And then the foundation is really a a vehicle to um turn the money that we get from companies into effective change. Yeah. If you have ([View Highlight](https://read.readwise.io/read/01jz3jd4bsher7fmxxc3snshtg))