3: PHP Alive and Kicking with Gina Banyard  🔗 **Source:** [3: PHP Alive and Kicking with Gina Banyard](https://www.youtube.com/watch?v=DQqW5LRVJPg) > [!note]+ Document Notes > tags: [PHP, Open Source, Community] > author: [MISSING] > source: [YouTube] > reference: [https://www.youtube.com/watch?v=DQqW5LRVJPg] > date created: {{date:YYYY-MM-DD}} {{time:HH:mm}} > > # 🏷️ Title: 3: PHP Alive and Kicking with Gina Banyard > <!-- 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](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - Include links cited in or relevant to the article. ## 📝 Summary - The episode features Gina Banyard on PHP internals and community. - It matters because core funding and process shape PHP’s future. - Stakeholders include PHP users, core devs, companies, and educators. - Risks include bus-factor issues and outdated docs causing confusion. - Bottom line: PHP remains active, funded, and community-driven. ## 📖 Main Content - Gina traces a path from docs translation to core development. - She explains contribution paths: docs, tests, extensions, and engine code. - The RFC process uses mailing lists and formal voting windows ([wiki.php.net/rfc](https://wiki.php.net/rfc), [news.php.net](https://news.php.net/)). - The PHP Foundation funds maintenance, reviews, and security work ([Open Collective](https://opencollective.com/phpfoundation)). - She notes tradeoffs: fixing long-standing bugs can break workarounds. - She highlights test coverage gaps and CI parallelization needs. - She urges positive advocacy instead of “PHP is dead” framing. - She previews interest in pipes, partials, and generics discussions. - Uncertainties remain around timelines, adoption, and implementation scope. - Documentation quality varies; community PRs help reduce gaps ([php.net/docs](https://www.php.net/docs.php)). ### 🗒️ Notes #### ⏱️ [00:10](https://www.youtube.com/watch?v=DQqW5LRVJPg&t=10) Live show kickoff - Hosts introduce format and community chat. - Magazine, CFP, and swag mentions. #### ⏱️ [05:14](https://www.youtube.com/watch?v=DQqW5LRVJPg&t=314) Guest intro - Gina joins as PHP core developer. - Shares conference speaking experiences. #### ⏱️ [09:56](https://www.youtube.com/watch?v=DQqW5LRVJPg&t=596) Origin story - Started with a Lego website. - Learned C by hacking on PHP. #### ⏱️ [16:50](https://www.youtube.com/watch?v=DQqW5LRVJPg&t=1010) Contribution surface - Docs, translations, tests, extensions, engine. - Encourages bug reports and PRs. #### ⏱️ [22:46](https://www.youtube.com/watch?v=DQqW5LRVJPg&t=1366) RFC workflow - Two-week discussion, then voting. - Mailing list is open to all. #### ⏱️ [24:47](https://www.youtube.com/watch?v=DQqW5LRVJPg&t=1487) Implementation reality - RFCs need implementers. - Votes can pause if issues arise. #### ⏱️ [31:03](https://www.youtube.com/watch?v=DQqW5LRVJPg&t=1863) Bug-fix fallout - SPL change broke community workarounds. - Lesson: stability and expectations matter. #### ⏱️ [37:00](https://www.youtube.com/watch?v=DQqW5LRVJPg&t=2220) Docs notes cleanup - Monthly script prunes downvoted notes. - Notes live separate from docs. #### ⏱️ [43:04](https://www.youtube.com/watch?v=DQqW5LRVJPg&t=2584) Docs ownership gaps - Some extensions lack maintainers. - PRs welcome; issues optional. #### ⏱️ [47:23](https://www.youtube.com/watch?v=DQqW5LRVJPg&t=2843) Foundation model - Open Collective funds dev time. - Reviews accelerate community PRs. #### ⏱️ [55:45](https://www.youtube.com/watch?v=DQqW5LRVJPg&t=3345) Transparency - Transactions visible on Open Collective. - Other communities study the model. #### ⏱️ [59:55](https://www.youtube.com/watch?v=DQqW5LRVJPg&t=3595) Narrative framing - Avoid “PHP is dead” phrasing. - Promote real, current wins. #### ⏱️ [01:05:23](https://www.youtube.com/watch?v=DQqW5LRVJPg&t=3923) Roadmap hints - Interest in partials and generics talks. - Pipes improve ergonomics. #### ⏱️ [01:13:23](https://www.youtube.com/watch?v=DQqW5LRVJPg&t=4403) Community vibe - Conferences are friendly and inclusive. - Social anxiety tips shared. ## 📚 References - YouTube: Episode page: [3: PHP Alive and Kicking with Gina Banyard](https://www.youtube.com/watch?v=DQqW5LRVJPg) - PHP RFC process: [wiki.php.net/rfc](https://wiki.php.net/rfc) - PHP internals mailing list index: [news.php.net](https://news.php.net/) - Externals mirror: [externals.io](https://externals.io/) - PHP docs: [php.net/docs](https://www.php.net/docs.php) - The PHP Foundation on Open Collective: [opencollective.com/phpfoundation](https://opencollective.com/phpfoundation) - PHP source: [github.com/php/php-src](https://github.com/php/php-src) - WordPress Make network (context): [make.wordpress.org](https://make.wordpress.org/) ## 🗣️ Paraphrase - The episode shows PHP’s health through process, people, and funding. - Gina explains how newcomers can contribute and how governance works. ## 📰 Newsletter - PHP is thriving across versions, frameworks, and tooling. - Want to contribute? Start with docs, tests, or a bug report. - Track RFCs via [wiki.php.net/rfc](https://wiki.php.net/rfc) and [externals.io](https://externals.io/). - Explore The WPCC programs and community funding approaches ([thewpcommunitycollective.com](https://thewpcommunitycollective.com)). - WordPress contributors: follow [make.wordpress.org/core](https://make.wordpress.org/core/). - Learning picks: PHP docs, RFC diffs, and recorded talks from recent events. ## ✅ Action Items - **DevRel** - Publish a “Start here for PHP contributions” guide with video. - Host monthly office hours for RFC and docs questions. - Track PR review times and celebrate first-time contributors. - **Developer advocacy** - Demo pipes and partials with real refactors. - Present “From issue to RFC” live walkthroughs. - Measure: PR merged count, time-to-first-review, NPS. - **Education** - Build a mini-curriculum on tests and CI for extensions. - Offer mentorship cohorts focused on docs modernization. - Run contributor onboarding workshops quarterly. - **Developer experience** - Provide example test matrices and parallel DB test templates. - Ship standardized ext skeletons and checklists. - Maintain quickstarts for php-src builds on major OSes. - **Developer marketing** - Shift narratives away from “PHP is dead.” - Share case studies on modern PHP success. - Attribute signups to content via UTM tracking. - **Community management** - Moderate forums with clear codes of conduct. - Run pulse surveys on contributor friction points. - Publish response timelines and escalation paths. - **Internal/external/cross-project** - Align with framework leads on RFC priorities. - Define SLAs for security reports and release notes. - Create a feedback loop between hosts, docs, and foundations. - **OSPO** - **Policy & Governance**: Define decision rights for upstream engagement. - **License Compliance**: Automate scans and training cadence. - **Security Management**: Establish vuln intake and embargo policy. - **Software Inventory**: Adopt SBOMs with freshness SLOs. - **Developer Support**: Open office hours for upstream questions. - **Community Engagement**: Draft MoUs with foundations. - **Strategic Alignment**: Report OSS KPIs to executives. - **Community** - **Maintainers**: Host roadmap clinics and release hygiene reviews. - **Contributors**: Run “first issue” rotations and pairing. - **Sponsors**: Publish budgets and impact reports. - **Ecosystem**: Drill coordinated disclosure exercises. - **WordPress** - **Core**: Prioritize perf budgets and clear release criteria. - **Core Performance**: Set profiling plans and dashboards. - **Core AI**: Define responsible AI guardrails and eval sets. - **Core Program**: Improve cross-team rituals and retros. - **Mobile**: Review offline UX and telemetry. - **Playground**: Build labs for reproducible bugs and lessons. - **Community**: Ship meetup kits and speaker mentorship. - **Training**: Publish lesson paths and certification pilots. - **Marketing**: Maintain editorial calendars and themes. - **Support**: Tighten SLAs and escalate wisely. - **Design**: Establish design tokens and UX audits. - **Documentation**: Close DevHub/HelpHub gaps with examples-first. - **Photos/TV**: Improve taxonomy and caption quality. - **Polyglots**: Align glossaries and sprint on locales. - **Accessibility**: Heatmap issues and run audits on cadence. - **Meta**: Strengthen .org API reliability and contributor tools. - **CLI**: Expand commands and plugin scaffolds. - **Hosting**: Share defaults and reliability telemetry. - **Tide**: Increase scoring transparency and review loops. - **Openverse**: Clarify moderation and education tie-ins. - **Themes/Plugins**: Improve review throughput and provenance checks. - **The WPCC** - **Programs**: Launch fellowships and maintainer stipends. - **Projects**: Run governance clinics and doc sprints. - **Funding experiments**: Test matched grants and milestone payouts. - **FAIR** - **Technical independence**: Verify provenance and signatures locally. - **Policies**: Enforce transparency and sunset clauses. - **Artifacts**: Publish charters, operator agreements, scorecards. ## 🧪 Hypotheses - Funding predictability increases PR review velocity and quality. - Positive narratives raise newcomer contribution rates. - Structured onboarding reduces docs and tests backlog. - Clear RFC tracking improves community engagement metrics. - Cross-foundation MoUs reduce duplicate effort across ecosystems. ### 📊 Methodology - Run A/B tests on documentation entry points. - Time-series analysis of review latency pre/post funding campaigns. - Survey contributors on blockers and clarity of process. - Track RFC discussions and participation via mailing list mirrors. - Correlate narrative shifts with contributor funnel metrics. ### ❓ Questions - Which tests offer the highest ROI for stability today? - How should the community phase in partials and pipes safely? - What governance updates best balance speed and stability? - How can The WPCC model fund WordPress maintenance reliably? ### 🔮 Future Research - Study long-lived bug workarounds and deprecation strategies. - Evaluate CI parallelization patterns across extensions. - Assess note-moderation impacts on documentation accuracy. - Map OSPO practices that best support upstream PHP. ### 💡 Implications - Practice: Newcomers can start with docs and tests confidently. - Policy: Fund maintainers and reviewers, not just features. - Security: Formalize intake and JIT-related expertise backups. - Education: Teach RFC etiquette and test culture. - Funding: Publish transparent ledgers and impact narratives. ### 🧠 Learning Styles Assessment - Reading level estimate: Flesch-Kincaid Grade ≈ 9–10 (approximate). - **Visual learners** - Present: Simple lists and linked resources. - Improve: Flow diagrams for RFC and PR lifecycles. - **Aural learners** - Present: Podcast format aids comprehension. - Improve: 3–5 minute audio summaries. - **Verbal learners** - Present: Definitions and examples in plain language. - Improve: Side-by-side term comparisons. - **Kinesthetic learners** - Present: Try-a-test and “first PR” tasks. - Improve: Step-by-step labs and checklists. - **Logical learners** - Present: Process stages and timelines. - Improve: Decision trees and RACI tables. - **Social learners** - Present: Discord chats and conferences. - Improve: Cohort guides and moderated Q&A. - **Solitary learners** - Present: Self-paced resources and docs. - Improve: Reflection prompts and self-check quizzes. - **Naturalistic learners** - Present: Ecosystem view of projects. - Improve: Lifecycle and sustainability framing. ### 📊 Accessibility Assessment - **Screen reader semantics** - Present: Clear headings and landmarks. - Improve: Descriptive alt text norms. - **Keyboard navigation** - Present: Logical reading order in docs. - Improve: Ensure visible focus and skip links. - **Contrast and readability** - Present: Aim for 4.5:1 minimum. - Improve: Validate large-text thresholds and line-height. - **Text resizing and reflow** - Present: Responsive layouts in docs. - Improve: 200% zoom checks and reduced motion support. - **Media and captions** - Present: Captions on videos where possible. - Improve: Audio descriptions and downloadable transcripts. - **Forms and interactions** - Present: Labeled inputs and error handling. - Improve: Inline validation and generous hit targets. - **Standards reference** - Map gaps to WCAG 2.2 AA success criteria. ### 🌍 DEIB Assessment - **Cultural breadth** - Present: Global contributors and examples. - Improve: More multilingual links and case studies. - **Inclusive language** - Present: Gender-neutral, plain language guidance. - Improve: Fewer idioms and broader glossaries. - **Neurodiversity support** - Present: Chunked sections and structure. - Improve: Predictable patterns and icon+text labels. - **Representation** - Present: Voices from varied roles. - Improve: Balance quotes and imagery inclusively. - **Psychological safety** - Present: Respectful framing and codes of conduct. - Improve: Clear moderation and escalation paths. ### ✅ Logical Validity - **Strong reasoning** - Inductive cases link funding to review throughput. This fits foundation reports and lived experience. - Causal links between outdated docs and developer errors appear reasonable and observed. - **Fallacies** - Possible hasty generalization about “nobody uses X” when bugs go unreported. Prefer measurement or surveys. - **Tone of voice** - Practical, candid, and community-oriented throughout. ### 🛡️ DARVO Analysis - **Deny** - No denial patterns observed. - **Attack** - No attacks on accusers or credibility. - **Reverse victim/offender** - Not present. The discussion stays collaborative. ## 🎯 Conclusion - PHP remains vibrant due to open governance and steady funding. - Practical next steps: write tests, update docs, join RFC threads, and support foundations. <!-- deep-read:sections end --> [[3. Resources/Readwise/Full Document Contents/Articles/3 PHP Alive and Kicking with Gina Banyard|Full Document Contents]] ## Highlights - I just got into PHP because I wanted to make a website for my Lego city when I was 12. That that's literally like how I got into PHP. Uh so uh like in France there's like this well I mean you now know it it's now known as open classrooms but back back in the day it was called which means the the website for noobs basically which has this very good PHP tutorial. I think if you ask 70% of devs PHP devs in France if they learned it from before 2010 they would ([View Highlight](https://read.readwise.io/read/01k6fw4bjjeepdqb6smdg44rrf)) - it once. So I did it. So yeah, I mean that that's a good way of learning. So I guess this sort of leads us on to the the PHP foundation. it its main job, as I understand it, is to allow people to work on PHP core full-time and funded through donations from varying different sources, companies, individuals. But I guess that is still an open-source aspect. So ([View Highlight](https://read.readwise.io/read/01k6fw4bkhaay19cfq6zhsm6ts)) - So, let's um let's bring the the the knowledge down bit. I I have no knowledge of C. Um I'm fairly new into the PHP world. Um, so it's it's it's very interesting uh to me about the the whole process that you go through when making changes. So you have the uh RFC process. I'm interested to see what that looks like from internal developers view. So we we get to hear little bits ([View Highlight](https://read.readwise.io/read/01k6fw4bmyfx7222z2qd4kbkh0)) - will go through the function and just like stare and like if they like download it quite a lot just will just delete. I was like oh this is out of date or if it mentions like oh PHP4 or PHP 5 I'm like well okay that's probably just out of date and not applicable anymore. Uh so can probably get deleted. Um but I think the other thing is like yeah if you see something in a node which is useful then maybe trying to incorporate this into the documentation and then being like oh like have a PR which is oh I'm incorporating notes like there's an ([View Highlight](https://read.readwise.io/read/01k6fw4bsmbfbz0hswzbrasxyc)) - to it that some of those comments are so out of date that it things just don't work that way anymore. So yeah, I've I've been tripped up a few times myself in in the early days. So yeah, just go on. I I was going to say is like the the problem is like the thing with the PHP documentation as well is that like it's not like stuff that is I want to say in control of like PHP ([View Highlight](https://read.readwise.io/read/01k6fw4c1zwrz5axptb11d0ca9)) - cannot say tonight, excites you about PHP at the moment with what's going on or coming up. Uh, I think I mean it's weird because with like PHP 8.5 like tagged and branched, it's just like like, oh, okay, this is going to be there. That's cool. That's great. And there are some things that I'm looking forward to like the pipe operator already I'm writing tooling and I'm like oh god I need this um like this is stuff and where it's like so that I'm quite ([View Highlight](https://read.readwise.io/read/01k6fw4ce8ckmxyqwrzh65wh1v)) - like new collection stuff due to technical reasons. But that's something I'm working on and hopefully will get done next year if it doesn't take all of my time and more. Uh but yeah know I I think PHP is like is in like more stuff is happening. Plenty of stuff is happening. So much to see forward and a lot of stuff that I don't even know is going to happen because like somebody new just comes in ([View Highlight](https://read.readwise.io/read/01k6fw4cxfj3dytap2kwwgz920)) - and contributes something. I was like, "Oh, this is a neat idea." Um, so yeah, if you have an idea, just uh you can submit a patch if you're brave enough. I guess it's the is the carrier. Okay. Yeah. Well, um, yeah, go on, Chris. That is kind of how native PHP came about. They just said, "How can we make mobile apps work?" Answer is like this. Yeah. I mean, it's also like with Franken PHP, right? Is they Yeah. Like I ([View Highlight](https://read.readwise.io/read/01k6fw4decfbrjkhsp730204mw)) - core developer and not known that? But also that's awesome. Yeah. No, that's cool. Like that's what conferences are for. It's like you talk to people and then you realize like, oh wait, I know you from that. So yeah. No, I I I I was at tech for the first time last year and it was a it really it was an interesting experience for me. I hadn't been to any PHP conferences yet. Um I was obviously there to work but still had the chance ([View Highlight](https://read.readwise.io/read/01k6fw4dwnd389e530q12w25d1)) - being someone like that being so open and just talking to anyone there. There's no no sort of um elitist group of people that are all the the big names in the in in our community. It's all one community and I think PHP is probably one of the friendliest communities and has like some of the friendliest conferences like there are so many conferences which are just nice community vibes very enjoyable everybody's approachable like it's yeah ([View Highlight](https://read.readwise.io/read/01k6fw4e8qkx7t7s1yp6b4hqq0))