Openverse, a WordPress Project  Full Document Contents/Articles/Openverse, a WordPress Project.md, Openverse, a WordPress Project, Samuel Sidler. > [!note]+ Document Notes > tags: [#WordPress, #OpenSource, #Openverse] > - #WordPress > - #OpenSource > - #Openverse > Author: Anna Tumadóttir (Partial reference to Creative Commons CEO) > Source: Delta Blog > Reference: [Delta Blog - Openverse Article](https://www.delta.blog/openverse-a-wordpress-project/?__readwiseLocation=) > date created: 2024-12-07 14:30 > > # Title: **Unraveling Openverse: Ownership, Transition, and Ecosystem Implications** > <!-- deep-read:sections start --> ## Table of Contents: 1. 📝 [Summary](#-summary) 2. 📖 [Main Content](#-main-content) - 🗒️ [Notes](#️-notes) 3. 🗣️ [Paraphrase](#-paraphrase) 4. 📰 [Newsletter Blurb](#-newsletter) 5. ✅ [Action Items](#-action-items) 6. 🧪 [Hypotheses](#-hypotheses) 7. 📊 [Methodology](#-methodology) 8. ❓ [Questions](#-questions) 9. 🔮 [Future Research](#-future-research) 10. 💡 [Implications](#-implications) 11. 🧠 [Learning Styles Assessment](#-learning-styles-assessment) 12. 📊 [Accessibility Assessment](#-accessibility-assessment) 13. 🌍 [DEIB Assessment](#-deib-assessment) 14. ✅ [Logical Validity](#-logical-validity) 15. 🔍 [DARVO Analysis](#-darvo-analysis) 16. 🔍 [SEO Evaluation](#-seo-evaluation) 17. 🎯 [Conclusion](#-conclusion) --- ## 📝 Summary: This article explores the complexities surrounding Openverse, a project transitioned from Creative Commons (CC Search) to WordPress.org. Despite its presentation as part of the WordPress project, ownership remains convoluted. Key points include Automattic’s financial role, the WordPress Foundation’s trademark control, and Matt Mullenweg's operational control. These dynamics highlight the intricate web of WordPress ecosystem governance. --- ## 📖 Main Content: ### 🗒️ Notes: - **Creative Commons and CC Search**: - CC Search became unsustainable for Creative Commons. - Transitioned to WordPress.org in 2021 and renamed Openverse. - **Automattic’s Role**: - Paid Creative Commons for the transition. - Hired former CC Search employees. - **WordPress Foundation’s Involvement**: - Filed trademarks for Openverse. - No operational control; trademarks primarily managed by Mullenweg. - **Operational Complexities**: - Openverse is hosted on WordPress.org, Mullenweg’s personal property. - Automattic funds development under the guise of contributing to WordPress.org. - **Trademark Ownership**: - WordPress Foundation holds trademarks, but its website lacks direct references to Openverse. - **Public Statements**: - Mullenweg portrays Openverse as part of the WordPress project while privately managing it through Automattic. --- ## 🗣️ Paraphrase: 1. **Original**: "The transition to WordPress.org began with Slack channels, GitHub repositories, and rebranding efforts." **Paraphrased**: "Openverse’s integration into WordPress.org started with setting up new collaboration tools and renaming initiatives." 2. **Original**: "Mullenweg emphasizes contributions to WordPress.org while controlling operations." **Paraphrased**: "Although portrayed as part of the WordPress ecosystem, Mullenweg retains centralized control over Openverse’s functioning." --- ## 📰 Newsletter: **🌟 Openverse: An Open Source Asset in Transition** The Openverse project, formerly CC Search, exemplifies WordPress.org's expansion of open-source capabilities. Transitioned from Creative Commons in 2021, Openverse provides access to CC-licensed content. Despite its value, ownership intricacies raise questions about governance within the WordPress ecosystem. Dive deeper into how Openverse serves the community while sparking debates about transparency and control. [Read More](https://www.delta.blog/openverse-a-wordpress-project/?__readwiseLocation=) --- ## ✅ Action Items: 1. **For Advocacy**: Highlight Openverse as a case study in governance models within open-source projects. 2. **For Contributor Engagement**: Examine ways to increase transparency in ownership to attract and retain contributors. 3. **For OSPO Goals**: Use Openverse as a model for advocating operational clarity in projects combining open-source and corporate management. --- ## 🧪 Hypotheses: - Projects with ambiguous ownership structures face challenges in contributor retention. - Transparent governance increases trust and adoption in open-source communities. --- ## 📊 Methodology: - Conduct surveys with WordPress contributors on perceptions of governance. - Analyze contributor retention rates pre-and-post Openverse transition. --- ## ❓ Questions: - How does Openverse’s governance model affect trust within the WordPress community? - Could clearer ownership improve community engagement? --- ## 🔮 Future Research: - Explore models for balancing corporate and non-profit roles in open-source projects. - Investigate the impact of trademark ownership on contributor dynamics. --- ## 💡 Implications: Clarifying Openverse’s ownership could set a precedent for governance in mixed-entity open-source projects, fostering transparency and community trust. --- ## 🧠 Learning Styles Assessment: - **Visual**: Minimal visuals; recommend adding infographics to explain ownership. - **Aural**: Lacks auditory options; add podcasts discussing governance issues. - **Verbal**: Well-written with detailed examples. - **Kinesthetic**: Could improve with interactive tools or scenarios for governance challenges. --- ## 📊 Accessibility Assessment: - **Strengths**: Clear language, good structure. - **Weaknesses**: Lacks alt-text for images; no audio options. - **Improvements**: Add alt-text, audio summaries, and keyboard navigation support. --- ## 🌍 DEIB Assessment: - **Inclusive Language**: Neutral and accessible. - **Representation**: No cultural or diverse examples; recommend including global community insights. - **Neurodiversity**: Structure supports clarity but could benefit from simpler paragraphs. --- ## ✅ Logical Validity: - **Strengths**: Provides detailed evidence for claims. - **Fallacies**: Slight appeal to authority in citing trademarks without operational details. --- ## 🔍 DARVO Analysis: - **Deny**: Mullenweg downplays the WordPress Foundation’s operational absence. - **Attack**: None identified. - **Reverse Victim**: Subtle narrative shifts portray governance questions as overcomplications. --- ## 🔍 SEO Evaluation: - **Keywords**: Effective use of "Openverse," "WordPress," and "ownership." - **Improvements**: Optimize meta description and use schema for enhanced discoverability. --- ## 🎯 Conclusion: Openverse, while a testament to WordPress.org’s innovation, underscores governance challenges. Clarifying ownership could strengthen community trust and project sustainability. <!-- deep-read:sections end --> ## Highlights - A team was formed to shepherd the transition and maintain the site, with Creative Commons employees hired by Automattic[[6]](https://www.delta.blog/openverse-a-wordpress-project/#fn6) and working alongside existing Automatticians, who spearheaded the initiative. ([View Highlight](https://read.readwise.io/read/01jeh7s573mdwqg5s4zexycszc)) - [Automattic’s](https://storage.courtlistener.com/recap/gov.uscourts.cand.437474/gov.uscourts.cand.437474.62.0.pdf?ref=delta.blog) [order](https://storage.courtlistener.com/recap/gov.uscourts.cand.437474/gov.uscourts.cand.437474.62.1.pdf?ref=delta.blog) is… not an order. I’m not entirely certain what strategy Automattic is employing with their submissions. ([View Highlight](https://read.readwise.io/read/01jeh8dxcrjpjh4s99ts9af8rr)) - In *not* submitting something the court could directly use, Automattic could be relying on the judge being confused, and writing an order that, ultimately, is not meaningful. ([View Highlight](https://read.readwise.io/read/01jeh8ees2kng18bjkbe7ne2ka)) - **Second: delay, delay, delay.** Related to the above point, in making it harder to craft an order that is both effective *and* what the court feels reasonable at this stage, Automattic may be buying itself more time. Testing the court’s patience, however, is not a good idea. ([View Highlight](https://read.readwise.io/read/01jeh8exjv8wd8cf4psfjfrfac)) - Judge AMO explicitly dismissed WPE’s lawyer, when she raised actions that were not in evidence.[[5]](https://www.delta.blog/openverse-a-wordpress-project/#fn5) The only reason I can think to cite new case law is in preparation for appeal. ([View Highlight](https://read.readwise.io/read/01jeh8fwsvkntr8v9zcenb6zgm)) - The application of the wordmark was made by the WordPress Foundation, with Mullenweg signing the paperwork with a title of “CEO.”[[9]](https://www.delta.blog/openverse-a-wordpress-project/#fn9) Meanwhile, on the trademark application for the logo, Mullenweg signed the paperwork with a title of “Founder.” ([View Highlight](https://read.readwise.io/read/01jeh8jepndta55xbve14yp1er)) - “Openverse adheres to the privacy policy of all WordPress.org websites.” ([View Highlight](https://read.readwise.io/read/01jeh8jypdzbreftbqtmx6wjk6)) - As the community has so clearly discovered recently, WordPress.org is owned solely by Mullenweg, as his own personal site. In using Openverse, you are agreeing to the privacy policy drafted by Mullenweg. ([View Highlight](https://read.readwise.io/read/01jeh8kamp5hw3rrewbdehdhna)) - **Matt Mullenweg:** It’s a little complicated because, as you know, **WordPress.org is not part of the Foundation**. So basically, **Automattic paid Creative Commons**, the nonprofit. ([View Highlight](https://read.readwise.io/read/01jeh8m8dgjt6byqpebeh73nyz)) - The WordPress Foundation filed trademarks for Openverse, which they do not use, only Mullenweg does on his Openverse website ([View Highlight](https://read.readwise.io/read/01jeh8mwnkw3rnddq71evnw2xe)) - Mullenweg hosts and runs Openverse on his WordPress.org infrastructure ([View Highlight](https://read.readwise.io/read/01jeh8mzp4ph2xxxaxnq21jbgv))