Meeting Agenda No topic up for discussion at…

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

Nilambar Sharma 4:43 am on November 24, 2015

It is great to see that abandoned tickets are getting some movement after they are brought to the New queue. But after that New queue is getting longer and longer. Can we do something to reduce it? How about pinging inactive reviewers for reviewing few tickets?
Currently reviewers cannot take tickets from New queue themselves. It needs to be manually assigned by admin. May be if ticket status is changed to `new` or `reopened`, reviewers can assign ticket themselves [This is just my idea].
Also queue push program could be done weekly for few weeks until queue is brought down to normal.
- Code Pixelz Market 11:18 am on November 24, 2015
  
  +1 to @Nilambar‘s suggestion of changing ticket status. As I wanted to clear themes from the queue but I had to ask on 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/. and you later assigned them to me. if I could take those myself, would have been faster and easier. 🙂
- Jose Castaneda 5:55 pm on November 24, 2015
  
  Yes, I was reached out by another that wanted to tackle that as well. I want to say it is a tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. thing, so if you want to try, create a metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. ticket for it. As far as I know, admins are not able to change the status of the ticket, just priority which isn’t what needs changing.
bkjproductions 5:00 pm on December 12, 2015

Here is an idea about theme updates, perhaps for discussion in this group?

I have noticed that when WP checks to see if a theme needs updating, it is looking mostly at the Version mentioned in the style.css and the Folder name of the theme. How much more difficult would it be to look at the theme NAME as well? Then if a theme name had been changed, but the folder name was the same, then either a) notify the user there is potentially a problem or b) just skip the update notification altogether.

For example, I recently picked up a client whose previous developer had named the theme folder “blossom”. The theme had been heavily customized, yet the theme folder name was unfortunately the same name as one in the WP theme repository… A month later or whatever, the client clicked on the “Update” button when seeing a notice that the theme needed to be updated, and BANG, suddenly everything went wonky. The theme NAME was clearly different than the theme in the WP Theme repository.

I think doing something like this wouldn’t be that hard, and would save a lot of grief for all concerned. I know, I know, people are supposed to use child themes, or rename folders, but not everyone is doing this!

Welcome to the Themes team!

Handbooks and review requirements

Coding standards and plugins

Code Packages

Communication

Share this: