You can find the full meeting transcript on Slack (login required)
Meeting coordinator: @kafleg
Notes kept by @aristath
Weekly updates
Currently 56 new parent themes and 15 new child themes are waiting for review. Waiting time is currently 2 weeks.
In the past 7 days:
- 310 tickets were opened
- 326 tickets were closed:
- 303 tickets were made live.
- 19 new Themes were made live.
- 284 Theme updates were made live.
- 2 more were approved but are waiting to be made live.
- 23 tickets were not-approved.
- 0 tickets were closed-newer-version-uploaded.
Number of reviewers: 8
Discussion on Next Steps on Themes and Reviews
How will we help new authors feel confident in how to build themes?
@williampatton suggested to hold monthly meetings with new authors, guiding them and walking them through the process. This will help build confidence for authors, and hopefully result in higher quality themes. A post will be created asking for feedback about whether such an endeavor should be pursued or not.
@acosmin pointed out that in the Next Steps on Themes and Reviews post, the outlined goal is that “The human moderation process occurs post-commit and primarily for reported issues/spot checks”, which should also help with creativity.
Automated checks on block-based (FSE) themes
automatic theme-checks will need to be modified for FSE themes. PHP can be checked with a modified subset of the current theme-checks, but HTML can’t be currently validated. The future of the repository as outlined in the next-steps post mentioned above relies more on user reports and reviews, so it’s more empowering for users and relies less on manual code reviews.
Open floor
@aristath mentioned a pull-request which was merged in Gutenberg. It’s a first step towards hybrid themes and allows using a mixture of PHP and HTML templates. Details about the implementation can be found in the pull-request’s description.