Changes in Theme Review Process

We all know that queue time is around 3 months. We have quite a small numbers of active theme reviewers at the moment, and even when a ticket is being reviewed, the review process itself can take pretty long to complete.

The change is based on moving burden from reviewer’s shoulder to theme author’s and making theme authors more responsible. From today, reviewers can check mainly following issues to pass the review.

  • Security
  • Licensing
  • Malicious or egregious stuff
  • Content Creation

Although these are the points to pass the theme review, theme authors are expected to follow the guidelines (required and recommended) like how it is going currently.

Moderators will spot check the themes after it is set live. If theme authors are found intentionally not following the guideline, Moderators will ask theme authors to fix the critical issues. In the case of not abiding the guidelines, theme could be on temporary or permanent suspension.

#themereview

Agenda for 2018 March 27

The Theme Review Team holds a fortnightly meeting and we encourage all members to attend.

Channel: #themereview | Time: Tuesday, March 27, 2018 at 17:00 UTC 17:00 UTC

The following will be discussed during the meeting:

  • 100% GPL themes (Clarification on licensing)
  • Giving Theme Reviewer badge automatically rather than waiting for 6 months.
  • Method for selection for new Leads

The meetings typically last 30 minutes, however may last up to 60 minutes. If time permits, additional topics may be discussed.

If you would like to discuss additional topics to those mentioned above, then please reply to this post and include the topic, along with a brief description of what you would like to discuss.

#agenda

Agenda for 2018 February 27

The Theme Review Team holds a fortnightly meeting and we encourage all members to attend.

Channel: #themereview | Time: Tuesday, February 27, 2018 at 17:00 UTC 17:00 UTC

The following will be discussed during the meeting:

  • Goal and plan for 2018.
  • Project status. Current ongoing projects can be found here.

The meetings typically last 30 minutes, however may last up to 60 minutes. If time permits, additional topics may be discussed.

If you would like to discuss additional topics to those mentioned above, then please reply to this post and include the topic, along with a brief description of what you would like to discuss.

#agenda

Meeting notes for 2018 February 13

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

Items discussed:

  • Update for child handbook page
    • Forum team are planning to update the child themes page in the handbook.
    • Those interested in helping can leave comments in a gdoc here: https://docs.google.com/document/d/1-DO9kAWigalNvV2eFsoCVliGeQ4bzkvAgHUmCj2_GaY/edit.
  • Preventing users removing footer copyright messages
    • Authors should not make it excessively difficult for users to remove footer messages.
    • Please see comment: https://wordpress.slack.com/archives/C02RP4Y3K/p1517936627000097
  • Admin pointers
    • Use of admin pointers was originally disallowed as it was expected that stable Admin Pointer API would be in core.
    • As there’s no clear indication of whether this feature will soon be in core, we discussed allowing the use of admin pointers in themes.
    • The main objections to allowing these was their use in upselling, and also excessive use therefore cluttering the admin area.
    • Discussed allowing the use of admin pointers, initially with no rules. A vote during the meeting showed 10 in favour of this, and 1 against. Vote results.
    • Additional guidelines governing the use of admin pointers would be made at a later date once authors begin adopting this feature.
    • Team leads have decided to allow admin pointers. The situation will be monitored and new rules added in future if needed.
  • Gutenberg
    • A separate post will soon be published to allow everyone to share their opinions.
    • This will give an opportunity for other teams and the wider WP theme dev community to also share in the conversation.
    • The topic will be discussed at a later meeting.
  • Dealing with theme breaking guidelines
    • Themes that violate the most serious guidelines (e.g. security) are subject to suspension. This has always been the case.
    • If a theme is breaking the guidelines, first comment in-ticket requesting the author address the issues quickly.
    • If an author fails, or refuses, to fix issues in a timely manner they may be warned to fix issues within 7 days or the theme may be suspended.

#meeting-notes, #themereview

Agenda for 2017 December 19

This meeting will focus on the recent discussions regarding custom blocks in themes.

This topic has been discussed in the #core-editor and #themereview channels on Slack. Those interested in attending the meeting may want to read up on the chat history so far [ link ], [ link ].

  • Content creation in blocks, -a quick recap of how blocks work and what happens when you switch themes.
  • What type of blocks are suitable in themes?
  • What type of blocks should be plugin only?

Preparing for changes:

  • Possible changes to guidelines and tags.
    • Addition of a custom-block tag?
  • Example code on TRT github