Forks and Copies  🔗 **Source:** [Forks and Copies](https://make.wordpress.org/plugins/2015/08/26/forks-and-copies/) > [!note]+ Document Notes > tags: [#WordPress, #GPL, #PluginReview, #Forks, #PluginPolicy, #CommunityGovernance] > Author: [Make WordPress Plugins] > Source: [Make WordPress Plugins Blog] > Reference: [https://make.wordpress.org/plugins/2015/08/26/forks-and-copies](https://make.wordpress.org/plugins/2015/08/26/forks-and-copies) > date created: 2024-11-27 15:45 > > # Title: Forks and Copies: WordPress Plugin Policy > <!-- 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 Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🔍 DARVO Analysis](#-darvo-analysis) - [🔍 SEO Evaluation](#-seo-evaluation) - [🎯 Conclusion](#-conclusion) --- ## 📝 Summary: This post clarifies WordPress.org’s plugin policy regarding forks and identical copies. It emphasizes that while GPL licenses permit forking, hosted plugins must demonstrate substantial changes beyond simple rebranding or function renaming. The Plugin Review Team enforces guidelines to prevent duplicates and ensure proper attribution while fostering innovation. --- ## 📖 Main Content: ### 🗒️ Notes: - **Policy Overview**: - Forking is allowed under GPL but must meet WordPress.org’s “substantial change” requirement. - Direct copies without significant changes or attribution are rejected. - Examples of acceptable changes: - Adding/removing features. - Code modernization or cleanup. - Differentiating functionalities. - **Plugin Review Process**: - All plugins are reviewed to detect duplicates. - Tools like diff comparisons assess changes between the original and the fork. - If violations occur: - Original developers may be contacted. - Duplicates are removed unless they meet substantial change criteria. - **Reporting Duplicates**: - Users can report suspected copies to [email protected]. - Provide links and context to streamline the review process. - **Developer Guidance**: - Fork creators must retain original attributions and copyrights. - Surface-level changes (e.g., renaming functions) are insufficient. - **Challenges with External Plugins**: - Reporting issues with non-hosted plugins requires original developers to engage with WordPress.org. - Barriers include unresponsive support from premium plugin developers. --- ## 📖 References: - [Make WordPress Plugins Blog](https://make.wordpress.org/plugins/2015/08/26/forks-and-copies) --- ## 🗣️ Paraphrase: 1. **Original**: "We don’t want to have 100 plugins that are the same, save the credits." **Paraphrased**: "Our goal is to avoid hosting numerous plugins that only differ in their credit lines." 2. **Original**: "If you’re the original developer, email us a copy of your plugin (we promise not to steal it)..." **Paraphrased**: "Original developers should email us their plugin for comparison, assuring that their work won’t be misused." --- ## 📰 Newsletter: 🎉 **WordPress Plugin Policies Update**: Ever wondered how WordPress handles plugin forks? The latest insights from the Plugin Review Team explain it all: forks must show meaningful changes, not just rebranding. Learn how these policies ensure innovation and fairness in the ecosystem. Details: [Read More](https://make.wordpress.org/plugins/2015/08/26/forks-and-copies). --- ## ✅ Action Items: - Advocate for clearer definitions of "substantial change" to guide developers. - Raise awareness about reporting processes to prevent duplicate plugins. - Promote transparency in plugin review workflows for community trust. --- ## 🧪 Hypotheses: - Strengthening fork requirements will reduce duplicate plugins on WordPress.org. - Streamlining reporting mechanisms could improve response times and accuracy. --- ## 📊 Methodology: - Analyze plugin approval and rejection trends to identify common issues. - Conduct surveys of plugin developers to assess awareness of forking guidelines. --- ## ❓ Questions: 1. How can WordPress.org enforce attribution compliance effectively? 2. Should external plugin developers have a formal pathway to address duplicate reports? --- ## 🔮 Future Research: - Evaluate how fork policies influence plugin innovation and competition. - Explore user satisfaction with WordPress.org's reporting mechanisms. --- ## 💡 Implications: - Improved policies may enhance developer accountability. - Clearer processes could strengthen trust within the WordPress ecosystem. --- ## 🧠 Learning Styles Assessment: - **Visual**: Include flowcharts of plugin review processes. - **Verbal**: Enhance with case studies of acceptable forks. - **Logical**: Use data on duplicate plugin rejection rates to highlight trends. --- ## 📊 Accessibility Assessment: - **Improve**: Add alt-text to examples of acceptable vs. unacceptable forks. - **Improve**: Ensure policy documentation is mobile-friendly and screen-reader compatible. --- ## 🌍 DEIB Assessment: - **Cultural Relevance**: Consider diverse use cases for plugins globally. - **Neurodiversity Support**: Simplify policy language for clarity and accessibility. --- ## ✅ Logical Validity: - **Strength**: Clear reasoning supports the need for substantial changes in forks. - **Weakness**: The post could provide more concrete examples to reduce ambiguity. --- ## 🔍 DARVO Analysis: 1. **Deny**: The policy avoids denying responsibility, emphasizing fairness. 2. **Attack**: No evidence of aggressive responses to reporters or developers. 3. **Reverse Victim**: Maintains objectivity without framing developers as adversaries. --- ## 🔍 SEO Evaluation: - **Keywords**: "WordPress plugin policy," "plugin forks," "GPL compliance." - **Meta Description**: Focuses on explaining WordPress.org’s plugin fork guidelines. - **Internal Links**: Links to related plugin policies and reporting procedures. --- ## 🎯 Conclusion: WordPress.org's plugin policy ensures fair practices by mandating substantial changes for forks. Developers and users alike benefit from robust guidelines, fostering innovation and accountability in the ecosystem. <!-- deep-read:sections end --> 📄 **Full text:** ![[Full Document Contents/Articles/Forks and Copies|Forks and Copies, Make WordPress Plugins]] ## Highlights - You have to add new features, remove features, modernize, fix, clean up, or otherwise make a change to the plugin that differentiates it from the original. In rare cases, a simple clean-up will be accepted, but normally we try to get a hold of the original authors and have the fixes folded in to the original plugin. ([View Highlight](https://read.readwise.io/read/01jdq46xckdshhc1m1d08nvzjj))