Editor chat summary: March 15th, 2023

This post summarizes the weekly editor chat meeting (agenda for March 15th meeting) held on  Wednesday, March 15, 2023, 03:00 PM GMT+1. in Slack. Moderated by @bph

Announcements & Links

Key project updates


posted an update on the Phase 2 Overview Tracking Issue (Update March 13, 2023) (Sorry, I overlooked it for the meeting)


posted an update from the Mobile team

Task Coordination


commented on the agenda post: “I’m seeking feedback on some proposals to preload Navigation Menus and Template Parts (server side) in order to improve the perceived editor load times.It does involve certain compromises and assumptions which I’d like to discuss in more detail and also find more concrete evidence for. Any help much appreciated.”

Open Floor


commented on the agenda:  “I vote to improve the perceived load times on the Browser Mode + also on the “back to WP adminadmin (and super admin) menu” action (when clicking on the site logo on top left) !!! (here on FF it is very slow, i did not test on Chrome)….”  @ndiego suggested you create new GitHub issue, detailing exactly what you are seeing . In his experience, slowness in the Site Editor that is exacerbated by third-party plugins, so it would be good to also understand the setup you use.


“As everyone is aware, we have a LOT of open issues and PRs 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/ repo. The Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. team does a fantastic job, and @mamaduka and I have been running weekly 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. scrubs here in #coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-editor. Yet, the number of open items continues to rise. After the 6.2 release, I will be spending some time thinking about how we can better tackle this situation, but I did want to also call attention to a discussion started by @tomjdevisser 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/ Discussion: “Auto-closing inactive issues to shift focus towards important issues” If you have time to provide feedback or thoughts, it would be much appreciated.”

Here is a post from two year’s ago. Stale Issues in Gutenberg Repository  but with no solution/decision.

@hellofromtonya contributed how it is handled in TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.

“In Trac, there are 2 ways it’s handled:

  • Add a close keyword with a comment that it will be closed in x amount of time without reporter follow-up.
  • Or close with a reason and a comment to re-open if more information is available for further investigation or consideration.

This is a manual ticketticket Created for both bug reports and feature development on the bug tracker.-by-ticket triage process” She clarified further: “The close keyword with message gives all who previously contributed to the ticket the opportunity to revive it. If they are still interested in it, it invites them back while also setting the expectation that it will be closed otherwise.”

You can read throught the comments in the meeting following the message

Meeting participants were asked to contribute their ideas to the GitHub Discussion: “Auto-closing inactive issues… “ as well.

Props to @paaljoachim for review

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