Tag Archives: summary

Emily Clarke 3:55 pm on October 8, 2024
Tags: , , , , summary   

Performance Chat Summary: 8 October 2024

Meeting agenda here and the full chat log is available beginning here on Slack.

Announcements

  • Welcome to our new members of #core-performance
  • WordPress 6.7 BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 2 is October 8, with Beta 3 following on October 15
  • New Web Worker Offloading 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 is now published and available for download
  • Official announcement that the Plugin Check has been incorporated into the submission process for all new WordPress plugins

Priority Items

  • WordPress performance TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets
  • Performance Lab plugin (and other performance plugins)
  • Active priority projects

WordPress Performance Trac Tickets

  • There are currently 8 performance issues in 6.7 (bugs)
  • Will be discussed in tomorrow’s bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrub

Performance Lab Plugin (and other Performance Plugins)

Active Priority Projects

Investigate INP Improvements

  • No updates this week

Improving the calculation of image size attributes

  • @mukesh27 Regarding the improvements to the calculation, the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. ticketticket Created for both bug reports and feature development on the bug tracker. #62046, I’ve opened PR #7522, which includes unit tests. The tests have passed, so could @joemcgill please take a look when you have a moment?

Enable Client Side Modern Image Generation

  • No updates this week

Enhance Onboarding Experience of Performance Lab Plugin

  • @flixos90 This already predated last week’s meeting, but I don’t think I shared it here: In https://github.com/WordPress/performance/issues/1032#issuecomment-2384151984 I summarized some of the responses for the onboarding feedback form so far.
    • I think the biggest priority based on the onboarding feedback is to make the feature/plugin activation work via AJAX. Because right now it results in a fresh page load, it means quickly activating multiple features is unnecessarily slow. It can sometimes even lead to weird errors if users click multiple buttons too fast (before the page reloaded)
    • @flixos90 to open an issue for this

Open Floor

  • @mukesh27 The WP 6.7 Beta 2 Performance Benchmark Report shows the regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. in 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. (TT4) theme, For full details check https://github.com/WordPress/performance/issues/1572#issuecomment-2398943461

Our next chat will be held on Tuesday, October 15, 2024 at 15:00 UTC in the #core-performance channel in Slack.

#core-performance, #hosting, #performance, #performance-chat, #summary

Sarah Norris 1:51 am on October 3, 2024
Tags: , , , summary   

Summary, Dev Chat, October 2, 2024

Start of the meeting in 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/., facilitated by @joemcgill. 🔗 Agenda post.

Announcements

WordPress 6.7 Beta 1 was released on October 1. Thank you to everyone who contributed to this release and attended the release party! There is a helpful guide here on how to help test this release.

Forthcoming releases

Next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.: 6.7

We are currently in the WordPress 6.7 release cycle. WordPress 6.7 BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 2 is scheduled for Tuesday, October 8. For specific release times, review the release party schedule post.

@peterwilsoncc noted that the release is now in the phase of bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. fixes only. No further enhancements or features can be committed to WordPress-Develop until the 6.7 branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch". is forked in a few weeks time after RCrelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). 1. Tasks can also be completed at this stage, such as the about page, etc.

@peterwilsoncc also mentioned that the Twenty Twenty-Five theme is still being worked on in the 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. https://github.com/ repository and he’s sure the theme team would love assistance there https://github.com/WordPress/twentytwentyfive/issues.

https://core.trac.wordpress.org/ticket/49985 could do with some eyes on it and is currently in the 6.7 milestone. Also, getting eyes and follow-ups on the items marked as needing changes in the milestone report by workflow would be helpful.

On the Editor side, @noisysocks suggested diving into fixing bugs that are in the 6.7 board if you’re interested in helping out.

Next maintenance release

There are no maintenance releases planned at this time. Currently, the next minor report is clear.

Next 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/ release: 19.4

The next Gutenberg release will be 19.4, scheduled for October 9, and will include the following issues.

Discussion

There were no discussion topics raised this week.

Open Floor

@akirk left a comment on the agenda asking whether the WordPress project wanted to be represented at FOSDEM 2025, happening in Brussels this coming Feb. To quote his comment on the agenda:

I believe bringing a dedicated WordPress room to this open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. conference could be beneficial for WordPress to connect more with other open source projects. We could select talks for the devroom (given that they’d be proposed) that can inspire and take inspiration from other open source projects, for example about WordPress Playground, or how the WordPress project does translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization..

Proposals need to be submitted by Oct 10. Alex is looking for feedback about whether it makes sense to engage in the FOSDEM environment and to gather interest in submitting talks if the room is accepted. Please reach out to @akirk directly if you’d like more information about this.

Props to @joemcgill for proofreading.

#6-7, #core, #dev-chat, #summary

Emily Clarke 3:56 pm on October 1, 2024
Tags: , , , , summary   

Performance Chat Summary: 1 October 2024

Meeting agenda here and the full chat log is available beginning here on Slack.

Announcements

  • Welcome to our new members of #core-performance
  • WordPress 6.7 BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 2 is next week, October 8

Priority Items

  • WordPress performance TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets
  • Performance Lab 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 (and other performance plugins)
  • Active priority projects

WordPress Performance Trac Tickets

  • There are currently 9 performance issues in 6.7 (bugs)
  • @joemcgill planning on punting #59600, because I don’t think we have any clear next steps to move that forward
    • Just want to review it an make sure there aren’t any follow-up items in that ticketticket Created for both bug reports and feature development on the bug tracker. that need to be tended to first
    • I also noticed that there was an issue with the performance tests during the release party due to the inclusion of a new default theme. Curious if we already have a ticket to update this, or any next steps we need to do. @mukesh27 do you know?
      • @mukesh27 it was fixed in #59151
      • @joemcgill will spin up a new ticket to conditionally test TT5 on WP versions that support that theme
  • @mukesh27 ran WP 6.7 Beta 1 Performance Benchmark Report – please seehttps://wordpress.slack.com/archives/C02KGN5K076/p1727785426773919 shows the regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. in 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. theme

Performance Lab Plugin (and other Performance Plugins)

Active Priority Projects

Investigate INP Improvements

  • @adamsilverstein noticed a new comment in the INP opportunities doc (created in March) noting that Elementor has fixed one of the issues identified there. Their new release has the fix which loads CSSCSS Cascading Style Sheets. more dynamically based on content.

Improving the calculation of image size attributes

  • @joemcgill For improving the calculation of image sizes attributes, we’ve been doing some experimentation with using block context to pass layout information from parent blocks to their ancestors and have noticed that #62046 is affecting our work. I’d like to see if we could get this solved for 6.7 so we don’t need to ship a workaround for this bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. in our feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins. implementation. @gziolo flagged this as too late for 6.7 on the ticket, but as a bug, I think it could still land during betas.

Enable Client Side Modern Image Generation

Enhance Onboarding Experience of Performance Lab Plugin

Open Floor

  • Further discussion on WP 6.7 performance benchmarks
    • @joemcgill regarding (Slack post) the performance metrics for classic themes looks pretty steady, which is great! For TT4, it seems like we need to investigate the cause of the additional performance regression during template rendering, because adding 10% is not great.
    • Can we spin up a tracking issue in our performance repo to collect each of these benchmarks during the release and have a place to discuss the potential causes/remediation efforts?

Our next chat will be held on Tuesday, October 8, 2024 at 15:00 UTC in the #core-performance channel in Slack.

#core-performance, #hosting, #performance, #performance-chat, #summary

Joe McGill 10:04 am on September 25, 2024
Tags: , , , summary   

Summary, Dev Chat, September 25, 2024

Start of the meeting in 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/., facilitated by @joemcgill. 🔗 Agenda post.

Announcements

There are no announcements this week. However, last week many from the community attended WordCamp US 2024 in Portland, OR. If you missed it, or just want to reminisce, several folks contributed to this PDX + WCUS 2024: A Recap post from the week.

Forthcoming releases

Next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.: 6.7

We are currently in the WordPress 6.7 release cycle. WordPress 6.7 BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 is one week away. The Road Map post can be found here.

In case you missed it, @davidbaumwald just published the WordPress 6.7 Release Party Schedule.

@peterwilsoncc reminded that all enhancements need to be committed prior to the beta so folks wishing to get something in should do so sooner rather than later.

The final release of 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/ 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 for WP 6.7 has been released and the 6.7 branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch". for the plugin created.

One of the bigger tasks is to get Twenty Twenty-Five committed, so the team working on that is pretty focused this week. It would be very valuable if people could take some time to test the theme and log any issues, create PRs (if able to), etc. To do so, visit https://github.com/WordPress/twentytwentyfive. There are instructions in the repo explaining how to set it up and get it running.

Next maintenance release

There are no maintenance releases planned at this time.

Next Gutenberg release: 19.3

The next Gutenberg release will be 19.3, scheduled for September 25, and will include the following issues.

Discussion

There were no discussion topics raised this week.

Open Floor

