This post summarises the weekly editor chat meeting (agenda here) held on 2023-01-25 14:00 UTC in Slack. Moderated by @get_dave.
- Please note than the RC 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). of Gutenberg 15.1.0 will be delayed to align better with the upcoming WordPress 6.2 beta (to be released on 7th of February).
- A project board for WordPress 6.2 Editor tasks is available.
Updates based on updated scope for site editing projects
The following items were shared by folks to update us on what work is in progress or where help is needed:
- primarily working on PHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher backports for WP core Core is the set of software required to run WordPress. The Core Development Team builds WordPress..
- We’ve got a nice tracking issue if anyone is interested. Please check the issue description if your username is mentioned, and let us know if you can help with backports. Tracking issue:
@paaljoachim – gave a lot of feedback to the current call for FSE testing.
@ndiego – working on Editor Triage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. for 6.2. If you see an issue/PR that you feel needs attention for the 6.2 release. Please feel free to add it to the 6.2 Project Board. We will triage from there.
The full Open Floor discussion is available on Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..
A new contributor joins us – welcome Alex
- Alex raised their hand as a new contributor and asked for guidance on getting started.
- The following advice was provided:
- @get_dave offered to be a temporary point of contact for any questions that can’t be answered in the main channel.
Ongoing value of these chats/meetings
- @paaljoachim asked if/how we can improve the value of the Core Editor meetings.
- @get_dave suggested including more of a triage session and wondered whether that would interfere with @ndiego‘s efforts.
- @poena highlighted meeting time of day as a key blocker A bug which is so severe that it blocks a release..
- @ndiego noted that the triage sessions are also suffering from low attendance. He agreed that we should consider ways to improve the value of the chat.
- @danielbachhuber suggested a better form of async meeting/scrubbing.
- @danielbachhuber also highlighted the problem that it’s hard to get product decisions and feedback if you are not:
- on a team working full time on Gutenberg.
- working on something directly related to the roadmap
Thanks to everyone who attended the chat.
#core-editor, #core-editor-summary, #meeting-notes, #summary