Performance team meeting summary 7 June2022

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

Announcements

@shetheliving

  • Huge thank you to everyone who participated in any way in our work at WCEU! Feedback was extremely positive and we have lots of new people who are interested in contributing
  • Our weekly chat is held in the #performance channel on Tuesdays at 15:00 UTC and our GitHub repo is here; feel free to take a look at open issues and add new issues
  • You can watch @flixos90‘s talk from WCEU here

Focus group updates

Images

@adamsilverstein @mikeschroder

GitHub project

Feedback requested

Object Cache

@tillkruess @spacedmonkey

GitHub project

Feedback requested

Site Health

N/A

GitHub project

Feedback requested

Measurement

N/A

GitHub project

  • We’re seeking 1-2 POCs for this group; if you’re interested, please comment here or ping in Slack
  • No updates

Feedback requested

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/.

@aristath @sergiomdgomes

GitHub project

  • @aristath (async): Working on ways to apply some tree-shaking to blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. styles. Created a proof of concept in Tree-shaking block styles on the frontend #41020 and would appreciate feedback. Also working on an alternative method which would not require 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. changes to block.json, but worried about server-side performance. Current implementation in the POC is far from perfect but enough to be a good conversation starter to move this forward.

Feedback requested

Infrastructure

@flixos90

GitHub project

Feedback requested

Open floor

  • @clarkeemily: Working on collating photos and stories from WCEU and will share with the wider group soon

Help wanted

#core-js, #core-media, #performance, #performance-chat, #summary

#hosting-community

Editor Chat Summary: June 1st, 2022

This post summarizes the weekly editor chat meeting (agenda here) held on 2022-06-01 14:00 UTC in Slack. Moderated by @andraganescu.

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/ 13.4 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).

The 13.4 RC version of Gutenberg was released on June 1st by @priethor. Check it out here.

WordPress 6.1

It’s time to focus on the 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. of WordPress, version 6.0.1. It already has a project on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ concerning fixes and backports from Gutenberg.

Key project updates

Task Coordination

@andraganescu

@hellofromtonya

  • I’m working on wrangling web font needs to support 6.1 tasks. First step is to create a single epic issue that shares the vision (from Matías), a list of open work, prioritizations, and status.
    • Goal is to have this epic ticketticket Created for both bug reports and feature development on the bug tracker. available this week

Open Floor

Announcements, questions and discussions.

@mdxfr

Asked about support for current-menu-ancestor in the navigation 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..

@mdxfr

Asked about how to quicken the landing of gutenberg fixes/improvements (already made within 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) into coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. through minor releases?

  • @andraganescu suggested  labeling with Backport to WP Minor Release merged PR’s that should sooner into core and monitoring the WordPress 6.0.1 project on GitHub
  • @hellofromtonya suggested to bring this topic to the weekly Core DevChat for broader discussion on how to do faster, more frequent minor releases to ship fixes faster.

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

Editor Chat Summary: May 25, 2022

This post summarizes the weekly editor chat meeting (agenda here) held on 2022-05-25 14:00 UTC in Slack. Moderated by @zieladam.

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/ 13.3

The 13.3 version was released on May 25th by @welcher. Find out more in the What’s New in Gutenberg 13.3.0 post.

WordPress 6.0

The long-awaited WordPress 6.0 stable version has been released this Tuesday!

The highlights include:

  • Enhanced Writing Experience
  • Style Switching
  • More Template Choices
  • Integrated Patterns
  • Additional Design Tools

Key project updates

Task Coordination

@amustaque97

@mamaduka

  • I’m mostly doing PR reviews last couple of days

@isabel_brison

  • I’ll mostly be migrating flaky e2e tests to Playwright this week

@zieladam

@welcher

@ntsekouras

  • I’ve started the work for expanding the templates in site editor. The first part will be for custom post types and their archive pages.

Open Floor

Announcements, questions and discussions.

@markhowellsmead

Asked about the motivation behind moving coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. CSSCSS Cascading Style Sheets. inline.

This change has directly lead to many specificity problems, not least that it’s very difficult (and somtimes impossible) to override inline styles using rules in external CSS files.
Ref. https://github.com/WordPress/gutenberg/issues/38719
Ref: https://github.com/WordPress/gutenberg/issues/40159

