Andrei Draganescu 6:29 pm on October 10, 2023
Tags:   

Editor Chat Agenda: 10 October 2023

Facilitator and notetaker: @andraganescu

This is the agenda for the weekly editor chat scheduled for Wednesday, October 4, 2023, 5:00 pm (UTC+03:00). This meeting is held in the #core-editor channel in the Making 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/..

  • Announcements
  • Project updates
  • Task Coordination
  • Open Floor – extended edition.

If you are not able to attend the meeting, you are encouraged to share anything relevant for the discussion:

  • If you have an update for the main site editing projects, please feel free to share it as a comment or come prepared for the meeting itself.
  • If you have anything to share for the Task Coordination section, please leave it as a comment on this post.
  • If you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below.

#agenda, #core-editor, #core-editor-agenda, #meeting

#core-editor-agenda

Emily Clarke 4:07 pm on October 10, 2023
Tags: , , ,   

Performance Chat Summary: 10 October 2023

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.4 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. 3 is today
  • Reminder about the Performance Hallway Hangout next week Thursday, October 19, 2023 at 04:00 PM GMT+1

Priority Projects

Server Response Time

Link to roadmap projects

Contributors: @joemcgill @spacedmonkey @swissspidy @thekt12 @mukesh27

  • @joemcgill Everything planned for 6.4 has been resolved. I’m keep an eye out for issues that come up during the last week of beta and 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).. Otherwise, am beginning to start focusing on opportunities for 6.5, like Improving Template Loading and Improvements to the way 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. widgets are registered (ex: #55595)
  • @spacedmonkey
  • @mukesh27 #59360 to be committed today. It was reopened for some concern that I’m looking into right now
  • @swissspidy Performant Translations is doing well. There are already PRs and tickets for all the relevant areas this touches. I’m working on further simplifying 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 & coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing.. Once 6.4 is released we can continue with the next steps for a 6.5 merge.
  • @flixos90 I would like to flag this Slack thread – just spotted this literally 5 minutes ago, but it looks like the most significant performance fix for TT4 caused a 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., which now with the fix for that bug effectively may have reverted almost all the performance benefit
    • In my benchmark yesterday, TT4 was about ~10% slower than TT3. Now it’s again ~25% slower
    • @spacedmonkey to re-open #59541 to see if it helps
    • @joemcgill to run some profiles, but assuming it’s due to parse_blocks() being called way more often.
  • @thekt12 I have picked up https://github.com/WordPress/performance/issues/746 (just a while ago), checking through tickets that are still left

Database Optimization

Link to roadmap projects

Contributors: @spacedmonkey @mukesh27 @thekt12

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/. & CSSCSS Cascading Style Sheets.

Link to roadmap project

Contributors: @mukesh27 @10upsimon @westonruter @spacedmonkey

  • @westonruter Yesterday I committed the removal of unload event listeners and use of pagehide and pageshow where appropriate for #55491 . In the best case this will improve performance by allowing bfcache to speed up page navigations. But as I mentioned before, bfcache is also disabled when Cache-Control: no-store is present, and this was added to all authenticated page requests in 6.3 with #21938. Lastly, the heartbeat script is only used on 0.25% of HTTPHTTP HTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. Archive pages (which would be unauthenticated).  So in practice the performance benefits will be marginal. Nevertheless, the unload event is unreliable so the change is an improvement regardless.
  • @adamsilverstein I have been working on adoption of the script strategy feature with plugins and have been having some success. Its great how easy it is to layer on the new APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. without breaking old use cases (especially using `wp_script_add_data`). One potential issue I have discovered that could cause regressions has to do with dependencies and the footer attribute.
    • Here is the scenerio:
      • Popular plugin “Plugin A” currently enqueues a script on the front end, using `in_footer` => true, so the script is essentially non blocking
      • To get a slight performance gain, in WP >= 6.3 the plugin changes `in_footer` to `array( ‘strategy => ‘defer’ )`. Great, now the script is in the 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. so it can be discovered slightly earlier, and it is marked as `defer` so it is non-blocking.
    • Now… along comes “Plugin B”, they enqueue a script that depends on the script from “Plugin A”, and they still use `in_footer => true`. Now the script from “Plugin A” can no longer be deferred, so it is not – however it remains in the header. The result: we now have a new blocking script in the header.
    • I wonder if we had considered this during the design? Maybe in my scenario I should instead use `array( ‘strategy => ‘defer’, ‘in_fooer’ => true )`
    • @flixos90 I think opening a ticket would be good. If a script has defer, it should always be fine to load it in the footer (since with defer it only loads after the DOM anyway). So I think that would be a good fix: If a script is in the head and its defer is forced back to blocking, move it to the footer
    • @adamsilverstein I was thinking that also, but it might have other implications…Also in my testing I noticed that in_footer already has some dependency behavior built in that can move scripts to the header:
      Script A is marked for the footer. If script b depends on script a and is marked for the header, script a also gets put in the header
    • @10upsimon That makes sense @flixos90 I think we only never did that because by design you’d only usually have deferred in the header, generally, correct?
      • @flixos90 Not sure, I don’t remember us ever thinking about the head vs footer implication of a deferred script being forced back to blocking. So we may just have missed that consideration. To me what @adamsilverstein pointed out above is something we should be able to fix in a rather straightforward way
      • @adamsilverstein yea, I don’t think we considered that exact scenereo, I came across it trying to implement/use the feature
    • @flixos90 I think the latter has been the case forever, so that wouldn’t be a 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.
    • @joemcgill We could do some analysis of how many registered deferred scripts end up in the head, since we added some data attributes to track that sort of thing
    • @westonruter We don’t currently capture whether a script was originally registered with $in_footer in the data attributes like we do with the script strategies though
    • @flixos90 FWIW I cannot see any concerns with moving a head defer script to footer from a functional perspective. In both cases it would be loaded after the DOM. Not sure how important the impact research would be for that bug specifically
    • @adamsilverstein to open a ticket to discuss further

Images

Link to roadmap projects

Contributors: @flixos90 @thekt12 @adamsilverstein @joemcgill @pereirinha

  • @joemcgill I’m planning to follow up on two things we’ve discussed, related to improving how WordPress calculates the sizes attribute.
  • @adamsilverstein I’ve been testing the fetchpriority attribute and wanted to raise some potential issues. First: I created a simple plugin that adds an advanced image control that lets users set the fetchpriority manually for individual images – https://github.com/adamsilverstein/wp-fetchpriority-control
    • Noticed a few edge cases with our approach in testing –
    • I think these are all addressable in some form and the first may already be covered by an existing ticket; I’ll plan to open tickets for further discussion
  • @flixos90 I opened a new ticket yesterday for a recently found limitation of wp_get_loading_optimization_attributes() when it comes to images in block templates #59577 that affects TT4
  • @pereirinha I’m looking for good candidates to pick up, but nothing yet. Happy to assist here.

Measurement

Link to roadmap projects

Contributors: @adamsilverstein @joemcgill @mukesh27 @swissspidy @flixos90

  • @flixos90 Nothing from my end, other than running benchmarks on several tickets this week
  • @mukesh27 Planning to run benchmarks for beta 3 tomorrow.
  • @swissspidy Continuing working on documenting ways for improving the core performance test setup & reducing test variance. Nothing concrete right now
  • @joemcgill Another thing we’ve been discussing for the past few weeks is how to improve the confidence we have in our benchmarking setups. Many of us have been using an automated script that @swissspidy put together to run benchmarks for each release, and we’re getting consistent numbers, but those numbers are showing much bigger performance gains than what @flixos90 has been reporting with his local setup. I’m planning to dig into this a bit more today. @swissspidy I saw that you’re making good progress on converting performance tests to Playwrite. Anything we can help with there?

Ecosystem Tools

Link to roadmap projects

Contributors: @mukesh27 @swissspidy @westonruter

Creating Standalone Plugins

Link to GitHub overview issue

Contributors: @flixos90 @mukesh27 @10upsimon

  • @10upsimon No major updates from me at the moment, I did decide to refactor some code to be more WordPress’y when it comes to the standalone plug-in card rendering within WPP settings screen, so I’ll open said PR for standalone plug-ins UIUI User interface soon, via a feature 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"..

Open Floor

  • @spacedmonkey I am changing roles ( I am leaving XWP ). I will not have sponsored time to work on this project. So as of the end of this week, I will be stepping down from this project. That means I will not be around to answer questions or code review. If you need anything, please message me before the end of the week.

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

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

Emily Clarke 9:27 am on October 10, 2023
Tags: , , ,   

Performance Chat Agenda: 10 October 2023

Here is the agenda for this week’s performance team meeting scheduled for Oct 10, 2023 at 15:00 UTC. If you have any topics you’d like to add to this agenda, please add them in the comments below.

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

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

Ajit Bohra 3:39 pm on October 6, 2023
Tags: , , , ,   

Editor chat summary: October 04th, 2023

This post summarizes the latest weekly Editor meeting (agenda, slack transcript), held in the #core-editor 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, on Wednesday, October 04, 2023, 14:00 UTC moderated by @ajitbohra

Accouncements

  • WordPress 6.4 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 available for testing.
  • WordPress 6.4 Editor Tasks Project Board.
  • Gutenberg 16.8.0 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 is available for testing.

Async key project updates

Read the latest updates directly from the following tracking issues:

@hellofromtonya

The Font Library’s REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. has been significantly redesigned. It’ll need testing and release to gain wider in the wild testing.

Task Coordination

No updates.

Open Floor

@get_dave

I’m working on a PR which changes the Post Title in the Post Editor to render HTML in normal (“Visual”) mode and output raw HTML in “Code view” mode. It also strips all HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. from anything pasted into the title field in Visual mode. As this is a change that may impact editorial workflows I wanted to flag it for more visibility.

@vcanales
I’m wondering if we are open to releasing 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/ 16.8.0 on Monday rather than Wednesday so that the new APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. makes it to a release before Beta 3.

Note: Anyone reading this summary outside of the meeting, please drop a comment in the post summary, if you can/want to help with something.

Read complete transcript

#core-editor, #core-editor-summary, #gutenberg, #meeting-notes, #summary

Jb Audras 3:05 pm on October 6, 2023
Tags: , ,   

WordPress 6.3.2 RC1 is now available

Update (Oct. 9): In order to accommodate the need for hosts to deal with the pending curl 8.4.0 security release on Wednesday, the 6.3.2 final release date will be delayed to Thursday, Oct 12.

WordPress 6.3.2 Release Candidate 1 (RC1) is available for testing! Some ways you can help test this minor release:

  • Use the WordPress Beta Tester 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
    • As this is a minor 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). release, select the Point Release channel and the Nightlies stream. This is the latest build including the RC and potentially any subsequent commits in trunk.
  • Use WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/ https://make.wordpress.org/cli/ to test:
    wp core update https://wordpress.org/wordpress-6.3.2-RC1.zip
  • Directly download the Beta/RC version.

