Why I'm Not Jazzed About FAIR  ## Metadata - Author: [[WP Minute Podcasts]] - Full Title: Why I'm Not Jazzed About FAIR - Category: #articles - Document Note: --- tags: - #WordPress - #FAIR - #OpenSource - #LinuxFoundation - #PluginManagement - #EcosystemGovernance Author: Joe Howard (The Repository Podcast) Source: YouTube Video "Why I'm not jazzed about FAIR" (The Repository) Reference: https://www.youtube.com/watch?v=H6YeK-gpH7M date created: 2025-06-10 18:15 --- # Title: Critical Analysis of the FAIR Initiative for WordPress Ecosystem ## 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 - 🔍 SEO Evaluation - 🎯 Conclusion ### References: - Linux Foundation FAIR Project Announcement - The Repository Podcast, YouTube: https://www.youtube.com/watch?v=H6YeK-gpH7M - WordPress.org Forums and Community Discussions ## 📝 Summary: This episode provides a skeptical perspective on the FAIR initiative, a new federated package management project under the Linux Foundation intended to decentralize WordPress plugin and theme distribution. The speaker questions FAIR's practical impact, adoption challenges, commercial backing, and how it fits within the existing WordPress ecosystem. Concerns include its timing, unclear benefits for agency owners and power users, potential fragmentation, and whether it genuinely innovates or improves WordPress software for users. The narrative critiques the lack of broad community engagement and possible exclusivity of the rollout while highlighting the importance of collaboration for FAIR’s success. ## 📖 Main Content: FAIR aims to distribute WordPress plugins and themes through decentralized repositories, reducing reliance on a single source (WordPress.org). While this theoretically stabilizes the ecosystem, the speaker raises doubts about actual adoption, given the entrenched distribution through hosting providers and agencies reliant on WordPress.org's ubiquity. The initiative is overseen by a technical steering committee of known WordPress contributors but lacks clear communication to broader community power users and agency owners. The timing of the announcement—right before WordCamp Europe—appears strategic to build buzz but lacks substantive clarity. The speaker expresses concern about how commercial interests will be integrated and monetized within FAIR, questioning whether funds and contributions will translate to tangible development benefits. Historical skepticism toward WordPress funding and project follow-through colors this view. Marketing and messaging to the typical agency owner or freelancer remain vague, leaving unclear why they should adopt FAIR. The rollout seems coordinated but insular, potentially reinforcing exclusivity and limiting broad participation beyond core developer circles. Ultimately, the speaker doubts whether FAIR meaningfully innovates WordPress’s core experience or enhances its attractiveness amid growing competition from commercial CMS and AI-driven platforms. They emphasize that WordPress’s biggest challenges remain marketing, packaging, and brand relevance. ## 🗒️ Notes ### [00:06 - Introduction to FAIR Initiative](https://www.youtube.com/watch?v=H6YeK-gpH7M&t=6s) - FAIR is launched by the Linux Foundation as a federated and independent package manager for WordPress plugins and themes. - The goal is ecosystem stability by decentralizing control away from WordPress.org. - Announcement timed strategically before WordCamp Europe to maximize community attention. ### [02:10 - Speaker’s Perspective and Linux Foundation Role](https://www.youtube.com/watch?v=H6YeK-gpH7M&t=130s) - Speaker identifies as power user and agency owner, focusing on practical impact. - Questions Linux Foundation’s role and need for financial/organizational backing. - Concern over clarity about FAIR’s broader scope beyond WordPress. ### [04:28 - FAIR’s Position within Open Source CMS Landscape](https://www.youtube.com/watch?v=H6YeK-gpH7M&t=268s) - FAIR is designed as a neutral community solution, not a fork of WordPress. - Aims to create a new backend for plugin/theme distribution. - Compares to Linux package management concepts for redundancy and resilience. ### [06:40 - Challenges in Adoption and Hosting Ecosystem](https://www.youtube.com/watch?v=H6YeK-gpH7M&t=400s) - WordPress’s distribution advantage lies heavily in widespread web host support. - FAIR’s success depends on host adoption and replacement of WordPress.org APIs. - Introduces the concept of decentralized mirrors for plugin and theme data. ### [09:00 - Potential Evolution Beyond WordPress](https://www.youtube.com/watch?v=H6YeK-gpH7M&t=540s) - FAIR may evolve to support multiple CMS platforms beyond WordPress. - Raises questions about commercial integration and stakeholder incentives. ### [11:11 - Adoption Necessity and Community Collaboration](https://www.youtube.com/watch?v=H6YeK-gpH7M&t=671s) - FAIR must reach WordPress-level adoption to impact the ecosystem meaningfully. - Collaboration among hosts, developers, and agencies is critical. - Current rollout perceived as exclusive, which may hinder broad adoption. ### [13:29 - Transparency and Funding Concerns](https://www.youtube.com/watch?v=H6YeK-gpH7M&t=809s) - Skepticism about how funding and contributions will support development. - References to WPCC’s funding history and GoDaddy contributions. - Uncertainty about FAIR’s governance and transparency in resource allocation. ### [16:10 - Marketing and Practical Impact for Agencies](https://www.youtube.com/watch?v=H6YeK-gpH7M&t=970s) - Unclear messaging to agency owners about FAIR’s benefits. - Questions about how FAIR will be marketed and adopted by web hosts. - Challenges in explaining FAIR’s value beyond “insurance policy” against single points of failure. ### [18:11 - Ecosystem Exclusivity and Division](https://www.youtube.com/watch?v=H6YeK-gpH7M&t=1091s) - Perception of WordPress ecosystem as a “club” with limited inclusivity. - Core developer and open-source purist focus may alienate broader community voices. - Speaker highlights ongoing challenges in broad community engagement. ### [20:24 - Innovation Questions and Competitive Landscape](https://www.youtube.com/watch?v=H6YeK-gpH7M&t=1224s) - Doubts whether FAIR truly innovates WordPress or just decentralizes backend. - WordPress faces increasing competition from commercial CMSs like Wix, Webflow, and AI-driven tools. - Concerns about WordPress’s future appeal to developers and users. ### [22:43 - Branding, User Experience, and the Future](https://www.youtube.com/watch?v=H6YeK-gpH7M&t=1363s) - WordPress struggles with marketing, packaging, and branding amid hype around AI and other platforms. - Calls for WordPress to remain exciting and easy to use for all kinds of projects. - Final reflection on FAIR’s role in supporting innovation and sustainability for the WordPress ecosystem. ## 📖 References: - Linux Foundation FAIR Package Manager Announcement: https://www.linuxfoundation.org/press-release/fair-package-manager - WordPress.org Forums Discussions on FAIR: https://wordpress.org/support/forum/fair-package-manager - The Repository Podcast: https://www.youtube.com/watch?v=H6YeK-gpH7M ## 🗣️ Paraphrase:  1. Original: "Fair is a new announcement scooped by the repository... It's a federated and independent repository of trusted plugins and themes for end users, web hosts, commercial plugins, and tool developers in the WordPress ecosystem." Paraphrase: The FAIR project, recently introduced by the Linux Foundation, proposes a decentralized and autonomous platform for managing trusted WordPress plugins and themes, targeting users, hosting providers, commercial plugin creators, and developers within the WordPress community. 2. Original: "But in order to package it and present it to the average person... there's a marketing, branding, more marketing, like marketing and messaging. What does this really mea - Summary: In this episode, I unpack the big announcement behind FAIR — the Federated and Independent Repository — a new package manager initiative under the Linux Foundation. Scooped by The Repository and launched during WordCamp Europe week, FAIR promises decentralized plugin and theme distribution for WordPress, reducing reliance on wordpress.org and introducing a new governance model for the ecosystem. On paper, that’s a huge shift. But I’ve got more questions than answers. Why the Linux Foundation? Is this really just for WordPress? And what does “a replacement for the ecosystem” even mean? For freelancers, agency owners, and power users like you and me, the pitch feels abstract. FAIR might offer technical insurance, but what does it actually do to help us build faster, better, more sustainable sites today? This episode is less about hot takes and more about critical thinking — exploring FAIR from the lens of a working professional in WordPress, not someone living in contributor Slack channels. I want to know how this changes our day-to-day, and whether FAIR will drive real innovation… or just become another layer of complexity. Key Takeaways: • “This isn’t a fork of WordPress — it’s a backend distribution layer, a replacement for the plugin update plumbing we all rely on.” • “I have more questions than clarity: is this really just about stability, or is it something much bigger?” • “Adoption is everything. Without host and agency support, FAIR is just another plugin.” • “WordPress has a packaging problem. FAIR needs to solve that — not just technically, but with messaging that speaks to the average power user.” • “We want open source to thrive. But we also want clarity, transparency, and solutions that actually make WordPress better for our clients.” URLs Mentioned: • FAIR press release from the Linux Foundation (https://www.linuxfoundation.org/press/linux-foundation-announces-the-fair-package-manager-project-for-open-source-content-manageme... - URL: https://www.youtube.com/watch?v=H6YeK-gpH7M What is fair? Fair is a newannouncement scooped by the repository.I had a chance to get a tiny appetizerof fair, not the best appetizer either.It was like a cold mozzarella stickserving where you only got four and youwere like, "How much did I pay forthis?" When Kareem took the stageonce again with the repository atPrescom earlier this year, and he wastrying to explain what fair was upto, but you know it was a little early on. So he was probably just trying to buildsome buzz. Let me just read the pressrelease that hit my inbox this morning. Idon’t often publish press releases,and I still am not going to after youknow, after today. But I’ll I’ll read theopening salvo from this press releasefrom the Linux Foundation. Sotoday, the Linux Foundation launched theFair Package Manager project, afederated and independent repository oftrusted plugins and themes for endusers, web hosts, commercial plugins, andtool developers in the WordPressecosystem. The fair package managerproject stabilizes the entire WordPressecosystem. It eliminates the reliance onany single source of core updates. Plugins, themes, and more unites afragmented ecosystem by bringingtogether plugins from any source andbuilds security into the supply chain. Itprovides governance in the open-sourcecontent management ecosystem, especiallyas corporate interests threaten toencroach on open-source freedoms. Thiswas announced at an event called AltControl, which just so happens to runright before WordCamp Europe as of thisrecording. This was Friday, and uh, MattMullen will be, or should be, taking thestage tomorrow, as of this recording, todo his typical keynote at WordCampevents. So, obviously, it is not an interestingtiming. It was the timing that theywanted to announce thisspecifically. So, this is where we are. We have this new initiative calledFAIR. It's under the Linux Foundation.Just a few things I wantto get out of the way as I go aboutthis. I've never been approached byanyone part of the FAIR group ormembership council, whatever it is. Uh,no one's asked me to review anything oryou know, I certainly don't have anyother insights, and I'm much more of apower user. I represent agency owners and freelancers,again, power users of WordPress. I am notsomebody that is writing lines of codeor committing lines of code. I look at thestuff that is impacting WordPress or Isee what WordPress is doing, and I try to disseminate this down for theWordPress professional. Like I justsaid, freelancer, power user, agencyowner. How will this impact myday-to-day survival in WordPresslike building sites for people? How do Iuse these plugins? I'm a huge advocateof open source. I love it — love the ideaof it. And I love open source WordPress,of course. So this is the lens I look through, andthroughout this episode, I really justhave more questions than I have concreteanswers or beliefs. I don't knowwhich way to go with that. So theLinux Foundation — I have questions there.I mean, it makes sensethat FAIR is going under the LinuxFoundation umbrella. They have 900 opensource projects. Again, they've beendoing this for decades. They kind ofunderstand what it's like to usher inopen source projects, and they havethat infrastructure or plumbing. Guidance, assuming they do that, will helpthroughout thisproject. It is being overseen by athree-person technical steering committeecomprised of longtime contributorsCarrie Dills, Mika Epstein, and Ry Q.That's a snippet from the repository'spost. I'll link that up in the shownotes, and the efforts being coordinatedby Yoast and crowd-favorite CEO KareemMarooi. So I guess the first question iswhy the Linux Foundation, aside from myassumption of, well, it makes sense theyneed the backing; they need potentiallythe financial backing to organize stuff at a higherlevel. I'll also link up the live streamof the alt-cont control org event, and youcan get some of those answers bylistening to that episode or that livestream. But the one thing that I'msort of concerned over, like the thingthat makes my right eyebrow go up when Iread just the title that waspublished on the Linux Foundation isLinux Foundation announces the FairPackage Manager project for open-sourcecontent management system stability. So while it's opening up with WordPresstoday, the Fair Package Manager project forOpen source content management system. Stability does not say WordPress.They’re starting with WordPress?But I’m curious if this evolves into something greaterand WordPress just happens to be the great, you know, first step.Here’s a quote from the Linux Foundation blog post.Quote, "The fair package managerproject paves the way for stability and growth of open source contentmanagement, giving contributors andbusiness additional options governed by a neutralcommunity," said Jim Zlin, executivedirector of the Linux Foundation. "Welook forward to growth in community andcontributions this important project attracts."So, no mention of WordPress there.Of course, you know, the rest of the article is talking about howthey’re working with WordPress, at least at the start, right? So, there’s that. This is not a fork of WordPress.I think they’re making that clear.This is a way to build the back end of distribution.And let me just break that down for you.So, I’ve been a longtime Linux user.Although I say long time, I haven’t used it inIt's been about 15 years since I installed itmyself. Well, that's not fairbecause I was playing around with aRaspberry Pi and I installed some stuffa couple of years ago. So, uh, manyyears ago as a system admin,when you installed Linux, it wasnot just from one server;it was from a collectionof servers with some packages on someservers. You know, the same package onhundreds of servers, right? It'sthis layer ofdistribution, and it's going to helpfrom that single point of failure, whichis WordPress.org. Now, we're looking atit from the perspective of a single point of failure,being Mullenweg. Of course, with the recentactions, it does make sense, right? This makes sense from a packagemanagement perspective. Why wouldn'twe want to do this? The challenge isgetting people to adopt it. Right? So, Ididn't hear or read any mention ofany web hosts. I've said this on otherpodcast episodes: the biggest moatthat WordPress has is distribution, whichfar too manypeople don't talk about when they talkabout. Alternativesto WordPress core and WordPress plug-inmanagement include forking WordPress, asit is on so many web hosts. Many webhosts promote it because it is a freeresource to them, literally to gainpaidcustomers. It's naturally gettingdistributed at an insane rate. This isalso why, to be fair, Mullen WG wantsweb hosts that benefit so greatlymonetarily from WordPress to give back. So I see both sides of it. It makes sensetome. By installing this plugin, atleast, you know, as of this recording,which is literally the day theyannounced it, you're not going to seeanything really different. It's going todo an API replacement as it stands. Itreplaces communication withWordPress.org or APIs such as updatechecks and event feeds using local, infavor of using local or fair governedalternatives. Fair also introduces a newpackage distribution model for themesand plugins and supports opt-in packagesthat use the fair protocol and enableshosts to configure their own mirrors forPlugins and themes data using the AspirePress for their own domains or usingAspire Press for their own domains. While stable plugins currently usemirrors from wordpress.org, futureversions will fully support fairnativepackages.So, it can be kind of confusing if you're notliving and breathing this stuff on aday-to-day basis, but it does makesense. Like, yes, I want decentralizedpackage management. I want to knowthat if something happens toWordPress.org or through a lawsuit ora decision being made, that the pluginsthat I've installed on client sites ormy own sites are still healthy andupdating; that makes total sense. Will thisevolve? Will this fair packagemanagement system under the LinuxFoundation umbrella evolve intosomething else where eventually we’re not just talking aboutWordPress anymore. We’re talking aboutall these other CMSs. Again, fine, butyou know how that goes, right? A billgets introduced to Congress, goes up anddown the aisles, and before you know it,the name has changed, and a gazillionOther things have been added in. This isjust human nature. So, will we see thiskind of thing happen with the FAIRpackage management system? I think it'sa fair question. I'm going to play on thatpun for awhile. So, what's going to happen in thefuture? Who knows? I also listened to aninterview with Kareem and Yoast on apodcast called kraut.press or krautpress where they talked about this. ```htmlYoast had a passing statement where hesaid it is a replacement for theecosystem.So that's what FAIR is. It's areplacement for the org ecosystem, afederated replacement, which I don'tknow what that means. I would unpackthis broader vision for a replacementfor the ecosystem. And when I hearthat, I just have to behonest; like where's the commerciallevel levied somewhere in, like where arewe levying the commercial side of thingsin this space? Because that willbe the next big domino to fall in theadoption and perception of FAIR. One ofthe things that many people have alwaysI said, myself included, to MattMullenweg, why not make WordPress.organ official marketplace where you canbuy stuff? Now, I think now that we've had this lawsuit, it's all beenuncovered and we kind of know a littlebit more about WordPress.org and theplumbing behind that. We know why, like,that's not happening over there. Butthey are seemingly making it happen onWordPress.com. WordPress.comalready has and had paidplugins through WordPress.com, and maybenow they'll push it even furtherbecause of everything that hashappened. It's sort of like this, I don'twant to say fragmentation, but it'sfragmented in the senseof, well, the bigger issue withthe fair package manager is if this doesn'tget adopted, like it must get adopted,that same level of distributionthat WordPress thrives and survives on,fair needs to do that too. ```Otherwise, you know, you're justinstalling fair one website at a time.You need many hosts to really make adent in the overall footprint ofWordPress being installed. You needagency owners. It's going to be theThe same challenge. The same challenge thatI've always had, or the same criticismI've always had with Mullenweg andWordPress, WordPress.com automaticis people need to work together, andthat’s like the big flag that everyone’sflying. We need to work together onthis. Like if it's this is good, yes,no, thumbs up. This is good foreverybody. Yeah, I think so. Now we allhave to work together to make thishappen. And that’ll be the stickingpoint. It’ll be the sticking point wherethe samecriticisms can happen towards FAIR thathave happened towards Matt and WordPressandautomatic, and you know I’m reallycurious if everyone is ready for that. Right when Yos says this is areplacement for theecosystem, I mean, knowing Yos, likehe’s probably thinking, "Okay, how can wemonetarily survive?" and alsothinking, "How can we help othercommercial plug-in developers survive aswell?" There’s going to be somethingthere. What is that something? I don’tknow. How does that work across webhosts, agencies, enterprise where KareemSpends most of his time? What's theirvision for that? And along those samelines oftransparency, you know, I think we'regoing to start to see that across theboard. Uh, say Reed fromWPCC received back in January over ahalf a million dollars from GoDaddy andother contributors. I contributed a fewyears ago on behalf of the WP Minute. Actually, I'm not quite sure where thathas landed. I know there was some kindof fork. I've asked questions, but Idon't really fully understand whathappened with the WPCC and some of thosefunds over there. They split thenonprofit or something; it's neitherhere nor there. But the point is,Ithink, you know, it's been about halfa year—roughly almost a half year—of theWPCC and the $500,000 plus from GoDaddy. Courtney Robertson from GoDaddy askedSeed about sponsoringcontributors, and I'm curious how willFair fare with contributions from peoplesupporting others to help thedevelopment of that? Will we seefunds fromWPCC go to support development ofThis initiative? I don't want to say the dust hassettled, but as the dust is settling,maybe on the automatic and WP Enginestuff, anyone who's truly working onan initiative to do something else forWordPress, like Fair or WPCC, must beopen to the same criticisms that we'vegiven Mullenweg, Automatic, andthe WordPress Foundation for many years.Because we want to see thingshappen. We don’t want to hear thatsomething's happening. We hear thatsomething's happening, and then nothinghappens. This is something that hasplagued WordPress forever, both in code,features, and the community andcommunity-drivenprojects. Like, what is happening, right?We want to support this thing. We wantto support this person. The person getsmoney. The project gets attention. Mediaoutlets cover it, and nothinghappens. And I'm not sayingthat falls squarely on theperson who started it. It’s just, it’stough. It is tough. Open source is somuch about humaninvolvement. So the question is really, youKnow where it's at. And what's thepromise behind this? The way that I'm seeing it is theuse of fair, the fair use of fair, isgoing to help that technical level ofdistribution. But does that turn intosomething else? And how does this ultimatelyimpact the agencies, the people who arewhat I will say, call them cheerleaders, call thempeople working in the trenches to getWordPress out there, not only for theirclient, but for their own livelihood oftheir own agency. How is this going tohelp somebody? Okay, we have theinsurance policy of WordPress.org, butwhat else is that? I'm kind of finewith that. I'm kind of fine with that, but my guttells me that it's going to try toevolve into something else. It'll taketime, but it'll try to evolve intosomething else because I think whatwe're going to see is larger interestedparties want to know what's in itfor them. Onceagain, humannature. And I think one of the biggestissues too is like in order to getTo that next step, as I said, distributionunderstanding more humaninteraction. This also came up in thelivestream. How do you market this thing? How does it make sense other than thatinsurance policy? You'll get thestakeholders at web host to doit to installit. Will you get them to install it bydefault? Don't know. Will it beinstalled as an optional thing? Don'tknow. But in order to package it andpresent it to the average person, and bythe average person I mean like theaverage agency owner who's making adozen to 100 websites for people a year,if that's still athing, to install and use this stuff,too. So, there's a marketing, abranding, more marketing, like marketingand messaging. What does this reallymean for us power users and agencyowners? Why should we use this? I'vetalked about this before and I this is atouchysubject, and this is something that wesee more and more in thespace. Well, this is something what I'm about to say is something that we seeMore and more in reallife. But it's like you're either on oneside or the other, and there's no youcan't be in the middle with anything:politics, the food you like, the car youdrive, the CMS platform you use. But nowit'll be the distribution server ofchoice. And I will tell you like this:this rollout is definitely acoordinated rollout. Obviously, nothingagainst it, but it's definitely acoordinated rollout. And it does reallykind of feellike for people that want this to beadopted and expanded upon, it stillfeels like a club. And by the way,getting into WordPress feels like a clubas well. Oh, and by the way, as somebodywho has published content for 15 plusyears in the WordPressspace, it still feels like a club. Like when I talk or when anyone that Ifeel like I might representtalks, if you're not talking pure opensource, if you're not talking puredeveloper speak, if you're not talkingpurely about Automatic or againstAutomatic, then you're just not, youknow, listened to. Or if you don't go toevery single WordCamp, uh, and go toEvery single contributor day, your voice issort of muffled out. And this is something that I pay closeattention to. We got a bit of response from theecosystem already, people reaching outlike, "Hey, we're also worried. We haveour thoughts." Then there was a post onWordPress.org about us doing a fork,which we weren't doing. And then we gota lot more reach out from people aroundthe ecosystem. At the time before wewere speaking about the need forfederation and the need for the ideaaround how do we create an ecosystemthat everybody can work with. And as hesaid when we first posted, we thought wewere relatively alone. But then theseother groups all started quietlyreaching out. So there were only a fewright up until Matt posted the JK presspost that sort of pushed it over theedge and the outreach became immense. Hopefully, we want to work witheverybody. It truly doesn’t mean we onlywant to work with people who are againstMatt andAutomatic. Because here's the finalThing, and this is what I’m going toclose with. And I did hear Yoast saythis luckily kind of saved it as I waslistening to this,because I wasn’t screaming at therooftops. This is really not impactingmy life on a Friday night to thatdegree. But what I’m nothearing is howthis innovates WordPress. Now he did usethat keyword as his closingstatement in the livestream. He calls itinnovation. Okay. Yes, it’s innovativeto havea distribution, you know, a federateddistribution for WordPress. Okay. It’sinnovative in the sense we’ve never hadit before. But what does that mean? How doesthat go further? How does that go a stepfurther?Because I don’t see this actually makingWordPress better as a piece of software.I don’t see it making WordPress moreattractive for the end user. And by theway, WordPress’s attractiveness has neverbeen in the crosshairs more than it istoday with all the competitionof commercial and closed source CMSs. That you can just go buy and spin up,Webflow, Wix, etc.And now with AI, I’m wondering will thefuture developers even want to useWordPress to build things with? Is the essence of opensource con just getting eroded throughAI, or will we see a whole other layer of open source?But that’s the bigthing for me.WordPress already has a marketingissue, a packaging issue, and abranding issue. What can it do? Everyone’s so down on it, and wow, look atthis shiny thing called AI over here.I want to support thingsthat encourage WordPress to thrive andto be used as thetool that it’s intended to be. Or justhow you want to useit. Like pulling WordPress off the shelfto use in aproject should be exciting. It should beeasy. It should feel like you made theright choice to start a website, a blog,community site, the framework for anapp, a visual database layer fordata that you’re piping in through theREST API with all these other AI toolsyou’re helping build alongside of. It’s like, you should feel good you pickedWordPress. And now what we have ispeople just scratching their heads, going,“Do I use this? Is this for me? Whatis?” Now we're all fightingwith each other. We’re fighting with webhosts. Like, what’s happening? You knowwhat? I’m just going to go over here anduse this otherthing. So really, at the end of all ofthis presentation about FAIR, I guessthe most important thing thatI really see eye to eye with isinnovation.And how do we continue to make WordPressthe innovativesolution in the open-sourceecosystem for the futuredevelopers and for the end users whowant to use a turnkey solution?, Why I'm Not Jazzed About FAIR, WP Minute Podcasts, 01jxe18ppk1j8ht1x271q7wfh6.