Episode 22 The WP Community Collective - CourtneyR.dev's 2nd Brain

Episode 22: The WP Community Collective ![rw-book-cover](https://img.youtube.com/vi/FTYTdOi44pc/maxresdefault.jpg) 🔗 **Source:** [Episode 22: The WP Community Collective](https://www.youtube.com/watch?v=FTYTdOi44pc) > [!note]+ Document Notes > tags: #wordpress #community #open-source #funding #contributors > author: Community and Code > source: YouTube > reference: https://www.youtube.com/watch?v=FTYTdOi44pc > date created: 2024-12-22 14:30 > > # 🏷️ Title: Episode 22: The WP Community Collective >  ## 🧰 Action Inbox - [H1] Join as member or partner to fund WordPress contributor projects — WPCC website #wordpress - [H2] Address broken contribution model that relies on infinite human capital — organizational change #sustainability - [H3] Create clear pathways for companies to contribute meaningfully — fellowship/project models #funding ## 🧭 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 - [WP Community Collective](https://wpcommunity.org) - [WordPress Foundation](https://wordpressfoundation.org) ## 📝 Summary - **What happened**: Board members of the WP Community Collective discussed the organization's origin and mission during a special podcast episode for Podcastathon - **Why it matters**: The current WordPress contributor model is unsustainable, relying on volunteer burnout and creating barriers for meaningful corporate contribution - **Key stakeholders**: WordPress contributors, hosting companies, agencies, open source maintainers, and the broader WordPress community - **Risks and tradeoffs**: Without sustainable funding models, WordPress risks losing innovative contributors and falling behind technically - **Bottom line**: The WPCC offers a new model using fellowships and time-constrained projects to sustainably fund WordPress ecosystem development ## 📖 Main Content The WordPress ecosystem faces a fundamental sustainability crisis. While powered by passionate volunteers, the current model burns through human capital at an unsustainable rate. Companies struggle to contribute meaningfully due to unclear pathways and governance challenges. The WP Community Collective emerged after WordPress Foundation leadership explicitly stated they would never hire staff or fund contribution directly. This created a gap that needed filling through an independent nonprofit organization. The WPCC operates on two main tracks: fellowships that provide autonomy for expert contributors to work on broad topics, and time-constrained projects with specific deliverables and compensation. This member-driven model includes community participation in organizational direction while maintaining operational efficiency. ## 🗒️ Notes #### ⏱️ [00:00](https://youtu.be/FTYTdOi44pc?t=0) — [H1] Introduction to special Podcastathon episode - Key idea: Community and Code featuring WP Community Collective board members - Evidence: "This episode is happening in the context of Podcastathon, a global event where podcasters release episodes to raise awareness for nonprofit organizations" #### ⏱️ [02:30](https://youtu.be/FTYTdOi44pc?t=150) — [H2] The fundamental WordPress contribution problem - Key idea: Power imbalance between paid and volunteer contributors - Evidence: "Volunteers were always bringing their passion, but they could never be the leaders in the community that the people who were being paid to be there could be" #### ⏱️ [05:45](https://youtu.be/FTYTdOi44pc?t=345) — [H1] WordCamp San Diego catalyst moment - Key idea: Matt Mullenweg's definitive statement killed foundation funding hopes - Evidence: "Matt said clearly and without any qualifications that the WordPress foundation was never going to hire someone" #### ⏱️ [08:20](https://youtu.be/FTYTdOi44pc?t=500) — [H3] Corporate contribution challenges at GoDaddy - Key idea: Companies need proper accounting processes for contribution funding - Evidence: "I can't shove money into envelopes to get it to people to do the work. We need to have a proper process that accounts for things" #### ⏱️ [12:15](https://youtu.be/FTYTdOi44pc?t=735) — [H2] The problem with sponsored contributors - Key idea: HR and governance issues when employees work on external projects - Evidence: "How do you govern that person? What if that person has an issue within WordPress? Do they go to their company HR?" #### ⏱️ [18:45](https://youtu.be/FTYTdOi44pc?t=1125) — [H1] Chris's font manager intervention example - Key idea: Outside perspectives catch critical issues that insiders miss - Evidence: "Because I said that this was possibly a problem, more discussion was needed and lots of other people that were smarter than me came in" #### ⏱️ [23:10](https://youtu.be/FTYTdOi44pc?t=1390) — [H2] Google's retreat from open source contribution - Key idea: Even large companies struggle with sustainable contribution models - Evidence: "Google decided that they didn't want to have open source contributors paid that are just doing open source work" #### ⏱️ [28:30](https://youtu.be/FTYTdOi44pc?t=1710) — [H3] Jonno's perspective on systemic infrastructure gaps - Key idea: WordPress lacks framework for sustainable contribution at every level - Evidence: "At every step and every angle and every approach to this thing there is no infrastructure, no framework, no standardization" #### ⏱️ [35:20](https://youtu.be/FTYTdOi44pc?t=2120) — [H1] The human capital burnout cycle - Key idea: WordPress burns through talented contributors due to structural failures - Evidence: "The churn I saw in core contributors who just disappeared because they couldn't handle the ecosystem, the politics, the processes" #### ⏱️ [42:00](https://youtu.be/FTYTdOi44pc?t=2520) — [H2] Chris's feature plugin dead-end experience - Key idea: Contributor projects getting killed without explanation drives people away - Evidence: "After that project kind of got deadended, that really killed my desire to ever contribute anything to core ever again" #### ⏱️ [48:15](https://youtu.be/FTYTdOi44pc?t=2895) — [H3] Innovation requires human diversity, not AI - Key idea: AI cannot replace the diverse perspectives that drive innovation - Evidence: "AI is not going to pop into that font manager conversation and be like, 'you know what? I have this use case that this is going to cause a real problem'" #### ⏱️ [52:40](https://youtu.be/FTYTdOi44pc?t=3160) — [H1] WPCC's innovative member organization model - Key idea: Members participate in organizational direction, not just funding - Evidence: "The members are invited but encouraged requested to come and participate, give their opinion, approve new board members" #### ⏱️ [56:30](https://youtu.be/FTYTdOi44pc?t=3390) — [H2] Fellowship vs project funding models - Key idea: Two tracks provide flexibility for different types of contribution work - Evidence: "Fellowships where someone is paid to work on a topic with autonomy, and time-constrained projects with specific deliverables" ## 📚 References - [WP Community Collective](https://wpcommunity.org/) - [WordPress Foundation](https://wordpressfoundation.org/) - [Podcastathon](https://podcastathon.com/) - [Community and Code Podcast](https://communityandcode.com/) ## 🗣️ Paraphrase - WordPress's volunteer-driven contribution model is fundamentally broken, burning through talented contributors without sustainable support structures - Companies want to contribute but lack clear pathways that align with business processes and governance requirements - The WPCC fills the gap left by the WordPress Foundation's explicit refusal to fund contribution through fellowships and project-based compensation ## 📰 Newsletter The WordPress community faces a sustainability crisis that affects everyone building with WordPress. The WP Community Collective offers a promising solution through innovative funding models that could reshape how open source projects support their contributors. **Key Innovation**: Unlike traditional corporate sponsorship or volunteer models, the WPCC creates fellowship and project-based funding that gives contributors autonomy while ensuring accountability through deliverables and member oversight. **Why This Matters**: As we've seen with recent departures from projects like FAIR, the current system isn't working. Without sustainable paths for contribution, WordPress risks losing the diverse perspectives that drive innovation. **Get Involved**: Consider joining as a member or exploring partnership opportunities to help build this new model for open source sustainability. Resources: [Learn WordPress](https://learn.wordpress.org/), [Developer Docs](https://developer.wordpress.org/), [WP-CLI](https://wp-cli.org/) ## ✅ Action Items #### WordPress - Core: Develop clearer pathways for community-funded features to enter core - Community: Create onboarding materials explaining WPCC funding model - Documentation: Document successful contribution models for other projects to reference - Marketing: Amplify stories of successful contributor funding to encourage participation #### OSPO - Policy & Governance: Study WPCC model for applicability to other open source projects - Community Engagement: Evaluate partnership opportunities with member organizations - Strategic Alignment: Assess how sustainable contribution models affect project health metrics #### Community - Maintainers: Consider WPCC fellowship model for critical infrastructure projects - Contributors: Explore WPCC membership for sustainable contribution opportunities - Sponsors: Evaluate WPCC partnership for structured contribution funding #### The WPCC - Programs: Launch first fellowship and project cohorts to demonstrate model - Projects: Document processes and outcomes for transparency and replication - Funding: Develop clear partnership packages for corporate contributors ## 🧪 Hypotheses - Fellowship models will attract higher-quality contributors than traditional volunteering - Member-driven governance will create stronger buy-in for project outcomes than top-down funding - Time-constrained projects with clear deliverables will have higher completion rates than open-ended volunteer work - Corporate partners will prefer structured contribution pathways over ad-hoc sponsorship ### 📊 Methodology - Track fellowship participant retention and contribution quality over 12-month periods - Survey member satisfaction with governance participation and decision-making processes - Measure project completion rates and deliverable quality against traditional volunteer projects - Compare corporate partner satisfaction with WPCC model versus previous contribution attempts ### ❓ Questions - How will the WPCC model scale if successful beyond the WordPress ecosystem? - What happens when WPCC-funded projects conflict with WordPress Foundation or Automattic priorities? - Can the fellowship model maintain quality while expanding to serve more contributors? ### 🔮 Future Research - Comparative analysis of contribution sustainability across different open source projects - Economic impact assessment of sustainable contributor funding on project velocity - Study of governance models that balance member participation with operational efficiency ### 💡 Implications - Practice: Contributors need clear funding pathways that don't require corporate employment - Policy: Open source projects should develop explicit sustainability strategies beyond volunteerism - Security: Sustainable funding reduces bus factor risks in critical infrastructure projects - Education: Developer education should include open source sustainability and funding models - Funding: Traditional corporate sponsorship models may need restructuring for effectiveness ### 🧠 Learning Styles Assessment Reading level estimate: 12th grade #### 👀 Visual learners - Present: Podcast format limits visual elements - Improve: Organizational charts showing WPCC structure, flowcharts of fellowship vs project tracks #### 🔊 Aural learners - Present: Full audio discussion with multiple perspectives - Improve: Chapter markers for easier navigation to specific topics #### 🗣️ Verbal learners - Present: Detailed explanations of concepts, real-world examples and analogies - Improve: Glossary of terms like "fellowship model" and "sponsored contributor" #### 🧩 Kinesthetic learners - Present: Limited hands-on elements in podcast format - Improve: Interactive membership signup process, project proposal templates #### 🧠 Logical learners - Present: Clear cause-and-effect discussion of contribution problems and solutions - Improve: Decision trees for choosing fellowship vs project funding, ROI calculations #### 🧑‍🤝‍🧑 Social learners - Present: Multi-person discussion format encourages different viewpoints - Improve: Community forum for members to discuss episodes, Discord server #### 🧘‍♀️ Solitary learners - Present: Individual podcast consumption allows reflection time - Improve: Reflection questions, self-assessment tools for contribution readiness #### 🌿 Naturalistic learners - Present: Ecosystem analogies for WordPress community health - Improve: More biological metaphors for sustainable community growth ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Audio format naturally accessible to screen readers through transcripts - Improve: Structured transcript with proper heading hierarchy #### Keyboard navigation - Present: Standard podcast player controls work with keyboard navigation - Improve: Ensure website and signup forms are fully keyboard accessible #### Contrast and readability - Present: Audio-first format avoids visual contrast issues - Improve: Ensure supporting materials meet WCAG AA standards #### Text resizing and reflow - Present: Responsive web design for podcast website - Improve: Test transcript display at 200% zoom levels #### Media and captions - Present: Full transcript available for podcast content - Improve: Time-synced captions, downloadable transcript formats #### Forms and interactions - Present: Basic membership signup process - Improve: Clear error messages, progress indicators for multi-step forms ### 🌍 DEIB Assessment #### Cultural breadth - Present: Discussion includes global perspective on open source contribution - Improve: More examples from non-US WordPress communities, multilingual content #### Inclusive language - Present: Gender-neutral terms throughout discussion - Improve: Define technical jargon more consistently for newcomers #### Neurodiversity support - Present: Conversational format may be easier for some listeners than formal presentation - Improve: Provide multiple content formats (audio, text, visual summaries) #### Representation - Present: Mix of gender identities represented on board - Improve: Ensure geographic and cultural diversity in future episodes #### Psychological safety - Present: Respectful discussion of disagreements and challenges - Improve: Clear community guidelines for member interactions ### ✅ Logical Validity #### Strong reasoning - Deductive strength: Strong logical progression from problem identification to solution design - Inductive strength: Multiple examples support general conclusions about contribution challenges - Causal reasoning: Clear cause-effect relationships between funding models and contributor sustainability - Analogical strength: Effective comparison to academic fellowship models #### Fallacies - False dichotomy: Implied either/or choice between current volunteer model and WPCC approach, when hybrid models might work - Appeal to novelty: Assumption that new model is better simply because current model has problems #### Tone of voice - Overall tone: Collaborative and solution-focused, with appropriate frustration about systemic problems ### 🛡️ DARVO Analysis - Deny: No significant denial patterns detected - Attack: Criticism focuses on systems and structures rather than personal attacks - Reverse victim/offender: No evidence of victim/offender reversal - Emotional cues: Appropriate frustration with broken systems, hope for solutions ## 🎯 Conclusion The WP Community Collective represents a crucial experiment in sustainable open source funding. By creating clear pathways for both individual contributors and corporate sponsors, the WPCC addresses fundamental structural problems that have led to contributor burnout and project stagnation. The key insight is that WordPress needs professional-grade infrastructure for contribution, not just passionate volunteers. The fellowship and project-based models offer promising alternatives that balance contributor autonomy with accountability. For the WordPress ecosystem to thrive long-term, sustainable contribution models like the WPCC aren't just helpful—they're essential for maintaining the innovation and diversity that have made WordPress successful. ## 🧱 Refactor Appendix ### 📚 Literature Split Pad ### [H1] Member-driven governance enables sustainable contribution > [!quote] Episode 22: The WP Community Collective by Community and Code via YouTube. Published 2024. Accessed 2024-12-22. > "The members are invited but encouraged requested to come and participate, give their opinion, approve new board members" Demonstrates innovation in open source governance beyond traditional foundation models. [view highlight](https://youtu.be/FTYTdOi44pc?t=3 --- ## Full Transcript [00:17] Hey, welcome back to Community and Code, [00:19] the podcast about the human beings [00:20] behind the commits. This episode is a [00:22] little bit different. The timing is [00:24] different. This is coming out on a [00:25] Friday and we just had an episode last [00:27] week on Wednesday. So FYI, the next [00:29] episode will be in a week and a half [00:30] instead of next week. Uh, and I've got [00:33] not one but three guests on the show [00:35] today. And full disclosure, I'm not [00:36] really just the host this time. I'm also [00:38] one of the people we're talking about [00:40] because this episode is happening in the [00:41] context of Podcastathon, a global event [00:44] where podcasters release episodes to [00:46] raise awareness for nonprofit [00:47] organizations. And the nonprofit I'm [00:50] spotlighting today is one that I'm [00:52] personally involved in, the WP Community [00:54] Collective. The WPCC is built around a [00:57] pretty simple premise. The way WordPress [00:59] or honestly all of open source has [01:01] funded or maybe more accurately hasn't [01:03] funded its contributors is broken and [01:06] someone needed to try and fix it. So [01:08] Seed and Courtney Robertson started [01:10] talking and the WPCC was born. In this [01:14] episode, you'll hear from my fellow [01:16] members of the WPCC board of directors. [01:18] Courtney Robertson, who you might know [01:20] as a developer advocate at GoDaddy and [01:22] one of the most dedicated contributor [01:24] advocates in the ecosystem. Save Reed, [01:26] CEO and co-founder who's been doing this [01:28] work since before before the org had a [01:30] name. And Jonno Alderson, a technical [01:32] SEO and web performance nerd, former [01:34] Yoast and someone with a gift for saying [01:37] uncomfortable true things out loud. We [01:39] get into the origin story of the WPCC, [01:42] the structural problems that made it [01:43] necessary, some personal war stories [01:46] from the contributor trenches, and what [01:48] the WPCC is actually trying to build. If [01:51] you care about the future of WordPress, [01:53] this one's for you. [01:59] Welcome to community and code the [02:01] podcast where we talk to the human [02:03] beings behind the commit. I am here for [02:06] a I don't know community and code first [02:08] because I have more than one human on [02:10] the screen today. Um this is [02:14] >> allegedly this is a bit of a different [02:17] uh show uh today because we're doing it [02:19] during the week of the podcastathon. Um, [02:21] Podcastathon is a sort of global [02:24] podcasting event where uh podcasters can [02:27] talk to nonprofits or about nonprofits [02:30] to raise money for said nonprofits. And [02:31] I just happen to know some folks uh that [02:36] are involved in a nonprofit, including [02:40] uh myself. So, uh I'm here today with [02:43] the WPCC, the WP uh community collected [02:46] collective. Um and I'm just going to go. [02:49] >> We're also collected. We're collected [02:51] here. Uh so I'm just going to let you [02:53] all introduce yourselves rather than [02:55] giving you an introduction. Uh I'm going [02:57] to go down uh around in the circle and [02:59] then I'll introduce myself last because [03:01] I don't know uh I'm also on the screen [03:03] and I'm also uh in the board of [03:06] directors. So topping starting at my top [03:09] right I see Courtney Robertson. [03:12] >> Hello everybody. I am indeed Courtney [03:14] Robertson. Courtney R.ev. Uh these days [03:17] you'll find me as a developer advocate [03:20] at GoodDaddy, a longtime WordPress [03:23] contributor, [03:24] one who is active in multiple [03:26] open-source communities, and I really [03:29] care about sustaining the open- source [03:32] communities and the pipeline of [03:34] contributors. [03:36] >> Yes. Yes. And then we have Se say, [03:38] introduce yourself. [03:39] >> Get me. Hi, I'm Seed and um I am the [03:43] CEO, part-time CEO of the WPCC, also a [03:46] board member as a CEO and um [03:51] gosh, I don't that's all I got for the [03:53] intro. [03:56] >> I feel like I feel like you have the [03:57] more storied at least podcasting career [04:00] than some of the rest of us on this [04:02] show. [04:02] >> Yeah, I had that podcast for a while, [04:04] but you know, here here we are. No [04:08] podcast, [04:09] >> but all podcast. [04:11] >> Yes, all all the podcasts. And then uh [04:13] directly underneath me, Jonno, introduce [04:16] yourself. [04:17] >> Hi. Yeah, I'm increasingly concerned [04:19] about identifying as a human. Like every [04:21] time I have to do a capture and it asks, [04:22] I'm like, at what point am I [04:25] sufficiently augmented to cross the [04:26] line? Anyway, yeah. Hi. Um, I'm Jono. [04:28] I'm a technical SEO and web performance [04:31] nerd and a deep deep WordPress nerd. Um [04:34] yeah, I've got a background in all sorts [04:36] of kind of WordPressy stuff and [04:37] consultancy and enterprise spaces and [04:40] worked at Yoast for a little bit. Um [04:42] give or take five years. Yeah. And [04:44] recently joined the WPCC as a board [04:45] member to try and work out how on earth [04:47] we wrangle this ecosystem to make it I [04:50] want to say functional as a kind of [04:52] aspirational starting point. Sure. We [04:55] can get into more of that later. [04:57] >> Uh and I'm Chris. I'm the host of this [04:59] podcast. uh in the hat that I am wearing [05:01] today. I am also uh the interim [05:04] president of the WPCC. Um I have been in [05:07] WordPress for 20ish years, I guess. Um I [05:13] have done all sorts of things in the [05:15] WordPress ecosystem. I freelanced for a [05:17] long time. I uh did online developer [05:20] training. Uh I worked at agencies and [05:23] now I'm a uh developer advocate at [05:25] Pantheon. Uh Courtney and I share uh the [05:28] developer advocate uh hat among the hats [05:31] that we wear. Um so we're here to talk a [05:34] little bit about uh the WPCC uh and I [05:39] mean also like about ourselves and how [05:40] we got involved in in our our own paths [05:43] uh here. But because we're doing this [05:45] special thing uh with all the board of [05:47] directors on uh I kind of want to talk [05:49] about the WPCC. So uh I will will turn [05:53] it over to probably Courtney or say or [05:56] perhaps both of you to talk about sort [05:58] of the origin story of this community [06:01] collective like what was sort of the [06:03] idea uh besides [ __ ] be broken yo um [06:09] that that led to the the organization [06:12] >> I didn't say it quite like that [06:13] >> say could you take us back to work camp [06:16] us in San Diego Go. [06:21] >> Yeah, exactly. Um, well, once upon a [06:24] time there was a thing called word [06:26] camps. Just kidding. [06:28] >> Once upon a time. Oh, no. What happened? [06:30] >> Oh, yeah. No. Um, so the, uh, the [06:34] problem of [06:36] sponsored and volunteer contribution has [06:40] been on my mind for a very long time. [06:42] Uh, prefounding the WPCC. Um, basically [06:47] ever since I I was involved in in [06:48] WordPress, it it there there was a power [06:51] imbalance. Um, there was a a volunteers [06:55] were always bringing their passion, but [06:58] they could never be the leaders in the [07:01] community that the people who were being [07:03] paid to be there could be because they [07:05] just had another job. And it was it was [07:09] difficult to watch volunteers who were [07:13] there with their own for their own heart [07:17] for people to be um not not totally [07:22] sidelined but just be a little bit [07:24] diminished versus the folks who were [07:26] being paid to show up there. And not [07:28] that those folks were not also full of [07:31] passion. a lot of times they were but [07:33] it's a just that that it's it's a weird [07:36] tension. The other issue that was clear [07:40] um even at that time was the issue that [07:45] other than companies who are strictly uh [07:49] basically WordPress companies um they [07:53] have they they have normal rules and in [07:56] the capitalism rules uh you have [07:59] employees and you have those employees [08:02] work on things that make you money [08:03] generally that's the general idea. So [08:06] hiring an employee to then go send them [08:09] off to work on something that you don't [08:11] really have any control over that you [08:14] can't uh really judge there's no metrics [08:17] we don't know how productive people are [08:19] being there's no standard there I saw [08:23] company and I talked to a lot of [08:24] companies who who couldn't contribute [08:28] who couldn't find a way to contribute [08:30] and you know we even this week there's [08:33] been just a lot of talk about the will [08:35] to contribute [08:36] And I think that it is difficult to say [08:40] definitively that there is no will to [08:43] contribute or there people don't want to [08:45] contribute when there isn't a clear way [08:47] to contribute. If there was a clear way [08:50] to contribute and no one was [08:51] contributing, you know, company-wise, [08:53] then that would sure make that [08:55] conclusion. But until we make something [08:57] that makes sense, um I it's not the [09:00] conclusion that I would draw. So, this [09:03] is something that I tossed around in my [09:05] head for a long time. Courtney and I of [09:07] course uh have known each other for a [09:09] long time in the word press world and uh [09:12] would talk about this. Um Courtney's [09:14] worked for the big companies and has [09:16] seen firsthand that struggle of [09:20] contribution versus the business model [09:23] of the actual business. Um, and I was [09:26] really of the mindset that there was uh [09:31] an a nonprofit organization that could [09:34] do this. I've worked in nonprofit for [09:36] basically my whole career um with [09:39] nonprofits. So, I know that they're [09:40] capable of managing a space, hiring [09:44] staff, etc. Um, so in uh that word camp [09:49] San Diego in 2022, I think it was 2022. [09:52] >> Yeah. [09:53] >> Um, familiar. [09:55] >> We uh were at a Q&A. Courtney and I were [09:57] at a Q&A with Matt who was doing Matt [09:59] Mullenwig who was um speaking and um [10:02] someone asked a question. I actually [10:04] don't recall at the moment who asked [10:05] that question. Wasn't me and they said [10:07] you know what's something something the [10:08] foundation going to do about this and uh [10:12] Matt said clearly and without any [10:16] qualifications that the WordPress [10:18] foundation was never going to hire [10:20] someone. they were never going to fund [10:22] the contribution. And up until that [10:24] point, I had been reluctant to do [10:27] anything about this problem because I [10:29] thought that would be step overstepping [10:32] that that would be stepping on the [10:33] boundaries of the where the foundation [10:35] was. Learning this that it was not going [10:39] to happen. Basically, after that [10:42] meeting, Courtney and I were like, well, [10:45] I guess someone needs to do it. [10:48] >> Yeah. I was on the flip side of this. [10:50] >> Um [10:51] >> I had asked Matt a different question [10:53] kind of related to this. I should go [10:55] back and look at that video. Um it was [10:57] one of the first camps right after the [10:59] pandemic lifted travel regulations and [11:01] things. And so um you know on my end [11:04] there is a challenge. GoDaddy does [11:06] sponsor several individuals. We have two [11:09] full-time staff. We have one uh engineer [11:12] that puts 10 hours a week into the [11:14] plug-and review team and then we also [11:16] sponsor two other folks. One of them [11:17] being Joe Doulson um part-time uh just [11:21] for a certain amount for contract hours. [11:22] And I was looking at all of this from [11:24] the internals of how hard is it to [11:26] explain exactly why we need to do this, [11:29] how to do it. And then at the end of the [11:31] day, I can't shove money into envelopes [11:34] to get it to people to do the work. We [11:36] need to have a proper process that [11:38] accounts for things, I don't know, like [11:40] taxes envelopes. [11:42] >> Yeah. Can't put cash in envelopes to [11:45] give to contributors. Um, and also [11:48] wanting to make sure that the the [11:49] funding went to kind of specific areas [11:52] in particular. So, what are the spots? [11:55] You know, we have sort of two different [11:57] needs going on in the WordPress space. [12:00] Um, and I've done some looking beyond [12:01] the WordPress space to see how others [12:03] sort of solve for this and different [12:05] projects have different ways. But, uh, [12:08] we have people that are really [12:09] passionate about doing a thing that [12:12] can't get the funding to keep doing it. [12:14] And it may not be critical to what's [12:18] coming in the next release or you know [12:20] what's good for the entire community and [12:23] also um a struggle to perhaps see what [12:29] is going on throughout the project that [12:31] needs some funding like if we spot that [12:34] the docs team I just saw that very [12:36] recently I was so glad to see this that [12:38] the uh parser tool was broken to get dev [12:40] docs done. So being able to spot what [12:43] are the big needs of a project. [12:45] >> I was happy to see that the parser tool [12:46] was broken. Right. [12:47] >> No, [12:49] I was I was happy to see it got fixed. [12:52] Right. And so [12:53] >> there you go. There you go. [12:53] >> Being able to spot some of those areas [12:56] across all the teams and identify and [12:58] what does having the dev docs mean to [13:01] devs mean to contributors, mean to AI, [13:05] mean to general search results? It's [13:07] it's kind of an important feature I [13:09] would think, but it wasn't deemed a [13:11] priority enough to get fixed in a timely [13:13] manner. And so we're sort of going back [13:15] and playing catch-up on these things. So [13:17] these are bits of the project that are [13:19] critical infrastructure. One would argue [13:22] and clearly needed some reinforcement [13:25] and some advocacy work of like who can [13:27] do this part. [13:30] >> Interrupted by dog. Um [13:32] >> sorry, no worries. Um [13:34] >> kind of interruption. Let's let's I want [13:37] to take a step a little bit back and [13:38] talk about like we tal say you were [13:40] talking about like the things that the [13:42] WPCC stepped in to fix for for people [13:45] that don't that are outside the [13:46] WordPress community um who might not [13:49] know what the contributor model that we [13:51] all because we've been in this uh this [13:53] place for a long time uh do know like [13:55] what does it look like for like how does [13:59] how does the existing status quo really [14:02] work in uh I I'll I'll toss it to you, [14:05] Courtney, because like you said, you you [14:07] have some folks who actually are paid [14:09] staff um who who work on core and [14:13] there's some other organizations, some [14:14] agencies and stuff that that sponsor [14:16] development. Um but like really like you [14:19] said earlier, that's like we have [14:22] somebody on staff who's doing this [14:24] thing, but like it's basically like [14:27] they're not an employee anymore, right? [14:28] They're just working on this other [14:29] thing. Um [14:30] >> so it kind of depends. Um, so in our [14:34] context, Kira Schroeder, who has been [14:37] with the project, uh, oh gosh, I want to [14:40] say 20 years as almost as a sponsored [14:44] contributor at various organizations. [14:46] She has done amazing work, but her work [14:48] is often hidden because it's security [14:50] work or it's research work that involves [14:53] reading over really old track tickets to [14:55] understand why people came to [14:57] conclusions they did and use that as a [14:59] decision maker moving forward. So, it's [15:01] not obvious work, but it's important [15:04] work. Um, I believe that came about when [15:06] Aaron Campbell was still at GoDaddy at [15:08] the time. And Aaron was able to express [15:10] to executives, here is the real need and [15:13] what and why. And Kira and our other [15:15] contributor, George Madame, goes by the [15:18] handle Maduka. Um, George works on [15:20] specifically Gutenberg projects. They [15:22] both live in nations that GoDaddy [15:24] doesn't actually even technically hire [15:26] in. So, uh, in both of their cases, they [15:29] are contracted staff, which is slightly [15:32] different if you get into human [15:33] resources and knowing our companies can [15:35] be open. So, that's another headache. [15:37] Um, [15:38] there are plenty of them. And what [15:41] budget does this go to and who are they [15:43] reporting to and what are they doing? [15:45] But one of the things that we're [15:46] actively doing, um, I had the chance, [15:49] it's almost two weeks ago now, Matt [15:51] Mullenweg did a tour of the walkthrough [15:53] on WordPress 7.0 [15:55] and specifically mentioned GoDaddy and [15:57] Blue Host in that and um it was in the [16:00] context of testing on collaborative [16:02] editing and of course we're going to be [16:04] testing on collaborative editing. George [16:06] came back and said, "Oh, we would like [16:08] to do this." And so part of my role has [16:10] been internally to facilitate, let's [16:12] talk to our hosting folks that can do [16:14] load balance testing. And that piece of [16:18] the performance puzzle is what does this [16:20] look like in our page plans down to our [16:23] shared hosting plans. you know, [16:25] everything from an enterprise agency to [16:27] a small individual person that may or [16:29] may not be a business owner even um [16:32] building out their websites and who's [16:33] going to use this and what does it look [16:35] like when we have a thousand people at [16:37] the same time on many different websites [16:40] but two people actively trying to edit a [16:43] thing at the same time. What does that [16:45] do to the hosting environments? So in a [16:47] sense there are feedback loops and [16:48] mechanisms but what is the struggle is [16:51] that they really are primarily dedicated [16:53] just to the project. So being able to [16:55] say like okay now have them provide us [16:58] with what we should be testing and doing [17:01] um facilitate those meetings across [17:03] strange time zones as one does and on [17:06] top of that then ensure that we're [17:08] providing the relevant feedback of our [17:10] experience. Not just what's it do for [17:12] our own customers, but also if we need [17:15] this to be something that changes. [17:16] Here's the results. Let's tell core team [17:20] what we can, let's tell the hosting team [17:22] what we can about that experience as [17:24] well. Not giving out proprietary [17:26] information, but giving out things that [17:27] would help the future of the release, [17:29] right? And so there's logistics that can [17:32] be had to sort of interoperate between [17:34] those. And I think it's up to each [17:36] company. And perhaps there may be [17:37] seasons where there is more of that [17:40] feedback mechanism happening between the [17:42] sponsored contributors and the host [17:44] themselves or the plugin, the theme [17:46] company, whomever is sponsoring them. [17:48] There can be some of those seasons where [17:49] you have a lot of internal collaboration [17:52] as well. And then other seasons where [17:54] there's not much of that going on. It [17:55] just depends on what's going into the [17:57] release and where things are. [18:00] Speaking for myself, I'm not paid to be [18:02] a sponsored contributor to core, but [18:04] obviously as a somebody who works at a [18:06] hosting company. Uh things that go into [18:09] WordPress matter very deeply to the [18:12] things that we work on. And uh my recent [18:14] or not so recent anymore uh but a claim [18:17] to fame that I wear as a badge of honor [18:19] is that I was able to single-handedly [18:21] mostly single-handedly uh punt uh the [18:24] font manager uh out of uh a version of [18:27] WordPress to a later version of [18:29] WordPress because I raised the question, [18:31] hey, what does this do if uh if how does [18:37] this like I need a way to tell the the [18:40] file system that where you're storing [18:41] these files is actually someplace I need [18:43] a I need a way to put these files in a [18:46] different place because uh Pantheon as a [18:48] host has a readonly file system on our [18:50] production sites. You can't just write [18:52] files to WP content. The way that we do [18:55] that is we map it to a writable [18:57] directory. And then the other part of [18:58] that was um that there's database [19:02] references uh that are made to all those [19:04] fonts and we have three different [19:06] environments, dev, test, and live. So [19:08] which one is the canonical source of [19:09] truth? Right? If we were to say, "Oh, [19:11] we're going to put those in the file [19:13] system and commit them in the dev [19:15] environment," then it would be committed [19:17] files up through the chain and then but [19:20] the production environment wouldn't know [19:22] about the fi the existence of those [19:23] files because they're not in the [19:25] database and we don't want to be like [19:27] playing with database like backups from [19:30] a dev environment into the production [19:32] environment. That seems dumb. Um, so [19:34] like because I said that this was [19:38] possibly a problem, it would be a [19:39] problem for us and anyone else who might [19:41] have a similar sort of uh uh [19:43] infrastructure like other AWS platforms [19:46] would would fall into this category. Uh [19:49] more discussion was needed. More stuff [19:51] happened. I didn't do anything other [19:53] than raise my hand in Slack and like put [19:55] some comments on a on a uh Gutenberg [19:57] ticket uh in in GitHub, but lots of [20:00] other people that were smarter than me [20:02] came in and and then came to a [20:04] conclusion and basically said, "Hey, [20:05] does this work?" And I'm like, "Yeah, [20:07] honestly, all I need is a filter, but [20:09] that's great, too." [20:10] >> Um, so but but outside of that, too, [20:13] like so like again, I'm not sponsored. [20:16] There are companies or agencies that do [20:19] have a paid staff member on on their [20:22] staff. The problem that that that [20:25] potentially introduces, I'm thinking [20:27] very recently of uh Google had some [20:30] sponsored open source contributors that [20:32] were contributing directly to core. And [20:34] recently Google decided that they didn't [20:37] want to have open- source contributors [20:40] paid that are just doing open source [20:42] work that are not actually doing Google [20:43] work. and they kind of got rid of that [20:46] team. So like there is this economics of [20:49] like does it make sense for this [20:51] company? Google's a really big company. [20:52] They could throw money around like crazy [20:54] a lot more so than than my company or [20:56] your company Courtney. And but like if [20:59] it's not matching up with those those I [21:02] don't know success metrics uh then it's [21:05] a pretty easy thing to say yeah we're [21:07] going to reallocate you to something [21:09] else or we're just not going to have you [21:11] do this anymore. It's it's not even just [21:14] economic. It is obviously that's a huge [21:16] part of it like is this com this person [21:18] who's working like you know marketing is [21:20] not usually although I think that it is [21:22] but people look at marketing as the [21:24] first people they fire because they're [21:25] not producing something they're not like [21:27] making the money right um again I argue [21:30] that that is untrue but that is the [21:32] general take right um and I think that [21:36] so obviously the economics of you know [21:38] paying someone to do something that's [21:40] not producing a product or working on [21:42] something is one thing but there's also [21:44] HR are like how do you govern that [21:47] person like how do you like what if that [21:50] person has an issue within WordPress [21:52] that never happens um and you know do [21:55] they go to their company HR or what's [21:57] the deal because they're a contractor [21:59] and not a company and do they go to the [22:01] company meetings like it it and do are [22:03] they included in the all hands right [22:05] like even though they don't know what [22:06] those projects are because they're not [22:08] even working on them so it really it [22:10] creates it's just a difficult situation [22:13] when you have like basically someone in [22:15] a bubble that works full-time for a [22:17] company, but that company has no like [22:20] really say over what they're doing or [22:22] anything. So, I I think it's that [22:23] tension that is really the problem that [22:26] that we have identified and the the the [22:32] one of the values, one of the greatest [22:34] values in my mind of the community is [22:36] exactly what you just said, Chris, like [22:38] you weren't working on this particular [22:40] issue. You weren't doing the coding for [22:41] it. you just looked at it and because [22:43] you're coming at it from an outside [22:45] perspective, you have a different use [22:47] case. You have different needs for your [22:49] company and for your clients, you were [22:52] able to say, "Hey, I can I can look at [22:53] this in a different way." The people who [22:55] were working on it, they have uh what [22:57] are those like blinder things? Horse [22:59] blinders like this. You're focused on [23:01] your stuff. When we have the community, [23:05] we're bringing in all of those use [23:06] cases. It's like the mini eyeballs or [23:08] mini hands make light work, you know, [23:10] and more eyeballs on something means you [23:13] can see more things. And that value is [23:17] is to me what has created the the [23:23] juggernaut that is WordPress. I I do not [23:26] believe that it is because of a single [23:29] person's vision or the paid contributors [23:32] who have been coding like it's it's been [23:36] much more than that and that is a value [23:39] that is really intangible. But even like [23:42] what you said, you you you probably [23:44] saved like hosts the world over from [23:47] mass chaos because you brought in [23:51] information and sort of an innovative [23:53] idea or an outofthe-box way of thinking. [23:55] I don't even know what the right word [23:56] for it is, but it's just a different [23:59] perspective and it turns out it's [24:01] valuable. [24:02] >> Isn't that fascinating that [24:04] >> Yeah. on an off chance somebody who [24:07] happened to be already inside that [24:09] ecosystem caught something that would in [24:12] the grand scheme of the universe fairly [24:13] minor but yeah consequential right there [24:15] would have been issues there would have [24:15] been overheads there would have been [24:16] support there would have been time blah [24:17] blah blah blah blah and then you look at [24:19] the two examples Courtney and say you've [24:21] raised that on one hand you've got the [24:24] enthusiastic practical individuals who [24:27] just want to do the thing and yet there [24:29] is no clear route as to how they can do [24:32] that so they're functionally blocked [24:34] from contributing in a meaningful way [24:36] that's sustainable. And then say at the [24:38] other end of the scale, you've got one [24:39] of the biggest companies in the world, [24:41] Google, who are for a thousand reasons [24:44] obviously incentivized to influence and [24:46] shape this thing for whatever reason, [24:48] even if it's something as simple as I [24:49] don't know if we can shave 2 kilobytes [24:52] off every WordPress homepage. That saves [24:54] rainforests. And yet simultaneously, [24:57] they can't develop a business case of an [25:00] argument or clarity around how that [25:01] should work and why they should do it [25:02] and what does success look like. So at [25:04] every every step and every angle and [25:06] every approach to this thing there is no [25:08] infrastructure there is no framework [25:10] there is no standardization and the only [25:13] thing that keeps us going and yeah even [25:16] even keeps us moving forward which maybe [25:17] masks some of how hideously broken this [25:19] is is the enthusiasm of the people who [25:21] are already inside that bubble and [25:22] ecosystem catching things spotting [25:24] things and being willing to continue but [25:26] I don't see I don't see a way forward [25:28] where we maintain that current [25:30] enthusiasm and resourcing without [25:33] improving the onboarding, the [25:34] facilitation, the governance, all of [25:36] those other words around how do we [25:38] encourage, invite, sustain, support and [25:40] yeah, so hugely excited that we might [25:43] try and address some of that. [25:45] >> One of my favorite words. I just want to [25:46] say you just [25:50] >> on boarding and like inclusion. It's [25:52] amazing. I I want to I want to shift [25:55] gears and and go into your uh origin or [25:58] origin story into the WPCC in a second, [26:01] Jonno, but like what you just said, like [26:03] we are recording this the day after two [26:06] very influential members of the [26:07] WordPress community have uh publicly [26:09] announced that they're stepping back [26:11] from the fair project, which is uh [26:13] federated and independent repositories, [26:15] a project that started uh largely last [26:17] year as a package manager for WordPress [26:20] that is an alternative to the uh essent [26:23] potentially single point of failure that [26:26] is everything that is on the wpu [26:28] wordpress.org uh infrastructure. The [26:31] idea being that if there are disperate [26:34] uh sources of where stuff comes from [26:38] then it it spreads the load and it means [26:40] that if WordPress.org goes down or if [26:43] the maintainer of WordPress.org or [26:45] heaven forbid does something to a plugin [26:49] for example that just hypothetically [26:52] that affects everybody that is a [26:54] consumer of that plugin then uh then the [26:58] like there's there's a a buffer there [27:00] that's a supply chain issue right and so [27:02] the idea was we can create this [27:04] federated list of servers that then [27:06] create uh that create some some distance [27:09] from that from that supply chain uh [27:11] security uh vulnerability um And the [27:14] they're stepping back because they spent [27:16] the last year going to various people, a [27:20] lot of them hosts looking for funding so [27:22] they could form a board so they could [27:24] fund the development of this of this [27:25] infrastructure package. Uh and basically [27:29] the answer they got was we don't have an [27:31] appetite for it because of the status [27:32] quo because of all the things. So like [27:35] in many ways uh the WPCC [27:38] uh to me represents like okay that was [27:41] that was the old model that's like the [27:43] old way of of thinking about how [27:45] contribution works and how community [27:48] projects work. Uh perhaps perhaps the [27:51] WPCC is a new way or something different [27:55] that could happen uh instead. Um but [27:58] >> that's the plan. [28:00] >> Yeah, that's that's my plan. That's the [28:03] theory of change that we are working [28:04] under. [28:05] >> Yeah. Um but Jon because mostly because [28:08] uh we've we've heard a lot from from S [28:10] and Courtney, I'd like to hear from you [28:12] about like how you like what attracted [28:15] you to this community collective to this [28:19] project um and made you want to get [28:22] involved in it to begin with. [28:24] >> Well, that's big, isn't it? Um [28:27] >> I I think the short version is I am [28:32] driven by hope for a better web, a [28:36] better humanity, a better world, etc. In [28:39] the broadest possible sense, as I'm sure [28:41] many of us are. And as one small and [28:44] probably quite inconsequential human, [28:46] the one small surface area of that that [28:48] I can affect is the web where I work and [28:51] I consult and I try and help businesses [28:54] to take their terrible, slow, unhelpful [28:56] websites and to make them marginally [28:58] better in the hopes that in aggregate [29:00] that has some kind of positive impact. [29:02] So I've been doing that for a long time. [29:03] started out in web development in [29:05] agencies in SAS platforms and was [29:08] continually frustrated by how poor a lot [29:12] of the tech was. So they're on content [29:14] management systems that that break that [29:16] don't have basic functionality etc. I [29:18] spent most of 2013 working in I don't [29:21] know enterprise CMSs that were doing [29:24] versions of what WordPress had done 10 [29:26] years ago badly. [29:29] And I think of all the of all the things [29:32] we could be doing on the web and all the [29:34] things we should be doing, I see the [29:36] idea of WordPress as the operating [29:37] system really resonating. I think this [29:40] is as a piece of tech and a platform the [29:43] right way to build the right kinds of [29:45] things for what we need as a society as [29:47] businesses as individuals. I think the [29:49] idea of democrat democratizing [29:50] publishing yeah super nice but there's a [29:53] much bigger impact here about [29:54] democratizing the web anyway all of [29:56] that. So I joined Yoast SEO to try and [30:00] do a bit of that to try and go how do we [30:02] make every site 1% better in a way that [30:04] meaningfully impacts the world and helps [30:06] people and helps businesses and makes [30:07] money and fuels the the engines of [30:09] capitalism [30:09] >> and saves the [30:11] >> Yeah. Yeah. That too. Yeah. Yeah. [30:12] Meaningful impact etc. Um and that was [30:14] must have been around 2016ish I think [30:16] maybe even earlier. And it was the first [30:18] time that I'd gone from being a [30:19] WordPress developer to really meeting [30:20] and understanding the community and the [30:22] ecosystem. So I've been building [30:24] WordPress sites since maybe I don't know [30:26] 2006ish but I hadn't even discovered the [30:28] community at all and as a result having [30:31] come from a background in agencies and [30:33] capitalism I felt found the whole space [30:35] really strange like what is this product [30:38] and where is the road map and where's [30:41] the governance and WordPress.org or is [30:45] weird, right? operationally like this [30:47] thing that sits in the middle and word [30:49] camps as event weird very friendly very [30:53] pleasant little bit cultish don't behave [30:55] like any other normal conference that [30:57] I've been to which I've been to hundreds [30:58] and spoken at hundreds and this doesn't [31:00] look and feel like the same thing fight [31:01] for the future bit weird right everybody [31:03] is lovely but underneath all of that all [31:06] of these things seem to be just powered [31:09] by feeding more humans into the boiler [31:12] and we burn people out we upset and [31:15] offend them we alienate them, we confuse [31:18] them, we don't support them, we don't [31:20] blah blah blah blah blah blah blah. And [31:21] even over like the five years I was [31:23] working at Yos, the churn I saw in core [31:26] contributors, in documentation, in event [31:28] attendees, in people who I spoke to [31:30] multiple times a day about projects they [31:33] were passionate about who then just [31:34] disappeared because they couldn't handle [31:37] the ecosystem, the politics, the [31:38] processes or the lack of processes, etc. [31:40] And increasingly it feels like to me the [31:44] tech is great. Like there's some there's [31:45] some interesting questions about [31:46] direction and strategy and roadmap and [31:48] whether Gutenberg was insane or [31:50] visionary or both. Fine. But underneath [31:53] all of that, it feels like we're cooking [31:55] at the seams because we pretend that we [31:57] have an infinite talent pool and that we [32:00] can just keep feeding more humans to the [32:02] boiler. And I don't think that's true. I [32:05] think that if we want to survive and [32:07] thrive and build this incredibly [32:10] important platform and framework that [32:12] powers the open web that fuels societies [32:15] and economies in a way that none of the [32:18] alternatives come even close to like [32:20] show me a wick site that even has a [32:22] correct XML sitemah no like there is [32:25] nothing else close despite all of these [32:27] flaws and yet the fuel that we need to [32:31] make this thing work in a much nicer [32:33] sense of a stable uh sustainable [32:36] community of volunteers and contributors [32:38] and people who actually are rewarded for [32:40] their time. We don't have any posters [32:42] for that. We don't have any frameworks, [32:43] who don't have any platforms. And that [32:44] terrifies me existentially, not least of [32:46] which because my my livelihood is tied [32:49] very closely to this thing. And my [32:51] identity as somebody who firmly believes [32:55] in understanding what good looks like in [32:57] tech is very closely tied to this thing. [32:59] And I'm very very keen not to look like [33:01] a hypocrite and to be proven wrong. So [33:03] yeah, I'm keen that we try and work out [33:05] how do we reinforce, not even reinforce, [33:07] how do we construct the underlying [33:09] foundations underneath this thing [33:11] because they don't exist and we've just [33:13] pretended that human capital is an [33:16] infinite resource and that goodwill is [33:18] an infinite resource and recent events [33:20] have I think to everyone outside that [33:22] demonstrated that's not the case. Yet we [33:24] continue to pretend it is. So yeah, step [33:26] one, let's work out how we get people [33:29] engaged and how we reward them. And then [33:30] we gradually unpick all the rest of [33:32] this. [33:32] >> Yeah. Let's talk about that that uh even [33:36] before recent events that that [33:38] assumption of of infinite uh human [33:40] capital. Um I will tell like my own [33:43] personal experience. Uh there was a [33:46] period of time when I was really [33:47] involved with the docs team. Uh and one [33:50] of the projects that we like basically [33:53] this was back in the day WordPress used [33:55] to have uh the concept of feature [33:58] plugins that as a way of like oh if you [34:01] want [34:01] >> Wait you mean you mean canonical plugins [34:02] don't you? [34:03] >> No no this is this is before that. Uh [34:06] the the idea was that if you had a an a [34:09] cool idea for something to be put into [34:11] core, you could start it off as a [34:13] feature plugin and put all your [34:14] development there and then the feature [34:15] plugin gets evaluated and then someone [34:18] from the core maintainer group or [34:20] someone somewhere uh decides yes this is [34:23] good or no it's not. Um, and [34:25] >> I just wanna before I just want to point [34:27] out at that same time there was also a [34:29] theory that the things that go into core [34:32] those feature plugins should apply to [34:34] 80% of the people who are using that. So [34:37] those feature plugins were used to sort [34:39] of map out that use case and be like yes [34:43] we're testing the code and everything [34:44] but also is this something that 80% of [34:47] the people who use this software are [34:48] going to use or should it stay in a [34:49] plug-in because it's only 20%. So I just [34:52] that has gone far by the wayside. But I [34:54] I it was that same era of feature [34:56] plugins. It that seemed reasonable to me [34:59] like that seemed like a reasonable way [35:01] to test new features. I I liked that [35:04] era. [35:04] >> So So the project that that I was [35:07] working on was uh to try to solve the [35:09] problem of WordPress users being [35:12] overwhelmed by all this stuff when they [35:15] log in like new user experience [35:17] basically. Um, and like the thing is [35:20] that there are all these things that are [35:22] built into WordPress um, that already [35:26] exist that could be tools to help people [35:29] out with that problem. For instance, [35:31] like there is a help tab that appears on [35:34] pages in the admin, but nobody clicks on [35:36] that because nobody knows it exists [35:38] because it's just hidden up there. [35:40] There's a screen options tab up there. I [35:42] knew about those things myself because I [35:44] had recently recorded a course for [35:46] Pluralsight that was literally going [35:48] through every screen in the WordPress [35:49] admin. And one of the things that I [35:51] noticed when I was doing that is there's [35:52] these tabs that you can click on and [35:54] they do stuff. So, our theory was how [35:59] can we bring people bring more awareness [36:01] to the stuff that's already there, the [36:03] little tab in the corner, um to get to [36:07] maybe help people out or maybe there's [36:08] like some sort of like guided tours that [36:11] things pop up on the screen or whatever. [36:13] Um, so that was the feature plugin that [36:15] I was involved in working on. It [36:17] involved learning about how to like add [36:19] stuff into those pages and and uh it's [36:24] kind of janky code because nobody's [36:25] looked at it in probably 15 years. Um, [36:29] and uh and building out this plugin that [36:32] that tried to do something better. Um, [36:35] we did we actually did user research. [36:37] Um, we did a number of we like I don't [36:40] like there's a user testing.com or [36:42] something and we had an account that was [36:44] paid for probably by the foundation or [36:46] someone some someone not me um that [36:48] allowed us [36:50] >> that allowed us to like actually get [36:51] real human beings that are just random [36:54] folks that apply to to do this thing and [36:56] I think they're like compensated five [36:58] bucks or something to go through the [36:59] thing and we asked them to go through [37:00] and do a like go log in uh make a make a [37:05] blog post start writing stuff whatever. [37:08] And uh and then we would watch these [37:10] videos and we would try to figure out [37:11] like, oh, is this more helpful? And then [37:13] we would make a little bit of a change [37:14] and we'd do another round of of user [37:16] testing and see if to see if it would [37:18] get any feedback. So we put a lot of [37:19] work and time into this thing. Um and [37:22] then when it did come time to like [37:24] actually present on the thing that we [37:25] did, uh it was like nope, nope, we're [37:28] not going to we're not going to do this. [37:29] We're not going to pursue this. And [37:31] >> and probably no path for it was just a [37:33] dead end, right? like [37:35] >> let's tweak it or maybe this way just [37:37] like [37:38] >> just a unilateral no. Um, and [37:40] >> Chris related to that, I never knew that [37:44] one of your early onboarding routes was [37:46] a new user experience model because [37:50] >> circle when I joined uh contributing to [37:53] the training team in 2014, Drew James [37:56] had been leading a nu exploration for [37:59] what you see when you first log in. And [38:01] this was the days before we had Slack. [38:03] We were all in IRC and I was a very [38:06] intimidated contributor. And that [38:09] project also just still sits right where [38:11] we left it. It's where I met Morton. [38:15] >> Yeah. Yeah. Um that I mean there the [38:20] good I will say that came out of that I [38:22] mean uh was that I was because I was [38:25] involved in that project and because I [38:26] was involved in the docs team I was [38:27] invited to the community summit in at [38:29] Word Camp San Francisco in whatever 2015 [38:33] 2014 something like that. Um, and I got [38:35] to meet meet Kim Parcel. And so [38:40] I love her and rest in peace. She I I [38:43] she was one of the first people that [38:44] greeted me in in the community summit. [38:46] This is total tangent. Um, she was one [38:48] of the first people that greeted me and [38:50] she said, "Hi, I'm Kim." And I said, [38:51] "Hi, I'm Chris." And she's like, and I [38:54] knew who she was because I knew her [38:56] handle. Cuz her handle was probably her [38:58] name or something. Uh, and mine was Jazz [39:00] Sequence. And I and she kind of like [39:02] gave me a look and she's like, "What are [39:03] you here with?" and I'm here with the [39:04] doc. Oh, and she's like, "Oh, I work on [39:05] the docs team." Like, "Oh, yeah, I I [39:07] know. I'm jazz sequence." And she's [39:08] like, "Oh." And she immediately gave me [39:10] a hug. And like to speak to to Jonno, [39:14] like your comment and everybody like [39:16] here knows like the community is [39:18] amazing. Like the people here are [39:20] amazing. Um, and that was really that [39:23] was sort of my introduction to the the [39:25] broader sort of contributor community. [39:27] But the flip side of that is after sort [39:30] of that project kind of got deadended, [39:33] that really killed my desire to ever [39:38] contribute anything to core ever again. [39:40] Like I have zero interest uh since then. [39:44] And so even even if it's not like like [39:48] the onboarding process for contributors [39:50] or like getting like working up this [39:52] like Matt likes to talk about Mr. Melon [39:55] likes to talk about how it's a [39:56] meritocracy, but it can't even be a [39:58] meritocracy if we are kind of stopping [40:01] people at the gate and and preventing [40:04] them from feeling like they're invited [40:06] through the gate. [40:08] >> Yeah. I mean, and the rules don't It's [40:10] like this is how you get through the [40:12] gate, but then you follow the rules to [40:13] get through the gate and you're not [40:14] anywhere near the gate. It's like So, [40:16] it's actually it's it's not even just [40:18] that it's like a blocked gate, right? [40:20] It's that you're told that there's a [40:22] gate there. you're told that if you [40:24] build this feature plugin and you do [40:25] this stuff like and this has been sort [40:27] of the the problem to bring it back to [40:30] the WPCC [40:32] it's [40:34] we the the individuals who experience [40:37] this like you said Jonno and like you [40:38] you were like oh I hit that and I hit [40:40] the wall and I was like done right [40:42] that's the human the human churn we've [40:45] talked about that we've all seen amazing [40:48] intelligent creative people leave the [40:50] community um ethical people leave the [40:53] community um because they they aren't [40:56] just going to work for they're already [40:58] working for nothing in terms of [41:00] financial compensation. So to also work [41:03] for work that on something that then is [41:05] just literally futile and completely [41:07] negated there's no benefit there. [41:10] There's not like no one's coming in for [41:11] that. And the the issue is, you know, [41:14] when you treat I think this is a this is [41:17] an entrepreneur tech bro issue, right? [41:20] That um and and really more like even [41:23] just big corporations, you start to [41:24] treat your employees as if they're [41:26] interchangeable cogs in a wheel, right? [41:28] And and this is why I actually said a [41:30] comment yesterday about how the the [41:32] community is not valued in the way that [41:34] it should be valued. Um even when we're [41:36] talking about AI, right? Everyone's [41:38] like, "Oh, AI is going to do [41:39] everything." You know, AI is not going [41:42] to pop into that tech that font manager [41:44] conversation and be like, "Oh, you know [41:47] what? I have this use case over here [41:49] that this is going to cause a real [41:50] problem and whatever." Like, AI is not [41:53] going to innovate. AI is not going to [41:57] make those connections of of this use [42:00] case versus this use case and how those [42:02] might interact because it it's not being [42:04] fed that information because it's it has [42:07] to come from a human. And if the human [42:09] isn't there to feed it that information, [42:12] it's not going to innovate. It's only [42:14] going to use what it has in the past. So [42:18] I I I across the tech industry right [42:21] now, I think it's so funny. Everyone's [42:22] like AI AI. And I'm like, what happened [42:24] to innovation? Like what happened to [42:26] like creating new things? Because what [42:29] we're doing right now is we're just [42:30] going to like, you know, just like AI [42:33] and then copies AI and then copies AI. [42:35] you get the copy of a copy of a copy and [42:37] then you know it's like um it's almost [42:39] like inbreeding at a certain point like [42:42] you need but I mean it's genetics right [42:45] if you have even like an animal [42:46] population [42:47] >> genetics Yep. [42:48] >> Yeah. If you have an animal population [42:50] that's just breeding within itself like [42:52] it's a contained thing. It it has [42:54] problems because you need diversity in [42:58] order to have new ideas, new genetics, [43:01] new whatever come in and create the new [43:04] things. And without that input, um you [43:08] you you are stuck with just the soup [43:10] that you have. And because of the way [43:15] that we've survived is by doing what [43:17] Jonno said, which is just feeding more [43:18] humans into there. And then when they've [43:21] given their innovative ideas, you just [43:22] they're gone. They leave. More humans [43:24] come in with innovation. You know, we [43:28] want to do something here about that [43:29] like and then the humans leave part and [43:31] also the the empowering of like what [43:33] you're doing. But that not only is that [43:37] not an inexhaustible source and you know [43:40] goodwill has been has been spent [43:42] mightily, but we you know we this it's [43:47] not done like we're not done building [43:49] the internet. We're not done building [43:50] the web. Like, are we just like [43:52] perfecting this one thing that we have? [43:55] We can't even do that with AI. So, the [43:57] humans [43:59] are are are what even drives the AI. [44:02] It's like, you know, a car might be [44:04] sitting there and and I guess this is a [44:05] bad example now with like Whimo and the [44:07] self-driving cars, but still like the [44:09] self-driving car still needs a human. [44:11] Like that's just all it otherwise it's [44:13] literally just sitting there. Like the [44:15] car is not driving itself around for [44:16] fun. Like [44:17] >> I thought we I thought we found out that [44:18] all the self-driving cars, all the [44:20] Whimos were actually controlled remotely [44:22] by some dudes. [44:22] >> Oh my god, them too. [44:23] >> In the Philippines. [44:25] >> Most of them are, but I didn't know it [44:27] was the Whimos, too. [44:28] >> Yeah. [44:28] >> Yes. [44:29] >> Oh my god. This is [44:33] >> I just found this out. This is like Sage [44:34] shocked face. Like I knew there was a [44:36] lot of the like person in the box, you [44:38] know, doing the AI, but I didn't realize [44:40] that the Whimos were also part of that. [44:42] Um I've never been in a Whimo. I'm never [44:43] getting in a Whimo. Like I don't I'm [44:45] sorry. just not doing it. Um, but the [44:48] point is here is that we all all the all [44:50] the powers that be are like AI. Even the [44:52] companies are like AI and it's like [44:55] that's just not going to be where the [44:58] innovation comes from. It's just it's [45:00] not [45:01] >> it's a desperate push for efficiency [45:03] which means removing humans and [45:05] squeezing margins etc. which yeah you [45:07] could make an ARY for and there's [45:09] there's economic presence blah blah blah [45:10] blah blah but it completely sidesteps [45:13] the underlying problems that yeah where [45:15] is the pipeline of contribution and new [45:17] ideas and resources to do stuff [45:19] otherwise what gets built and where are [45:21] these new featured plugins coming from [45:23] and if all we end up with is AI that [45:25] summarizes the other stuff that the AI [45:27] built maybe Wix is the better choice [45:29] that's not cool [45:31] >> we we've talked we've talked a lot about [45:34] uh the problem base um why the WPCC [45:38] exists um I'd like to shift focus a [45:42] little bit into okay so what is the [45:44] solution so by by shifting into this [45:47] gear I'd like to ask uh say Courtney [45:51] probably say because uh you talk about [45:54] this all the time um I think I think a [45:58] lot of people assume uh or put a lot of [46:01] things like you do uh onto what uh onto [46:05] the WPCC because they expect it to [46:07] behave in a particular way or expect it [46:08] to work in a particular way. Um and then [46:11] it doesn't because we're actually trying [46:13] to do something new and different. Um so [46:16] for everyone who does who has now heard [46:19] about like why the WPCC exists, maybe [46:21] you've gone to the the website and like [46:22] scrolled through a little bit uh while [46:24] we were having this conversation or [46:25] maybe clicked pause, gasp and now you're [46:27] coming back. Uh how does uh the WPCC try [46:33] to solve this problem? How does it work? [46:36] You are muted. Say [46:39] it works by being on unmute. Um the you [46:44] know our organization this is I could [46:47] talk philosophically about how we work [46:49] or about literally like our our output [46:51] like what we are creating but I just for [46:55] a touch on the philosophical part this [46:57] is we we've built and we are building an [46:59] innovative model across the board and [47:02] the foundation of that is a member [47:04] organization where the members are invi [47:08] not just invited but encouraged [47:10] requested We need them to we want them [47:12] to come and participate come and have a [47:15] mechanism for giving their opinion for [47:18] approving new board members for [47:20] approving changes so that it's not that [47:22] they have to do the the day-to-day work [47:24] of the organization but they are [47:26] participating in the direction of the [47:28] organization and that is in and of [47:31] itself an innovative model because that [47:34] doesn't exist especially in tech. Um it [47:37] does exist obviously in in some other [47:39] nonprofit worlds but not in this tech [47:41] one. Um but in terms of like our output [47:45] and what we are creating um what we have [47:48] essentially established are two main um [47:52] two main sort of like uh uh paths for [47:55] that. One is off off of the sort of more [47:59] academic and nonprofit model that exists [48:02] in the world of fellowships where [48:04] someone is paid full-time, part-time, [48:08] whatever it is, but paid to work on a [48:11] topic to deepen their knowledge, to work [48:13] on a specific project where they are [48:16] trusted as a fellow with um autonomy in [48:20] a in a in a spec, you know, they're part [48:22] of a team, but they are not having to [48:24] report, you their metrics. They're we're [48:27] not analyzing their work based off ROI, [48:29] right? This is this model exists again [48:32] in other fields, usually in thought [48:34] fields, but bringing we're bringing that [48:36] model into um into WordPress, into tech, [48:39] into open source because that model fits [48:43] so much better than the paid employee [48:45] model for what we're talking about doing [48:47] because contributors one are usually [48:50] extremely knowledgeable and expert. they [48:53] are in a very diverse sort of weird [48:56] field and those things can't be put into [48:58] tiny metrics that can then be handed to [49:01] uh a board to then judge if their you [49:03] know employee production is enough right [49:06] so that model is gives some freedom with [49:10] also some guidelines and I think it's [49:13] just a really valuable model for what um [49:16] for for this for open source um and then [49:18] the other model is projects and projects [49:21] are essentially anything that people [49:23] need to work on I time time constrained [49:28] with deliverables because a lot of the [49:30] things that we see in WordPress are [49:32] passion projects and I understand that [49:35] but it you can't fund something um just [49:40] forever right without some sort of guy [49:42] it just the the it gets exhausted the [49:44] funding gets exhausted the people get [49:46] exhausted so by having time constrained [49:48] projects and the goals of each project [49:50] is that the people who work on them are [49:52] paid. So it's not an individual person [49:54] being paid to sort of have overview of a [49:57] field but instead it is people working [49:59] on a specific project with specific [50:01] deliverables, specific compensation, [50:04] specific clear expectations. So at the [50:06] end of that we can be like okay this is [50:08] that project and now everyone can we can [50:11] maybe we do another project but we have [50:13] these tangible things that we're able to [50:16] understand and and complete. I think [50:18] completing those things is really [50:20] important and ideally uh even if we had [50:23] like say we had a project like the one [50:24] you were working on the onboarding one [50:26] you were talking about Chris you know [50:29] ideally our our vision here is that if [50:31] someone worked on that if it wasn't [50:33] being worked on with core or whatnot [50:36] that we would have this project and then [50:37] the WPCC [50:39] not one person the organization the [50:42] leadership and the membership would come [50:44] and be like you know then we are working [50:46] as a collective together to be like we [50:49] want this thing, we are doing this thing [50:51] and the sort of relationship between and [50:56] this is where the theory part comes in [50:57] because this is you know you never know [50:59] how this is going to go but in theory if [51:00] we have you know an entire group of [51:02] people who are advocating for a thing [51:05] who are bought into a thing it's a lot [51:07] easier to move that thing forward than [51:10] it is for just one person to sit there [51:12] and be like I really believe in this and [51:14] have to rally an entire group of people [51:17] around them in this frame with the [51:19] organization. We are that group of [51:21] people. The members have already said [51:24] yes, we like this project. We want this [51:25] project to go forward and succeed. Um [51:28] and then when it's done, then we all are [51:31] bought into that. We all are the project [51:33] is part of the organization's [51:35] um uh just what we're doing and it [51:38] doesn't it's not at that point then we [51:41] have to make a case for it or we have to [51:43] explain to our members what it's doing. [51:45] So this is a different model and I think [51:48] it's been difficult for people in our [51:50] space to sort of understand that and [51:53] that's okay. We will be demonstrating a [51:56] lot of that this year. [51:57] >> Yeah, [51:58] >> I'm really excited about it. So, because [52:00] this is a podcast uh during a particular [52:03] podcast Aathon that is trying to raise [52:05] money for these nonprofit organizations, [52:08] uh how can people either contribute or [52:11] become members or where do people go to [52:14] give us money? [52:17] >> Um well, if they want to give us money, [52:19] great. Um people are can donate. That's [52:22] fine. Um it's not a tax write-off. We're [52:24] not a 501c3. We're not a public charity. [52:27] Um, so they would just, you know, be [52:29] giving us money, not getting a tax write [52:30] off, which is fine. But the way we [52:32] really want to interact with people is [52:34] either as members, so they join as a [52:37] member and they can make any amount of [52:39] membership donation they want. Um, and [52:42] then we also work with people as [52:44] partners. So if someone wanted to, you [52:48] know, get something done or wanted to [52:49] work on a specific project, we would [52:51] want to work with them to do that and [52:53] work with them to fund it. They can fund [52:55] it. We can work on finding sponsors to [52:58] fund it. We can crowdfund for it and be [53:01] the financial repository for that [53:03] project and be the the authority on that [53:07] project. We hold the money and you know [53:09] make sure that the metrics are being met [53:10] and whatnot. Um so [53:14] it's not so much really that we want to [53:16] be like hey just go donate money to the [53:17] WPCC. What we really want is hey come [53:20] join the WPCC first of all and [53:24] participate as a member. Right now it's [53:26] $5. You can come on in and just, you [53:28] know, a year, not a month. Everyone's [53:29] like, "A month, right?" I'm like, "No, [53:30] just a year." The members will probably [53:32] be changing that fee, but it's going to [53:34] be up to the members to change. Like, [53:36] the members are going to decide. We're [53:38] not being like, "Okay, well, now it's [53:39] $100 to join. But if the members decide [53:42] that that's what they think is relevant [53:43] and important, then we'll go in that [53:45] direction." So, we want people to join [53:48] as members and we want people to join as [53:50] partners and sponsors to work on things. [53:53] So it is a that that is also a different [53:56] model. We're not just saying hand us [53:58] cash and then see you later. We [54:02] it is it's really in the name of the [54:04] collective um that we are a collective [54:08] but this is operating with the idea that [54:10] we are better together and not that a [54:13] unilateral direction is the right thing. [54:16] valuing the diversity of our community [54:18] and the innovation and intelligence that [54:21] that brings. I mean, you have all these [54:24] AI agents talking to each other, right? [54:26] And it's like, oh, they're so smart. I [54:27] was like, have you ever seen a group of [54:29] humans work on something? Cuz that's [54:31] pretty cool, too. [54:33] Like, if people are excited and [54:35] passionate and they're bringing ideas, [54:36] like that's amazing. And it is much [54:38] faster than AI, actually. Turns out [54:41] >> to bring it to bring it sort of full [54:43] circle around uh in the in the example [54:46] of of like partnering or sponsoring WPCC [54:50] uh we were talking before about you know [54:52] companies like GoDaddy, companies like [54:54] Google or or agencies like Tennup that [54:56] are actually like have a paid [54:58] contributor on staff. Um instead of that [55:01] model which is the existing model which [55:02] our hypothesis is that is a broken [55:04] model. [55:06] The solution, the the the thing that is [55:09] offered instead is rather than having [55:13] them on file, partner with the WPCC or [55:16] on on staff, partner with the WPCC. You [55:19] can still have your name associated with [55:21] a contribution level for whatever thing. [55:24] It's now just you don't have to worry [55:26] about like directing them. You don't [55:28] have to worry about them being an [55:30] employee of your company. Like they are [55:32] you're funneling your money essentially. [55:35] Funneling is probably a bad word, but [55:36] you're you're you're directing your [55:38] money through the WPCC to that [55:41] particular thing because you want to see [55:43] that done. And it's the WPCC that then [55:45] says, "Hey, who's the best person to [55:47] solve this problem?" And then that also [55:49] means that, you know, you don't have to [55:50] put out a job uh posting for a role that [55:54] is going to be a staff role for [55:56] something that's really not going to be [55:57] providing value to your company. uh if [55:59] if that's how you perceive uh an open [56:01] source contributor on staff, the [56:03] alternative is uh you know, oh having an [56:06] open source contributor on staff. Oh, [56:08] like I think that there's this idea that [56:09] like uh if there if you have some a core [56:12] contributor on staff, they can like [56:13] direct the direction of core in whatever [56:16] direction benefits the company that you [56:18] work for. But the reality is that's not [56:20] always true. But [56:21] >> they they are alone because they don't [56:24] have the business behind them. So [56:25] they're even that that single [56:28] contributor who's in theory sponsored [56:30] and has the weight of their company [56:31] behind them is in those meetings alone. [56:34] They don't actually they're just it's [56:36] just them. So [56:36] >> unless they're not alone, unless you [56:38] have a critical mass of paid uh [56:41] contributors uh [56:42] >> and membership behind you supporting [56:44] you. Exactly my point. Yes, we are [56:47] together backing these things and it's [56:50] not just we're all out there fighting [56:52] individual battles that are all the same [56:54] battles, which is like let's work [56:55] together. [56:57] In all of human history, I just want to [57:00] point out it's when humans work together [57:02] that things get done. It's like not [57:04] actually that crazy of a model. It [57:06] really isn't. It just in this weird [57:08] times and especially in tech, we all get [57:11] very siloed. We're all at our little [57:12] computers alone and we all feel alone. [57:15] But you are not alone. [57:17] >> Well, thank you all for coming on. Uh [57:19] this is sort of an historic uh community [57:22] in code. It's in an historic uh thing [57:25] for the WPCC because I don't think we've [57:26] been on uh on a podcast at least all [57:30] together at the same time. So this is [57:31] >> we're still missing one of our board [57:33] members, but [57:33] >> we are missing we are missing one of our [57:35] board members. Um Katie uh but uh but [57:38] even so uh this is it's a big deal for [57:41] for all of us. It's a big deal for the [57:43] podcast. Thank you all for coming on. [57:45] Uh, where can people go to find out more [57:49] about the WPCC? [57:52] >> Well, you can go to the wp [57:54] communityolctive.com. [57:57] >> Awesome. [57:58] >> Community [57:59] >> and uh yeah, I'll I'll I'll put [58:02] everyone's sort of social stuff in the [58:04] show notes uh in there. Uh we've got a [58:07] lot of people, so I don't want to be [58:08] labor the the time, but uh thank you [58:10] again for everybody for coming on. Thank [58:12] you, Jonno. Thank you, Courtney. Thank [58:14] you, Se. Uh thank you, Chris. Uh and [58:16] thank you all of all of the people that [58:19] are watching this uh in the future. Uh [58:22] and uh we'll see you all on the [58:24] internet. [58:24] >> Come join us. [58:27] >> Let's do it together.  📄 **Full text:** ![[Full Document Contents/Articles/Episode 22 The WP Community Collective|Episode 22: The WP Community Collective, YouTube]] ## Highlights - communities and the pipeline of contributors. >> Yes. Yes. And then we have Se say, introduce yourself. >> Get me. Hi, I'm Seed and um I am the CEO, part-time CEO of the WPCC, also a board member as a CEO and um gosh, I don't that's all I got for the intro. >> I feel like I feel like you have the more storied at least podcasting career ([View Highlight](https://read.readwise.io/read/01knwy1jvvaqqc7cqcma2xqx9c)) - Tags: 👻 ai highlighted - nerd and a deep deep WordPress nerd. Um yeah, I've got a background in all sorts of kind of WordPressy stuff and consultancy and enterprise spaces and worked at Yoast for a little bit. Um give or take five years. Yeah. And recently joined the WPCC as a board member to try and work out how on earth we wrangle this ecosystem to make it I want to say functional as a kind of aspirational starting point. Sure. We can get into more of that later. >> Uh and I'm Chris. I'm the host of this podcast. uh in the hat that I am wearing ([View Highlight](https://read.readwise.io/read/01knwy1jwb6nv05gtf1yhrwnsn)) - Tags: 👻 ai highlighted - >> Oh, yeah. No. Um, so the, uh, the problem of sponsored and volunteer contribution has been on my mind for a very long time. Uh, prefounding the WPCC. Um, basically ever since I I was involved in in WordPress, it it there there was a power imbalance. Um, there was a a volunteers were always bringing their passion, but they could never be the leaders in the ([View Highlight](https://read.readwise.io/read/01knwy1jwrjd034zhpe9dabhcf)) - Tags: 👻 ai highlighted - Um, and I've done some looking beyond the WordPress space to see how others sort of solve for this and different projects have different ways. But, uh, we have people that are really passionate about doing a thing that can't get the funding to keep doing it. And it may not be critical to what's coming in the next release or you know what's good for the entire community and also um a struggle to perhaps see what is going on throughout the project that ([View Highlight](https://read.readwise.io/read/01knwy1jxjy0kk5dha853zw3bz)) - Tags: 👻 ai highlighted - work in uh I I'll I'll toss it to you, Courtney, because like you said, you you have some folks who actually are paid staff um who who work on core and there's some other organizations, some agencies and stuff that that sponsor development. Um but like really like you said earlier, that's like we have somebody on staff who's doing this thing, but like it's basically like they're not an employee anymore, right? They're just working on this other thing. Um ([View Highlight](https://read.readwise.io/read/01knwy1jys2ch90za8wn62qmy2)) - Tags: 👻 ai highlighted - appetite for it because of the status quo because of all the things. So like in many ways uh the WPCC uh to me represents like okay that was that was the old model that's like the old way of of thinking about how contribution works and how community projects work. Uh perhaps perhaps the WPCC is a new way or something different that could happen uh instead. Um but >> that's the plan. ([View Highlight](https://read.readwise.io/read/01knwy1k530g1k70xnm61r7y4y)) - Tags: 👻 ai highlighted - make this thing work in a much nicer sense of a stable uh sustainable community of volunteers and contributors and people who actually are rewarded for their time. We don't have any posters for that. We don't have any frameworks, who don't have any platforms. And that terrifies me existentially, not least of which because my my livelihood is tied very closely to this thing. And my identity as somebody who firmly believes in understanding what good looks like in tech is very closely tied to this thing. And I'm very very keen not to look like ([View Highlight](https://read.readwise.io/read/01knwy1k9zrw8wdh7m8eevc86a)) - Tags: 👻 ai highlighted - we gradually unpick all the rest of this. >> Yeah. Let's talk about that that uh even before recent events that that assumption of of infinite uh human capital. Um I will tell like my own personal experience. Uh there was a period of time when I was really involved with the docs team. Uh and one of the projects that we like basically this was back in the day WordPress used to have uh the concept of feature plugins that as a way of like oh if you ([View Highlight](https://read.readwise.io/read/01knwy1kevf2y98zr729g6wxv7)) - Tags: 👻 ai highlighted - bought into that. We all are the project is part of the organization's um uh just what we're doing and it doesn't it's not at that point then we have to make a case for it or we have to explain to our members what it's doing. So this is a different model and I think it's been difficult for people in our space to sort of understand that and that's okay. We will be demonstrating a lot of that this year. >> Yeah, >> I'm really excited about it. So, because ([View Highlight](https://read.readwise.io/read/01knwy1kqnk64d4kc1srqcs4jj)) - Tags: 👻 ai highlighted - pretty cool, too. Like, if people are excited and passionate and they're bringing ideas, like that's amazing. And it is much faster than AI, actually. Turns out >> to bring it to bring it sort of full circle around uh in the in the example of of like partnering or sponsoring WPCC uh we were talking before about you know companies like GoDaddy, companies like Google or or agencies like Tennup that are actually like have a paid contributor on staff. Um instead of that ([View Highlight](https://read.readwise.io/read/01knwy1m2045t4k4agse3ze3fj)) - Tags: 👻 ai highlighted