 |
VOOZH | about |
|
VOOZH | about |
This document specifies the licensing terms for the BuddyPress VIP Go plugin, including the license type, copyright holders, key terms, and how the license integrates with the WordPress ecosystem. For information about plugin distribution and packaging, see Build and Distribution Process.
The BuddyPress VIP Go plugin is licensed under GPL-2.0-or-later (GNU General Public License version 2.0 or any later version). This license designation appears in multiple locations within the codebase to ensure clear legal identification.
The following diagram maps where license information is declared in the repository structure:
Sources: composer.json4 LICENSE1-280
The composer.json file declares the license in machine-readable format:
| Field | Value | Line Reference |
|---|---|---|
license | GPL-2.0-or-later | composer.json4 |
type | wordpress-plugin | composer.json5 |
name | automattic/buddypress-vip-go | composer.json2 |
This declaration ensures that package managers and dependency analysis tools correctly identify the plugin's license terms.
Sources: composer.json1-15
The plugin is jointly copyrighted by two organizations, as declared in the authors field of composer.json:
| Organization | Homepage | Role |
|---|---|---|
| Human Made | https://humanmade.com/ | Original development and WordPress VIP integration |
| Automattic | https://automattic.com/ | Ongoing maintenance and WordPress VIP platform provider |
Sources: composer.json6-14
The "GPL-2.0-or-later" designation allows users to choose between GPL version 2.0 or any later version published by the Free Software Foundation. This provides flexibility as the GPL evolves while maintaining current compatibility.
The GPL-2.0 license grants four essential freedoms, as outlined in the license preamble LICENSE9-26:
Sources: LICENSE9-26 LICENSE155-164
The GPL-2.0 includes copyleft provisions that require derivative works to maintain the same license terms:
| Requirement | Description | License Section |
|---|---|---|
| Source Distribution | Must provide complete source code with binary distributions | LICENSE134-154 |
| License Preservation | Modified versions must remain GPL-licensed | LICENSE90-102 |
| License Inclusion | Must include GPL license text with distributions | LICENSE79-88 |
| Modification Notice | Must mark modified files with change notices | LICENSE95-96 |
| No Additional Restrictions | Cannot impose further restrictions on recipients | LICENSE189-195 |
Sources: LICENSE56-227
The license explicitly disclaims warranty, as stated in sections 11-12:
BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
This means the plugin is provided "AS IS" without warranties of merchantability or fitness for a particular purpose LICENSE260-268
Sources: LICENSE258-280
The BuddyPress VIP Go plugin's GPL-2.0-or-later license ensures compatibility with the WordPress ecosystem, which is also GPL-licensed.
Sources: composer.json21-30
Development dependencies use permissive licenses that are GPL-compatible:
| Package | License | Compatibility | Purpose |
|---|---|---|---|
automattic/vipwpcs | MIT | GPL-compatible | Code standards enforcement |
phpunit/phpunit | BSD-3-Clause | GPL-compatible | Unit testing framework |
php-parallel-lint/php-parallel-lint | BSD-2-Clause | GPL-compatible | Syntax validation |
phpcompatibility/phpcompatibility-wp | LGPL-3.0 | GPL-compatible | PHP version compatibility |
yoast/wp-test-utils | BSD-3-Clause | GPL-compatible | WordPress test utilities |
These permissive licenses (MIT, BSD) allow integration into GPL-licensed projects without restriction.
Sources: composer.json25-30
The GPL-2.0-or-later license choice ensures full compliance with WordPress.org plugin directory requirements and WordPress VIP platform policies.
WordPress.org requires all hosted plugins to be "100% GPL or compatible" to ensure the entire WordPress ecosystem remains free software. The GPL-2.0-or-later designation meets this requirement.
WordPress VIP's platform infrastructure uses proprietary components (VIP File Hosting Service, CDN, etc.), but these are accessed through GPL-licensed APIs. The plugin's GPL license does not restrict VIP from providing proprietary hosting services.
This architectural separation allows the plugin to remain GPL while operating on proprietary infrastructure—a common pattern in WordPress hosting.
Sources: composer.json4
The complete GPL-2.0 license text resides in the repository root:
| File | Size | Purpose |
|---|---|---|
LICENSE | 280 lines | Full GNU General Public License Version 2 text |
The license file structure follows the standard GNU layout:
This file must be included in all distributions of the plugin to comply with GPL section 1 requirements.
Sources: LICENSE1-280
Users of the BuddyPress VIP Go plugin have the following rights:
Organizations deploying the plugin on WordPress VIP:
Developers who modify or extend the plugin:
Organizations or platforms redistributing the plugin:
Sources: LICENSE1-280 composer.json4
The "or-later" suffix in GPL-2.0-or-later provides flexibility:
Users may choose to apply GPL-2.0 terms or any later version published by the Free Software Foundation. The current GPL version is 3.0, which includes additional provisions for:
Most WordPress plugins use GPL-2.0-or-later for maximum compatibility with WordPress core.
Sources: composer.json4 LICENSE237-248
| Aspect | Details |
|---|---|
| License | GPL-2.0-or-later |
| License File | LICENSE1-280 |
| Declaration | composer.json4 |
| Copyright | Human Made, Automattic |
| Freedoms | Use, study, share, modify |
| Requirements | Copyleft, source distribution |
| Warranty | None (AS IS) |
| Ecosystem | WordPress-compatible |
| Development | GPL-compatible dependencies |
The GPL-2.0-or-later license ensures the BuddyPress VIP Go plugin remains free and open source software, compatible with the WordPress ecosystem, while allowing flexible version selection for downstream users.
Sources: composer.json1-68 LICENSE1-280
Refresh this wiki