Techstrong TV’s Post  ## Metadata - Author: [[Techstrong TV]] - Full Title: Techstrong TV’s Post - Category: #articles - Document Note: --- tags: - #wordpress - #opensource - #governance - #supplychain - #decentralization - #fairnessinitiative - #packagemanager - #pluginsecurity - #maintainability - #community Author: Techstrong TV Source: LinkedIn post Reference: https://www.linkedin.com/posts/techstrong-tv_can-wordpress-remain-open-and-fair-joost-ugcPost-7346696329793859584-UMCM date created: 2025-08-20 00:00 --- # Title: Can WordPress remain open and fair? The Fairness Initiative and “Fair Package Manager” ## Table of Contents: - 🔗 [References](#references) - 📝 [Summary](#-summary) - 📖 [Main Content](#-main-content) - 🗒️ [Notes](#️-notes) - 📖 [References (Detailed)](#-references-1) - 🗣️ [Paraphrase](#-paraphrase) - 📰 [Newsletter](#-newsletter) - ✅ [Action Items](#-action-items) - 🧪 [Hypotheses](#-hypotheses) - 📊 [Methodology](#-methodology) - ❓ [Questions](#--questions) - 🔮 [Future Research](#-future-research) - 💡 [Implications](#-implications) - 🧠 [Learning Styles Assessment](#-learning-styles-assessment) - 📊 [Accessibility Assessment](#-accessibility-assessment) - 🌍 [DEIB Assessment](#-deib-assessment) - ✅ [Logical validity](#-logical-validity) - 🔍 [DARVO Analysis Prompt](#-darvo-analysis-prompt) - 🔍 [SEO Evaluation](#-seo-evaluation) - 🎯 [Conclusion](#-conclusion) ### References: - Techstrong TV LinkedIn post: “Can WordPress remain open and fair?” featuring Joost de Valk (Emilia Capital) and Karim Marucchi (Crowd Favorite). Watch: https://lnkd.in/efXjyVGr ## 📝 Summary: This Techstrong TV post promotes a video conversation where Joost de Valk and Karim Marucchi introduce the Fairness Initiative, proposing a decentralized “Fair Package manager” for WordPress. With WordPress powering over 40% of the web, they argue the ecosystem faces risks including supply chain vulnerabilities, legacy infrastructure strain, and unclear governance. The initiative aims to increase transparency, resilience, and equity across the plugin/theme distribution pipeline and community decision-making. ## 📖 Main Content: The post’s core message: WordPress’s scale creates concentrated risk. A decentralized package management approach—complementary to or layered with the existing WordPress.org directory—could: - Reduce single points of failure in distribution and discovery. - Improve supply chain security (signing, provenance, SBOMs). - Encourage transparent governance and sustainable funding for maintainers. - Modernize legacy infrastructure with interoperable standards. While details are in the linked video, the framing suggests alignment with broader trends in open source: package provenance (Sigstore), dependency health, and open governance models. It implicitly calls for community buy-in, cross-company collaboration, and a path that respects WordPress’s backward compatibility and accessibility strengths. ### 🗒️ Notes - Context - WordPress powers 40%+ of the web; platform risk is systemic. - Plugin/theme distribution concentrated in WordPress.org plus commercial vendors. - Fairness Initiative goals - Fair Package manager to decentralize distribution. - Improve transparency: governance, funding, decision-making. - Address legacy infrastructure challenges with modern standards. - Supply chain and security - Introduce verifiable signing, checksums, provenance. - Encourage SBOMs and dependency disclosure. - Mitigate typosquatting and impersonation via namespacing and identity proofing. - Governance - Clarify roles between contributors, companies, and leadership. - Establish open, documented processes for inclusion, deprecation, and dispute resolution. - Developer experience - CLI-first workflows, machine-readable manifests, semantic versioning, channels (stable/beta). - Backward compatibility guarantees and rollback mechanisms. - Sustainability - Funding signals (badges), optional patronage links, marketplace interoperability without lock-in. - Metrics that reward maintenance quality, not just downloads. - Community adoption path - Start as opt-in adjunct to .org directory. - Provide bridges for wp.org metadata and composer interoperability. - Gradual rollout with clear deprecation policies, education, and migration tooling. - Risks and mitigations - Fragmentation risk → standard schemas and compatibility layers. - Governance capture → term limits, multi-stakeholder steering, transparency reports. - Added complexity → sane defaults, zero-config for beginners. ## 📖 References: - Techstrong TV LinkedIn post and video link: https://lnkd.in/efXjyVGr - Background concepts for context: - Sigstore for software signing and provenance: https://www.sigstore.dev - SBOM guidance (NTIA/CISA overview): https://www.cisa.gov/sbom ## 🗣️ Paraphrase: - Original idea: “The Fairness Initiative… decentralize WordPress through the Fair Package manager… addresses supply chain risks, legacy infrastructure challenges, and the demand for transparent governance.” - Paraphrase: The Fairness Initiative proposes a decentralized package management system for WordPress designed to harden the plugin/theme supply chain, modernize older infrastructure, and make how decisions are made more open and understandable. - Original idea: “With WordPress powering over 40% of the web…” - Paraphrase: Because WordPress underpins a massive share of websites, any weaknesses in its extension ecosystem can have outsized, internet-wide consequences. ## 📰 Newsletter: Headline: Can WordPress Stay Open—and Fair? Blurb: This week we’re watching Joost de Valk and Karim Marucchi introduce the Fairness Initiative, a push toward a decentralized “Fair Package manager” for WordPress. Why care? With WP running 40%+ of the web, a stronger supply chain (signing, SBOMs, provenance), clearer governance, and sustainable maintainer funding aren’t “nice-to-haves”—they’re table stakes. Expect conversations about namespacing, verifiable releases, and how a package layer could coexist with WordPress.org without fragmenting the ecosystem. If you teach, build, or secure WP, this is one to bookmark. Watch the discussion on Techstrong TV: the “Can WordPress remain open and fair?” segment on LinkedIn. For context on supply-chain best practices, see Sigstore and CISA’s SBOM primer. ## ✅ Action Items: Tailored prompt for your role: - Purpose: Analyze how each new article aligns with open-source advocacy, contributor engagement, and education, supporting a path toward an OSPO leadership role. - Use this prompt on future articles: “As a Developer Advocate focused on WordPress and open source, evaluate this article for: 1) Open-source governance and transparency: What models are proposed, how inclusive are decision pathways, and how do they map to OSPO practices? 2) Contributor engagement and onboarding: What mechanisms (documentation, mentorship, tooling) are suggested to grow and retain contributors? Identify adaptable tactics for WP contributor days and Git/GitHub curricula. 3) Supply chain health and sustainability: How does the piece address dependency risk, provenance, and maintainer funding? Propose actions I can champion at GoDaddy and in the WP community. 4) Educational impact: Which concepts should be transformed into workshops, labs, or docs for PHP/JS/HTML/CSS/Git/GitHub learners? 5) DEIB and accessibility: Where can inclusive language, representation, and accessible design be improved? Offer concrete updates. 6) Strategic alignment with OSPO goals: Extract policies, metrics, and governance processes that inform an OSPO roadmap (e.g., project intake, compliance, SBOMs, code-of-conduct, transparency reports). Deliver: a summary; a mapping to my objectives; prioritized recommendations (near-term 0–90 days, mid-term 90–180, long-term 6–18 months); and success metrics.” ## 🧪 Hypotheses: - H1: A decentralized package manager with signed releases will reduce malicious plugin incidents by ≥30% year-over-year. - H2: Transparent governance with published decision logs increases contributor retention by ≥15%. - H3: Introducing SBOMs for top 1,000 plugins lowers mean-time-to-remediate supply-chain vulnerabilities by ≥25%. - H4: Funding badges and patronage links increase maintainer revenue - Summary: Can WordPress remain open and fair? Joost de Valk of Emilia Capital and Karim Marucchi of Crowd Favorite introduce The Fairness Initiative, an ambitious effort to decentralize WordPress through the Fair Package manager. With WordPress powering over 40% of the web, the project addresses supply chain risks, legacy infrastructure challenges, and the demand for transparent governance. Watch here: https://lnkd.in/efXjyVGr - URL: https://www.linkedin.com/posts/techstrong-tv_can-wordpress-remain-open-and-fair-joost-ugcPost-7346696329793859584-UMCM?utm_source=share&utm_medium=member_desktop&rcm=ACoAAAD0NvEBPtYCnSVTg0yvFSLaHHE9PeEfFY4 [Techstrong TV](https://www.linkedin.com/company/techstrong-tv?trk=public_post_feed-actor-name) 2,616 followers Can WordPress remain open and fair? [Joost de Valk](https://nl.linkedin.com/in/jdevalk?trk=public_post-text) of [Emilia Capital](https://nl.linkedin.com/company/emilia-capital?trk=public_post-text) and [Karim Marucchi](https://www.linkedin.com/in/karimmarucchi?trk=public_post-text) of [Crowd Favorite](https://www.linkedin.com/company/crowdfavorite?trk=public_post-text) introduce The Fairness Initiative, an ambitious effort to decentralize WordPress through the Fair Package manager. With WordPress powering over 40% of the web, the project addresses supply chain risks, legacy infrastructure challenges, and the demand for transparent governance. Watch here: [https://lnkd.in/efXjyVGr](https://www.linkedin.com/redir/redirect?url=https%3A%2F%2Flnkd%2Ein%2FefXjyVGr&urlhash=dB2i&trk=public_post-text) Play VideoVideo Player is loading.Loaded: 0%PlayBack to startStream Type LIVE Current Time 0:00/Duration -:-1x Playback RateShow CaptionsMuteFullscreen, Techstrong TV’s Post, Techstrong TV, 01jzdmbhtrnshsmwqqm0x76n2v.