Cory Hughart shared that during 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/. at WCUS, the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Fields table spent the day diving through bleeding-edge Gutenberg code related to the new DataViews in posts and pages areas of the site editor. @sc0ttkclark is working on a dev blogblog (versus network, site) post, but the TL;DR is that we want to add some options to register_meta functions in PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher to enable quick edit for custom fields. We’ll be talking more about it in the days ahead in #core-fields.

We finished Dev Chat by reviewing the tickets in the 6.7 milestone marked early.

Props to @mikachan for proofreading.

#6-7, #core, #dev-chat, #summary

Emily Clarke 8:43 am on September 25, 2024
Tags: , , , , summary   

Performance Chat Summary: 24 September 2024

Meeting agenda here and the full chat log is available beginning here on Slack.

Announcements

  • Welcome to our new members of #core-performance
  • WordPress 6.7 BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 is next week, October 1
  • Performance Lab release 3.4.1 was published yesterday
  • The WordPress Performance Team is looking for feedback to streamline the onboarding experience of the Performance Lab 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. We would appreciate it if would you took 5 minutes of your time to set up the plugin and share your feedback.

Priority Items

  • WordPress performance TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets
  • Performance Lab plugin (and other performance plugins)
  • Active priority projects

WordPress Performance Trac Tickets

  • There are currently 19 performance issues in 6.7
  • To be discussed on tomorrow’s bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrub

Performance Lab Plugin (and other Performance Plugins)

Active Priority Projects

Investigate INP Improvements

  • No updates this week

Improving the calculation of image size attributes

  • No updates this week

Enable Client Side Modern Image Generation

  • @swissspidy I gave a talk about this last week at WCUS, which was a great success. Lots of positive feedback and interest in helping to contribute. Writing a blogblog (versus network, site) post now with details etc
    • @joemcgill Once this effort gets past the initial experiments phase, I think it would benefit from more people being able to support Pascal in implementing some of these ideas. What do you think?
    • @swissspidy Definitely 🙂 As soon as this is in 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/, more eyes are definitely helpful. But even now it can’t hurt to at least test the existing plugin and provide feedback

Enhance Onboarding Experience of Performance Lab Plugin

Open Floor

  • n/a

Our next chat will be held on Tuesday, October 1, 2024 at 15:00 UTC in the #core-performance channel in Slack.

#core-performance, #hosting, #performance, #performance-chat, #summary

Carolina Nymark 9:56 am on September 13, 2024
Tags: , , summary,   

Default Theme Chat Summary, September 11, 2024

This post summarizes the latest Default Theme meeting (agenda, slack transcript).

Status update

We’ve made significant progress with patterns and templates this past week.
The work on Twenty Twenty-Five is happening in the GitHub repository.

  • 36 open issues.
  • 19 open pull requests.

In the Figma file you can see what is completed by looking for a green circle. Designs in progress have a yellow circle, and anything that is blocked or not planned at this time, is labeled with a red circle.

Priorities

  • Finish the work for all the remaining block patterns.
  • Work on the style variations. There’s an open issue to address these.
  • Work on items that are set to [Priority] High.

Once we finish adding the remaining 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. patterns and templates, we’ll start adding issues and instructions on how to proceed with i18ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill. (making strings translatable, etc.), indentation, and polishing the patterns/templates.

Open floor

@erichmond brought up that it is difficult to pick issues to work on, and that even if a contributor is assigned to an issue, there may be duplicate pull requests submitted.

The intention is to follow the assignment to the person who has shown interest in the issue first. A recommendation would be to see if there are pull requests open before starting to work on a given issue.

@luminuu Asked if it would be a good idea to test the theme during the WCUS 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/. on Tuesday the 17th of September, and if anyone would be available online during the start of the contributor day.

It is difficult to predict what kind of issues that may be open in the repository on the 17th and if they are suitable to work on during a contributor day. A new label in the repository can help contributor day attendees to select issues to work on.

Thanks to @beafialho & @juanfra for reviewing the summary.

#bundled-theme, #core-themes, #summary, #twenty-twenty-five

Joe McGill 12:40 am on September 13, 2024
Tags: , , , summary   

Summary, Dev Chat, September 11, 2024

Start of the meeting in 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/., facilitated by @joemcgill. 🔗 Agenda post.

Announcements

WordPress 6.2.2 was released this week.

Forthcoming Releases

Next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.: 6.7

We are currently in the WordPress 6.7 release cycle. WordPress 6.7 BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 is scheduled for Tuesday, October 1. The Road Map post can be found here.

Next minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality.: 6.6.3

Following the recent WordPress 6.6.2 release, the next maintenance release (if needed) will be WordPress 6.6.3. There were not updates shared in the meeting.

