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

Updates

In the past seven days:

• 239 tickets were opened
• 238 tickets were closed:
  • 222 tickets were made live
    • 11 new Themes were made live
    • 211 Theme updates were made live
    • 10 more were approved but are waiting to be made live
  • 16 tickets were not-approved
  • 0 tickets were closed-newer-version-uploaded

Removing recommendations page

The current recommendations page in the review handbook had a lot of outdated data, so the team agreed that we should remove it and improve the resource page instead.

Should we separate code quality from license and upselling?

Currently there is no priority in what things should be checked first while doing a theme review.

On the requirements page, licensing and upsell is listed together with code requirements. This can cause confusion.

We want to point out the important issues first, so that issues like missing licenses, and upsell issues are found first and that this can be fixed quickly. Only after this precheck issues are fixed will the review continue.

This is done so that the reviewers don’t waste valuable time, and can review more tickets quickly. We hope this will improve on the queue length a bit.

Should Requirements that are checked with Theme Check remain listed on a separate page?

No decision was reached about this issue. For now the Theme Check page will be on a separate page.

Open floor

There was a suggestion to encourage building a stronger community between and with the theme authors.

A proposal was made to add a new meeting that would revolve the blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience.-based themes. As mentioned by @kjellr:

There’s already a lot of full-site editing work going on, and there are already experimental reference documents for block-based themes. It’s important for the TRT and the theme community to keep up to date on this work, and to develop a clear communication loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. with the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ teams.

A new meeting regarding block based themes will happen next Wednesday at 16:00 UTC.

Tonight we’ll have a triage meeting at 18:00 UTC, going through metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. tickets and other open-source issues.

#meeting, #meeting-notes, #trt