Meeting Notes for Tuesday 28th January 2020

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

Theme Review Team Meeting Agenda for January 28

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, 28th January 2020, 17:00 UTC

Meeting Agenda

  1. Weekly Updates
  2. Removing recommendations page
  3. Should we separate code quality from license and upselling?
  4. Should Requirements that are checked with Theme Check remain listed on a separate page? (Not all the required items will prevent a theme from being uploaded)
  5. Open floor

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

Meetings usually last around 60 minutes. Attend and share your valuable feedback and suggestions.

#agenda, #meeting, #trt

Meeting Notes for Tuesday 14th January 2020

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:

  • 289 tickets were opened
  • 287 tickets were closed:
    • 267 tickets were made live
      • 7 new Themes were made live
      • 260 Theme updates were made live
      • 14 more were approved but are waiting to be made live
    • 17 tickets were not-approved
    • 3 tickets were closed-newer-version-uploaded

How to gain new reviewers and keep the experienced ones

Theme Review Team discussed the issue of the lack of reviewers in general. New reviewers often leave because they have no supervision and have no feedback on whether their review was good. The feedback often comes in the admin review, and by that time reviewers lose interest in doing any reviews.

Incentives usually don’t work (as was demonstrated by the trusted author programme).

One idea was to close the reviews to the public. This would lessen the pressure on the reviewer from any negative feedback from the author. But would be hard to accomplish from the technical side.

Another pain point is the number of requirements that have grown over time.

The second idea was to focus our efforts on improving our automation tools as much as possible. For that to happen we would need to get more code-savvy contributors.

The issue that team reps are battling with at the moment is handling authors that try to game the system with multiple accounts.

@aristath proposed a possible system we could impose

  • 1 theme limit – just like now.
  • If an author successfully completes a review, they get the ability to upload an extra theme.

What constitutes a “successful” review:

  • If on the final review we find more than 3 issues that were not covered by the initial review, then it’s a fail.
  • If they do 5 rushed/incomplete/bad reviews, they lose the ability to participate for 3 months in the multi-themes thing.

First, they do a good review, then after the theme goes live and we’re satisfied it was an OK review, they get the ability to upload a 2nd one. If we catch them with multi-accounts after that is in effect, we’d suspend the author for 6 months.

The idea is to try to make authors see what the issues are and in that way educate them to write better code.

We’d also need a way to track the success of such implementation. The team reps will discuss how an implementation of this would look like in more detail and post the plan on the make blog.

Focus areas for 2020

The key focus area the TRT will have to focus on is the full site editing with the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. editor (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/).

Changes are already happening and we need to educate and prepare theme authors and theme reviewers for the upcoming changes to the way the theme role will be in the future of WordPress.

One thing is clear: if we want to have any impact, we (the TRT) need to participate actively in the development of Gutenberg.
Participation and contribution don’t necessarily have to be code additions. It can be testing out the new features and providing valuable feedback to the core editor team. This will steer the editor in the way that is favorable to both end-users and theme authors.

An option that we can consider is to try to allow experimental themes to the repository in order to get more valuable feedback.

If you want to contribute, the best way is to discuss and get involved with the Gutenberg tickets labeled [Feature] Full Site Editing.

Other than that you can explore the experimental themes, play with them and offer your insight by opening issues in the repo.

Every contribution, no matter how small, is beneficial.

Other news (open floor)

There is a proposal to start having regular polls so that we can see the public opinion on certain theme review related issues.

We will look into it and we’ll try to get some help into formulating interesting and valuable poll questions.

#meeting, #meeting-notes, #trt

Theme Review Team Meeting Agenda for January 14

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, 14th January 2020, 18:00 UTC

Meeting Agenda

  1. Weekly Updates
  2. Discussion about the issue of low review turnout – how to gain new reviewers and keep the experienced ones
  3. Focus areas for 2020
  4. Open floor

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

Meetings usually last around 60 minutes. Attend and share your valuable feedback and suggestions.

#agenda, #meeting, #trt

Theme Review Team Meeting Agenda for December 10

First, apologies for not posting meeting notes for November 26.

In case anyone missed it, we also had an extra meeting on December 4.

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, 10th December 2019, 17:00 UTC

Meeting Agenda

  1. Weekly Updates
    • Featured themes- no news to report.
    • Theme Review Team Badges -no news to report.
    • Suspensions -There is still a large backlog of reports.
  2. Fonts: Privacy related to google fonts, and enqueuing variable fonts.
  3. Recap of the future of themes meeting. Status report on our two current tasks regarding 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. editor:
    • Get a list of things that are in discussion and relates to themes
    • Get a list of blocks that are missing for themes
  4. Do not contact reviewers outside official channels

#meeting, #trt