Next 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/ release: 19.2

The next Gutenberg release will be 19.2, scheduled for September 11 (this release occurred after the meeting).

Discussion

@peterwilsoncc requested that we discuss 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. Bindings UIUI User interface feature, TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticketticket Created for both bug reports and feature development on the bug tracker. #61945.

To summarize his concern:

My main concern here is that the approach is to hide the UI from users with low permissions. I don’t feel that this is a great approach to handling a UI that is considered too technical, as I don’t think there is anything to suggest that an administrator will understand what an author does not.

So I’m of the view the interface ought to be improved and made less technical before it’s shipped in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..

@noisysocks suggested waiting on an update from Mario Santos, who is working on the feature, but added:

I’d be fine with just updating this to use caps. The interface doesn’t strike me as being too technical. Can put it in the Advanced tab if we’re worried…

…The short of it is that I’m okay with fixing the cap issue (add a new cap, don’t check against a role) and shipping in 6.7 or leaving it in the 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 for more testing. Up to the team working on it. We have until beta 1 to decide.

@joemcgill highlighted two additional Slack updates this week:

Open Floor

@mikachan provided an update on #61708 on the agenda:

I’ve addressed the feedback by adding a deprecation notice to the pattern rather than removing it. I’d appreciate any thoughts on if this feels like a better approach.

@peterwilsoncc agreed to review.

@joemcgill pointed out #62004. @jrf recently asked all committers to review in full here. Julia shared the following updates during the meeting:

Ticket #53010 is basically the first step: splitting up the huge test classes to smaller classes which each only test one thing, i.e. one global function, one method in a class etc.

This includes making sure that the new test files comply with the PHPUnit naming conventions.

There are a number of patches attached to the ticket which can be used to see how to do this (mind: not all have been reviewed yet for the latest info).

I also think it would be great if we could get a decision on yes/no namespacing the test classes. I believe we should and that now is the time.

And followed up with

The other thing which would really really help, is to make sure that any new tests go in “clean”. As in: comply with the requirements for newer PHPUnit versions. The task is large enough as it is without having to clean up after new commits.

#6-7, #core, #dev-chat, #summary

Birgit Pauli-Haack 8:14 am on September 11, 2024
Tags: , , , summary   

Summary of the Developer Blog editorial meeting on 5 September 2024

Summary of the WordPress Developer Blogblog (versus network, site) meeting, which took place in the  #core-dev-blog channel on the Make 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/.. Start of the meeting in Slack.

Attendees: @greenshady @webcommsat @oglekler @ndiego @zeelthakkar @jagirbahesh @bcworkz (async) and @bph (facilitator).

Last meeting notes: Developer Blog editorial meeting summary 1 August 2024

In this article

Contributor updates

  • Congrats to @ajlendelende and @aljullu to receiving their Documentation Contributor badges for their contributions to the Developer Blog.  
  • Call for contributors to take on What’s new for Developers roundup post for November? @greenshady @ndiego or I (@bph) will be right with you to guide you through the research as well as the writing part. If you want to take it on, come to the #core-dev-blog channel or DM either one of us.

Newly published posts since last meeting

Since the last meeting, we published the following articles

Huge Thank You to the writer and reviewers! 

Project status

The project board for Developer Blog content is on 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. https://github.com/.

Issues closed

In review

In progress

On the to-do-list, assigned to writers

Topics approved, in need of a writer

If you are interested in taking on a topic from this list or know someone who would be a good person to write about them, comment on the Issue or pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” @bph in Slack either in the #core-dev-blog channel or in a DM.

New topics approved

The topic idea Modifying text with the HTML API in WordPress 6.7 needs to simmer some more to see if there will be more elaborate examples coming in the next major WordPress version. Justin will bring it back to the October meeting should the topic deemed mature enough for a blog post.

Open floor

@greenshady inquired about the possibility of translating the content of the Developer blog into other languages. Currently, there isn’t a formal proposal for a process and tools. It’s worth exploring, though. It was stated that it’s complicated for Rosetta sites, and it might not be easy to translate. It would be better if the translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. can be put right into the adminadmin (and super admin). If there is someone who translated an article, we could publish it on the Dev Blog under “other languages” and once we have a critical mass, we can create categories for Spanish, German etc. The bigger issue than the technological implementation is the recruiting and onboarding of translators to be contributors.

@bph is to reach out to the training team, to learn about their process, as they are a few steps ahead in working with translators.

@greenshady will open an issue, where we can follow up on discussion and progress.

Next meeting: October 3rd, 2024, at 13:00 UTC in the #core-dev-blog channel

