Meeting notes We had a meeting today archive…

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 notes

We had a meeting today, archive here:
https://wordpress.slack.com/archives/themereview/p1430243960008321

AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) reviews

We talked about these and getting a training plan. @joedolson and @davidakennedy are going to be working on a doing_it_accessible_wrong theme and some screencasts. People will work through these and we can have a baseline then for them to pass before move onto tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/.. This should be done within 2 weeks. We plan to get the first batch of people trained up inside a month. They are going to report back in 2 weeks.

Changelogs

Having in readme.txt seems to make sense and is the consensus from the thread. @jcastaneda will be looking into how we start doing that and then report back next week on make.blog.

gsayed786 7:29 pm on April 29, 2015

Hi,
Need some help from you !
I had submitted my theme on wordpress for review ..however because of the natural disaster in nepal the reviewer cannot continue with the review and has asked me to contact admin to assign my theme to another person for review ..Can you help me how to contact admin regarding this .
Thanks
Ghafir
- Ulrich 6:32 am on April 30, 2015
  
  Hey Ghafir, I will try and find you a new reviewer. It might take some time.
Ulrich 12:50 pm on May 1, 2015
Can we discuss in the next meeting how we can reduce the number of tickets that need a new reviewer?

Here are some ideas to get use started.
- Add popup to confirm to review a theme. Related https://meta.trac.wordpress.org/ticket/960
- Improve the initial email when assigned a ticket with further information. Like what the requirements are and what the workflow is.
- Automatic reminders after 4 days. I believe some people forget that they have requested a theme to review.