Mark and other theme developers have seen feedback that hints how editor devs (in some cases) don’t want to “allow” others to modify layout or logical decisions through the use of code in themes or plugins. By blocking access to allow themes and plugins to override what should be simple core CSS rules, we’re being forced towards a complete deactivation of core CSS in some projects.  It’s admirable to release devs from the burden of basic CSS by way of the Style Engine, but there are limitless requirements for custom-built themes which neither belong in core, nor which can be solved by a generic 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..

@amustaque97

Asked whether https://github.com/WordPress/gutenberg/issues/40809 is 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. or enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature.. @zieladam thought it was a bug since it reports a mismatch between the editor and the website.

@welcher

Asked whether anyone is aware of any commits that need to be cherry-picked.

@manfcarlo

Reported that https://github.com/WordPress/gutenberg/issues/29484 is currently closed but it needs to be re-opened. The issue has been reopened since then.

@greenshady

Requested feedback on https://github.com/WordPress/gutenberg/issues/41324. The vertical alignment options for Row and Buttons (flex) blocks is always centered on the front end, even when choosing something like top alignment. This seems to be an issue with WordPress 6.0 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". but not with Gutenberg 13.2.2 active.

@bph

Proposed a theme.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. ‘allow-list’ to limit the number of patterns offered to the users through the patterns directory.

To get more details go directly to the Open Floor discussions 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.

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

Dev Chat Summary, May 25, 2022

Agenda followed for the weekly WordPress Developers Chat. The meeting was facilitated by @annezazu.

Start of the meeting in #Core 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/..

2. Announcements

  • WordPress 6.0 “Arturo” was released yesterday! Big props to all involved.
  • The dry run for the WordPress 6.0 Release took place on May 23, followed by a 24-hour code freeze.
  • WordPress 6.0 RC4 was released over the last week on May 20, 2022.

If you haven’t seen it yet, here is a great video covering the latest release:

If anyone is wondering how that amazing video was made, it is a combination of Figma storyboards and motion design in After Effects.

3. Blogblog (versus network, site) posts of note

  • 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/ 13.3 is in the process of being released today as we speak.
  • The latest core editor improvement post on container blocks and blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. locking shows off some new features to explore with row/stack/group.
  • A recap of the latest hallway hangout happened this morning on FSE topics and might be of interest to folks here.

Next week, there will be a doubled up version of “This week in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.” too.

4. Upcoming releases

With 6.0 just out the door, the focus turns to both 6.0.x and 6.1. Initial steps have been taken following the post release items in the handbook so stay tuned for more! Currently, a project board is open for 6.0.1 in case anyone likes to follow the details: https://github.com/orgs/WordPress/projects/31

There is only one reported issue so far and @annezazu, as co-release coordinator will be checking with other teams for any other issues reported with 6.0.

5. Component maintainers

Build/Test Tools reported by @sergeybiryukov:

  • GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ Action Slack notifications now link to a specific run attempt. This makes it easier for someone to see the proper context of a specific notification in case of failure. See ticketticket Created for both bug reports and feature development on the bug tracker. #55652 for more details. Thanks @desrosj
  • Some instabilities (test leaks) were fixed in unit tests for comments. See ticket #54725 for more details. Thanks @hellofromtonya
  • General: The recommended minimum version for MariaDB was bumped to 10.3. See ticket #55791 for more details. Thanks @hellofromtonya, again! 
  • Date/Time, 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., Permalinks: No major news this week

Update/install reported by @afragen

Sitemaps component reported by @pbiron:

  • There is one ticket ready to commit for 6.1, #55633

6. Open floor

@audrasjb prepared some great stats on WordPress 6.0 contributors.

@hifidesign brought up a PR that documents pretty big 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. w/r/t to unnecessary duotone code being added to non-FSE themes #38299 and @annezazu mentioned that all of the work is being tracked in that ticket for anyone to follow up.

@afragen has a list of tickets that need a committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. review:

@pbironmentioned that the non-direct filesystem classes are difficult to test because it is often hard to set up a testing environment to test them. There is a proposal on the works to do a review/improvements of the various WP-Filesystem classes.

Props to: @estelaris for writing the summary and @annezazu for reviewing.

#6-0, #dev-chat, #summary

Performance team meeting summary 24 May 2022

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

Announcements

@shetheliving

  • Reminder: No meeting next week, 31 May, as many folks will be traveling/prepping to travel to WCEU
  • We’ll be well-represented at WCEU with three talks and a large section of the WP community booth; see this doc for details and info on contributing
  • Bethany will be offline 1-15 June and @clarkeemily will run the 6 and 13 June meetings

Focus group updates

Images

@adamsilverstein @mikeschroder

GitHub project

  • @adamsilverstein: Finishing up some WebP issues, primarily around handling edit and restore actions correctly. Several multi-mime type/WebP features 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 were not in the 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. yet, so working on follow-up core patches to add them. For example, this patch adds the ability to always use the smaller image size for image references. Also did some research this week on a polyfill to enable WebP support for older browsers and developed a script to use a capability check before dynamically loading the library to add support. We also have sent out a survey to hosting providers about image storage to get more data about the impact of WebP on storage.
  • @pbearne @spacedmonkey: Add low quality image placeholders #19 should be ready to merge (example)
    • @adamsilverstein will take another look and @shetheliving will make sure @flixos90 does when he’s back online
    • @adamsilverstein: Since this is a proposed core patch, is there already a matching 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.?
    • @pbearne @spacedmonkey: No; that is a wider conversation about porting over functionality to core and when/how this should happen (and how/if we remove it from the plugin)
    • @shetheliving: We’ll add this to the 6 June meeting agenda cc @clarkeemily

Feedback requested

Object Cache

@tillkruess @spacedmonkey

GitHub project

Feedback requested

Site Health

N/A

GitHub project

  • We’re seeking 1-2 POCs for this group; if you’re interested, please comment here 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.” 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/.
  • @furi3r: Add Site Health test for full page caching (advanced cache) #220 was moved to 1.2.0 is just about ready and waiting for testing. Need to determine how/if we want to port any existing Site Health modules to core.

Feedback requested

Measurement

N/A

GitHub project

  • We’re seeking 1-2 POCs for this group; if you’re interested, please comment here or ping in Slack
  • No updates

Feedback requested

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/.

@aristath @sergiomdgomes

GitHub project

  • No updates

Feedback requested

Infrastructure

@flixos90

GitHub project

  • @flixos90 offline
  • @shetheliving: If you haven’t already, review the module proposal workflow and leave any feedback on the PR. Next step would be to merge this and create a new GH issue template for module proposals.
  • @shetheliving: Reminder that next release will be 1.2.0 on Monday, June 20, so we should target merge for anything for that release by about June 15.

Feedback requested

Open floor

  • @spacedmonkey: Is there anything we want to specifically focus on for 6.1?
    • @olliejones: Maybe more/better large-site performance increases? WHERE wp_usermeta.meta_key = 'wp_capabilities' AND meta_value LIKE '%editor%' is the performance botch; ticket here. Probably needs another because this one mentions 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/, but problem also exists in Users, Posts, and Pages.
    • @clorith: Query improvements for 6.0 were nice and don’t look large, but it all adds up quickly, so would love to see more of a review of queries and how they can be improved. May be some old ones from years back where smarter queries now exist.
    • @spacedmonkey: Would focus on SQL_CALC_FOUND_ROWS is deprecated as of MySQL 8.0.17 #47280
    • @pbearne: Have been digging into the rest and FSE queries are seeing a lot of low-hanging fruit that could be improved

Help wanted

#core-js, #core-media, #performance, #performance-chat, #summary

#hosting-community

Dev Chat Summary, May 18, 2022

Update May 23, 2022 @webcommsat: the 6.0 Release Party will take place on May 24, 2022 at about 18:30 in the #core 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/.. Find out more about what happens on the day and join in the testing.

Agenda followed for the weekly WordPress Developers Chat which included updates on the 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.0. The meeting was facilitated by @marybaum and @webcommsat

Start of the meeting in #Core channel on the Make WordPress Slack.

2. Announcements

WordPress 6.0 RC3 is available for testing (released May 17, 2022). Since the RC1 release on May 3, 2022, there have been approximately 50 issues resolved in Gutenberg and Trac. Thanks to everyone involved and people who came along to test at the release party.

3. Blogblog (versus network, site) posts of note to coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.

A Week in Core – May 16, 2022  – thanks to @audrasjb.

What’s New in Gutenberg 13.2 (May 11, 2022.)

New free resources on Learn WordPress published in April 2022. Please help share.

4. Upcoming releases

Next major release: WordPress 6.0

Update

@annezazu : 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). 4 is planned for Friday May 20, 2022, with the Dry Run still slated for May 23, 2022 and the final release for May 24, 2022. Everything is on track, including a 6.0 video.

Update post-dev chat from the release co-ordinators:

You’re invited to the 6.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). 4, Dry Run, and Final Release Parties. Each party will aim to be held at 16:00 UTC in #core channel on Slack.

  • RC4 on May 20, 2022 (Friday)
  • Dry Run on May 23, 2022 (Monday)
  • Final Release on May 24, 2022 (Tuesday)

Final Release on May 24, 2022 (Tuesday) will happen 24 hours after the Dry Run completes. This is part of a true 24-hour code freeze. This means it will likely start more around 17:00 UTC assuming all goes well with the dry run. Please check #core and 6.0 release leads slack channel for any updates.

Recap of useful resources on 6.0

We share this expanding list every week in dev chat in the run up to the release, particularly to help those new to dev chat or those coming to find out about the release. If you have items for it, please  let us know on the agenda or during in the meeting.

Early bug schedule for 6.1

Release update relating to Learn WordPress and associated docs

@webcommsat: A cross-team update on where we are with training and Learn WordPress, and mapping this with end user on documentation and other opportunities for the release.

We have completed an extensive review (link to the full update in the #training channel on Slack) on where things are on the Learn WordPress side for 6.0, and will be continuing with the mapping and linking with end user documentation. There are a number of high priority items that need some further assistance for Learn WordPress.

If you are able to help with this, please add a comment in the #training Slack and with what you might be able to help with. We have put together some help for any developers / those familiar with the release who are able to help with this who are new to using the Learn WordPress side.

Thanks to Training, Documentation, Core and wider who have collaborated on this over the last weeks, and in advance as the work continues post release day too.

5. Open Floor

If you are a component maintainer or running 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. scrub and have any updates not already mentioned under 6.0 updates, you can raise them in this section too.

a) Component maintainers – items of note

Update from @sergeybiryukov

Build/Test Tools, Date/Time, General, 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., Permalinks:  No major news this week. 

b) 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. Europe 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/., June 2, 2022 – core tables.
@desrosj is bringing this together for the core tables at the event. Core will share an update on this hopefully next week. If you can volunteer to help on the day, contact @desrosj.

Props to: @estelaris for writing the summary, @webcommsat, @marybaum and @annezazu for reviewing.

#6-0, #dev-chat, #summary

Editor Chat Summary: 18th May 2022

This post summarises the weekly editor chat meeting (agenda here) held on 2022-05-18 14:00 UTC in Slack. Moderated by @get_dave.

Status Updates

Task Coordination

The following items were shared by folks to update us on what work is in progress or where help is needed:

@noisysocks:

@manfcarlo (not present – shared by @paaljoachim):

  • I want to draw attention to Page Break block ( core/nextpage ) not working as expected.
  • It was patched in January but there are some problems with the 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. that will need to be re-patched.
  • Details are in the latest comment on the issue.

@mamaduka – I got sidetracked with shiny new issues, but I plan to continue working on 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. Locking feature.

@vcanales:

  • I’ve created a draft PR with a small proof of concept on creating random color palettes in 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. Styles panel, with colors that work well together in terms of legibility.
  • It’s very early on, but I’ll be updating that PR with whatever issues I can surface. I’ll also come back every week to ask for input

@get_dave:

@tomasz:

  • I wanted to call for a review of Search Block extensibility: search query vars (now merged).
  • I would really appreciate a review of the proposed implementation as this would enable our team at Woo to provide more contributions around the Search Block if we could rely on this extensibility feature.

@zieladam:

  • I’ve been working with @gziolo on merging 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/ changes into the WordPress 6.0 release 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 RC3 was released yesterday as @get_dave mentioned, next stop: RC4 and a stable version next week.
  • I’ve shipped [Gutenberg Data Tutorial] Part 4: Creating pages
  • I’ve proposed Typescript Entity configuration types – the last blockerblocker A bug which is so severe that it blocks a release. before shipping TypeScript types for getEntityRecord and other coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-data selectors for a great  autocompletion experience

@glendaviesnz (not present – shared by @paaljoachim):

  • There have been some requests for the addition of spacing presets in Gutenberg, similar to the font size presets that are already available, to allow theme designers to specify a select list of spacing values that can be applied to blocks.
  • It would be good to get some design feedback on this, in terms of the feasibility of adding this to the UIUI User interface, and how the UI for this might be structured.
  • I think there has been some ongoing discussion about the suitability of the current UI for selecting the font size presets, so would be good not to repeat any problems that might exist there.

Open Floor

The full Open Floor discussion is available on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..

Right click action on List View (and in wider editor)

  • @andrewserong would like to surface this PR which explore adding right click behaviour to the List View.
  • He’d love feedback on whether overriding the native right click behaviour is something we want to do in Gutenberg.
  • @get_dave, @zieladam and @mamaduka were in favour so long as it considered a11yAccessibility 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) concerns.
  • @paaljoachim had reservations around discoverability.
  • It was noted that @alexstine had already provided a11y feedback and an opt out via editor settings has been added to the PR.
  • @hypest also noted that it should consider mobile interactions as well.
  • Agreed to leave further feedback on the Issue/PR itself.

Request for feedback: enabling styling of interaction states in editor

  • @get_dave wanted to surface these design explorations on enabling styling of interaction states (:hover, :focus .etc) within the editor.
  • Now is a good time to provide feedback and raise concerns in order that the first iteration of the interface can be as good as it can be.
  • Folks were broadly in favour of this functionality being added.
  • @fabiankaegy was concerned about adding a lot of additional clicks to every interaction – felt this would be better served with a persistent setting instead of a local state in every component.
  • @get_dave requested input from folks experienced with Global Styles and Theme JSONJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. to discuss the potential data structure for such a feature.
  • @tomasz noted it would be nice to have a full overview of the state ie. color + typography etc. rather than split between different panels. A summary would avoid having to keep a mental map in your head of all interactions.
  • Please continue to discuss on the Issue.

Breaking change: promoting experimentalFetchLinkSuggestions to stable 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.

  • @get_dave would like to flag a PR which renames a long-standing experimental API to stable.
  • There’s been lots of discussion around experimental APIs and the deprecation strategy recently, so I wanted to flag this one final time before it gets merged.
  • Hopefully the impact is minor but it’s worth being aware of as it’s been around as __experimental for quite some time.
  • Noted that outreach has been done to community Plugins making use of the API.
  • Will merge this week unless there are any blockers raised.

Thanks to everyone who attended the meeting.

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

Performance team meeting summary 17 May 2022

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

Announcements

Focus group updates

Images

@adamsilverstein @mikeschroder

GitHub project

Feedback requested

Object Cache

@tillkruess @spacedmonkey

GitHub project

Feedback requested

Site Health

N/A

GitHub project

  • We’re seeking 1-2 POCs for this group; if you’re interested, please comment here 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.” 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/.
  • @furi3r: Add Site Health test for full page caching (advanced cache) #220 was moved to 1.2.0 is just about ready and waiting for testing

Feedback requested

Measurement

N/A

GitHub project

  • We’re seeking 1-2 POCs for this group; if you’re interested, please comment here or ping in Slack
  • No updates

Feedback requested

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/.

@aristath @sergiomdgomes

GitHub project

  • No updates

Feedback requested

Infrastructure

@flixos90

GitHub project

  • @shetheliving: Review the module proposal workflow and leave any feedback on the PR
    • @flixos90: We’ve been working on this to have a long-term plan for each module; want to avoid a module going into the plugin and growing stale without any iterations or next steps
    • @jeffpaul: I’ll review with an eye from the core perspective
    • @flixos90: Another benefit of this documentation is that it includes a high-level overview of how to propose a feature project for core, which isn’t really documented right now; this could be a good starting point for the future
  • @olliejones: Might be cool to have a stub performance-lab module for modification by would-be contributors
    • @flixos90: That’s a great idea, though there would be little to start with since a module can be pretty much anything. The best place to start right now is with the writing a module doc, though that’s more about the technical starting point and the new proposal doc is more about overall workflow.
  • @flixos90: Released v1.1.0 yesterday. Next release will be 1.2.0 on Monday, June 20, so we should target merge for anything for that release by about June 15.

Feedback requested

Open floor

  • @olliejones: Following up on the large site/many users work: https://core.trac.wordpress.org/ticket/55749
    • Have a new plugin to address the issues outlined there
    • Might be a candidate for a Performance Lab module
    • These issues are mostly fixable with filters and actions, but not completely
    • @adamsilverstein: Looks like a core side issue; 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. describes hte issue better. Is the issue specific to the REST endpoint or more generally about how the user query is constructed?
    • @olliejones: It’s actually central to WP_User_Query and WP_Meta_Query, but at the same time the REST endpoint’s set of parameters doesn’t allow for avoiding the query-pagination overhead

Help wanted

#core-js, #core-media, #performance, #performance-chat, #summary

Editor chat summary: 11 May, 2022

This post summarizes the weekly editor chat meeting (agenda here) held on Wednesday, May 11 2022, 03:00 PM GMT+1 in Slack. Moderated by @paaljoachim.

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 releases

Gutenberg 13.2 released 11 May.
Whats new in Gutenberg 13.2.

WordPress 6.0

WordPress 6.0 Project board
Project board for Dev Notes
Help Wanted: Test WordPress 6.0

Key project updates

Task Coordination

@amustaque97

I will be looking into issue: Post Comments block: Whitespace on top of warning message

@tomasztunik

A while ago I’ve shared a core Search Block extensibility feature request to give the ability for 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. variations to provide custom search query parameters. Since then I’ve also shared a proposed implementation and I’d love some feedback. This would allow projects like WooCommerce or other projects that introduce custom post types to re-use the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. search experience to provide custom search components for their extensions.But it would also allow creating custom searches for core WordPress experience ie. searching only within specific categories, tags or authors.

Open Floor

Announcements, questions and discussions.

@annezazu

I’d like to start a discussion around adding a new label to the new label to the Gutenberg repo around issues that impact adoption. The aim would be to have an easier way to see, at a glance, what big issues are impacting the adoption of Gutenberg.

  • Would folks find value in having those issues clearly communicated?
  • Does a new GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ label seem like the right approach? If not, what other approaches would work well?
  • If a new GitHub label works well, what name would work best?

Here are a few suggestions:

  • [Type] Adoption Blockerblocker A bug which is so severe that it blocks a release.
  • [Type] Impacts Adoption

@marybaum
I like Adoption Blocker.
Could also make it active: Blocks Adoption.
@fabiankaegy
I also like the idea of that. Though it is difficult to really gauge the actual impact it has on the party that is blocked from adoption. I guess I’d like to understand what requirements a ticketticket Created for both bug reports and feature development on the bug tracker. needs to fulfill in order to “justify” getting that label applied.
@tomasztunik
I think if people had this at the back of their heads when triaging issues or evaluating feature requests this could shift the perspective toward the product and ecosystem more than the problem itself. Like another “standard” question to ask yourself when evaluating something.
@priethor
This is an example of an issue that would need that label: something already existing in WP but that Gutenberg doesn’t support, preventing Gutenberg adoption and users needing to stick with classic implementations:
https://github.com/WordPress/gutenberg/issues/3144
@mikachan
Another alternative for the label itself could be ‘migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. blocker’ (or ‘impacts migration’ / ‘blocks migration’).

@ndiego

This is a thought-provoking question that I asked earlier in #6-0-release-leads (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/.). When we fix bugs in Gutenberg (and also in Core), they can have unintended consequences when users upgrade to the new versions where the bugs have been fixed. Thought I would share it here as well.

To get more details go directly to the Open Floor discussions in the Core Editor Slack channel.

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

Dev Chat Summary, May 11, 2022

Agenda followed for Dev Chat for the weekly WordPress Developers Chat which included updates on the 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.0. The meeting was facilitated by @marybaum and @webcommsat.

Start of the meeting in #Core Slack

2. Announcements

WordPress 6.0 RC2 is available for testing (released May 10, 2022). Since the RC1 release on May 3, 2022, there have been approximately 40 issues resolved in Gutenberg and Trac. Thanks to everyone involved and people who came along to test at the release party.

Gutenberg 13.2 has landed!

Early bug schedule for 6.1 – thanks @costdev. Note change of day – these will now happen on Thursdays 18:00 UTC and not Mondays.

3. Blogblog (versus network, site) posts of note to coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.

A Week in Core – May 9, 2022 (published May 11, 2022) – thanks to @audrasjb

Performance Team Meeting Summary, May 10, 2022 – includes some updates on WebP, some POCs needed for the Site Health and Measurement sub groups. At the end of the post, there is a list of areas where help is needed.

Open floor item in the Editor Chat agenda for May 11, 2022 on a discussion around adding a new label to 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/ repo around issues that impact adoption. The aim would be to have an easier way to see, at a glance, what big issues are impacting the adoption of Gutenberg.

Full Site Editing Program Testing Call 14 – Rallying Recipe Reviewers. Deadline for feedback: 18 May 2022

4. Upcoming releases

Next major release: WordPress 6.0

Updates

Update via @annezazu
No big updates to share on 6.0 — the release squad is really crushing it and things are moving forward as expected. Some quick updates to be safe though:

  • The 6.0 video continues to progress nicely and is on track to ship the day before the release still.
  • Props are in progress thanks to a wonderful effort by @desrosj.
  • A 6.0.1 board has been started so we carry momentum into the point 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.https://github.com/orgs/WordPress/projects/31

Thank you to everyone who is making this release possible. Please keep testing and, if you can’t, encourage others to do so. It all helps.

Update via @costdev on bugs scrub and testing side: Monitoring new tickets regularly and things are going well.

6.0 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). 3

6.0 RC3 Release Party on May 17, 2022, 16:00 UTC
Meet in the #core 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. As always with releases, there’s a chance this time may change the day of depending on how things are progressing. The time will be communicated across channels (#core-editor#6-0-release-leads, and in #core). All welcome.

The next major 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 before RC3 will be on Thursday May 12, 2022, 21:00 UTC. The full bug scrub schedule for 6.0

Recap of useful resources on 6.0

5. Open Floor

If you are a component maintainer or running a bug scrub and have any updates not already mentioned under 6.0 updates, you can raise them in this section too.

a) Component maintainers – items of note

Update from @sergeybiryukov
Build/Test Tools: The local development environment can now run on Apple M1 machines without requiring local configuration changes. Ticketticket Created for both bug reports and feature development on the bug tracker. #52356 for more details.

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.: An edge case was fixed in the script loader where the dependency order was incorrect for scripts with translations in some cases. Ticket #55628 for more details.

General, Date/Time, Permalinks: No major news this week. 

b) 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. Europe 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/., June 2, 2022 – core tables.
Update from @desrosj: If anyone will be at WCEU Contributor Day and has a specific topic they would like to focus on for the day at the Core tables, please share the topic and a brief one or two sentence description by Friday. I have a few generic topics, but if anyone is looking to lead specific discussions, please send them over!

@marybaum: later in the summer, there will be similar planning for WordCamp US.

c) Rubber duck emoji request! It all happens at dev chat!

d) @clorith brought up Ticket Gutenberg 40316 and the issue of experimental APIs versus backward compatibility. A lively discussion followed, with several suggestions on how to get input from the community at large. (Note from Core Team repTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. @marybaum: If you’re new, dev chat is not a forum for making final decisions. But it is a great place to surface topics that warrant wider discussion, and to explore where those conversations should start).

Props to: @webcommsat for writing the summary, @marybaum and annezazu for reviewing.

#6-0, #dev-chat, #summary, #week-in-core