Performance team meeting summary – November, 30 2021

This is the agenda for the meeting. You can read the logs here on Slack.

Focus groups updates

Images

@adamsilverstein gave a great update on the progress of the focus. First, all issues and ideas related to focus will be tracked in this GitHub project. This will facilitate asynchronous contributions and discussions. The top priority issue on the project is this one, for creating a WebP module, and port the code to the repository.

On top of that, the focus meeting last Thursday was a success and the team is planning to hold a next one. Keep an eye on the Make/CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. blogblog (versus network, site) and the #core-media channel 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/. to keep up with the agenda.

There were also several discussions about the main projects of the focus: WebP by default in WordPress Core and the migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. of existing images into the WebP format. Here are the links to the discussion pieces on Slack:

JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/.

Since most of the people in this focus are deeply involved in the next release, there are no major updates at the moment.

Measurement

For this focus, there were some discussions about starting a dedicated side conversation (see thread). Currently, the team is still thinking about the best form for this conversation, chat or video call. If you have any opinions, feel free to leave a comment in the thread linked above or on this post.

Performance features development coordination

There is currently this issue on the GitHubGitHub GitHub is a website that offers online implementation of git repositories that can 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. https://github.com/ repository regarding the code infrastructure of the performance modules. This step is very important to move forward, so feel free to leave a comment or feedback on the issue.

Open Floor

Jérôme Vieilledent (@lolautruche on Slack) mentioned before the meeting that Blackfire and Platform.sh are willing to support the WordPress Performance team initiative. Blackfire might be interested in donating an account 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/ organization for the team’s purposes. See Slack discussion here.

#meeting, #performance, #performance-chat, #summary

Performance Chat Agenda: November 30, 2021

Here is the agenda for this week’s performance team meeting to occur on November 30, 2021, at 16:00 UTC.

This meeting happens in the #performance channel. To join the meeting, you’ll need an account on the Making WordPress Slack.

#agenda, #meeting, #performance, #performance-chat

Performance team meeting summary – November, 23 2021

This is the agenda for the meeting. You can read the logs here on Slack.

Focus group projects discussion

Image focus

@adamsilverstein shared an update for the Image focus. The group plans to go through the ideas in this document to discuss the impact, level of difficulty, etc. and generally prioritize our work. Also, in addition to taking some time during the regular media meeting, the group members are proposing a regular second “performance image focus” meeting in a friendly timezone to APEC contributors. The first try for that meeting will be November 25, 2021, at 02:00 UTC.

JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. focus

The JavaScript focus update was shared by @gziolo. The team is still collecting ideas for issues to work on in this document. They also discussed during the last week during #core-js office hours how to bring ES Modules and Import Maps to WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. The next office hour, focused on issues prioritization is planned on next Tuesday.

Object caching focus

@spacedmonkey put together a list of related tickets he is willing to work on.

Measurement focus

@wp-source stated that the team has some interesting projects ideas. Now, there is a need for some short and regular sync chat for the focus group members to discuss this project. If you are interested in attending one of these chats, please share your interest in this thread on Slack.

Performance features development coordination

@flixos90 shared some insights about the coordination repository proposal. Here are the main outcomes of these:

  • WordPress has historically relied on feature plugins to test future WordPress core features “in the wild”. The proposal here is to follow that approach, however by creating modules in a single “performance features wrapper 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 WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party”.
  • By centralizing these efforts in 1 plugin instead of x plugins, the hope is to significantly reduce maintenance, encourage cross-collaboration between different performance efforts, and have a centralized place for any performance-related conversations.
  • For example, a central GitHubGitHub GitHub is a website that offers online implementation of git repositories that can 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. https://github.com/ repository could be used to open issues with new performance enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. ideas, discuss them etc, even if they don’t right away lead to a new performance module.
  • A single wrapper plugin also can help from an adoption perspective, essentially interested users can install the plugin once and then will get access to any new performance features as soon as they are added – they can then enable whatever they are interested in to try out.

There have been several discussions about where this repository should be created. The main locations being the Gutenberg repository, and under the GitHub WordPress organization.

After a vote, the repository has been created under the GitHub WordPress organization, and you can find it here.

