Themes Team Meeting Notes – April 13, 2021

You can find the full meeting transcript on Slack (login required)

Meeting coordinator: @kafleg
Notes kept by @kafleg

Weekly updates

Currently 46 new parent themes and 10 new child themes are waiting for review.
The waiting time is 3 weeks.

In the past 7 days,

  • 401 tickets were opened.
  • 417 tickets were closed.
  • 389 tickets were made live.
  • 23 new Themes were made live.
  • 366 Theme updates were made live.
  • 1 more were approved but are waiting to be made live.
  • 27 tickets were not-approved.
  • 1 tickets were closed-newer-version-uploaded.

Number of reviewers: 5

You can find more information here.

Changing the name of Theme Unit Test

There were some suggestions in GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. for the possible name of Theme Unit Test. Among them, Theme Test Data was simplest and most reasonable suggestion by @kjellr. We finalized the name from the meeting. Now, Theme Unit Test will be Theme Test Data.

Project updates

Currently, there are 4 projects running,

  • Security testing tools for themes
  • Theme review action
  • Theme unit test
  • Requirements page review

We would like to request respected projects leads to provide the updates about the work. We were not able to take the updates during the meeting because none of the leads were present.

@kafleg is working on the requirements page review and he will consult with the themes team reps and try to reduce the requirements list.

Open Floor

During open floor, @joyously raised a question about using pre_get_posts in theme. She said, this seems to me to be pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the Plugin Directory or can be cost-based plugin from a third-party functionality. 

@kafleg replied, In most of the cases themes use pre_get_posts to exclude the categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. IDs in blog post. That might be the reason that you get 905 matches.

@greenshady said, Theme authors should mostly avoid pre_get_posts because most of the time this should be done via plugin. However, there are exceptions to this.  For example, a theme author might want to pull all the sticky posts into a slider at the top of the home/blog page.  And, because they wouldn’t want duplicate posts, it makes sense to hook into pre_get_posts to remove them from the main query.

You can read the entire conversation here.

At last, thank you all for your active participation in the meeting.

#meeting-notes, #themes-team