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 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

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

Meeting notes for 2017 November 28

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

Items discussed:

  • Seasonal Themes: Seasonal/holiday themes are now given priority in the queue. Theme authors are still allowed to submit seasonal themes even if his/her another theme is in the queue.
  • Report button for themes: Possibility for implementation of report button was discussed. Since plugin team has already shelved the reporting system for plugins due to complexity, it would be difficult to implement reporting system for themes in near future.
  • Onboarding library: Onboarding script integrated in themes could be very useful for users for theme setup. Current hot library MerlinWP was mentioned. Everyone is encouraged to try and review the library and check if it is compatible with TRT guidelines.
  • Accessibility review: Currently we have very few Accessibility reviewers. To ease the Accessibility review for new reviewers @poena has published a blog post Getting ready to do accessibility reviews.

#meeting-notes