Meeting notes Tuesday 7th of July 2020

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

Weekly Updates

In the past seven days:

  • 257 tickets were opened
  • 275 tickets were closed:
  • 254 tickets were made live.
  • 20 new Themes were made live.
  • 234 Theme updates were made live.
  • 2 more were approved but are waiting to be made live.
  • 21 tickets were not-approved.
  • 0 tickets were closed-newer-version-uploaded.

The current waiting time for new themes is 4 weeks. 73 themes are in the new queue.

Using reusable blocks to ease the transition to 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

@aristath Has written a post about using reusable blocks outside the content.

Reusable blocks can be used as a stepping stone for themes that want to make use of the block editor for headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes./footer/sidebars etc. before FSE is officially released.

It was suggested during the chat that theme authors should try full site editing instead of a temporary solution. Full site editing is not stable enough to be used in production, but reusable blocks are stable and can be used with existing themes.

Theme uploads that are blocked by Theme Check because of their images

Older themes with images from Unsplash and Pixabay, where the images were added to the theme before the website’s license change, have been blocked by Theme Check when uploaded to the WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ theme directory.

The check in Theme Check does not only prevent the images but the use of the word Unsplash. Related: https://github.com/WordPress/theme-check/issues/259

It was decided that Theme Check will be updated to no longer block the images. This is a very small code change.

Allowing themes to place their admin page outside the appearance menu for increased visibility

This topic arose from a question about whether themes are allowed to add a panel with information to the block editor sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme./tools panel. This is not allowed.

To keep the editor free from clutter, advertising and upsell, with the customizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. being used less, and no dashboard widgets being allowed, can we give theme authors a better place to include their information, and limit upsell to that area?

If a top level menu item would be allowed, these restrictions were suggested:

  • No priority may be used.
  • No UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. or color changes are allowed for the menu item.
  • The title must be kept short and not include spam.
  • If a custom icon is used it must be a single color.
  • No more than 3 subpages.

A longer more heated discussion took place after the meeting, and the decision was postponed. A new post will be created on the teams make blog to discuss it further.

We want to remind everyone that the requirement for not adding any obtrusive upsell is still in place.

How do we best handle updates to themes that have not been updated in two years?

Updates to themes that had not been updated in two years used to “get stuck” because reviewers were not able to see that they did not go live automatically.

We now have these updates listed in their own queue on the themes TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. https://themes.trac.wordpress.org/report/1 And while the new queue is 4 weeks, this queue is 3 months.

  • There are not enough reviewers to cover all queues.
  • Theme authors may not be aware that their update is not going live automatically
  • Theme authors may not be aware of that old themes has to follow the current requirements.

It was suggested that these themes should be set live, and there was a short discussion about if it was safe to set them live. It is common for these themes to not follow the current requirements.

The discussions resulted in no changes being made to the queue. We need to remind theme reviewers to also review themes from this queue.

Update on the navigation block/navigation screen

The navigation block and navigation screen will not be ready in time for WordPress 5.5. Please help test these features.

There is a new meeting about navigation on Wednesdays at 07:00 UTC in the #core channel on the WordPress slackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..

@aristath Has created and written about a menu filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. that helps theme authors add markup and CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. classes used by the block to the current nav menu.

This will help theme authors use the same styling for their current navigation and the navigation block.

It was suggested during the navigation meeting that the Navigation block should output markup that is as identical as possible to existing menus.

Date and time of the next meeting

It was agreed that the next team meeting will be on Tuesday, August 4th, 2020 at 1700 UTC.

#themes-team

Themes Team Meeting Agenda for July 7

The themes team conducts a meeting on the second and fourth Tuesday of the month, and once per month during the summer and holiday periods.

Along with the fixed agendas, we have an open floor 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, July 7 2020, 17:00 UTC

Meeting Agenda

  1. Weekly Updates
  2. Using reusable blocks to ease the transition to 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
  3. Old themes with images that are not compatible with GPLGPL GPL is an acronym for GNU Public License. It is the standard license WordPress uses for Open Source licensing https://wordpress.org/about/license/. The GPL is a ‘copyleft’ license https://www.gnu.org/licenses/copyleft.en.html. This means that derivative work can only be distributed under the same license terms. This is in distinction to permissive free software licenses, of which the BSD license and the MIT License are widely used examples. due to license changes are blocked by Theme Check. What is the correct way to handle these images?
  4. How do we best handle updates to themes that has not been updated in two years?
  5. Date and time of the next meeting

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

