Recently, a WordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. organizing team raised a question to Community Deputies Community Program Supporters (formerly Deputies) are a team of people worldwide who review WordCamp and Meetup applications, interview lead organizers, and keep things moving at WordCamp Central. Find more about program supporters in our Program Supporter Handbook. about a potential sponsor’s product, a WordPress derivative, being promoted in competition with WordPress and putting WordPress in an unflattering light. This question naturally prompted some discussion around where our expectations could be clarified to address WordPress derivatives and how they are promoted by sponsors, speakers, and organizers.
A WordPress derivative can be defined as any software that is built on top of WordPress – this primarily consists of plugins, themes and distributions.
The Community Team asks that everyone associated with a WordCamp in an official capacity — organizer, speaker, sponsor, or volunteer — uphold the principles of the WordPress open source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. project, including the GPL GPL is an acronym for GNU Public License. It is the standard license WordPress uses for Open Source licensing https://wordpress.org/about/license/. The GPL is a ‘copyleft’ license https://www.gnu.org/licenses/copyleft.en.html. This means that derivative work can only be distributed under the same license terms. This is in distinction to permissive free software licenses, of which the BSD license and the MIT License are widely used examples.. This helps protect users/attendees, who might not realize that by using a non-GPL plugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party or theme, they are giving away the rights that WordPress provides them.
Additionally it is important to ensure that this community remains safe, inclusive and welcoming. To ensure that these values are reflected in WordPress events, the WordPress Community team has long stood by the following expectations for individuals and companies who want to be a part of the WordPress events program as found in the WordCamp Organizer Handbook:
- No discrimination on the basis of economic or social status, race, color, ethnic origin, national origin, creed, religion, political belief, sex, sexual orientation, marital status, age, or disability.
- No incitement to violence or promotion of hate
- No spammers
- No jerks
- Respect the WordPress trademark.
- Don’t promote companies or people that violate the trademark or distribute WordPress derivative works which aren’t 100% GPL compatible.
This brings us to our two questions!
In the comments, please share your thoughts on the following questions to help make decisions on how to move forward on this topic.
Should the WordCamp and meetup Meetup groups are locally-organized groups that get together for face-to-face events on a regular basis (commonly once a month). Learn more about Meetups in our Meetup Organizer Handbook. programs accept sponsors, speakers and organizers who engage in competitive marketing against WordPress?
How should competitive advertising be defined in the WordPress space?
This discussion will remain open and ongoing until April 29, 2021. At that time we will close comments and summarize the discussion for final review.
Thank you to @sippis @angelasjin @andreamiddleton and @hlashbrooke for their contributions to this post