#meeting, #performance, #performance-chat, #summary

Performance Chat Agenda: November 23, 2021

Here is the agenda for this week’s performance team meeting to occur on November 23 2021, at 16:00 UTC.

  • Focus group projects discussion
  • Performance features development coordination: we will discuss the proposal to centralize and coordinate the development of performance features in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. (see proposal document here).
  • Open floor

This meeting happens in the #performance channel. To join the meeting, you’ll need an account on the Making WordPress Slack.

#agenda, #meeting, #performance, #performance-chat

Performance team meeting summary – November, 16 2021

This is the agenda for the meeting. You can read the logs here on Slack.

Focus group projects discussion

@audrasjb made an update about the progress for the Site Health group. Here’s the document with details about two projects for the focus group. The next step for this group is to use the next Site Health meeting time slot (November 22, 2021, at 16:00 UTC) to discuss these 2 projects.

@adamsilverstein shared that the Images focus group has a long list of ideas. The next task for this group would be to describe these ideas based on the template; listing their impact, complexity etc. and then based on that prioritizing the work of the group.

Should the performance team have its own Make blogblog (versus network, site)?

@spacedmonkey raised this question about having a Make blog for the Performance team.

@flixos90 mentioned that performance encompasses all areas of WordPress. And that having a dedicated performance blog is likely less impactful than posting in the area(s) where a certain topic mostly applies to – a dedicated performance blog may end up in some sort of silo, where only people who are into it anyway become aware of it.

Weekly meeting time

The team has voted to move the meeting time one hour later, at 4:00 PM UTC. The new meeting times are also updated here.

Object caching focus group

The object caching focus now has 7 contributor votes on the focus groups spreadsheet. With so many interested contributors, it is relevant to make it a focus group. @tillkruess and @dustinrue will be the POCs for this focus group.

#meeting, #performance, #performance-chat, #summary

Performance Chat Agenda: November 16, 2021

Here is the agenda for this week’s performance team meeting to occur on November 16 2021, at 15:00 UTC.

Focus group projects discussion

Over the current meeting and the next one (November 23), we will allocate 30 minutes for each focus group to share and discuss their plans with the overall performance team.

Weekly meeting time

Currently, our weekly meetings are held at the same time as the JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. and Themes team meetings. With several interested people unable to attend.

One option would be to hold our meetings an hour later, so at 4:00 PM UTC. What do you think about this?

This meeting happens in the #performance channel. To join the meeting, you’ll need an account on the Making WordPress Slack.

#agenda, #meeting, #performance, #performance-chat

Performance team meeting summary – November, 9 2021

@justinahinon led the meeting on this agenda. You can also read the Slack logs.

Updates about focus groups POCs (point of contacts)

@aristath and @gziolo are the POCs for the JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. focus group, with the support of @sergiomdgomes.

@josephscott and @wp-source are the Measurement focus group POCs.

@adamsilverstein and @audrasjb are the POCs for respectively the Images and Site Health focus groups.

Logistics, operations and projects prioritization for the focus groups

@flixos90 raised that we need to figure out the project priorities for each focus group. This document template has been prepared with some pointers on items to think about when writing down the focus group priorities. It also considers the others aspects of the projects as the technical complexity, the impact, the potential blockers, the timeline, etc.

Using a document makes asynchronous communications easier, and ad-hoc conversations can take place in the #performance channel 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/.. The POC of each focus group can now create a copy of the template and share it in the channel to allow other contributors to collaborate.

Open floor

Read the open floor log here on Slack.

#meeting-notes, #performance, #performance-chat, #summary

Performance Chat Agenda: November 9, 2021

Here is the agenda for this week’s performance team meeting to occur on November 9 2021, at 15:00 UTC

Agenda

  • Defining the logistics for each group (tracking, POCs etc.)
  • Focus group projects and prioritization
  • Next steps for the team and the focus groups
  • Open Floor

Defining the logistics for each group (tracking, POCs etc.)

In order for the focus groups to function properly, we need to define how they will operate. Some ideas have already been put forward and will be shared at the meeting. Please feel free to come and share yours as well.

Focus group projects and prioritization

For each of the focus groups, there are several projects on the table. It is therefore necessary to think about the roadmaps and prioritize the projects on which efforts will be concentrated.

