Dev-squad GitHubGitHubGitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ triage: Thursdays 07:00 UTC
Anyone can be a part of planning, scripting and creating tutorial videos on Learn WordPress. However, only people who embrace the WordPress trademark and licence can be presenters of the videos. To quote from the WordCamp speaker guidelines, the implication of this is:
They must embrace the WordPress license. This means that if they are distributing WordPress-derivative works (themes, plugins, WP distros), any person (or their business) should give their users the same freedoms that WordPress itself provides.
Note: this is one step above simple compliance, which requires PHPPHPPHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. http://php.net/manual/en/intro-whatis.php. code to be GPLGPLGPL 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./compatible but allows proprietary licenses for JavaScriptJavaScriptJavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/., CSSCSSCSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site., and images. 100% GPL or compatible is required in order to present a Learn WordPress video tutorial when WordPress-derivative works are involved – the same guidelines that are followed on WordPress.orgWordPress.orgThe community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/.
They must respect the WordPress trademarks. This means they do not operate websites with the word “WordPress” in a top-level domain, they do not use the logo in a way that violates the usage policy, they do not use the trademark in AdSense/AdWords, and they do not promote people/businesses/entities that do.
This post includes more information about why embracing the GPL is important in the WordPress project.
Also, at the bottom of this page, you’ll find a recording of an Online Workshop the Training Team titled “GPL in the WordPress Training Team’s Vetting Processes”. We explain GPL in detail, and demonstrate actually vetting an applicant.
Here are more details about how this will apply and play out on Learn WordPress:
Anyone contributing text-based content to Learn WordPress does not have to fulfil any GPL compliance requirements, this would apply to lesson plans and any other area that is text/image based.
Tutorial presenters (i.e. people who appear in videos whether on video or audio) must continue to be GPL compliant just like WordCampWordCampWordCamps 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. speakers need to be – presenters will be vetted at the time of their tutorial application just like WordCamp speakers are vetted.
Anyone contributing to tutorials who is not appearing in the video itself (i.e. helped to create the outline, script, slides, editing, or any other area) does not need to be GPL compliant.
Tutorial presenters will still be listed on the tutorial page with their name, avatarAvatarAn avatar is an image or illustration that specifically refers to a character that represents an online user. It’s usually a square box that appears next to the user’s name. and bio as they are now, while anyone contributing to the tutorial in any other capacity would be listed in a blockBlockBlock is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. titled “Other contributors” with their name that is linked to their WordPress.org profile, just like in the coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. release announcements.
All applications are sent to the Help Scout inbox and should be replied to using the Learn WordPress Help Scout– this ensures that emails come from the Training Team and can be replied to with any other individual with access to the inbox. If you need access to Help Scout please ask in the #training channel of the Make WordPress Slack. If this guide says you must email an applicant, then Help Scout is where you can do that.
Below are some processes to follow for this to help ensure that the presenter meets the eligibility criteria noted above.
Check the applicant’s WordPress.org profile: Look for activity in the support forums, any contributor badges, and how long the applicant has been a member. This will give you an indication of their experience with the WordPress community.
Check the applicant’s presence online: Look for how long they have worked with WordPress, what their knowledge of the tutorial topic appears to be, and if they have any trademark or GPL violations. Check all social media that you are able to access publicly including LinkedIn, MeetupMeetupAll local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area., Twitter, Facebook, Instagram, About.me, and personal blogs (you don’t need to send friend or connection requests – just look for what is available to you already). Especially be on the lookout for anything that indicates bigoted or discriminatory behaviour.
When recording this information, only use the notes section of the application and do not share any of it elsewhere. This is to ensure the privacy of applicants.
Check any background you can in Help Scout:
Look for unusual email conversations, lack of response, and anything else that might indicate that they could be unreliable (after taking timezone and availability details into consideration). Feel free to ask in the #training channel if there’s any history you should be aware of, but please respect the privacy of applicants and bear in mind that SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. is a public space.
In addition, check if they had previously applied for another Training Team role (e.g., Facilitator, Faculty, etc.) — if they have been vetted by the Training Team in the past year, you can refer to the previous vetting notes, which should save you some time!
Check if they have existing content on Learn WordPress: If they have existing content on Learn WordPress then there’s a good chance they have already been vetted in the past – have a look at their past tutorials to see if there are any vetting notes.
If you need more information from the presenter, then email them to ask for what you need (there is no saved reply for this), and tag the Help Scout ticket with more-info-requested.
If the application is declined, tag the Help Scout ticket with tutorial-declined, and send the appropriate saved reply (or customize your reply as necessary):
TUTORIAL: Declined (topic already exists)
TUTORIAL: Declined (topic already in planning)
or TUTORIAL: Declined (topic not relevant)
If the application passes the criteria,
Email them with the “TUTORIAL: Approved” saved reply.
TagTagTag is one of the pre-defined taxonomies in WordPress. Users can add tags to their WordPress posts along with categories. However, while a category may cover a broad range of topics, tags are smaller in scope and focused to specific topics. Think of them as keywords used for topics discussed in a particular post. the Help Scout ticket with tutorial-approved and update the status to “Pending”.
Add a note to the Help Scout ticket with your vetting notes.
Add the approved applicant to the Learn WordPress site as a Workshop Reviewer.
Spam applications typically include text that does not appropriately answer the given questions, lack a valid WordPress.org profile, and/or an invalid email address. When an application vetter comes across a spam application, we recommend tagging the message as spam and closing it out. Also, go to the Feedback page on the Learn WordPress site and mark the response as Spam. If the vetter is unsure of whether or not it is a spam application, don’t hesitate to reach out to a Training Team Representative or Faculty Member for guidance.
If you need any assistance with this process please ask in the #training channel on Slack.
Below is a recording of an Online Workshop the Training Team conducted in September 2023. The workshop will explain what GPL is in general, and how it applies to the vetting process for content creators in the Training Team. It is then followed by a live walkthrough of a Faculty Administrator vetting an application, giving a behind-the-scenes look at how GPL is applied in the team.