Meetings usually last around 90 minutes.

Attend and share your valuable feedback and suggestions.

#agenda, #meeting, #themes-team

Meeting notes Tuesday 9 June 2020

Today we held a meeting with the proposed agenda. The recap of the meeting is below and you can read the meeting transcript in the slack archives (a Slack account is required).

Weekly Updates

In the past seven days

  • 251 tickets were opened
  • 250 tickets were closed:
  • 230 tickets were made live.
    • 15 new Themes were made live.
    • 215 Theme updates were made live.
    • 2 more was approved but are waiting to be made live.
  • 20 tickets were not-approved.
  • 0 ticket was closed-newer-version-uploaded.

We have managed to cut down on the queue length, which is always good news.

We thank to all the reviewers, keep doing a great job 🎉

Biweekly meeting schedule to Monthly meeting for Themes Team

Summer is closing in and we realised (and observed during the last few months) that having many meetings (regular, 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. themes and triages) can be a bit tiring – both to the reps and to the contributors.

The proposal is to cut the Themes Team regular meeting to once a month plus an additional one if we have some urgent thing to discuss.

This will give us a bit more breathing room both to recharge and focus on priorities set by phase three of the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. editor development that are tied to the WordPress themes.

Open Floor

An issue was raised about Themes team not being a team anymore due to the lack of public discussions.

It was mentioned that the decisions are made and just announced.

This one is definitely on us (the reps). We should have been more tactful of how we presented the news (like changing the name of the team).
Team reps are always discussing and finding ways to improve this team’s impact in the WordPress community.

It’s hard to get noticed without active contributors, and in the last few years we have seen a decline in the active participants. To many authors theme repository is just one of the advertising avenues, which is disheartening.

One of the ways we wanted to spark the interest is to be involved with the core editor more, show that we are doing more than just review themes.

We definitely need to improve our transparency towards the community as team representatives. Writing more blogs about what we think would be a good way forward, and listening to advice and discussing them in the comments and then in the meetings.
What we do want to avoid are empty discussions that lead nowhere, as this is what kills the team. We need to adapt, change, and even innovate.

Andrea Middleton shared her experience from working in the Community Team:

In my observation, leading in the open is really difficult, and the process of learning how to do it effectively isn’t necessarily linear.

I’ve messed it up bunches of times — I think humans are just really prone to forming small groups, it helps us feel safe — and when it’s pointed out to me, I usually feel really dispirited and embarrassed.

For me, the best way to recover from that realization of “whoops, this conversation could/should have happened in the public channel” is to then go to the public channel and summarize the conversation there.

Andrea Middleton

It was also suggested that we should come up with a mission statement draft. Some goals that we as a team want to achieve.

This year we have put focus on Full Site Editing. We will continue working on preparing the community for the upcoming changes in the themes ecosystem.

Proofread by @williampatton

#meeting, #meeting-notes, #themes-team

WCEU office hours and contributor day

Office hours 2nd of june

The Themes team office hours will be on Tuesday June 2 @ 17:00 UTC.

During the office hours, you are welcome to ask questions about the team and how you can contribute.

To join, you need a WordPress.org slack account. Our channel is called #themereview.

If you are not able to attend, team members are usually available on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. during EU hours. You can post your questions and we can get back to you when we are available.


Contributor dayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. 4th of june

We would love to hear what you would like to learn more about during the contributor day. -Our plans are flexible depending on what you would like to do.

We would like to start with a one hour introduction to theme reviewing, between 14:00-15:00 UTC and we will do that in two groups, using Zoom. You do not need to use a camera or a microphone to participate.

We will talk about why we do reviews, how we perform reviews, and perhaps do a quick theme review together.

After our break, we would like to focus on full site editing and 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. So, for this part, we will have to wing it :). The goal is to test, learn and to create a theme together that eventually can be added to the theme directory.
You can join even if you have never tried or looked in to full site editing before.

Team members and team representatives will also be available on slack during the afternoon.


What you will need

You will need a WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ account and a WordPress slack account.

You will also need a WordPress install that you can use for testing.


Where to find information for new contributors

You can read more about the Themes team here.

On this page, you can read about how to get started at a contributor day:

Here, you can learn about reviewing themes:

#themes-team