Editor chat summary: Wednesday, November 30 2022

This post summarizes the weekly editor chat meeting on Wednesday, 30 November 2022, 04:00 PM GMT+2 held 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/.. You can view the full transcript here.

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

Gutenberg 14.6.1 was released on Nov. 25
Gutenberg Plugin 14.7 RC1 was released on Nov. 30, 22

Key project updates

The latest update on all the phase 2 issues was also posted by @annezazu

There are three tickets that still need dev help:

Task Coordination

@bernhard-reiter shared an issue that needs help getting reproduced. This was discussed more in the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. devchat:

We’re currently investigating the .is-layout-flex issue. I’ve suggested a strategy to test our tentative fix and ship a WP 6.1.2 point version that I’d like to discuss during that chat later tonight. If you’d like to help out or if you’re otherwise interested, please join the devchat in about 5.5 hours! (If you can’t make it, feel free to leave your comments below mine, or at the GitHub issue.) Thank you! ❤️

Open Floor

We spend the entirety of the open floor discussing ideas on how to make the core editor chats more valuable and engaging. Over the past year, we’ve seen less engagement and participation. So we think it’s time to rethink the format of these chats.

@get_dave, @bernhard-reiter, @bph, @priethor, and @daisyo all shared great ideas and insights. You can view the full conversation in slack.

The ideas we came up with during the open floor are:

  • Better updates on Key projects
  • Key contributors in the room
  • Get help/volunteers for small-scope projects
  • Dive into a specific feature every week so that more folks not actively working on it can give it a spin, provide feedback, and, in general, unblock it with broader testing
  • A more informal, less structured meeting, more like office hours
  • Improving collaboration with folks on what I’m working on

@daisyo summarized it nicely:

When we try to cover everything that is being worked there is never enough time to go deeper in this meeting. Compiling the conversation today I’d suggest a Weekly featured project that’s predetermined and that someone deeply knowledgeable about the history, current status, and planned future can share. This would require some coordination and preparation ahead of time, of course, and it could be that it’s not possible to do every week.

It could also end up being a forced march that nobody wants to volunteer for. In which case there is something to be said about throwing a topic (like how do we make these meetings more engaging) out and see if it resonates enough to start a conversation.

What would YOU want to get out of a core-editor meeting, that will make you come back every week for an hour?

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