PHP Foundation Director interview ![rw-book-cover](https://img.youtube.com/vi/x_KmbLtQiJ0/maxresdefault.jpg) ๐Ÿ”— **Source:** [PHP Foundation Director interview](https://www.youtube.com/watch?v=x_KmbLtQiJ0) > [!note]+ Document Notes > --- > tags: #php-foundation #open-source #community #developer-experience #language-governance > author: PHP Annotated > source: YouTube > reference: https://www.youtube.com/watch?v=x_KmbLtQiJ0 > date created: 2024-12-21 10:30 > --- > # ๐Ÿท๏ธ Title: PHP Foundation Director Interview - Elizabeth's Vision for PHP's Future > ## ๐Ÿงฐ Action Inbox > - [H1] Submit PHP talks to non-PHP conferences to increase visibility โ€” community advocacy #php-foundation > - [H2] Create community resources for conference speakers and writers โ€” foundation support initiative #community > - [H3] Establish clearer foundation-internals relationship processes โ€” governance clarity #php-foundation > ## ๐Ÿงญ Table of Contents > - [[#๐Ÿ“ Summary]] > - [[#๐Ÿ“– Main Content]] > - [[#๐Ÿ—’๏ธ Notes]] > - [[#๐Ÿ“š References]] > - [[#๐Ÿ—ฃ๏ธ Paraphrase]] > - [[#๐Ÿ“ฐ Newsletter]] > - [[#โœ… Action Items]] > - [[#๐Ÿงช Hypotheses]] > - [[#๐Ÿ“Š Methodology]] > - [[#โ“ Questions]] > - [[#๐Ÿ”ฎ Future Research]] > - [[#๐Ÿ’ก Implications]] > - [[#๐Ÿง  Learning Styles Assessment]] > - [[#๐Ÿ“Š Accessibility Assessment]] > - [[#๐ŸŒ DEIB Assessment]] > - [[#โœ… Logical Validity]] > - [[#๐Ÿ›ก๏ธ DARVO Analysis]] > - [[#๐ŸŽฏ Conclusion]] > ### ๐Ÿ”— References > - [PHP Foundation](https://thephp.foundation/) > - [ElizabethN Photography](https://elizabethnsphoto.com/) > ## ๐Ÿ“ Summary > - Elizabeth, new director of PHP Foundation, shares vision beyond just language development > - Foundation focuses on PHP sustainability through paid contractors and broader ecosystem support > - Key challenges: improving PHP's perception, modernizing processes, strengthening internals-community relationships > - Elizabeth brings extensive open source experience from SourceForge, GitHub, and CHAOSS > - Bottom line: PHP needs holistic approach combining technical excellence with community advocacy and marketing > ## ๐Ÿ“– Main Content > The interview reveals the PHP Foundation's evolving mission under new director Elizabeth. Originally created to pay developers for language work, the foundation now recognizes that language sustainability requires ecosystem-wide support including newcomer experience, education partnerships, conference advocacy, and perception management. > Elizabeth brings experience from major open source organizations and emphasizes that no programming language exists in a vacuum. She identifies critical gaps in PHP's current approach: outdated website perception, limited community representation in governance, and disconnect between framework users and language development. > The discussion highlights tensions between community ownership benefits (no single company control) and governance challenges (unclear roadmaps, aging processes). Elizabeth advocates for strengthening relationships between internals and broader community while maintaining collaborative rather than controlling foundation role. > ## ๐Ÿ—’๏ธ Notes > #### โฑ๏ธ [00:00](https://youtu.be/x_KmbLtQiJ0?t=0) โ€” [H1] Introduction and background > - Key idea: Elizabeth started with PHP in the "1900s" during ASP vs PHP era > - Evidence: "It was so easy to build things with. The community was fantastic." > #### โฑ๏ธ [05:30](https://youtu.be/x_KmbLtQiJ0?t=330) โ€” [H2] Open source community fascination > - Key idea: PHP community's collaborative nature without central management inspired career path > - Evidence: "Nobody was managing this team... you could just do it. You didn't need permission." > #### โฑ๏ธ [12:45](https://youtu.be/x_KmbLtQiJ0?t=765) โ€” [H2] Career journey through open source > - Key idea: Progression from SourceForge to GitHub to CHAOSS built community expertise > - Evidence: "GitHub from 2012 to 2018... there was like 125 people then" > #### โฑ๏ธ [18:20](https://youtu.be/x_KmbLtQiJ0?t=1100) โ€” [H1] PHP Foundation's core mission > - Key idea: Foundation created for PHP sustainability through paid development > - Evidence: "One person was getting paid to work on the language... that's concerning" > #### โฑ๏ธ [25:15](https://youtu.be/x_KmbLtQiJ0?t=1515) โ€” [H1] Language thriving requires ecosystem approach > - Key idea: Technical excellence alone insufficient; need users, education, perception management > - Evidence: "Nothing exists in a vacuum... making sure there are users around that want to use PHP" > #### โฑ๏ธ [32:40](https://youtu.be/x_KmbLtQiJ0?t=1960) โ€” [H2] PHP website perception problem > - Key idea: Outdated website creates incorrect assumptions about language vitality > - Evidence: "That has come up quite a few times... if someone comes to the page and it doesn't look updated" > #### โฑ๏ธ [38:50](https://youtu.be/x_KmbLtQiJ0?t=2330) โ€” [H1] Conference advocacy strategy > - Key idea: Community should flood open source conferences with PHP talks > - Evidence: "People keep submitting PHP talks... they don't get accepted... We should flood them" > #### โฑ๏ธ [45:30](https://youtu.be/x_KmbLtQiJ0?t=2730) โ€” [H2] Foundation-internals relationship needs clarity > - Key idea: Current prioritization process lacks transparency and clear communication > - Evidence: "We need to be clearer about how we do prioritize things... I have some questions" > #### โฑ๏ธ [52:10](https://youtu.be/x_KmbLtQiJ0?t=3130) โ€” [H1] Governance challenges with community ownership > - Key idea: Community ownership prevents corporate control but complicates unified roadmaps > - Evidence: "Blessing and a curse... no one company can shut it down... difficult to portray unified roadmap" > #### โฑ๏ธ [58:45](https://youtu.be/x_KmbLtQiJ0?t=3525) โ€” [H2] Framework influence in language decisions > - Key idea: Major PHP frameworks have minimal voice in language evolution despite driving adoption > - Evidence: "Biggest frameworks driving PHP's popularity have virtually no say in how language evolves" > #### โฑ๏ธ [1:05:20](https://youtu.be/x_KmbLtQiJ0?t=3920) โ€” [H1] Growing pains from PHP's evolution > - Key idea: 20-year-old processes may not scale for today's larger, more diverse community > - Evidence: "Process that worked 20 years ago... language was much smaller community... might not be sufficient" > #### โฑ๏ธ [1:12:30](https://youtu.be/x_KmbLtQiJ0?t=4350) โ€” [H2] Open source generational transition > - Key idea: Aging contributor base requires intentional onboarding for sustainability > - Evidence: "Graying of open source... we have to create space where people want to come" > #### โฑ๏ธ [1:18:15](https://youtu.be/x_KmbLtQiJ0?t=4695) โ€” [H1] Foundation's collaborative stance on technical decisions > - Key idea: Director avoids public technical positions to prevent perception of control > - Evidence: "I don't want to take over. I want to support and help and collaborate" > ## ๐Ÿ“š References > - [PHP Foundation Website](https://thephp.foundation/) > - [CHAOSS Project](https://chaoss.community/) > - [Elizabeth's Photography](https://elizabethnsphoto.com/) > - [Alfred P. Sloan Foundation](https://sloan.org/) > ## ๐Ÿ—ฃ๏ธ Paraphrase > - PHP Foundation's new director Elizabeth brings extensive open source community experience and views language sustainability as requiring ecosystem-wide support beyond just technical development > - The foundation faces governance challenges balancing community ownership benefits with need for clearer processes, unified roadmaps, and stronger internals-community relationships > - Elizabeth advocates for proactive PHP advocacy including conference submissions, education partnerships, and perception improvements while maintaining collaborative rather than controlling foundation role > ## ๐Ÿ“ฐ Newsletter > ๐Ÿš€ **PHP Foundation's New Vision Goes Beyond Code** > Elizabeth, the PHP Foundation's new director, shared an inspiring vision that extends far beyond paying developers to work on PHP core. Her message: language sustainability requires supporting the entire ecosystem. > **Key insights from the interview:** > - PHP needs better perception management and modern presentation > - Community should actively submit talks to non-PHP conferences > - Foundation will provide resources for community advocacy > - Governance processes need updating for today's larger community > This holistic approach recognizes that technical excellence alone isn't enoughโ€”PHP thrives when newcomers feel welcome, educators understand its value, and the broader tech community sees it as modern and relevant. > **What you can do:** Submit PHP talks to general tech conferences, write about modern PHP capabilities, and help welcome newcomers to our ecosystem. > Resources: [PHP Foundation](https://thephp.foundation/), [Learn PHP](https://learn-php.org/), [PHP: The Right Way](https://phptherightway.com/) > ## โœ… Action Items > #### Community > - Submit PHP talks to general open source and tech conferences > - Write blog posts showcasing modern PHP capabilities for broader audiences > - Create welcoming onboarding experiences for PHP newcomers > - Support local PHP user groups and community events > #### PHP Foundation > - Establish clear communication channels with broader PHP community > - Develop resources for community advocates (talking points, presentation guides) > - Facilitate stronger relationships between internals and framework communities > - Consider modernizing PHP homepage and official presentation materials > #### Governance Evolution > - Review and potentially update RFC voting eligibility criteria > - Create pathways for framework maintainers to have voice in language direction > - Establish clearer foundation-internals relationship processes > - Develop 5-year roadmap through community collaboration > ## ๐Ÿงช Hypotheses > - Active conference advocacy will improve PHP's perception in broader tech community > - Clearer governance processes will increase corporate confidence in PHP's future > - Better onboarding experiences will attract more contributors to PHP ecosystem > - Foundation-facilitated communication will bridge internals-community gaps > ### ๐Ÿ“Š Methodology > - Track PHP talk acceptance rates at general tech conferences over time > - Survey companies about factors influencing language adoption decisions > - Measure newcomer retention rates through improved onboarding programs > - Analyze communication effectiveness through community feedback mechanisms > ### โ“ Questions > - How can PHP governance evolve while maintaining community ownership benefits? > - What specific resources would most help community advocates promote PHP? > - How might framework maintainers gain appropriate voice in language direction? > ### ๐Ÿ”ฎ Future Research > - Comparative analysis of governance models across programming language foundations > - Developer survey on barriers to PHP adoption in modern development contexts > - Impact assessment of advocacy initiatives on language popularity metrics > ### ๐Ÿ’ก Implications > - Practice: Community members should actively advocate for PHP beyond technical circles > - Policy: Foundation may need expanded role in ecosystem support and advocacy > - Education: PHP education partnerships require active cultivation and support > - Governance: Current processes may require significant updates for community scale > ### ๐Ÿง  Learning Styles Assessment > Reading level estimate: Grade 12 > #### ๐Ÿ‘€ Visual learners > - Present: Interview format with clear speaker identification > - Improve: Governance process diagrams, ecosystem relationship charts > #### ๐Ÿ”Š Aural learners > - Present: Full video interview with natural conversation flow > - Improve: Audio-only version, key quotes highlights > #### ๐Ÿ—ฃ๏ธ Verbal learners > - Present: Rich analogies about community dynamics and growing pains > - Improve: Glossary of foundation/governance terms, metaphor expansions > #### ๐Ÿงฉ Kinesthetic learners > - Present: Actionable advocacy suggestions and community participation ideas > - Improve: Step-by-step conference submission guide, community engagement checklist > #### ๐Ÿง  Logical learners > - Present: Clear progression from problems to proposed solutions > - Improve: Decision trees for governance improvements, metrics frameworks > #### ๐Ÿง‘โ€๐Ÿคโ€๐Ÿง‘ Social learners > - Present: Community-focused discussion and collaborative themes > - Improve: Discussion prompts for community groups, collaboration frameworks > #### ๐Ÿง˜โ€โ™€๏ธ Solitary learners > - Present: Individual reflection opportunities on community participation > - Improve: Self-assessment tools for advocacy readiness, personal action planning > #### ๐ŸŒฟ Naturalistic learners > - Present: Organic community evolution analogies and ecosystem thinking > - Improve: Community lifecycle models, ecosystem health indicators > ### ๐Ÿ“Š Accessibility Assessment > #### Screen reader semantics > - Present: Clear speaker transitions and topic headings in transcript > - Improve: Enhanced section markers, better quote attribution > #### Keyboard navigation > - Present: Standard video controls with keyboard support > - Improve: Transcript navigation shortcuts, section jumping > #### Contrast and readability > - Present: High contrast video interface > - Improve: Customizable transcript display options > #### Media and captions > - Present: Full transcript available > - Improve: Timed captions, downloadable formats > ### ๐ŸŒ DEIB Assessment > #### Cultural breadth > - Present: Global perspective on open source collaboration > - Improve: More diverse geographic examples, internationalization discussion > #### Inclusive language > - Present: Welcoming community rhetoric, permission-free participation emphasis > - Improve: Explicit diversity value statements, barrier reduction focus > #### Neurodiversity support > - Present: Structured interview format with clear transitions > - Improve: Multiple content format options, processing time accommodations > #### Representation > - Present: Female leadership in technical foundation role > - Improve: Broader representation examples, accessibility discussions > ### โœ… Logical Validity > #### Strong reasoning > - Deductive strength: Clear cause-effect relationships between community health and language sustainability > - Inductive strength: Pattern recognition from experience across multiple open source projects > - Causal reasoning: Well-supported connections between advocacy efforts and perception improvements > - Analogical strength: Effective comparisons to other language communities and foundations > #### Fallacies > - Appeal to tradition: Some recognition that old processes may need updating, but could examine more critically > - False dichotomy: Occasionally presents either/or choices where multiple options might exist > #### Tone of voice > - Overall tone: Enthusiastic, collaborative, and inclusive with authentic passion for community building > ### ๐Ÿ›ก๏ธ DARVO Analysis > - Deny: No defensive patterns observed > - Attack: No attacks on critics or alternative viewpoints > - Reverse victim/offender: Not applicable to this content > - Emotional cues and rhetoric: Positive emotional appeals focused on community building and shared success > ## ๐ŸŽฏ Conclusion > Elizabeth's vision for the PHP Foundation represents a mature understanding that language sustainability requires ecosystem-wide thinking. Her emphasis on community advocacy, governance evolution, and perception management addresses real barriers to PHP's continued growth. The foundation's expanded mission beyond technical development, combined with Elizabeth's extensive open source experience, positions PHP well for addressing the growing pains of a large, successful language community. > ## ๐Ÿงฑ Refactor Appendix > ### ๐Ÿ“š Literature Split Pad > Purpose: Stage CEE units that become Literature notes. > Split level: H3 > ### [H1] Foundation directors must balance technical and community needs > > [!quote] PHP Foundation Director Interview by PHP Annotated via YouTube. Published 2024. Accessed 2024-12-21. > > "No code exists in a vacuum... there are users, companies, consultants, conference organizers." > Elizabeth's holistic view of language sustainability beyond pure technical development. > [view highlight](https://youtu.be/x_KmbLtQiJ0?t=1515) #xref #articleseed ID:rw_php_ecosystem > ### [H2] Community ownership creates governance tradeoffs > > [!quote] PHP Foundation Director Interview > > "Blessing and a curse... no one company can shut it down... difficult to portray unified roadmap." > The fundamental tension between independence and coordination in community-owned projects. > [view highlight](https://youtu.be/x_KmbLtQiJ0?t=3130) #xref ID:rw_governance_tradeoffs > --- > ### ๐Ÿ”– Atomic Split Pad (Zettel Candidates) > Purpose: Promote reusable claims into Atomic notes. > Split level: H4 > #### [Z1] Open source advocacy requires proactive community effort > - Applies to all programming languages seeking broader adoption > - Referenced throughout interview discussion of conference submissions > - Links: [[Community-Building]] [[Developer-Advocacy]] > #### [Z2] Governance processes must evolve with community scale > - Universal principle for growing open source projects > - Specific examples around RFC voting and framework representation > - Links: [[Project-Governance]] [[Scaling-Communities]] > --- > ### โœ๏ธ Fleeting Queue > Purpose: Capture quick actions for Fleeting notes. > - [F1] Research other language foundation governance models โ€” comparative analysis for PHP #fleeting #inbox > - [F2] Create PHP conference talk proposal template โ€” community resource development #fleeting #inbox > - [F3] Survey PHP developers about governance participation barriers โ€” community input gathering #fleeting #inbox > --- > ## Full Transcript > [00:00] But, uh we've talked a bit about<br>[00:02] elephants. I I I do want to take some<br>[00:05] time, Elizabeth, to get to know you a<br>[00:06] little bit and then uh spend the rest of<br>[00:09] the stream to to talk about PHP, the<br>[00:12] future for of PHP. Uh you're the<br>[00:14] director now. I I I do want to learn<br>[00:16] what that actually means. Believe it or<br>[00:18] not, I've spent a couple of years<br>[00:19] working with Roman and I don't actually<br>[00:21] yet fully understand what a director<br>[00:24] does. So, That is okay. I mean, I have<br>[00:27] so many questions lined up. If people in<br>[00:29] chat have questions as well, you can<br>[00:31] leave them. They will appear here and<br>[00:32] I'll try to keep track of them as well.<br>[00:34] I cannot promise we can answer<br>[00:36] everything, but but but I do have some<br>[00:39] some good news here. Um<br>[00:42] because if I'm not mistaken, Elizabeth,<br>[00:44] you're also coming in a couple of months<br>[00:47] to to PHP Verse, right?<br>[00:49] >> Yes. So, I am sure there will be a lot<br>[00:52] more room and time for more questions<br>[00:55] there. So, if you want to join PHP<br>[00:57] Verse, by the way,<br>[00:59] just follow this channel. It will be<br>[01:00] streamed here on PHP Annotated this<br>[01:02] year. Just subscribe on YouTube and<br>[01:05] you'll you'll be fine. Um<br>[01:08] Elizabeth,<br>[01:09] just very quickly, quick introduction,<br>[01:12] who are you and and what brings you<br>[01:15] here?<br>[01:16] Yeah. Yeah, happy to answer that. Um so,<br>[01:19] PHP is actually how I got my start in<br>[01:22] open source back in, you know, as the<br>[01:24] kids would say, my kids would say, the<br>[01:26] 1900s. Back in the 1900s,<br>[01:29] um when I started working [laughter]<br>[01:31] working on open source. Um<br>[01:33] and at the time, it was, you know, it's<br>[01:36] I you probably heard the story numerous<br>[01:38] times from other people, but at that<br>[01:40] time it was ASP or PHP, which were one<br>[01:44] are you going to use to build a website?<br>[01:45] And so, I thought, well, I'm going to<br>[01:47] try this PHP thing and just see how that<br>[01:50] goes. And it was awesome. And it was so<br>[01:53] easy to build things with. The community<br>[01:55] was fantastic. Everyone was so eager to<br>[01:58] help, so happy, and just a lot of fun.<br>[02:01] Um this is, you know, I'm talking about<br>[02:03] IRC that days, you know, PHPC in IRC. Um<br>[02:08] you know, we just we just had a ball.<br>[02:10] And<br>[02:11] quite frankly, we just had so much fun.<br>[02:13] Um and it just was so curious to me how<br>[02:17] all these seemingly random people came<br>[02:19] together from all over the world and<br>[02:21] we're just building things together and,<br>[02:24] you know, making each other laugh and<br>[02:25] just having a great time. Um but also<br>[02:27] still creating cool things. You know,<br>[02:30] nobody was managing this team of people.<br>[02:33] Nobody was, you know, telling people<br>[02:34] what to do. It was, you know, someone<br>[02:36] had an idea for something, whether it<br>[02:38] be, you know, a community conference or<br>[02:40] user group or whatever it was.<br>[02:42] And you could just do it. Like that was<br>[02:43] mind-blowing to me. You could just do<br>[02:44] it. You didn't need permission. And<br>[02:46] that's one thing I love about open<br>[02:47] source is you don't really need<br>[02:48] permission. You can just do things.<br>[02:50] So,<br>[02:52] so yeah, so I I got my start in PHP. I<br>[02:54] then, you know, was just really taken<br>[02:57] with this idea of community and and<br>[02:58] watching this uh you know, how people<br>[03:00] come together and build things together.<br>[03:02] So, I ended up going to uh<br>[03:06] you'll laugh at this if you know this uh<br>[03:08] SourceForge. If you know about<br>[03:09] SourceForge, you will probably get a<br>[03:11] chuckle out of that. Um but I did go to<br>[03:13] them as a community manager, an official<br>[03:14] community manager, which I was um like<br>[03:17] if someone's going to pay me to do<br>[03:18] community work that I had already been<br>[03:20] doing, then heck yeah. You know, give me<br>[03:22] that. So, I was at SourceForge for a<br>[03:24] little while. I went to another company<br>[03:25] called EngineYard for a little while who<br>[03:27] had just acquired um some PHP<br>[03:30] uh a PHP company and they wanted me to<br>[03:32] kind of be the liaison between their<br>[03:35] company and PHP cuz they were like a<br>[03:37] Rails shop mostly. So, I was kind of<br>[03:39] trying to bring everybody together.<br>[03:41] Um and from there I went to GitHub.<br>[03:44] And and and gone, but uh she'll be back.<br>[03:47] Some small hiccups here on the internet<br>[03:49] side.<br>[03:50] >> than than it is now. Um Just Yeah. Yeah.<br>[03:54] Uh<br>[03:54] backtracking to GitHub because your<br>[03:56] internet just uh decided to do a little<br>[03:58] thing. So, you went to GitHub and then<br>[04:00] you cut out for 5 seconds. So, so that's<br>[04:02] where we<br>[04:03] >> [laughter]<br>[04:04] >> Okay. I went to GitHub from 2012 to<br>[04:07] 2018. Um and it was a lot different than<br>[04:11] than it is now, for sure. There was like<br>[04:13] 125 people then, um you know, when I<br>[04:15] joined. And so, it was it was great. Um<br>[04:18] but it was pre-Microsoft. And so, uh<br>[04:21] yeah, I took a little a little<br>[04:22] sabbatical after that cuz it was<br>[04:25] a little bit stressful, honestly. It was<br>[04:27] it was pretty stressful.<br>[04:28] Um and then um I'm also a nature<br>[04:30] photographer on the side. So, I I sell<br>[04:33] my nature photography at art shows and<br>[04:35] things like that. And um<br>[04:37] I just focused on that for<br>[04:39] like a year and a half. And then COVID<br>[04:41] hit. And I had to uh there were no<br>[04:44] festivals, there were no art shows or<br>[04:46] anything like that. So, I ended up<br>[04:47] coming back to tech.<br>[04:48] I landed in with a absolutely fantastic<br>[04:52] open source project called CHAOSS,<br>[04:56] for those who aren't familiar with it.<br>[04:57] Um it's a Linux Foundation open source<br>[04:59] project. Um and I was the community<br>[05:01] manager there. And I uh we grew the<br>[05:03] community from a couple hundred to about<br>[05:05] 30 3,400, I think, are in there now. Um<br>[05:08] so, that's what I've been doing for the<br>[05:09] past 6 years. And um you know, CHAOSS<br>[05:13] was funded by a a grant from my position<br>[05:16] at CHAOSS was funded by a grant from the<br>[05:18] Alfred P. Sloan Foundation, which is a<br>[05:20] funding org in the in the states. And um<br>[05:23] they funded the project for three rounds<br>[05:26] of 3-year grants each, which is 9 years<br>[05:29] of funding, which is a really long time<br>[05:31] to be funded. So, um that was kind of<br>[05:33] coming that was getting sunset a little<br>[05:35] bit.<br>[05:36] And so, I thought, oh, I should probably<br>[05:38] look for<br>[05:39] look for some work somewhere. I should<br>[05:41] probably get a job. Um and someone sent<br>[05:43] me this uh application and I applied and<br>[05:45] ta-da, here I am.<br>[05:47] So, that's my long and sorted tale of my<br>[05:50] past. Yeah, I mean, really nice. I<br>[05:52] didn't know you were into uh nature<br>[05:53] photography as well. Like I I I you<br>[05:56] don't have it at hand, probably, but I I<br>[05:58] am curious like when you come up to PHP<br>[06:00] Verse, bring some of your favorite<br>[06:02] pictures. I'm curious to to like<br>[06:04] uh get to see those as well.<br>[06:08] >> If anybody wants to see it.<br>[06:10] >> ElizabethNPhoto.<br>[06:11] Oh, perfect. And and also, you'll see my<br>[06:13] name ElizabethN everywhere because I<br>[06:15] used to be Elizabeth Naramore. And so,<br>[06:17] everything I have is ElizabethN even<br>[06:19] though that's not my name now.<br>[06:21] >> Okay. Got it. Yeah. So, it's<br>[06:22] ElizabethNPhoto. So, Okay.<br>[06:25] Nice.<br>[06:26] So, so you're now at the PHP Foundation.<br>[06:29] Yeah.<br>[06:30] >> And I have<br>[06:32] a bunch of questions lined up that I<br>[06:34] gathered from the community as well<br>[06:36] about like how that's going. Of course,<br>[06:38] people are super curious to learn like<br>[06:41] what your future plans are. Um<br>[06:45] maybe you want to start by explaining a<br>[06:48] little bit what the director of the PHP<br>[06:50] Foundation does, but also maybe what the<br>[06:53] PHP Foundation on itself does because<br>[06:57] that might not be clear for everyone,<br>[06:59] actually. Um so,<br>[07:01] take it away.<br>[07:02] Yeah. Um okay. So, the foundation itself<br>[07:06] was created in order to bring more<br>[07:10] sustainability to the PHP language,<br>[07:12] frankly. Um there was a blog post, if I<br>[07:15] remember this correctly, someone correct<br>[07:17] me if I'm wrong, but there was a blog<br>[07:18] post written that basically pointed out<br>[07:21] that no one was getting like one person<br>[07:23] was getting paid to work on the<br>[07:24] language, right? And that's concerning<br>[07:26] to all of us who are, you know, we're<br>[07:29] our um<br>[07:30] depending on that language to stick<br>[07:31] around. So, um the idea then for the<br>[07:34] foundation came about and um the the<br>[07:37] sole focus at that time was to basically<br>[07:40] pay people to work on the language.<br>[07:42] You know, pretty pretty much, full stop.<br>[07:44] Um and in with a longer goal of keeping<br>[07:47] PHP going, keeping it sustainable,<br>[07:50] keeping it thriving.<br>[07:51] So, that's kind of the story of the<br>[07:53] foundation. That's what it was there<br>[07:54] for. Um<br>[07:57] I think over the years, you know, um<br>[08:00] we've kind of realized that there's more<br>[08:02] to it than that. Um so, that kind of<br>[08:05] speaks to my<br>[08:11] to<br>[08:12] uh manage the contractors, make sure<br>[08:15] that they have what they need to do a<br>[08:17] great job. Um that they are, you know,<br>[08:19] everybody's clear on what they're<br>[08:20] working on. Um so, a lot of that, a lot<br>[08:23] of communicating back to the community<br>[08:25] about what what things are being are<br>[08:27] being worked on and um technical blog<br>[08:29] posts sometimes um<br>[08:31] if they're not from they probably won't<br>[08:33] be from me, but if they are from me, um<br>[08:36] yeah, I mean,<br>[08:37] from the staff, you know, from the<br>[08:38] contractors or from whoever. And just<br>[08:40] managing all of that. Managing those<br>[08:42] communications externally.<br>[08:44] Mhm. Okay. Elizabeth, we'll be back in a<br>[08:47] second. You know, I had some some<br>[08:49] internet issues myself.<br>[08:51] >> feel like<br>[08:53] It's fine. It's fine. I I I fill the gap<br>[08:55] every time. I was just telling for the<br>[08:57] folks here that I had some internet<br>[09:00] issues myself today, like throughout the<br>[09:02] whole day. And my internet provider was<br>[09:04] just like, yeah, nope, it's not going to<br>[09:06] work. Uh we're trying to fix it. We<br>[09:08] don't know how it's going like<br>[09:09] >> [laughter]<br>[09:09] >> I was stressing out, but for on my side<br>[09:11] at least, it's working. And for you,<br>[09:14] it's fine. You drop out from from time<br>[09:15] to time a little bit, but then then I'll<br>[09:18] Um yeah, I'll I'll I'll fill the gaps.<br>[09:22] I I I want to uh pick up on something<br>[09:24] you said that<br>[09:27] the PHP Foundation is is was made for<br>[09:31] PHP as a language to to thrive.<br>[09:34] And a big part of PHP is its technical<br>[09:36] development, but you also already hinted<br>[09:38] that<br>[09:39] it's more than just technical stuff. So,<br>[09:41] what does it mean for a programming<br>[09:43] language to thrive? And what are your<br>[09:46] thoughts about that?<br>[09:48] Yeah, I mean, it you know, nothing no<br>[09:50] code exists in a vacuum, right? There's<br>[09:52] a lot of moving parts. There are, you<br>[09:54] know, your users, there are um companies<br>[09:58] that bring the language in. There are<br>[10:01] you know people who build companies,<br>[10:04] whether it be consultants or you know<br>[10:06] conference organizers or<br>[10:09] publications like<br>[10:10] you know whatever that means. There are<br>[10:12] other people involved in this ecosystem.<br>[10:15] So you know we can focus on one piece of<br>[10:18] it but how much better to focus on more<br>[10:21] pieces of it, right?<br>[10:23] So for instance you know making sure<br>[10:25] that there are users around that want to<br>[10:27] use PHP. I think it's [clears throat] a<br>[10:29] big piece of it because we can have the<br>[10:31] best language in the world if nobody<br>[10:32] knows about it, if nobody considers it<br>[10:35] an option or if nobody's learning about<br>[10:37] it then that's not great for a thriving<br>[10:39] language. So it's you know it's kind of<br>[10:42] circular.<br>[10:45] Something. It's a cycle. A cycle.<br>[10:47] >> [laughter]<br>[10:47] >> It's a cycle. And<br>[10:49] so you know part of the thing that I<br>[10:51] would love to see the foundation do is<br>[10:54] provide some more support for a broader<br>[10:56] set of<br>[10:58] pieces of that puzzle in the ecosystem.<br>[11:01] So things like you know newcomer<br>[11:02] experience. Like what is it like for a<br>[11:04] newcomer coming into the language?<br>[11:07] You know there are some opportunities<br>[11:08] for us to improve that experience in<br>[11:11] certain places, making it easier for<br>[11:13] them to learn, making sure the tutorials<br>[11:15] that are out there are updated.<br>[11:17] You know making sure that you know boot<br>[11:19] camps or universities or whoever<br>[11:21] understand that PHP is<br>[11:24] also an option. Right. Yeah. I know a<br>[11:26] lot of folks are just being taught<br>[11:28] Python JavaScript. That's it. So you<br>[11:30] know kind of making those<br>[11:33] relationships, building some some you<br>[11:35] know strengthening those with educators<br>[11:37] as well I think is a piece of it that I<br>[11:39] would like to see us do if possible.<br>[11:41] You know also<br>[11:43] supporting the user groups and the the<br>[11:45] communities that are being built around<br>[11:47] PHP, supporting conferences, community<br>[11:49] conferences in whatever way that looks.<br>[11:52] I don't I don't quite know what that<br>[11:53] looks like yet but they're doing the<br>[11:56] work to bring new people in and to keep<br>[11:59] people around. I mean I think that's<br>[12:01] also another piece of it is you know<br>[12:03] kind of building that cohesion and<br>[12:05] someone's much more likely to stick<br>[12:06] around if they feel like they belong, if<br>[12:09] they feel like they can find answers<br>[12:11] when they need them and they understand<br>[12:13] what they're doing and understand the<br>[12:14] power of a language. So<br>[12:16] you know it's it's a lot of different<br>[12:18] moving parts that all fit together to to<br>[12:20] really push it forward if that makes<br>[12:22] sense. Yeah. [snorts] I am Adrian is<br>[12:25] saying here in chat a new PHP homepage I<br>[12:28] think that's not from 20 years ago would<br>[12:30] be great<br>[12:32] and I can just speak to that for a<br>[12:34] minute. I I have been spending my first<br>[12:37] few weeks here just listening to people.<br>[12:39] You know I opened my calendar up. People<br>[12:41] have been coming in droves. I've talked<br>[12:43] to probably 55 people now at this point.<br>[12:46] You know developers, consultants, people<br>[12:48] at other open source foundations. I mean<br>[12:50] I've talked to so many people and that<br>[12:52] has actually come up quite a few times.<br>[12:53] Interesting. [laughter] It has come up<br>[12:56] because it's it's the optics, right?<br>[12:57] It's the optics of it and if someone<br>[12:58] comes to the page and it doesn't look<br>[13:00] like it's been updated then they're just<br>[13:03] going to make assumptions that are<br>[13:04] incorrect. So you know maybe there's<br>[13:06] something and I don't know if that's the<br>[13:08] foundation's role to do that. I don't I<br>[13:10] don't actually know and this is<br>[13:11] something we're going to have to figure<br>[13:12] out. You know to cuz we have to do all<br>[13:14] this together I think and so like the<br>[13:16] foundation doesn't want to you know come<br>[13:17] in and try to run everything. That's not<br>[13:20] our goal. Our goal is to collaborate and<br>[13:22] support and<br>[13:24] really work with folks to to everybody<br>[13:26] move together at the same place in the<br>[13:28] same way<br>[13:29] if that makes sense. But that is<br>[13:30] definitely something that has been<br>[13:32] >> [laughter]<br>[13:32] >> been brought up. You know and if we're<br>[13:33] trying to evangelize PHP outside this<br>[13:36] open source outside our own PHP bubble,<br>[13:39] you know in the greater open source<br>[13:40] world then yeah I mean we have to care<br>[13:43] about<br>[13:45] We have to care about and then we'll<br>[13:47] come back<br>[13:48] to that thought right away.<br>[13:51] You<br>[13:52] we have to care about it. That's<br>[13:55] I think that's what you're saying. You<br>[13:56] were you were cutting out again.<br>[13:59] The<br>[14:00] what I find interesting and this is this<br>[14:03] is something I'm I'm learning more and<br>[14:04] more throughout the years that I I'm<br>[14:06] also a little bit involved in in some<br>[14:09] community work as a as a developer<br>[14:11] advocate and I'm seeing things not from<br>[14:14] just a<br>[14:16] PHP developer's point of view anymore.<br>[14:19] And and that perception that you're<br>[14:21] talking about it's actually so<br>[14:23] important. I have I was doing this<br>[14:24] livestream with with Roman actually last<br>[14:27] week about PHP debugging and and how it<br>[14:30] could also be improved. Not because the<br>[14:32] current solutions don't work or don't<br>[14:35] get us where we need to be but just<br>[14:37] because for for that that entry level<br>[14:42] is is just it's there is too much<br>[14:44] friction there and I think it's really<br>[14:47] if if we want PHP to thrive and to be on<br>[14:50] the radar again of of<br>[14:53] like the wider web community.<br>[14:57] I think this is actually<br>[14:59] key. It's it's just a homepage. It's not<br>[15:02] going to change anything about the<br>[15:04] language itself. But we we may like it<br>[15:07] or not but it it does affect people's<br>[15:10] impression of PHP and that's just that's<br>[15:13] just yeah<br>[15:14] a fact and we have to deal with that<br>[15:16] whether we like that fact or not.<br>[15:18] Yeah. Yeah.<br>[15:19] So question here from Valerio that that<br>[15:22] I also got from other people um<br>[15:25] What do you think about competition with<br>[15:27] other languages because<br>[15:29] maybe maybe competition isn't the right<br>[15:31] word but<br>[15:33] when we talk about<br>[15:34] PHP as more of like from from this point<br>[15:38] of view it becomes more of a<br>[15:40] dare I say marketing problem rather than<br>[15:42] a technical problem solve.<br>[15:45] How do other languages actually solve<br>[15:47] this<br>[15:48] this problem because every every online<br>[15:51] community is dealing with this this<br>[15:53] first impression part and appealing to a<br>[15:56] potential new audiences and and<br>[15:59] programming languages on their own it's<br>[16:01] like it's it's a weird thing to market,<br>[16:03] right?<br>[16:04] Yeah, it is. It really is. But the thing<br>[16:07] is that if you don't spend any time<br>[16:10] doing that then nobody knows that you're<br>[16:13] there and nobody understands what you're<br>[16:15] about and so there is that piece that<br>[16:17] yeah you do need to tell your own story<br>[16:19] and tell tell people like why why should<br>[16:23] they use PHP? You know what is the the<br>[16:26] benefit and<br>[16:27] if you you know again if you don't tell<br>[16:29] that story then people don't know it.<br>[16:31] They just I mean it's not something that<br>[16:33] is that intuitive. They're not going to<br>[16:35] just know. You have to tell them.<br>[16:38] I actually have been talking to I<br>[16:40] mentioned before the some other<br>[16:42] executive directors at other open source<br>[16:45] foundations. So like the Rails<br>[16:46] Foundation,<br>[16:48] the OpenJS Foundation, Rust Foundation.<br>[16:50] And it's so funny that<br>[16:54] you know we're all in the<br>[16:56] we're all in the open source boat<br>[16:57] together really. You know it's like<br>[16:59] we're all kind of<br>[17:01] in the same space. So we we should<br>[17:04] collaborate with each other honestly if<br>[17:05] we all want to win, if we all want to<br>[17:07] you know maintain this this thing that<br>[17:10] we call open source.<br>[17:11] Cuz we all care about some of the same<br>[17:13] things like funding. You know funding<br>[17:15] across open source is<br>[17:17] like that's a hot topic right now of how<br>[17:20] do we how do we keep open source<br>[17:22] sustained?<br>[17:23] So you know those those directors are<br>[17:25] also wondering you know about this. AI<br>[17:28] is another thing. You know every we're<br>[17:30] all kind of faltering and struggling<br>[17:32] trying to find our way in those places.<br>[17:35] But and you know it's<br>[17:37] >> [laughter]<br>[17:37] >> Rails also has<br>[17:39] I won't say an image problem but that<br>[17:41] perception that they're an old older<br>[17:44] language, you know people want to go to<br>[17:45] something shiny new but you know so<br>[17:47] they're kind of in the same boat we are<br>[17:49] actually honestly.<br>[17:50] But the the thing is like we're stable<br>[17:52] and that's the story we should be<br>[17:53] telling. Is yeah we we might have been<br>[17:55] around a while but that means we're<br>[17:56] stable and that means that<br>[17:58] [clears throat] we're you know mature<br>[17:59] enough to to keep going. So like just<br>[18:03] being able to spin that a little bit<br>[18:04] instead of old and crusty we're actually<br>[18:06] stable and something you can rely on<br>[18:08] because we've you know been doing this<br>[18:10] for a long time.<br>[18:11] So<br>[18:12] it is curious that there you know we<br>[18:14] have some of the same problems and I<br>[18:16] would much rather us<br>[18:18] you know collaborate honestly with with<br>[18:20] other languages to make things better<br>[18:23] and you know maybe improve<br>[18:25] interoperability between us. I don't<br>[18:27] know what that looks like but you know<br>[18:29] just things like that that help<br>[18:30] everybody. Just help everybody. So it's<br>[18:33] less of a competition and more of a<br>[18:34] collaboration. Yeah.<br>[18:36] And you mentioned that you're not sure<br>[18:39] yet whether this falls under the the the<br>[18:44] jurisdiction is not the right word but<br>[18:45] like the<br>[18:48] the responsibilities.<br>[18:51] Yeah yeah you mentioned that you it's<br>[18:53] you're not sure yet that this is a<br>[18:54] responsibility of the foundation.<br>[18:57] I I hope that at least from my point of<br>[19:00] view it is really important and I want<br>[19:02] the foundation to do this. I realize<br>[19:04] there are many very talented technical<br>[19:07] developers on the project now being paid<br>[19:10] to work on PHP core but I think this is<br>[19:14] equally important if you want PHP to<br>[19:16] thrive.<br>[19:18] Yeah. I I do agree. I do agree with you<br>[19:21] 100%. Um<br>[19:22] I think that you know the the fuzzy part<br>[19:25] comes in with with things like the<br>[19:26] website and things you know like<br>[19:28] different things in the language but as<br>[19:30] far as the improving the perception of<br>[19:33] PHP I would love to see the foundation<br>[19:35] kind of help with that definitely. And<br>[19:37] also you know collaborate with others<br>[19:39] who are trying to do the same thing that<br>[19:42] have been doing that you know in their<br>[19:44] own spaces. Just keep you know they keep<br>[19:46] >> [laughter]<br>[19:47] >> I have talked to a few people who keep<br>[19:49] submitting PHP talks to open source<br>[19:50] conferences and they don't get accepted,<br>[19:52] but you know, we shouldn't stop. We<br>[19:54] should We should do more of that. We<br>[19:56] should flood them with PHP talks,<br>[19:58] honestly.<br>[19:59] >> Interesting, yeah. Because then they<br>[20:00] cannot ignore PHP. You know, if we if we<br>[20:03] don't try if we if we're not all trying<br>[20:05] to tell that story, or at least a lot of<br>[20:07] us, then, you know, I think if if that<br>[20:10] happens, then they they have a it's much<br>[20:13] harder to ignore PHP if we Yeah. This is<br>[20:16] coming straight from the director of the<br>[20:17] PHP Foundation, folks.<br>[20:19] Uh and and it's nice because it<br>[20:21] highlights that we're in<br>[20:23] this together, right? Not just the<br>[20:24] foundation, it's not just internals,<br>[20:27] it's all of us. Like it's it's actually<br>[20:29] it's an idea that makes so much sense to<br>[20:32] if you want PHP to be better known,<br>[20:34] let's go to let's submit to more<br>[20:36] conferences outside of PHP, and let's<br>[20:39] just keep spamming them. And that's<br>[20:41] that's on not all of us because not all<br>[20:43] of us are conference speakers, but that<br>[20:45] that's something we like the collective<br>[20:47] community<br>[20:48] >> Yeah. uh can and and and frankly should<br>[20:50] do. I think that's a really great idea.<br>[20:52] >> Yeah. And maybe it's writing, you know,<br>[20:54] writing blog posts, um writing more<br>[20:56] articles for different places, um just<br>[21:00] really kind of taking that taking that<br>[21:02] role of like this is this is my<br>[21:04] language, too. I mean, it it belongs<br>[21:06] {quote} to all of us. So, yeah, I mean,<br>[21:09] if<br>[21:10] again, you don't need permission. So, if<br>[21:11] you want to if you want to do this and<br>[21:13] you want to help PHP, then yeah, you<br>[21:16] know, go for it. Like I would love that.<br>[21:17] I would love to see that. I would love<br>[21:19] to see that. And you know, from a<br>[21:21] foundation standpoint, I'm thinking<br>[21:22] about like what what can we do to help<br>[21:25] people who do want to do that? So, maybe<br>[21:27] it's, you know, here are some talking<br>[21:29] points if you want to use them in your<br>[21:31] in in your talks, or here are some great<br>[21:33] things about PHP you can use, or here's<br>[21:37] a way here's a guide on how to give a<br>[21:39] talk, or how to write it an abstract.<br>[21:41] Like what whatever that is, I don't<br>[21:42] know.<br>[21:43] Um but you know, just providing<br>[21:44] resources for the community so that, you<br>[21:47] know, people can have the tools they<br>[21:48] need to do to do that thing. Whatever<br>[21:51] that is, whatever that looks like for<br>[21:52] them.<br>[21:53] It's it's it's really interesting, and<br>[21:55] I'm and honestly, on a personal level,<br>[21:57] super happy that this is<br>[22:00] on the radar.<br>[22:02] Uh because like I mentioned, the more I<br>[22:04] got into advocacy and the more I got to<br>[22:06] see from like other parts of the PHP<br>[22:08] community, the more I realized this this<br>[22:10] is actually important. It's it's easy to<br>[22:11] think from a developer's point of view,<br>[22:14] like let's just focus on features. I'm<br>[22:16] like I'm I'm a I like features as well.<br>[22:19] If there's one thing I I<br>[22:21] so many people mentioned this also<br>[22:23] before, and but like you generics, when<br>[22:24] are we getting generics? But actually,<br>[22:26] I would like generics, but I I really<br>[22:29] don't think like it's going to change a<br>[22:31] lot of newcomers' minds whether they<br>[22:33] will use PHP or not. So,<br>[22:36] um it's good that that this is on your<br>[22:38] radar, and I and I hope that we'll we'll<br>[22:40] hear more from this in the future. I<br>[22:42] think that's really<br>[22:43] >> absolutely will. 100%. You know, and it<br>[22:46] also kind of feeds back in to uh to<br>[22:49] companies when they are looking to build<br>[22:51] something, you know, what direction do<br>[22:53] they go in? And so, I think also a<br>[22:57] couple of I have I have a lot to say.<br>[22:58] I'm so sorry. I have a lot to say. Um<br>[23:01] but you know, I'm thinking about like<br>[23:03] should we be more um available to<br>[23:06] entrepreneurs? Like should we should we<br>[23:08] be more open in those spaces, or should<br>[23:10] we be, you know, promoting PHP to<br>[23:13] entrepreneurs who just want to build<br>[23:15] something quickly? Well, you know, why<br>[23:17] aren't you using PHP? And with things<br>[23:19] like native PHP, I mean,<br>[23:21] you know, there's just there's so much<br>[23:23] opportunity out there for us to just<br>[23:26] kind of um share our own enthusiasm for<br>[23:29] the language and share our own<br>[23:30] excitement for it. And you know, if I'm<br>[23:32] in a company trying to build something,<br>[23:34] and I have to decide how what do I what<br>[23:36] technology do I want to use? Um I<br>[23:40] you know, I think telling the story of a<br>[23:42] modern PHP<br>[23:46] We'll have to<br>[23:47] hold on a second. See uh So, if<br>[23:49] companies start Yeah, if companies start<br>[23:51] using PHP more, there are more PHP jobs<br>[23:54] for everybody. It just is like a cycle.<br>[23:56] Okay. Because, you know,<br>[23:57] universities are going to teach PHP.<br>[24:00] It's all in a pipeline. So, you know,<br>[24:02] kind of also focusing on every piece of<br>[24:04] that pipeline<br>[24:06] helps us, too. So, there you go. Some<br>[24:08] really really interesting thoughts.<br>[24:10] Thanks for sharing those, and I and I<br>[24:11] hope it's inspiring for people that are<br>[24:14] watching to also like maybe think about<br>[24:16] this a little bit more. I have uh some<br>[24:19] more questions for you.<br>[24:20] Um<br>[24:21] is Rajesh here was asking uh a little<br>[24:24] bit more about his technical side, and I<br>[24:25] noticed when I when I asked people<br>[24:28] to to send their questions, many were<br>[24:30] technical questions as well. There were<br>[24:32] some questions about like this this<br>[24:34] marketing side uh and and PHP's<br>[24:38] reputation within the open source world<br>[24:40] as a whole. Uh but many technical<br>[24:42] questions were there as well. And and I<br>[24:44] think Rajesh asks a very interesting<br>[24:46] question. How does the foundation<br>[24:48] decides<br>[24:50] uh which features make it into PHP core?<br>[24:53] Um<br>[24:54] and I want to link a couple more there<br>[24:56] because people were also asking about<br>[24:59] how the foundation works together with<br>[25:01] internals, the synergy there. Um<br>[25:04] and and<br>[25:06] I I'm curious to hear your thoughts on<br>[25:08] that whole process of how the language<br>[25:10] itself from a technical point of view is<br>[25:12] designed these days.<br>[25:15] Yeah. Yeah, that's a great Those are<br>[25:16] great questions, honestly. Those are<br>[25:17] really great questions. And I'm still<br>[25:20] frankly trying to<br>[25:21] fully understand all of the ins and outs<br>[25:24] of<br>[25:25] the the processes and the workflows that<br>[25:28] are being used.<br>[25:29] >> Yeah. Um and and to the point of um the,<br>[25:31] you know, the the relationship between<br>[25:33] internals and our contractors. So, and<br>[25:36] that's the piece that's a little bit<br>[25:37] fuzzy for a lot of folks, I know. Um<br>[25:40] and I think that, you know, over the<br>[25:41] coming months,<br>[25:42] um we need to be clear about internally,<br>[25:46] we need to be clearer, quite frankly,<br>[25:47] about how we do prioritize things. Um we<br>[25:51] have a team meeting on Monday, uh and<br>[25:53] there's some I have some questions.<br>[25:54] Okay. I have some questions [laughter]<br>[25:56] about that for for them for for our<br>[25:57] contractors. So, you know, like let's<br>[25:59] let's make sure that we can articulate<br>[26:01] these things for the community because I<br>[26:04] don't know that we have have them<br>[26:06] articulated anywhere clearly. Um and so,<br>[26:10] that's part of my job is just to make<br>[26:11] sure that we're all on the same page,<br>[26:13] that we can, you know, communicate that<br>[26:15] that bit.<br>[26:16] Um I think till now it has been um<br>[26:20] you know, kind of organic in the ways<br>[26:22] that those things happen, the way the<br>[26:23] projects happen. It's been very organic.<br>[26:26] Um and I would really love to see us<br>[26:29] uh coordinate and move along. I would<br>[26:32] love to see us provide a roadmap for<br>[26:33] folks. Um you know, so that<br>[26:36] people know kind of what we're thinking<br>[26:38] about and why, and um<br>[26:40] I think that, you know, improving<br>[26:42] communication with the with the<br>[26:43] community will be helpful, too, because<br>[26:45] I know I also kind of got that feedback<br>[26:48] um that it's not always clear what we're<br>[26:50] doing, what the impact of the work that<br>[26:53] we are doing is.<br>[26:54] Um and so, you know, that is something<br>[26:56] that I would like to do more of is to<br>[26:58] communicate with the the community.<br>[27:00] Um and and you know, whatever that looks<br>[27:03] like, maybe it's opening up a a channel<br>[27:05] somewhere, Discord, or, you know, I<br>[27:07] don't know. Um but some way for us to<br>[27:09] have a more direct communication also<br>[27:12] with the community because I don't know<br>[27:14] that that exists really anywhere to my<br>[27:16] knowledge. Um so, As with everything<br>[27:19] PHP, I would say it's it's very spread<br>[27:21] out across several subcommunities.<br>[27:24] Yeah. Yeah. Yeah, which is also a<br>[27:25] challenge for us. Right? There is no<br>[27:28] central place where we can all as a<br>[27:29] community, as a large community, come<br>[27:31] together and and and chat with each<br>[27:33] other. So, you have like your Reddit<br>[27:35] folks, you have Twitter folks, you have<br>[27:36] Discord folks, you have, you know, and<br>[27:38] so, that's challenging. I mean, that<br>[27:39] happens in a big community, of course,<br>[27:42] but it is a challenge for us, you know?<br>[27:45] Uh for our cohesion as a community, but<br>[27:47] but yeah. So, I don't know that I really<br>[27:49] answered those questions<br>[27:50] >> [laughter]<br>[27:50] >> very well. I'm I'm I'm just going to<br>[27:52] follow up if if I'm allowed to with kind<br>[27:54] of a tricky question, maybe.<br>[27:57] Uh<br>[27:58] >> [laughter]<br>[27:58] >> you're you're saying of course, but<br>[27:59] you're not saying you don't know what<br>[28:01] I'm going to ask.<br>[28:03] >> [laughter]<br>[28:04] >> And and<br>[28:05] this is a question uh maybe by by me,<br>[28:09] but<br>[28:10] um<br>[28:11] So, so here's what I'm wondering about.<br>[28:14] There is the foundation who is backed by<br>[28:17] a lot of companies from within the PHP<br>[28:20] community financially who say this is<br>[28:23] indeed what we want to invest in for the<br>[28:26] language that we depend on, that we in<br>[28:28] turn<br>[28:29] >> Yeah. rely on to to make money with,<br>[28:31] basically. We want to invest in this um<br>[28:34] foundation to make sure that PHP<br>[28:37] thrives,<br>[28:39] Um Yeah.<br>[28:42] I think that's really good because it it<br>[28:44] meant<br>[28:45] that<br>[28:47] I I'm going to hang on a second. So, so<br>[28:49] Elizabeth, okay. So, I I think that's a<br>[28:51] really good thing. Um<br>[28:54] because it means that we're now<br>[28:55] investing into having more people<br>[28:58] actually being able to work<br>[29:00] full-time or part-time paid on PHP to<br>[29:02] keep the the language going.<br>[29:04] Um<br>[29:05] and then and then there is<br>[29:07] internals<br>[29:08] who still holds in in like my from my<br>[29:12] point of view, hold all the power to<br>[29:13] decide where the language goes. So, here<br>[29:15] you have this the foundation, a group<br>[29:17] that is basically endorsed by a big part<br>[29:20] of the PHP community financially to<br>[29:23] actually develop this language.<br>[29:25] And it also feels like they are still at<br>[29:29] the mercy of another group, and there is<br>[29:31] some overlap there, of course.<br>[29:33] But of another other group of developers<br>[29:35] who have invested a lot of their their<br>[29:37] free time and and talent and effort over<br>[29:39] decades into this this language. Yeah.<br>[29:42] But<br>[29:43] it also to me, at least, doesn't feel<br>[29:45] 100% fair that<br>[29:48] like<br>[29:49] you<br>[29:50] the foundation is still at the mercy of<br>[29:52] the internals process and anything they<br>[29:55] want to do, even making changes to the<br>[29:57] to the PHP homepage, as far as I<br>[30:00] understand has to go through the RFC<br>[30:01] process, which the last last thing I<br>[30:04] heard Larry checked I did a a live<br>[30:07] stream with Larry Larry Garfield by the<br>[30:08] way a year ago or a year and a half ago<br>[30:11] about about some of his RFCs. I think he<br>[30:14] mentioned there there are around 1,500<br>[30:17] people who are eligible to vote. They're<br>[30:20] most of them are out of the picture, but<br>[30:23] it it it it feels like such a weird<br>[30:26] situation that we're in and I don't want<br>[30:29] to it's a bit of a controversial<br>[30:31] question and I don't want to stir up any<br>[30:32] feelings or or<br>[30:34] make people angry but<br>[30:36] I do feel like it's a genuine question<br>[30:38] to ask. Like is is is the situation as<br>[30:40] it is right now, is that really fair?<br>[30:44] So I have some thoughts.<br>[30:46] >> [laughter]<br>[30:46] >> So<br>[30:47] first I will say that having the<br>[30:50] language be kind of owned, for lack of a<br>[30:53] better word, by the community<br>[30:55] is both a blessing and a curse for us,<br>[30:58] right? So it's a blessing because there<br>[31:01] is no one company that can just decide<br>[31:04] to shut it down, which you know, if you<br>[31:06] think about like something like go, I<br>[31:07] mean that's a thing that could happen.<br>[31:09] Probably won't, but it could, you know,<br>[31:11] things could change very quickly.<br>[31:13] And that that won't happen with PHP<br>[31:15] because no one owns it.<br>[31:17] So that's great.<br>[31:19] On the other hand, it does make it<br>[31:22] difficult to<br>[31:24] portray kind of a unified roadmap of<br>[31:27] here's where we all want the language to<br>[31:29] be in 5 years. Here is where we're<br>[31:31] planning to go. There is no one really<br>[31:34] quote unquote steering the ship as it<br>[31:36] were and that's concerning for some<br>[31:38] companies who want to know what's in the<br>[31:41] future. Yeah. Right? So that is a<br>[31:43] challenge for us as a community as a<br>[31:45] language and we would have to solve that<br>[31:47] together.<br>[31:48] I would love to you know, the foundation<br>[31:50] to to support that if that's something<br>[31:53] that you know, if a roadmap could be<br>[31:55] could be solidified, you know, 5 years I<br>[31:59] don't know how how that would happen. I<br>[32:00] don't know how how that would happen,<br>[32:02] but<br>[32:03] you know, I think that that it's a it's<br>[32:05] a problem we all share, a challenge we<br>[32:06] all share. So<br>[32:09] you know, but we that's the path we've<br>[32:10] chosen. We have no benevolent dictator.<br>[32:12] We have we don't have that. So what do<br>[32:15] we do then? We we have this process that<br>[32:18] is um<br>[32:20] I will say it's imperfect. You know,<br>[32:22] there are pieces of it that could be<br>[32:24] improved. To your point about voting, I<br>[32:27] think you know, a lot of people<br>[32:29] mentioned that to me as as something<br>[32:30] that could be a little bit better of<br>[32:32] just you know, who who is that who are<br>[32:34] the active ones who are up to date, who<br>[32:36] understand you know, how things actually<br>[32:39] are in the moment versus folks who just<br>[32:42] you know, have the voting rights but<br>[32:44] haven't been around for you know, like<br>[32:46] you said<br>[32:46] >> if if I if I just can pick up there, I I<br>[32:49] know it's a<br>[32:50] a little bit of a personal not really<br>[32:52] rant but but<br>[32:54] I'm really passionate about this. It's<br>[32:55] mind-blowing to me that that like the<br>[32:58] biggest frameworks who are driving PHP's<br>[33:02] popularity have virtually no say in how<br>[33:05] the language evolves and I know people<br>[33:08] like Nicolas Grekas from from Symfony<br>[33:10] for example, he got involved in<br>[33:12] internals but only because he was<br>[33:14] working on internal features, not<br>[33:16] because he was<br>[33:18] driving Symfony, the second second<br>[33:20] largest framework in PHP, you know, and<br>[33:23] and that's that's<br>[33:24] I I find that<br>[33:27] very hard. Like I think that I agree<br>[33:29] with you. It's a really a challenge and<br>[33:31] also probably<br>[33:34] a worry for many companies who might<br>[33:36] consider PHP<br>[33:38] because it's<br>[33:39] maybe a a sign of instability or<br>[33:43] uncertainty.<br>[33:45] And yeah, I find I find that a little um<br>[33:49] a little worrying. I I hope that the the<br>[33:53] in the next 5 years or something that we<br>[33:56] may get a little bit more I know clarity<br>[33:59] there on that process, a better process<br>[34:02] actually, not just clarity but a better<br>[34:03] process. That's my hope. Yeah.<br>[34:06] Yeah. Yeah, and you know, what worked<br>[34:08] you know, 20 years ago<br>[34:11] maybe the process needs to evolve and<br>[34:14] the the fact that the community<br>[34:17] representation<br>[34:19] is limited in the voting rights is an<br>[34:22] issue. It's an issue for people. I mean,<br>[34:24] I know it's a controversial thing,<br>[34:27] but there are some things that you know,<br>[34:28] we as a community as a language, we<br>[34:31] might have to just rip the band-aid off<br>[34:33] and and just expose all this to the<br>[34:34] sunlight and figure out what we want to<br>[34:36] do with it together as a group. Because<br>[34:38] it affects everybody, right?<br>[34:41] It affects all of us. It affects our it<br>[34:43] affects my personal ability to talk<br>[34:45] about PHP and to talk about you know,<br>[34:47] what where I see the language going. I<br>[34:49] mean, quite frankly, it's hard to know<br>[34:52] what what is around the corner. It's<br>[34:54] it's hard to know what RFCs are going to<br>[34:56] pass and what aren't and<br>[34:58] it's I know it's it's a it's a thing and<br>[35:01] I would love to see the the foundation<br>[35:03] facilitate a stronger relationship<br>[35:06] between the users and internals because<br>[35:09] I think there's also a little bit of a<br>[35:10] disconnect there. You know, that there<br>[35:13] there's not really a good way to<br>[35:16] collaborate in that way of of what do<br>[35:19] people actually need and what are we<br>[35:21] working on because we want to work on<br>[35:23] this thing. You know, so<br>[35:25] again, I don't<br>[35:26] >> [laughter]<br>[35:26] >> I don't know what the foundation's role<br>[35:28] but I would really love to even just<br>[35:30] facilitate those conversations, you<br>[35:32] know, whether it be you know, let's have<br>[35:34] a summit. We bring everybody together in<br>[35:36] person because that's also affected our<br>[35:38] ability to produce things together is<br>[35:41] the since COVID, you know, user groups<br>[35:43] have kind of have kind of stagnated a<br>[35:46] little. The conferences have gone away.<br>[35:48] There is a resurgence now. People are<br>[35:51] craving that like in-person contact and<br>[35:54] being able to you know, have some<br>[35:56] controversial hard conversations with<br>[35:59] people in person. It's so much easier<br>[36:01] and it's it's much more productive I<br>[36:03] think in some cases than just you know,<br>[36:05] back and forth on a on a mailing list or<br>[36:07] an email or Twitter or whatever it is.<br>[36:08] So<br>[36:09] you know, maybe the foundation could do<br>[36:11] something. I don't know what that looks<br>[36:12] like yet, but I would I would love to<br>[36:14] see<br>[36:15] something like that happen, you know,<br>[36:17] where it's just [clears throat] okay,<br>[36:18] let's just stop and every you know, what<br>[36:21] I just we need a reset almost.<br>[36:23] [laughter] We need to figure out like<br>[36:24] how do we strengthen that relationship<br>[36:26] between users and and the internals.<br>[36:29] Yeah.<br>[36:30] Yeah. So I don't know. It's no, but and<br>[36:32] that's totally fine. That's totally<br>[36:33] fine.<br>[36:35] I didn't prepare you with these<br>[36:36] questions, so<br>[36:37] >> No, it's a great question. I really<br>[36:39] appreciate you you sharing these<br>[36:40] thoughts and and it's a process we're<br>[36:43] going through together and you're giving<br>[36:45] giving a lot of of good things to think<br>[36:46] about. Something that that I just<br>[36:48] realized while you were talking and<br>[36:49] mentioned that<br>[36:51] PHP is<br>[36:52] well<br>[36:53] more than 30 years old now. A process<br>[36:55] that worked 20 years ago and this might<br>[36:58] be a sign of PHP's popularity actually.<br>[37:00] A process that worked 20 years ago when<br>[37:02] the language was a much smaller<br>[37:04] community might not be sufficient<br>[37:05] anymore for<br>[37:07] now you know, when you look at<br>[37:08] frameworks like Laravel<br>[37:11] and people coming into that ecosystem,<br>[37:14] they don't actually consider themselves<br>[37:16] PHP developers anymore. They consider<br>[37:18] themselves Laravel developers and so<br>[37:20] we're talking it's<br>[37:22] like there is this huge shift within PHP<br>[37:26] over the past 10, 20 years and<br>[37:30] you're right, maybe the process that was<br>[37:32] that worked 20 years ago<br>[37:34] um may not be sufficient anymore and<br>[37:37] maybe that is that that might actually<br>[37:39] be<br>[37:40] a good sign of PHP growing and this<br>[37:44] being like the the growing pains.<br>[37:46] >> pains. Growing pains, yeah, that's yeah.<br>[37:48] Exactly. I totally believe that and I<br>[37:50] think that the language as a whole would<br>[37:52] be so much better off<br>[37:56] if we could strengthen those<br>[37:58] relationships and and that and and<br>[38:00] [clears throat] view it more as a you<br>[38:02] know, we need this thing in the language<br>[38:05] so you have to do this thing and<br>[38:07] internals saying, well, no, we don't<br>[38:09] want to do this thing whatever for<br>[38:10] whatever reason. Like it could be it<br>[38:13] could be so much better if we just<br>[38:14] collaborated and listened to each other<br>[38:16] and found a compromise and figured out<br>[38:17] how to how to work together because you<br>[38:20] know, again, it affects all of us.<br>[38:22] And all of everything anytime there's a<br>[38:25] breakdown or you know, a challenge,<br>[38:28] something could be better. Like yeah, I<br>[38:30] mean, it it just affects everybody. So<br>[38:32] we should all care about it. We should<br>[38:34] all kind of want that process to be to<br>[38:37] be great. And you know,<br>[38:39] Sorry, I'm I'm going off on a tangent.<br>[38:41] No, go go go.<br>[38:44] Oh, and then and then [laughter] she<br>[38:45] cuts out.<br>[38:48] We'll have to take it back from we'll<br>[38:50] have to take it back from the tangent.<br>[38:52] You just cut out on the<br>[38:54] perfect spot. Okay, your tangent. I'm<br>[38:55] going to count from 1 2 3 and go. You<br>[38:58] stage is yours. Your tangent.<br>[39:00] Okay. So there is an article by Abby at<br>[39:03] GitHub that talks about the quote<br>[39:05] unquote graying of open source, right?<br>[39:08] And it's how a lot of us are older now<br>[39:11] and we're all old and gray, myself<br>[39:13] included. Although I I do dye my hair so<br>[39:15] you would never know it, but yeah. Um<br>[39:17] And in you know, we have to be concerned<br>[39:19] about the new folks coming in. So we<br>[39:22] have to build on-ramps for people. We<br>[39:24] have to make space for people to come in<br>[39:27] to keep things going because if we all<br>[39:29] retire, then who's left, right? We need<br>[39:32] to keep that pipeline coming and we have<br>[39:34] to create a space where people want to<br>[39:36] come. They want to either contribute to<br>[39:38] internals or contribute to PHP in some<br>[39:40] other way, whether that's starting a<br>[39:42] user group or whatever, but we need to<br>[39:44] have that on-ramp and it<br>[39:46] you know, the the internals I've I've<br>[39:50] I've heard a couple of things that kind<br>[39:51] of contradict each other, so I'm not<br>[39:53] sure how I feel about it, but um<br>[39:56] some folks think that it's perfectly<br>[39:57] fine to be on a mailing list, perfectly<br>[39:59] okay the way<br>[40:01] the the culture of the mailing list is,<br>[40:04] um which is great, awesome. I've also<br>[40:07] heard from other folks that having it<br>[40:08] just be on a mailing list is an<br>[40:11] antiquated platform and it's makes it<br>[40:13] tricky for new people who don't even<br>[40:15] know what a mailing list is, don't know<br>[40:17] how it works, you know, that's just<br>[40:19] another barrier. So, you know, but then<br>[40:22] again switching to a whole other<br>[40:23] platform is like yeah, that's very<br>[40:26] tricky. I mean, they've been on the<br>[40:27] mailing list for forever, right? So, who<br>[40:29] knows? I don't know what the answer is.<br>[40:30] I don't know. I'm just relaying the<br>[40:32] message, but um but you know,<br>[40:35] just making sure that we are leaving<br>[40:37] space and we are bringing new folks in,<br>[40:40] I think is also a concern of mine<br>[40:42] personally. Um and that's kind of hard<br>[40:44] to do, you know, when you so much of<br>[40:47] what PHP is based on is is is on trust<br>[40:50] and there's so many people using the<br>[40:51] language, it's hard to trust new people<br>[40:54] because like do they even know what<br>[40:56] they're doing? Can you know, it's a big<br>[40:57] responsibility if you're contributing to<br>[41:00] this massive thing that people really<br>[41:02] depend on. Um so there's this like level<br>[41:04] of trust that is tricky sometimes in<br>[41:08] some places in the language for sure.<br>[41:10] But if we don't figure out how to solve<br>[41:12] that and how to how to trust new people,<br>[41:16] then then we have a problem or we are<br>[41:18] going to have a problem in 10, 20 years<br>[41:20] when we are all you know, tired<br>[41:23] >> [laughter]<br>[41:24] >> and don't have the energy to contribute<br>[41:25] anymore, Really old, really old.<br>[41:28] Oh, oh. By the way, just quick shout-out<br>[41:32] here. Celestino and Jed is saying they<br>[41:34] just started with PHP and I always love<br>[41:38] reading these messages because like<br>[41:40] truth be told, not many people say this<br>[41:43] and it is it is like a sign of the<br>[41:46] problem that we're talking about here It<br>[41:48] all feeds into itself, yeah. And I I<br>[41:51] wish that, you know,<br>[41:54] there are so many things that PHP could<br>[41:56] improve on. I I I have my my wish list<br>[41:59] for PHP. I make it I make it every year<br>[42:01] again. Um but even in its current state,<br>[42:05] it is it is such a great language and it<br>[42:08] is a stable language with such a rich<br>[42:11] ecosystem. Literally anything you can<br>[42:14] think of, just composer require it<br>[42:17] basically. That Yeah. And and<br>[42:20] it's<br>[42:22] that's that's why I love PHP so much. I<br>[42:25] I'm like for myself, I would like some<br>[42:27] syntax changes, right? And then and I I<br>[42:29] blog about this and then people tell me,<br>[42:32] "Oh, you're just describing C# or Java.<br>[42:34] Just go to C# or Java." And I don't tell<br>[42:37] them, "Yeah, but hang on,<br>[42:39] you know, these syntax changes, they<br>[42:41] would be nice for me, but you you don't<br>[42:43] really realize how much value there is<br>[42:46] in just this community and ecosystem<br>[42:50] and<br>[42:51] I don't want to leave that behind. There<br>[42:54] is it's such a valuable<br>[42:57] place to be<br>[42:58] Oh man, it so is. Yeah. I'm sorry. I'm<br>[43:01] like these are all the all the things<br>[43:03] going through my head when someone say<br>[43:06] says that they just started with PHP,<br>[43:08] but it makes me really happy because I I<br>[43:11] yeah, I I wish<br>[43:15] This is what I wish for PHP. I want<br>[43:18] people who have never experienced the<br>[43:20] community or never written with the<br>[43:21] language, people who are new to open<br>[43:23] source, whoever, I want them to get a<br>[43:25] seat at the table. I want them to<br>[43:26] experience the the awesomeness the same<br>[43:30] that I did, you know? I mean, I if I<br>[43:32] would have had a bad experience with<br>[43:34] PHP, I would not be in open source at<br>[43:36] all. I would have just left. I would<br>[43:37] have just, you know, use something else<br>[43:38] and then I would be coding in a basement<br>[43:40] somewhere, which yeah. I mean, is it<br>[43:43] terrible, but<br>[43:45] And you would be cutting out from time<br>[43:47] to time because in the basement there<br>[43:48] would be pretty pretty crappy<br>[43:50] connection.<br>[43:52] Yeah, I'm so sorry.<br>[43:53] >> [laughter]<br>[43:54] >> It's not. I'm so sorry. I I I I I I I I<br>[43:56] I I I You were in a basement, you were<br>[43:58] saying and then you cut out.<br>[43:59] >> [laughter]<br>[44:01] >> Maybe I should go to the basement.<br>[44:02] >> Yeah, well, who knows? Who knows?<br>[44:04] Maybe that would be better.<br>[44:05] I I I I I I I I I I I I I I I I I I I I<br>[44:06] I I I I I I I I I I I I I I I I I I I I<br>[44:07] I I I I I I I I I I I I I I I I I I I I<br>[44:08] I I I I I I I I I I I I I I I I I I I I<br>[44:09] I I I I I I I I I I I I I I I I I I I I<br>[44:09] I I I I I I I I<br>[44:15] PHP's the love in the community, that is<br>[44:18] what makes PHP special. I mean, the<br>[44:20] language is awesome and it can do<br>[44:22] anything you want, but the love, you<br>[44:24] can't replicate that, right? You can't<br>[44:26] you can't get that from an AI<br>[44:29] >> [laughter]<br>[44:29] >> you know, an an agent. You The love that<br>[44:31] we have for each other is what I want to<br>[44:34] see grow and and I want new people to<br>[44:36] experience it. I want them to thrive<br>[44:38] personally, individually. I want them to<br>[44:40] feel supported and that they belong.<br>[44:42] Like I want all of those things for<br>[44:44] everyone in this community, you know?<br>[44:47] I know, I'm I'm a big cheese ball, but<br>[44:48] oh well. I love cheese. It's great.<br>[44:50] We're we're getting we're getting to<br>[44:51] know you, Elizabeth. It's it's fine,<br>[44:53] it's fine. So, you know, many people<br>[44:55] asked technical questions as well. Um<br>[44:59] generics, when when are generics coming?<br>[45:01] >> [laughter]<br>[45:02] >> What's the status update update on the<br>[45:04] pattern matching RFC?<br>[45:06] What's your opinion on, you know,<br>[45:08] compiled PHP, multi-threaded PHP, async<br>[45:11] PHP?<br>[45:13] There was this whole list, but Yeah. You<br>[45:16] you may share some thoughts about it,<br>[45:17] but I think<br>[45:19] I kind of steered away from from the<br>[45:22] technical parts because it's so easy to<br>[45:25] get lost in discussions on, "Yeah, this<br>[45:28] is this is the way to go or this isn't<br>[45:30] the way to go." While I think like the<br>[45:33] the the most important topic to talk<br>[45:35] about is what we're talking about here<br>[45:37] and and that's So so I'm really happy<br>[45:41] that that<br>[45:43] we we aren't diving into deep rabbit<br>[45:45] holes about generics or<br>[45:48] async PHP or anything. I know people<br>[45:50] have questions about that and so so I<br>[45:53] did want to mention all like that that<br>[45:55] part that part of questions. I can just<br>[45:57] kind of make a statement here is that<br>[45:59] any opinion I have<br>[46:01] would be my own and not like I I shy<br>[46:04] away also. I mean, I am a little rusty.<br>[46:07] We'll just get there cuz it's been<br>[46:08] probably 15 years since I really dug<br>[46:10] deep and wrote code. Um that being said,<br>[46:13] um<br>[46:13] I do have some opinions. I will keep<br>[46:15] them to myself only because there is um<br>[46:21] some of the feedback I received was that<br>[46:23] the foundation can be seen as like<br>[46:26] trying to take over and we don't want<br>[46:28] that. I don't want [clears throat] to<br>[46:29] take over. I don't want to take over. I<br>[46:31] want to support and I want to help and I<br>[46:33] want to collaborate. So, I'm going to<br>[46:35] leave that<br>[46:36] just those discussions to other folks.<br>[46:39] Um either, you know, you can have that<br>[46:41] conversation with our contractors on a<br>[46:42] personal like their own personal thing.<br>[46:45] Um but they like none of those represent<br>[46:47] the foundation's official stance and I<br>[46:49] think that's where people get<br>[46:51] hung up, too, is like, "Oh well, the<br>[46:53] foundation said blah blah blah, then<br>[46:55] we're going to have to, you know, that<br>[46:57] No, I'm not doing that. So, um these are<br>[47:00] these are all, you know, kind of<br>[47:01] internals kind of questions and I know<br>[47:03] that's like a a<br>[47:05] terrible answer and it seems like a<br>[47:07] cop-out, but I I really honestly don't<br>[47:10] want anyone to confuse um my personal<br>[47:12] technical uh Right.<br>[47:15] >> uh thoughts from for being like an<br>[47:17] official foundation statement or or the<br>[47:19] right way because I I mean, I got<br>[47:21] thoughts, but I don't know, you know,<br>[47:23] there's a lot smarter people out there<br>[47:26] than me. And we have such a deep<br>[47:28] technical expertise pool at the at the<br>[47:32] foundation between the contractors and<br>[47:33] the board and, you know, the folks that<br>[47:35] we work with. So, yeah, I mean, that<br>[47:37] part's covered. So,<br>[47:38] >> [laughter]<br>[47:38] >> don't have to worry about that. Hm.<br>[47:41] Well, and<br>[47:43] I think that's a great stance<br>[47:46] and I think you're absolutely right. I<br>[47:48] will say<br>[47:49] I can be biased. We need runtime erased<br>[47:52] generics, folks. I'll just keep<br>[47:54] repeating that.<br>[47:55] You can say all you want, it's my<br>[47:58] opinion, but I<br>[47:58] >> [laughter]<br>[47:58] >> I know I'm right on that on that regard.<br>[48:01] And to be to be clear, any any of those<br>[48:04] types of opinions, I will I will collect<br>[48:06] like I will collect the data. And if if,<br>[48:09] you know, everyone who comes to me<br>[48:10] mentions something, then okay, like this<br>[48:13] is something that should be on<br>[48:14] somebody's radar, whether it's the<br>[48:16] foundation, whether it's, you know, the<br>[48:17] contracts like it should be there. So,<br>[48:20] you know,<br>[48:21] I I do want to hear opinions. So, just<br>[48:23] to be clear, I would love to hear what<br>[48:25] people have to say Well, in in that<br>[48:26] case, I have a little presentation<br>[48:28] prepared about generics. So, listen, no<br>[48:30] >> [laughter]<br>[48:34] >> Let's do a 1-hour presentation about<br>[48:36] generics. No, I did that on on this<br>[48:38] channel actually. If if you're<br>[48:40] interested, go to go to PHP Annotated<br>[48:43] and search for generics, you'll find it.<br>[48:46] But but yeah, Elizabeth is is is cutting<br>[48:48] out again, but it's the perfect time<br>[48:49] because I was going on my rant about<br>[48:51] generics, so that's that's that's great.<br>[48:54] That's the way to go. Yeah. You know,<br>[48:58] Elizabeth, I am<br>[49:00] I heard a lot of of of great things<br>[49:03] today and and this is this is the moment<br>[49:05] where I I think we're going to wrap up.<br>[49:07] Um<br>[49:08] but if if I can just try to summarize<br>[49:11] what you said and I'm really as I as I'm<br>[49:13] saying that I'm I'm like, "Oh, this this<br>[49:16] will be difficult." But but um<br>[49:19] PHP's is so much more than the language<br>[49:23] itself and the foundation's goal is for<br>[49:26] PHP to thrive. That's that's something I<br>[49:28] really remembered. And I think you<br>[49:31] mentioned a lot of great things,<br>[49:33] elements that contribute to that<br>[49:36] language thriving<br>[49:38] and the technical part is definitely an<br>[49:40] important part. We shouldn't like<br>[49:42] totally ignore that.<br>[49:44] No, no, no. But but it is so much more<br>[49:46] than that and I I really hope that as we<br>[49:50] as a PHP community<br>[49:52] um<br>[49:53] we we grow this this this<br>[49:57] um longing for our our favorite language<br>[50:00] to to be known again in as as a modern<br>[50:04] day language as not the language people<br>[50:07] used to know 20 years ago.<br>[50:09] 20 years ago it was really great. I mean<br>[50:11] that's that's when it it grew so much<br>[50:13] popularity but but<br>[50:15] I'm I'm looking forward to maybe that<br>[50:16] that second or is it third renaissance<br>[50:19] of PHP? Yeah.<br>[50:21] And and it is it is a very a tricky<br>[50:25] thing to do, I guess.<br>[50:27] But from from our conversation here<br>[50:30] I would say like I'm I'm really happy<br>[50:33] that that you have some thoughts here<br>[50:35] that you're bringing to the table that<br>[50:37] I think thinking are really important<br>[50:39] and and so I would say they they put the<br>[50:42] right person on<br>[50:44] for the job here. So um<br>[50:46] uh yeah, I I hope it will work out.<br>[50:49] We'll we'll talk again in a couple of<br>[50:50] years and if if nothing came from it and<br>[50:52] and maybe I'll change my opinion but<br>[50:54] >> [laughter]<br>[50:55] >> No pressure.<br>[50:59] uh<br>[51:00] uh Christian here is saying saying uh on<br>[51:03] chat features are the tools but<br>[51:05] leadership is the engine. Uh I'll have<br>[51:07] to think about it for a second but yeah,<br>[51:09] I think there there is there's something<br>[51:11] there.<br>[51:12] Uh I I would n-<br>[51:13] maybe also link in community there<br>[51:15] somewhere but it is it is more than uh<br>[51:19] just the code we write. And um it is<br>[51:23] something I will help advocate for in<br>[51:25] the future as well that this is this is<br>[51:28] something that that PHP is so much more<br>[51:30] than than the code.<br>[51:32] So It is. I'm so excited. I mean I'm I I<br>[51:36] can be annoying so apologies but I<br>[51:38] really [laughter] I'm so excited about<br>[51:41] >> After this stream is done I'm like oh<br>[51:42] this was such a no.<br>[51:45] >> [laughter]<br>[51:46] >> Who let her in? Yeah, you you you can be<br>[51:48] annoying. Yes, that were that's what we<br>[51:49] were saying. Yes, okay.<br>[51:51] Oh my goodness. No, um yeah, I I just<br>[51:54] I'm so excited for the future of PHP and<br>[51:57] I I think that you know, there are so<br>[52:00] many others in the community who share<br>[52:01] my enthusiasm and I really just want us<br>[52:04] to move forward as a community and it's<br>[52:07] cuz it's all on us, right? We're all in<br>[52:09] it together. So [clears throat] if we<br>[52:10] can all you know, kind of work to make<br>[52:12] this the language and to share it with<br>[52:15] the world, then I mean everybody's there<br>[52:18] will be no there won't be anything else<br>[52:20] but PHP. [clears throat] I'm just<br>[52:21] kidding. That would be weird.<br>[52:22] >> That would be I don't think I would like<br>[52:23] that. I wouldn't think I like it twice,<br>[52:24] you know, but um but yeah, I mean<br>[52:27] there's just so many great things about<br>[52:28] PHP and I just I want to share that. I<br>[52:31] want people to know and and to<br>[52:32] understand and to come join us, you<br>[52:34] know, come have a seat at our table and<br>[52:37] and enjoy yourselves and share knowledge<br>[52:39] and and make friends and have fun<br>[52:42] cuz that's what it's about, you know, we<br>[52:43] could be doing anything else with our<br>[52:44] time but if it's not enjoyable and if<br>[52:47] you don't get value out of it<br>[52:48] personally, then it's no good. So I<br>[52:50] really want that to yeah.<br>[52:53] With that we're going to to wrap up<br>[52:56] but but as I mentioned at the start of<br>[52:58] the stream, PHP verse is coming in June.<br>[53:01] More details will be revealed soon.<br>[53:03] Elizabeth, you will be there as well. I<br>[53:05] think you'll be doing a a small talk<br>[53:06] about like the foundation<br>[53:09] and then we'll have Q&A as well so then<br>[53:11] we can it will be a couple more months<br>[53:13] in the future and who knows<br>[53:15] what will have happened by then. Um but<br>[53:19] yeah, definitely make sure to subscribe<br>[53:21] to PHP annotated if you haven't yet<br>[53:23] because that's this is the place where<br>[53:25] we will stream<br>[53:26] uh PHP first this year. So that's going<br>[53:28] to be really cool.<br>[53:30] Thank you for your time, Elizabeth. It<br>[53:31] was really nice. Thank you. No, thank<br>[53:33] you. It's my pleasure. 100% my pleasure.<br>[53:36] And thank you everyone for participating<br>[53:38] in chat as well. I know we didn't cover<br>[53:39] every question but<br>[53:42] um I I really appreciate it people<br>[53:44] thinking along and sharing your<br>[53:46] thoughts.<br>[53:47] And then I hope to see all of you very<br>[53:50] soon. So Elizabeth, thank you for<br>[53:52] joining and<br>[53:54] I'll see you next time. Bye-bye. Unfortunately, Youtube does not provide subtitles for this video, PHP Foundation Director interview, YouTube, 01krc44z0cwz12nhz051a6aypr.