Props to @greenshady for the review of the post.

#meeting, #meta, #summary

Emily Clarke 4:01 pm on September 10, 2024
Tags: , , , , summary   

Performance Chat Summary: 10 September 2024

Meeting agenda here and the full chat log is available beginning here on Slack.

Announcements

  • Welcome to our new members of #core-performance
  • WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. US is coming up Sep 17-20 in Portland, Oregon – we will have a performance table at 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/. with Adam
  • WordPress 6.7 BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 is October 1
  • Performance Lab next release scheduled for Sep 23

Priority Items

  • WordPress performance TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets
  • Performance Lab 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 (and other performance plugins)
  • Active priority projects

WordPress Performance Trac Tickets

Performance Lab Plugin (and other Performance Plugins)

Active Priority Projects

Investigate INP Improvements

  • No updates this week

Improving the calculation of image size attributes

  • @joemcgill we’re still working through some details on the approach for incorporating layout info for ancestor blocks and hope to have an update later this week.

Enable Client Side Modern Image Generation

  • @swissspidy Nothing new really from my side since last week. A couple of smaller PRs got merged into GB, and I’m ironing out some build tooling issues. Apart from that, focusing on my WCUS talk

Enhance Onboarding Experience of Performance Lab Plugin

  • @flixos90 The only news on enhancing the onboarding experience is that we’re going to ask attendees at the Google booth at WCUS to give Performance Lab a spin. We hope that from there we get a diverse list of people, especially including ones that have not used the plugin before. That should help us get some idea on what people consider pain points in the onboarding process.

Open Floor

  • @swissspidy Performance chat sometimes clashes with release parties (like today). Should we consider moving the meeting on those occasions? e.g. by +1 hour or so. Or not a big deal?
    • @joemcgill I’m unsure how many of the release parties for this major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope. will happen at the usual time, given the timezone makeup of the team. I think @peterwilsoncc was planning on publishing a schedule for betas/RCs soon. Perhaps something to consider after that?
  • Suggestion to cancel next week’s meeting due to WordCamp US

Our next chat will be held on Tuesday, September 24, 2024 at 15:00 UTC in the #core-performance channel in Slack.

#core-performance, #hosting, #performance, #performance-chat, #summary

Beatriz Fialho 3:57 pm on September 5, 2024
Tags: , , summary,   

Default Theme Chat Summary, September 4, 2024

This post summarizes the latest Default Theme meeting (agenda).

Status update

The work on Twenty Twenty-Five is happening in the GitHub repository. At the time of the meeting, there were 54 open issues and 19 open pull requests.

There were about 45 patterns designed in total. 31 patterns were built/merged or had open in-progress PRs. 14 patterns were not yet built.

There were 34 templates designed in total, 22 templates are built (the default personal blogblog (versus network, site) and alternative ones for personal, photo and news blogs). Due to time constraints, the “blogging with sidebar” alternative likely won’t get built.

There’s an open issue to create the “combined” global style variations. 1 of the 8 variations has been created, 4 others are assigned.

It is possible to see what’s 🟢 built/ 🟡 not built/ 🔴 may not be built in the Figma file.

Some important information regarding the project timing was shared: the theme needs to be more or less complete before October 1, 2024, after that it is bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. fixes only. And text strings need to be final before October 22, 2024.

Priorities

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. patterns are the highest priority now, and need to be completed as soon as possible to be used to create the other layouts such as landing pages and homepages. There are “High priority” labels and they will also dictate what’s becoming a priority along the project.

Call notes

According to the agenda, a short, informal call happened to take a look at what’s built and what’s not, and determine if some of the original designs need to be left out. Those present were @beafialho, @poena, @juanfra, @luminuu and @oncecoupled.

The call focused on the progress and challenges of the development of Twenty Twenty-Five.

Key points:

  • The completion of personal default templates and alternatives, with some patterns still pending-
  • Four patterns are blocked due to the lack of image support for categories in search templates and the new accordion block’s delay, leading to the possibility to leave out three “categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging.” patterns
  • The team discussed the feasibility of adding patterns directly from the patterns 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. and the need for consistent naming and ordering of section styles
  • The team also considered the impact of WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. US contributions and the need for thorough testing and accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) checks

Action items:

  • Follow up on the new accordion block PR and status
  • Evaluate building search result patterns or leaving them out
  • Consider adding a “page” category for patterns
  • Eventually pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” accessibility reviewers for testing

Thanks to @juanfra for reviewing the summary.

#bundled-theme, #core-themes, #summary, #twenty-twenty-five