Meeting notes for 2018 March 13

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

Meeting [ link ]. A Slack account is needed to view the archives.

Items discussed:

Reducing rules to “essential”: There was intense discussion regarding the change in guidelines. Proposal was to reduce list to 3 essential points: licensing; security and egregious issues. Even though several attendees gave input regarding the agenda, no decision has been made.
For:
- This would reduce queue time drastically.
- This would move some burden from reviewer to theme author.
- If theme does something wrong, author will be affected by user’s rating, so author would be more careful.
- At we can run an experiment, for say 1 months and see how it goes
Against:
- This would let pass themes with some currently critical issues like content creation, prefixing, translation ready, etc.
- It is hard to trust theme authors as we have seen several examples with breaking of trust.
- If theme passes with issues and later asked to be fixed by reviewer then user will suffer.
- Even if we run this experiment for some period, we should first set some target and parameters to check after the experiment to decide whether continue or revert this change.

#meeting-notes

kafleg 4:21 am on March 22, 2018

Reviewing theme is essential for maintaining the quality of themes on .org. We always worried about reducing the queue but we need to think about how we can encourage new authors to submit themes in .org and motivate them to review theme as well.
Moreover, it is really hard to trust authors having themes in .org, so I am okay with the review process. Only one challenge of TRT is to get more theme authors, trusted authors and more quality reviews.
It’s okay that we can make varieties of the decision to reduce the queue but we can’t consider quality, security, translation, licensing etc.

Welcome to the Themes team!

Handbooks and review requirements

Coding standards and plugins

Code Packages

Communication

Share this: