Meeting notes for 2018 March 13

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.


Getting ready for Gutenberg

You may be already aware of Gutenberg editor which is under rapid development and targeting to be merged in WordPress 5.0. The concept “get ready to make your words, pictures, and layout look as good on screen as they do in your imagination, without any code” has been represented with Gutenberg. It has simplified to unlock the power of WordPress without being pro on coding.

Gutenberg is going to be available on core, exact date is not fixed yet. It provides the ability to create own custom blocks for theme and plugin developers and also works great on mobile if you need a quick edit on your phone.

The Gutenberg editor uses blocks to create all types of content, substituting a half-dozen inconsistent ways of customizing WordPress, bringing it in line with modern coding standards and aligning with open web initiatives. These custom blocks change how users, developers, and hosts interact with WordPress for building rich web content easier and more intuitive, democratizing publishing and work for everyone, regardless of technical ability.

Theme review team needs to make a decision about custom blocks that we should allow it or not on the theme? Before the Gutenberg merges into core, Theme Review Team need concrete decision regarding the custom blocks.

So please provide your views and suggestions about the custom block that we should allow it or not in the theme. If you recommend us to allow such blocks, please send us your reasons behind it and share your precious suggestions to clarify your view. If allowed then what types of custom blocks are good to be allowed. Similarly, if you don’t like to allow this, share your views as well, so that we can decide what would be best among them. Feel free to give your views, so that we can make the better environment here in theme review for Gutenberg and custom blocks.

We’re looking forward to hear from you!

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.


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:
  • Preventing users removing footer copyright messages
    • Authors should not make it excessively difficult for users to remove footer messages.
    • Please see comment:
  • 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

X-post: Dealing with Angry Users – Workshop on March 16, 2018

X-comment from Comment on Dealing with Angry Users – Workshop on March 16, 2018