What’s in this release candidate?

6.3.2 RC1 features 19 fixes on Core as well as 22 fixes for 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. Editor.

The following coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. tickets from TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. are fixed:

  • #59489 — Themes: Fix core block style paths on Windows
  • #59198 — Upgrade/Install: Check plugin compatibility during bulk upgrades
  • #59293 — Editor: Update packages with 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 for 6.3.2 
  • #59086 — Twenty Twenty: Fix style issues within iframed editor
  • #59196 — Build Tools: Avoid doing copy:dynamic when running grunt watch when using --dev option
  • #59193 — REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/.: Remove misleading comment in WP_REST_Blocks_Controller->get_item_schema
  • #59108 — Editor: Preserve block style variations when securing theme
  • #59041 — Post Types: allow trashing draft patterns
  • #59018 — Editor: Fix loading of assets in blocks in child themes where the directory name starts with the parent theme’s directory name
  • #59000 — Editor: Prevent possibility of a fatal error when previewing block themes
  • #58754 — Editor: Don’t use fluid layout value in typography
  • #58119 — HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways.: Remove all duplicate copies of an attribute when removing
  • #59394 — Build/Test Tools: Add sys_get_temp_dir() to open_basedir tests
  • #59320 — Upgrade/Install: Fix broken sprintf() call when deleting a backup
  • #59292 — HTML API: Skip over contents of RAWTEXT elements such as STYLE
  • #58779 — Build/Test Tools: Restore automatically retrying failed E2E tests once
  • #59111 — Themes: Avoid stale caches for core block styles
  • #59226 — Posts, Post Types: Reinstate missing sort_column options in get_pages()
  • #59224 — Posts, Post Types: Avoid redundant SQL query in get_pages()

