Team meeting: queues

Welcome to the Themes team!

We are a group of volunteers who review and approve themes submitted to be included in the official WordPress Theme directory.

We do license, security, and code quality reviews.

We help build and maintain default themes.

The primary focus of the team is to help theme authors transition to blockBlock Block 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.-based themes.

If this sounds interesting, read more about the team here. Check out our guide for new reviewers and the frequently asked questions.

Handbooks and review requirements

The team maintains the official Theme Review Requirements, the Theme Unit Test Data, and helps the documentation team with the Theme Developer Handbook.

Coding standards and plugins

We maintain the WPThemeReview Standard for PHP_CodeSniffer, the Theme Sniffer plugin and Theme Check

Code Packages

We have code packages for themes available for use on Github and Packagist

Communication

Meet us in the #themereview SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel.

Meetings:

Twice monthly at Tuesday @ 15:00 UTC.

#themereview

Note: These are all in note form from the team meetings that took place over 2 days after the WordPress summit. When words like everyone and we are used, they are done for the group that was there. This was a cross section of the people who review and work on this project.

This meeting’s objective was to discuss the queues.

Discussion:
Should we remove numbering?
Child themes are different case.
We need a better workflow.
Maybe looking at the way coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. tag first patch is good.
GPLGPL 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. compatible tag? Maybe this works better with lack of resources.
Maybe low hanging tasks like checking GPL and screenshots are a good entry point for reviewers. We joked about having a GPL police force.
It’s not clear anyone can comment on any ticket.
Time it takes to review a theme is a problem. Process is too long.
Why does a review take so long?
Theme reviews take time:

code review
frameworks
time that it takes to review is elastic

Should we be reaching out and educating about better themes.
Who are we when we contact people?

Actions:

Outreach program can also be used to stop the code coming in the first place.
We should be spreading the word about theme review process. Locally and making sure that the word gets out.

Welcome to the Themes team!

Handbooks and review requirements

Coding standards and plugins

Code Packages

Communication

Share this: