Meeting Notes for Tuesday 15th October 2019

A meeting was held with the proposed agenda.

The following is the recap of the meeting, you can read the meeting transcript in the slack archives (a Slack account is required).


In the past seven days:

  • 238 tickets were opened
  • 233 tickets were closed:
    • 208 tickets were made live
      • 3 new Themes were made live
      • 205 Theme updates were made live
      • 0 more were approved but are waiting to be made live
    • 15 tickets were not-approved
    • 0 tickets were closed-newer-version-uploaded

Handbook update regarding child themes

The current handbook is not presenting the recommended practices of how a child themeChild theme A Child Theme is a customized theme based upon a Parent Theme. It’s considered best practice to create a child theme if you want to modify the CSS of your theme. should handle loading the styles and overwriting the parent theme styles.

The argument is that child themes shouldn’t have to load the parent stylesheet using enqueue.
The handbook should explain the loading order and the non.overriding the stylesheet handle.

The proposal is to open up a google doc and make a draft of what would go to the handbook, this could then be discussed and added to the handbook.

Next review shindig planning

The last shindig had a low turnout, and there is a problem of having only one person doing it in one time zone. There was not much involvement from the community.

For now, we won’t continue with the monthly shindigs, unless people show more interest in it.

Featured page issue – proposals for solving it

During the last triage, there was a discussion regarding this ticket.
One proposal was to have a curated list of the themes featured for a certain amount of time.

A number of issues were discussed:

  • What are the criteria based on which the themes will be chosen?
  • How often will the themes be on the popular page?
  • Who will choose the themes?

We’ll need to come up with the rules regarding the featured themes (minimal upsell, unique design, good coding practices).

The TRT representatives will try to see if they can get an initial proposal regarding the featured page, the post will be made on the make page and we can continue discussing the details there, and finalize the discussion on the next meeting.

Other news

Next triage will be held on Wednesday October 23rd, 17:00 UTC

#meeting, #meeting-notes, #trt

Theme Review Team Meeting Agenda for October 15, 2019

Theme review team (TRT) conducts a meeting on the second and fourth Tuesday of the month. Along with the fixed agendas, we have open floor meeting at the end where you can ask or share anything related to themes.

We encourage all members and anyone interested to attend.

Channel: #themereview | Time: Tuesday, 15th October 2019, 17:00 UTC

Meeting Agenda

  1. Weekly Updates
  2. Handbook update regarding child themes (link to issue)
  3. Next review shindig planning
  4. Featured page issue – proposals for solving it
  5. Open floor

Meetings usually last around 60 minutes.

The discussion about the meeting agenda can be held in the comments below. You are encouraged to propose the topic for the agenda.

#meeting, #trt

X-post: WP 5.3: Introducing the spread operator

X-comment from Comment on WP 5.3: Introducing the spread operator

X-post: Calling all testing plugins

X-comment from Comment on Calling all testing plugins

Review weekend summary

We held our first review weekend after a long time. Here are some statistics from the event:

  • 0 new themes were set live.
  • 0 new themes were approved.
  • 8 themes from the approved but not live queue were reviewed and reopened.
  • 1 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). ( ready review was started.
  • 7 themes were closed as not approved (this included duplicates).

Several themes in the new queue were reviewed and are now awaiting updates from the theme author.

We did not have a zoom meeting because there was no interest at the time.

The team reps also did some general administration and maintenance of the themes TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub. and the blog. We continued the work on the Theme SnifferTheme Sniffer Theme Sniffer is a plugin utilizing custom sniffs for PHP_CodeSniffer that statically analyzes your theme and ensures that it adheres to WordPress coding conventions, as well as checking your code against PHP version compatibility. The plugin is available from the plugin directory and Github. Themes are not required to pass the Theme Sniffer scan without warnings or errors to be included in the theme directory. and the color control package.

The next shindig is planned for November 2.

We hope that we will be able to announce details of the next event ahead of time and that it will raise more interest.

If you would like to host a discussion, Q&A or group chat to introduce new reviewers, or if you have suggestions for topics, do let us know in the comments.

#report, #review-weekend