The following block editor issues from 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/ are fixed:

What’s next?

The dev-reviewed workflow (double committer sign-off) is now in effect when making changes to the 6.3 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"..

The final release is expected on Wednesday, October 11th, 2023 Thursday, October 12th, 2023. Please note that this date can change depending on possible issues after RC1 is released. Coordination will happen in 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/ 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/. #6-3-release-leads channel.

A special thanks to everyone who helped test, raised issues, and helped to fix tickets. With this release candidate, testing continues, so please help test!

The WordPress 6.3.2 first release candidaterelease 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). was led by @joemcgill and @audrasjb with the help of @davidbaumwald at mission control and @isabel_brison on Editor backports.

#6-3, #minor-releases, #releases

annezazu 10:00 pm on October 5, 2023
Tags:   

Core Editor Improvement: Ensuring Excellence in the Writing Experience

These “CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor Improvement…” posts (labeled with the #core-editor-improvement tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.)) are a series dedicated to highlighting various new features, improvements, and more from Core Editor related projects. 

Writing in WordPress, whether your latest post or a new page, needs to be seamless and enjoyable–the tooling should always aim to aid creativity rather than get in the way. Blocks with all of their variations, design tools, and transforms should leave you feeling empowered. To make sure of that, some extra effort was put into the 6.4 release cycle to make the simple act of writing better with new keyboard shortcuts, smoother list merging, some key fixes, and more. Below is a video demonstrating some of these enhancements in one cohesive flow starting with the captured toolbars in a Quote 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. and ending with easily merging two List blocks:

Cohesive Toolbar experience with Navigation, List, & Quote blocks

There’s a new toolbar experience for the Navigation, List, and Quote blocks. Each of these blocks have built-in child blocks and rather than having the toolbars for each child block visible, they are now seamlessly attached to the overall parent blocks. This both helps prevent toolbars from blocking other pieces of content, like a different list item than the one selected and provides a more organized editing experience where you always know where your tooling options are. 

Orange background with the words Toolsbars, captured next to a view of a list block with a few list items shown and the overall block toolbar remaining attached to the parent block.

Strengthening the experience

Several 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 and improvements contribute to a more seamless and predictable writing experience.

Updating List View 

List View has some neat, new options to get the most out of this robust tool: 

What’s next?

This work is never over and current efforts can be followed in this tracking issue. Consider this encouragement to continue sharing directly any issues you’re running into, whether a bug to fix or an experience to polish. 

#core-editor-improvement

Abha Thakor 2:46 pm on October 5, 2023
Tags: , , ,   

Developer Blog editorial meeting summary: October 5, 2023

A complete transcript of the meeting can be found in the #core-dev-blog channel in Making 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/..

Notes of the last editorial meeting on September 7, 2023 – thanks to @bph

Attendees: @bph, @milana_cap, @greenshady, @marybaum, @webcommsat, @oglekler

Site updates and new posts

Since the last editorial meeting, the following posts have been completed by writers and reviewers.

@bph shared a huge thank you to the writers, and their reviewers! Fantastic job!

Project board

Posts in progress

Posts for review

At the time of the meeting time, these posts were in need of review.

2nd review: New developer focused workflow article about how the login and registration works in WordPress.
1st review: A tutorial about the highlights of the browser and focus modes of the Navigation Block
1st review: #151 Type series post 3: Setting body-conscious type for long-form text#156

Action: comment on 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/ issue if you can review.

Posts on the to-do list

These were all approved topics, with writers assigned:

On the to-do list

@webcommsat to look at how to highlight call for writers on Dev Chat agendas post 6.4.

Posts that need writers

Two topics are still looking for writers:

Actions: If you know someone or want to write it yourself, post in the Developer-Blog channel on Slack.

Posts for approval

The group approved one new topic:

Open floor

Discussion to encourage writers to share GitHub tickets, Google Docs, public preview links to accompany a call for review in Slack to help reviewers. When writers and reviewers contributing in opposite time zones, these links can be particularly helpful.
Action: to guide contributors to use GitHub to capture comments/ changes, including when posts have moved to the CMS phase.

In the last quarter, many new writers have been inducted to the Dev Blogblog (versus network, site). Proposed a post for new writers with input from contributors recently joined.
Action: @webcommsat and @bph to take forward the post.

Agreement to allocate Documentation badges to contributors for writers and reviewers of the Dev Blog.
Action: @bph and @milana_cap

#core, #core-dev-blog, #dev-blog, #meeting

Abha Thakor 11:19 pm on October 4, 2023
Tags: , ,   

Dev Chat Summary, October 4, 2023

Summary from the weekly WordPress developers chat that took place on 2023-10-04 at 20:00 UTC  in the core channel of Make WordPress Slack.

Key items

Start of the Dev Chat on Slack

Summary of where to post items for discussion, shared by @hellofromtonya:

  • from last week’s discussions, an effort is underway to move all source code discussions / decision making out of the release channel to happen here in #core 
  • if there’s source code or tickets to be discussed, please post them into the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. channel of 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/., not in the #6-4-release-leads channel
  • if the release squad needs a heads up, it’s okay to post in the #6-4-release-leads channel. It’s helpful to share a link to where the discussion is happening in #core

Announcements

WordPress 6.4 Beta 2 is available – please help test and thanks to everyone who contributed and took part in the release party.

In the #core-editor channel, a change in 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/ 16.8 release was discussed and agreed:

  • shift the Gutenberg 16.8 final release to Monday, October 9 (instead of Wed), ahead of the 6.4 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. 3 release
  • if more changes happen for the Font Library, do another Release Candidaterelease 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). release before 16.8 final release

The change is to provide additional time to review and test requested changes to the Font Library’s REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. before Beta 3.

Highlighted posts

  • Hallway Hangout – working session on consolidating modes. November 15, 2023. This is part of efforts to improve 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) of the Site Editor.   
  • 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 checker repo is now in the WordPress organization 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/. https://github.com/WordPress/plugin-check.
  • Benchmark results on 6.4 Beta 1 from the Performance Team can be read on its meeting summary.

Forthcoming release updates

Next major WordPress release: 6.4

Reminder: WordPress 6.4 Beta 3 is scheduled for October 10, 2023 – the last scheduled beta before RC1.

Update from the release squad

  • No additional major updates than the items covered.
  • Calls/Action: Note that anyone can test or file bugs they find and do not need to wait for a scrub etc.
  • Highlighted 6.4 is a shorter release cycle than recent ones, and encouraged folk to help.
  • Commit freeze experiment: no commits starting 1 hour before the release party start time seemed to work well, and will be continued throughout the rest of the cycle
  • Still lots of bugfix tickets in the milestone that need help to further.

Calls: You can help with:

@hellofromtonya confirmed if needed an unscheduled beta can (and often does if more commits come in) happen before RC1.

Calls relating to specific 6.4 tickets

About Page for 6.4

  • Call for feedback on the first draft of the About Page for 6.4. @estelaris has asked for comments to be left either on the 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. #59289 or in Figma.
  • Confirmation: core developers will be able to build/commit the About Page. Request to share in the core channel when the different stages of the page are ready before each release milestone. Any additional help offers, please comment in the 6.4 release leads channel on Slack.

