Theme review team weekly notes The logs are…

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

Theme review team weekly notes

The logs are here:
https://wordpress.slack.com/archives/themereview/p1425405735000714

We talked about queues.
We are going to post two tickets to 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.. One will be to ask for amendments to the assignment button workflow to include for existing reviewers tickets unresponded to for 7 days. We are also going to look at getting a clean up script that closes tickets where an author hasn’t responded for 7 days.

We also talked about images and licenses.
With regards to model releases, for now we are going to not consider this as our review and go by the licence provided. So business as it was.

Ulrich 10:20 pm on March 3, 2015

I hate to be the nay sayer now but this is not the best solution. It is not right for a ticket to have to wait 7 days for no activity so to be reassigned. We want people to communicate with each other. When anyone comments in the ticket or mentions the ticket in 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/. then the modified date gets updated. I do not see the difference to this system to the tickets being set to “new” so that it gets re-added to the assignment button workflow.

Sorry for not mentioning it in the Slack discussion. It was not clear for me it the discussion.

I fear that it will not be so easy to find out when the author has not replied in 7 days. It is not that important.
- Tammie 12:38 pm on March 6, 2015
  
  We have to have a time period. You can’t expect everyone to be participating in daily conversations. The difference is that tickets don’t sit without anyone assigned to them. Marking as new does that, which isn’t good.
  
  As I said in the meeting, I personally am not keen on anything that reassigns like this from a psychological view. This however, is a better way than simply flagging back to new.
Jasmine Jazz 2:37 am on March 5, 2015

Hi I don’t know a lot but do need someone to look at my theme and help me out please.