#agenda, #meeting, #performance, #performance-chat

Performance team meeting summary – November, 2 2021

@justinahinon led the meeting. You can also read the Slack logs.

Performance team resources/reading materials

If this is the first time you are hearing about the WordPress performance team, here are some links to get you started:

Defining focus areas and working groups

Since the initial post on the proposal to create the team, there have been additional ideas on what it should work on. We need a bit of prioritization. Of course all performance work is important, and all contributions are welcome, as always.

To have a guideline for the next steps, the attendees decided to choose in the spreadsheet mentioned above from the aspects that have the highest number of interested contributors. These topics will be organized in working groups, that will be discussed during the weekly meetings.

Here are the working groups:

  • Images: Serving images in good quality but as small as possible
  • JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/.: Optimizing JavaScript orchestration
  • Site Health: Providing the user with data to understand performance
  • Measurement: Compiling data and analysis, and reporting on performance

To make sure we are making steady progress, we asked for at least one volunteer per working group to commit to attending weekly meetings to give updates on what is being done, and possibly how other contributors could help. Here’s the thread on Slack where you can express your interest in doing so.

Next steps for this team

The next steps for the team and the working groups are the following:

  1. Define the logistics for each group (tracking, POCs etc.)
  2. Kickoff meeting for each 4 area

If you are interested in exploring or helping with one of these, please feel free to add their .org username in the Focus Area speadsheet.

Open Floor

Several ideas were brought up during the meeting, about the organization of the team, potential tools or ideas for exploration. Here are some of them:

About tooling/documentation/information about performance and monitoring

About some work that is already being done for performance

@audrasjb is doing some work for the Site Health focus. Audras is working on a feature plugin on Benchmarks in Site Health, number of CSSCSS Cascading Style Sheets./JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. assets loaded.

Thanks @francina and @tweetythierry for the peer review

#meeting, #performance, #performance-chat, #summary

WordPress Performance Team kick off

Two weeks ago, Google and Yoast WordPress contributors posted a proposal to create a Performance team responsible for coordinating efforts to increase the performance (speed) of WordPress. The proposal was very well received overall, and many other contributors showed interest in joining the effort (thanks everyone).

This post aims at announcing the next steps.

Initial contributors coordination

As authors of the initial proposal, long time WordPress contributors, @tweetythierry, @flixos90, @aristath, @justinahinon, @adamsilverstein (in no particular order) are committed to:

  • lead the working groups formation
  • coordinate the initial administrative tasks (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/. channel, weekly meetings, schedule working groups representative nominations, etc.)
  • create a mission statement for the team
  • coordinate the areas to tackle
  • outline the scope and the roadmap

If you have interest in contributing to any of the above, please join the kickoff meeting, if you can, or use the comments of this post to do so.

Everybody is welcome to join working groups and contribute to performance enhancements without specific nomination 🙂

Kickoff meeting

Given the large interest from many contributors, it sounds like getting together is the first step.

By looking at the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Meetings calendar, Tuesdays at 3PM UTC seem good candidates. @justinahinon has offered to run chats ad interim, the kick-off meeting will happen on Tuesday, November 2nd 2021 at 3PM UTC in the #performance Slack channel.

Agenda

  • Welcome
  • Contributor interest open floor
  • Defining areas of focus

Defining focus areas and working groups

As we have seen from the initial post comments, there are no shortage of areas in need of performance enhancements in WordPress (which is a good problem to have in a way). With that in mind, we will initially aim to keep the scope limited by defining the most impactful area of focus and create working groups if need be. Defined focus areas will be the main points of discussion during weekly chats.

An agenda item for the first meetings will be to define the initial focus areas for the team. Every contributor will be asked to self-assign themselves to one or two areas, to indicate what they would like to work on. The performance projects are assembled in a spreadsheet which can already be reviewed ahead of the kickoff meeting.

This is not exclusive of any performance contributions.

Props

Thanks to the following for their involvement in authoring, proofreading and providing feedback on this post.

@francina, @flixos90, @aristath, @tweetythierry, @justinahinon (in no particular order)

#agenda, #meeting, #performance, #performance-chat