56922 Template/ Template Part RevisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision.

  • @spacedmonkey and @antonvlasenko asked for assistance to take forward a Pull Request on Trac Ticket #56922 to try and get it into 6.4. The ticket allows the Gutenberg team to make revisions for template / templates parts in the editor. There is a GitHub PR 3533. More information on the call in Slack.

Dev Notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase.

Docs release team update via @webcommsat

  • In the Docs release team, we are working on collating dev notes for 6.4.
  • Reaching out to component maintainers as part of this and appreciate replies and input. Those involved with or writing dev notes will be able to update the GitHub project board for tracking 6.4 docs (link will be shared when ready).
  • Request to not publish dev notes as the team will be doing a final review and publish these to avoid swamping core and the RSS feedRSS Feed RSS is an acronym for Real Simple Syndication which is a type of web feed which allows users to access updates to online content in a standardized, computer-readable format. This is the feed. with too many at the same time.

More 6.4 discussion areas

Not all of these were highlighted individually during the meeting due to time. The full list in the agenda was highlighted and is listed below to help people keep in the know.

Call to Contributors: Can you help with any of these items?

  1. Discussion in release leads/ core has been on Trac ticket #59526 issue relating to fixing image assets with the Twenty Twenty Four theme identified during 6.4 beta 2 release party. Discussion in core. Update in Dev Chat: this has now been fixed.
  2. Discussion on the issue of non-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 access to the site editor’s pattern page, Trac ticket #58827.
  3. Update on the Font Library and 6.4 beta 2 from the core Slack
  4. Trac Ticket #59443 opened on performance 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. by @spacedmonkey during testing WP 6.4 beta 2. Aim is to fix is before Beta 3. The Slack message in core.
  5. Note in the Beta 2 release post there is a reference to testing beta releases using Local environment: Use wp-now to set up a Node.js-based WordPress 6.4 Beta 2 install locally. Learn more in this guide. This was discussed in core to include as it is an experimental option.
  6. Discussion on Trac Ticket #58827 that exposes the Patterns menu to classic themes. Ticket was moved to an enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature.. Reasoning is on the ticket comment. The ticket has been punted to 6.5.
  7. Discussion on a request to allow #59131 to be committed as part of 6.4 Beta 2. Discussion thread that took place in core Slack this last week and links to previous messages on the reasoning.

Font Library update

Shared by @hellofromtonya

  • The REST API part of it:
    • works and has been working well. But its design is doing it wrong.
    • it’s in the process of a redesign in collaboration with the Core REST API maintainers
    • @timothyblynjacobs @spacedmonkey@swissspidyhave been providing feedback and guidance 
    • if the redesign can get done before next Monday, then it will ship in Gutenberg 16.8
    • changes are being done in Gutenberg and the Core PR to keep them in sync.
  • It did not ship in 6.4 Beta 2 because of this redesign.
  • When could it committed into Core?
    • Expectations: Redesign gets done, ships (in the plugin), and is approved by one of the Core REST API maintainers.
    • Once all of these expectations are met, a public discussion will be opened in #core in preparation for Beta 3.
    • Only bugfixes in GB 16.8 would come into Core. Not new features or enhancements, as the editor board was cleared of those at Beta 1.
  • Font Library testing instructions were included in 6.4 Beta 2 announcement post.

Existing 6.4 useful links

Next WordPress 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.3.2

Following Dev Chat, the discussion continued regarding timing for the 6.3.2 and 6.4 Beta 3 releases. These may be discussed further in #core, but keep an eye on the #6-3-release-leads and #6-4-release-leads channels for final timings.

Help requests: Components maintainers & Tickets

No other tickets were raised in the agenda comments or after Dev Chat.

Open Floor

There was not enough time for open floor discussion today.

Next meeting

The next meeting will be on 2023-10-11 at 20:00 UTC .

Props to: @hellofromtonya for facilitating the meeting,
@webcommsat for the agenda & summary, and to @ironprogrammer for review.

#6-4, #dev-chat, #summary

Jessica Lyschik 5:20 pm on October 4, 2023  

Default Theme Chat Summary: October 4, 2023

This post summarizes the latest weekly Default Theme meeting (agenda, slack transcript), held in the #core-themes 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, on 4th October 2023, 3pm UTC.

Project Board

The project board has been updated to serve for the remainder of the time until the release and not just on a per 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. release basis. There will be some updates to the board to include the most important issues to get into Beta 3. These will be mainly 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) and 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. fix related. Some housekeeping needs to be done for the patterns, @luminuu will take on this one.

Information about the Beta 2 Image issues

Yesterday the Beta 2 for 6.4 was released. During the release party, it was encountered that there is an issue with displaying the images in the patterns that are loaded from the theme. This issue happened at Beta 1 already, but got fixed in time; for Beta 2 this was unfortunately missed. The images have been partially renamed, and moving the data from 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/ to SVNSVN Subversion, the popular version control system (VCS) by the Apache project, used by WordPress to manage changes to its codebase. causes the issue of images having a file size of zero bytes. The CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team is aware of this, the update will happen with Beta 3, coming next Tuesday (October 10).

Call for testing with child themeChild theme A Child Theme is a customized theme based upon a Parent Theme. It’s considered best practice to create a child theme if you want to modify the CSS of your theme. https://developer.wordpress.org/themes/advanced-topics/child-themes/.

There’s an issue asking for testing Twenty Twenty-Four as parent theme for a child theme and making sure patterns work as expected. It can be tested with the Create 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 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, under certain circumstances it might fail, but it was reported that it did work for others. Having 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/ plugin installed and active can help with solving issues.

#6-4 #bundled-theme #core-themes #summary #twenty-twenty-four

Abha Thakor 8:30 am on October 4, 2023
Tags: , ,   

Dev Chat agenda, October 4, 2023

(Updated with Calls under 6.4 relating to the About Page. 2023/10/4)

