Automatically Blackballed  Full Document Contents/Articles/Automatically Blackballed.md, Automatically Blackballed, Jake Caputo. > [!note]+ Document Notes > tags: [#WordPress, #GPL, #ThemeForest, #Envato, #WordCamps] > Author: Jake Caputo > Source: DesignCrumbs.com > Reference: [Archived Link](https://web.archive.org/web/20160304045548/http://designcrumbs.com/automatically-blackballed) > date created: 2025-02-14 15:30 > > # Title: Automatically Blackballed – WordPress, ThemeForest, and the GPL Dilemma > <!-- deep-read:sections start --> ## Table of Contents: - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#-notes) - [📖 References](#-references) - [🗣️ 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 (Diversity, Equity, Inclusion, and Belonging) Assessment](#-deib-diversity-equity-inclusion-and-belonging-assessment) - [✅ Logical Validity](#-logical-validity) - [🔍 DARVO Analysis](#-darvo-analysis) - [🔍 SEO Evaluation](#-seo-evaluation) - [🎯 Conclusion](#-conclusion) ## 📝 Summary: The article "Automatically Blackballed" by Jake Caputo discusses his exclusion from WordCamp events due to his participation in selling themes on ThemeForest, an Envato marketplace that employs a split licensing model. The WordPress community enforces strict GPL compliance, requiring all components (PHP, CSS, JS, images) of WordPress-related products to be fully GPL. Since ThemeForest mandates a split license, Caputo and other ThemeForest authors are disqualified from contributing to WordCamps. The article raises concerns about fairness, community inclusion, and the larger implications of licensing conflicts. ## 📖 Main Content: The piece explores: - **The WordPress GPL licensing policy** and how it impacts developers. - **ThemeForest’s split license model** and why it conflicts with WordCamp guidelines. - **Personal and financial consequences** of the restriction for developers reliant on ThemeForest. - **Responses from WordPress leadership, including Matt Mullenweg**, and a lack of proposed resolutions. - **The broader issue of community exclusion**—not just for Caputo but for many developers. - **A call for constructive dialogue** between Envato and WordPress.org. ### 🗒️ Notes: - **Background:** - Caputo actively participated in WordCamps as a speaker and organizer. - He was banned from participating due to WordPress.org’s licensing requirements. - **GPL & WordCamp Policy:** - WordPress themes must be fully GPL to qualify for WordCamp participation. - ThemeForest employs a **split license**: PHP is GPL, but CSS/JS/images are not. - **ThemeForest’s Model:** - Caputo earns **100% of his income** from ThemeForest sales. - The **split license is mandatory**; authors cannot choose 100% GPL. - **Exclusion Impacts:** - Affects **high-profile contributors** who sell on Envato. - Creates **tensions between WordPress leadership and developers**. - Raises concerns about **accessibility, fairness, and openness**. - **Key Responses:** - **Matt Mullenweg:** Acknowledges it's a "sucky situation" but stands firm. - **Envato:** Defends split licensing to protect authors’ assets. - **Community Reaction:** - Widespread frustration from developers. - **Debate on whether WordPress.org should enforce stricter or more flexible licensing rules.** - **Final Takeaway:** - The situation remains unresolved. - Developers caught in the middle **face difficult decisions** about where to sell and how to participate in the WordPress ecosystem. ## 📖 References: - [WordPress Licensing Policy](https://wordpress.org/about/license/) - [ThemeForest Licensing Terms](https://web.archive.org/web/20160304045548/http://support.envato.com/) - [Discussion on GPL and Licensing](https://web.archive.org/web/20160304045548/http://wordpress.org/news/2009/07/themes-are-gpl-too/) ## 🗣️ Paraphrase: 1. **Original:** "That sucks. Matt explained why things are the way they are and why he/they won’t budge on principles." - **Paraphrased:** Matt Mullenweg acknowledged the unfortunate nature of the situation but reiterated that WordPress.org would maintain its strict GPL stance. 2. **Original:** "I am a casualty in a war between giants." - **Paraphrased:** Caputo sees himself as collateral damage in a larger dispute between WordPress.org and Envato. ## 📰 Newsletter: 🚀 **WordPress News & Insights** The ongoing debate about **GPL compliance** and **ThemeForest licensing** has raised questions about fairness in the WordPress ecosystem. Jake Caputo, a longtime contributor, was barred from participating in WordCamps due to his affiliation with Envato. The controversy highlights the challenges of balancing **open-source principles with economic realities** for developers. Read more [here](https://web.archive.org/web/20160304045548/http://designcrumbs.com/automatically-blackballed). ## ✅ Action Items: - Raise awareness of licensing issues affecting contributors. - Encourage discussions between **WordPress.org and Envato** to find a middle ground. - Explore **alternative marketplaces** that support full GPL compliance. - Advocate for **more inclusive community participation policies**. ## 🧪 Hypotheses: 1. If Envato allows **100% GPL licensing as an option**, more developers would comply with WordCamp rules. 2. Excluding ThemeForest authors from WordCamps negatively impacts **the diversity of knowledge shared**. ## 📊 Methodology: - Conduct surveys among **WordPress developers** about licensing preferences. - Analyze WordCamp participation **before and after the policy enforcement**. - Interview key stakeholders **from both WordPress and Envato**. ## ❓ Questions: 1. Should WordPress.org reconsider its strict **GPL enforcement**? 2. How can ThemeForest authors navigate these licensing conflicts? ## 🔮 Future Research: - Comparing licensing policies across **other open-source communities**. - Studying the **economic impact of GPL restrictions** on theme developers. ## 💡 Implications: - Could push developers **away from WordPress-based monetization**. - Might lead to **a split in the WordPress community**. ## 🧠 Learning Styles Assessment: - **Verbal**: Strong explanations of licensing issues. - **Logical**: Structured argument but lacks supporting data. - **Visual**: No diagrams; adding **infographics** could improve comprehension. ## 📊 Accessibility Assessment: - **Screen Reader Compatibility**: Adequate. - **Contrast & Readability**: Good but lacks **text structuring for easy navigation**. ## 🌍 DEIB (Diversity, Equity, Inclusion, and Belonging) Assessment: - **Potential bias**: The article focuses on **developers with existing financial ties** to ThemeForest. - **Improvement**: Consider perspectives from **non-ThemeForest developers**. ## ✅ Logical Validity: - **Valid Points**: - **ThemeForest licensing limits participation**. - **WordPress GPL stance is well-documented**. - **Logical Fallacies**: - **Slippery slope**: "2.3 million people are affected" is an overstatement. - **Appeal to emotion**: "I am a casualty in a war." ## 🔍 DARVO Analysis: - **Deny**: WordPress.org denies singling out Caputo. - **Attack**: Some community members attack **WordPress leadership**. - **Reverse Victim and Offender**: Caputo frames himself as **the victim**, though WordPress argues it is enforcing policy fairly. ## 🔍 SEO Evaluation: - **Keyword Optimization**: Strong use of "GPL," "ThemeForest," and "WordPress." - **Meta Description**: Needs improvement for clarity. ## 🎯 Conclusion: The **WordPress GPL policy vs. ThemeForest licensing debate** continues to spark controversy. While **WordPress.org enforces compliance**, many developers feel excluded. A **collaborative solution is needed** to ensure fairness while maintaining open-source principles. <!-- deep-read:sections end --> ## Highlights - The [Software Freedom Law Center explains](http://web.archive.org/web/20130606231740/http://wordpress.org/news/2009/07/themes-are-gpl-too/) that when it comes to themes, the GPL covers the PHP *but may or may not* include the CSS, JavaScript, and images. So legally, this is the bar that has been set. ([View Highlight](https://read.readwise.io/read/01jm2db7dpt8brprnfnsp7tfx6)) - The [WordCamp guidelines](http://web.archive.org/web/20130606231740/http://plan.wordcamp.org/become-an-organizer/representing-wordpress/) state that volunteers must: > Embrace the [WordPress license](http://web.archive.org/web/20130606231740/http://wordpress.org/about/license/). *If distributing WordPress-derivative works* (themes, plugins, WP distros), any person or business should give their users the same freedoms that WordPress itself provides. Note: this is one step above simple compliance, which requires PHP code to be GPL/compatible but allows proprietary licenses for JavaScript, CSS, and images. 100% GPL or compatible is required for promotion at WordCamps when WordPress-derivative works are involved, the same guidelines we follow on WordPress.org. ([View Highlight](https://read.readwise.io/read/01jm2dbjzbgtqr3q021bcr3h31)) - We spoke with Japh Thomson (WordPress Evangelist at Envato) on [Please Advise Episode 08](http://web.archive.org/web/20130606231740/http://pleaseadvise.fm/) and he explained Envato’s side of things. ([View Highlight](https://read.readwise.io/read/01jm2dd9rhdz2xjkm9hqg3g6fv)) - So the idea behind the split license is to protect authors in terms of their designs and things like that. The parts that have to be GPL *are* GPL, the parts that don’t have to be, we’re happy to provide that license to help you protect them. The other thing is that on the [Envato] marketplaces there are smaller component style items, so you could buy the extended license on the marketplace, and use that in your WordPress theme. And if you then make your WordPress theme 100% GPL, you just disregarded the license of the item you put into the theme ([View Highlight](https://read.readwise.io/read/01jm2ddfzg846p69z2zfxe75k0))