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

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

X-comment from +make.wordpress.org/support: Comment on Dealing with Angry Users – Workshop on March 16, 2018

Agenda for January 23, 2018

Channel: #themereview | Time: Tuesday January 23, 2018 1700UTC

Items to be discussed:

  • Update on review system [ link ]
  • Theme unit test [ link ]
  • PR review Theme Sniffer #79 [ link ]
  • Summary of review weekend, took place on 20th – 21st January.

#agenda

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

 

 

 

Meeting notes for 2017 December 12

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

Items discussed:

  • Christmas priority queue
    • Deadline for submitting seasonal themes is December 20th.
    • This gives a fair chance for all tickets to be reviewed prior to Christmas.
  • 1 theme / month limit
    • It was clarified that this limit applies to all themes submitted by an author.
      Seasonal themes are exempt from this rule.
  • No longer allow ticket swapping
    • Ticket swapping is no longer allowed.
    • Ticket swapping is where an author requests for a different theme to be reviewed instead of the theme that was picked up for review.
    • In these cases the original ticket was closed and the review continued in the new ticket.
  • Improving message to authors when a ticket is closed as not-approved
    • A template response can be found here: https://docs.google.com/document/d/1IoePkAt33eWDTsV8Xcp-gHM4_pgMnibSPizVP2MoffM/edit
  • Tide
    • We are continuing to monitor progress with Tide to get a better understanding of how it will impact the future review process.
    • It was proposed that we continue to maintain Theme Review plugin till the point we know how tide works.

#themereview