The next weekly WordPress developers chat will take place on Wednesday, October 4, 2023 at 20:00 UTC in the core channel of Make WordPress Slack. All are welcome.

Further items will continue to be added as they come up in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and release leads channels 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/.. This agenda was shared in draft after the 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 release to help collate information.

Welcome and housekeeping

Summary of Dev Chat, September 27, 2023 – thanks to @webcommsat @nalininonstopnewsuk @ironprogrammer

A reminder has been posted in the 6.4 release leads channel on Slack, for any discussions and/or decision making that impacts Core, to move those discussions to the #core channel. This follows a request from last week’s Dev Chat.

Announcements

WordPress 6.4 Beta 2 is available – please help test and make the release the best it can be. All details are on the post. Thanks to everyone who contributed towards Beta 2 and those who came and facilitated the release party on September 3.

Highlighted posts

Due to time constraints during a release and to prioritize 6.4 items, some of the highlighted posts may not be raised during the live Dev Chat meeting.

Hallway Hangout – working session on consolidating modes. November 15, 2023. This is part of efforts to improve 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) of the Site Editor.   

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 checker repo has moved to the WordPress organization 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/. This is for a tool for plugin developers to analyze their plugin code and flag any violations or concerns around plugin development best practices, from basic requirements like correct usage of internationalization functions to accessibility, performance, and security best practices. https://github.com/WordPress/plugin-check

Benchmark results on 6.4 Beta 1 from the Performance Team can be read on its meeting summary.

Forthcoming release updates

Next major WordPress release: 6.4

WordPress 6.4 Beta 3 is scheduled for October 10, 2023.

Calls relating to 6.4 tickets:

  • Docs and dev notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase.: component maintainers and committers. @webcommsat to share.
  • Call for feedback on the first draft of the About Page for 6.4. @estelaris has asked for comments to be left either on the 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. #59289 or in Figma.
  • A developer is needed to build/commit the About Page due to availability. In addition, to raising any hands in the meeting, please also volunteer in the 6.4 release leads channel on Slack.
  • @spacedmonkey and @antonvlasenko asked for assistance to take forward a Pull Request on Trac Ticket #56922 to try and get it into 6.4. The ticket allows 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/ team to make revisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. for template / templates parts in the editor. There is a GitHub PR 3533. More information on the call in Slack.

For information:

  • Discussion in release leads/ core has been on Trac ticket #59526 issue relating to fixing image assets with the Twenty Twenty Four theme identified during 6.4 beta 2 release party. This is likely to be fixed in beta 3. Discussion in core.
  • Discussion on the issue of non-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 access to the site editor’s pattern page, Trac ticket #58827.
  • Update on the Font Library and 6.4 beta 2 from the core Slack
  • Trac Ticket #59443 opened on performance 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. by @spacedmonkey during testing WP 6.4 beta 2. Aim is to fix is before Beta 3. The Slack message in core.
  • Note in the Beta 2 release post there is a reference to testing beta releases using Local environment: Use wp-now to set up a Node.js-based WordPress 6.4 Beta 2 install locally. Learn more in this guide. This was discussed in core to include as it is an experimental option.
  • Discussion on Trac Ticket #58827 that exposes the Patterns menu to classic themes. Ticket was moved to an enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature.. Reasoning is on the ticket comment. The ticket has been punted to 6.5.
  • Discussion on a request to allow #59131 to be committed as part of 6.4 Beta 2. Discussion thread that took place in core Slack this last week and links to previous messages on the reasoning.

Existing 6.4 useful links

Release parties schedule for 6.4

Roadmap to 6.4 – this release is scheduled for November 7, 2023.

Bug Scrub Schedule 6.4

6.4 Development Cycle

Project Board for Editor Tasks for WordPress 6.4 on GitHub

Next WordPress 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.3.2

Any update on timings can be shared in Dev Chat. Please allow follow the 6.3 release channel on Slack for updates.

Gutenberg

Tickets or Components help requests

Please add any items for this part of the agenda to the comments – tickets for 6.4 will be prioritized. If you can not attend dev chat live, don’t worry, include a note and the facilitator can highlight a ticket if needed.

Open floor

If you have any additional items to add to the agenda, please respond in the comments below to help the facilitator highlight them during the meeting.

Props to @webcommsat @hellofromtonya @nalininonstopnewsuk @marybaum and @estelaris for contributions to this agenda.

#6-4, #agenda, #dev-chat