Automatically Blackballed  ## Metadata - Author: [[Jake Caputo]] - Full Title: Automatically Blackballed - Category: #articles - Document Note: --- 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 ## 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. - Document Tags: [[gpl]] [[Matt Mullenweg]] [[WordPress]] [[wpdrama]] - Summary: Last year I attended three WordCamps and spoke at two of them. This year I was on the planning team for WordCamp Chicago and was asked to speak again. I am - URL: http://web.archive.org/web/20130606231740/http://www.designcrumbs.com/automatically-blackballed Last year I attended three WordCamps and spoke at two of them. This year I was on the planning team for WordCamp Chicago and was asked to speak again. I am passionate about WordPress and want to give back to the community. On Friday, January 18, I was told that I may no longer participate in WordCamps. More specifically, I was contacted by Andrea Middleton (Dot Organizer for Automattic). She said according to the WordCamp guidelines, I may not speak or volunteer at WordCamps while I sell my themes on ThemeForest with their split license as is. This post is not to argue about GPL (although I’m sure it’ll come up in the comments). *But*, the GPL is the reason why I am not able to participate in WordCamps. This post *is* to talk about those of us stuck in the middle. So while I don’t want to talk about the GPL… ##### Let’s Talk About The GPL 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. 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. > > As a themer, that means everything in my themes including the images, CSS, and JavaScript must be covered under the GPL. No big deal, right? I’d have to include things under the GPL that aren’t legally required to be under the GPL, but I have no problem with this. ##### Welcome To ThemeForest In March 2012 I made the move to selling themes full time. I chose to do so on [ThemeForest](http://web.archive.org/web/20130606231740/http://themes.designcrumbs.com/), mainly because of their reach. At the time of writing, they have **2,310,790** members. That’s a lot of people. I make a very comfortable living by selling my themes on ThemeForest, and it accounts for nearly 100% of my income. Now let’s talk about licenses. The *only* license available to authors on ThemeForest is a [split license](http://web.archive.org/web/20130606231740/http://support.envato.com/index.php?/Live/Knowledgebase/Article/View/428/0/split-licensing-and-the-gpl---what-does-it-all-mean). The PHP in our themes is covered under the GPL, but the images, CSS, and JavaScript *are not*. There’s nothing wrong with this, and I also have no problem with this; *But* it doesn’t meet those guidelines for WordCamps that I mentioned earlier. ##### I Am A Casualty In A War Between Giants At this point, I have **one** option that I personally can do; Remove my themes from ThemeForest. Doing so would mean my income would drop to $0 and I would have to lay off my one employee. This is not reasonable. Even if I moved my themes to another marketplace I’d take a hit of thousands of dollars a month. And this isn’t just about me. Any Envato-er is not allowed to contribute to WordCamps. There are brilliant people who sell their items on the Envato network including contributors to WordPress Core, WordPress.org plugin reviewers, highly respected members of the WordPress community, and even some of the biggest theme shops and frameworks out there (I won’t name names unless those people want to be named). The reach of this issue is much bigger than anyone may have initially thought. While I may not be the most important casualty, I’m merely one of the first. ##### So What’s The Answer? I’m not going to take sides. I won’t say that WordPress.org should bend their rules, and I won’t say that Envato should change their licensing. But we’re talking about two very heavy hitters here; Surely something can be figured out, right? Well, no. Not yet. After I received my ‘notice’ I was invited to chat with Matt Mullenweg about the situation via Skype. His answer: > That sucks. > > Matt explained why things are the way they are and why he/they won’t budge on principles. In the end, the conversation had no answers. > **Jake:** So in my shoes, what would you do? > > **Matt:** as I said earlier, it’s a sucky situation > > **Jake:** But in the short term, the answer is that I just don’t participate and hope for the best? > > **Matt:** I have forgone profit for principles many times and been lucky pretty much every time, but not everyone always is and I can’t speak to other people’s backgrounds or obligations > > While I couldn’t get a straight answer out of Matt, it seems like he thinks it’s worth bringing in no money in order to participate at WordCamp. 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. > 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. > > So as you can see, nobody can give a straight answer and nobody is willing to compromise. And really, this does not effect WordPress.org (WordPress Foundation, WordCamps, etc.) or Envato as much as it effect’s the WordPress community. As I said before, there are over **2.3 million** users on the Envato marketplaces. Simply by being a member there you are promoting ThemeForest, by promoting ThemeForest you are promoting the split-license, and this is against the WordCamp guidelines. Note that it isn’t “promote at a WordCamp” but rather just promote period. > Do not promote others who fail to respect the WordPress license or trademark. If a person or business does not distribute WordPress-derivative code, but promotes those who do, those they are promoting should meet the guidelines above. [The guidelines above in this post.] > > Something needs to be fixed here and I’m not sure how, nor have the power, to fix it. Over 2.3 million people are hanging in the balance. People who can’t speak, share their ideas, or share their expertise, at a WordCamp. Simply by Being part of the largest WordPress theme marketplace, we’re automatically blackballed. *Edit: It’s been pointed out that this has nothing to do with Automattic, but rather WordPress.org.* **Update 1-24-13**: Matt has responded in and to the comments on this post as well as many others that have popped up around the net. Collis (CEO of Envato) responded in a [post at wpdaily.co](http://web.archive.org/web/20130606231740/http://wpdaily.co/themeforest-wordcamps/), but he has not yet joined the community and replied to *any* comments, included some Matt left on his post. For now, it sounds like no change is coming. Many have tried to point out ways that I could still volunteer at a WordCamp, but that’s not the point. This isn’t about me; It’s about the community. And to be clear, I wasn’t “singled out” and Matt didn’t do anything personally. I simply showed up on the radar and the WordCamp Foundation did it’s job by informing me I can’t volunteer while I sell on ThemeForest. ThemeForest breaks the guidelines, so by selling there I break the guidelines. It’s as simple as that. **Update 1-29-13**: Collis has posted a plan to survey the authors of WP products on the Envato Marketplaces. [You can read about that over at wpdaily.co](http://web.archive.org/web/20130606231740/http://wpdaily.co/theme-clarity/). **Update 2-28-13**: Things have been cleared up. See [Un-Blackballed](http://web.archive.org/web/20130606231740/http://www.designcrumbs.com/un-blackballed).., Automatically Blackballed, Jake Caputo, 01jm0qt80rcjxtw30nfpng0wpz.