The weekly WordPress developers chat followed this agenda. @marybaum and @webcommsat facilitated.
Link to start of meeting on the Make WordPress 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/. core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. channel.
The last meeting happened May 25, 2022. If you’re new to the chat or would like some perspective, you can check out its dev chat summary. The Core Team reps and 6.0 release leads skipped the June 1 meeting in favor of live events at the WordCamp 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 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/..
WordCamp Europe 2-4 June 2022! In Porto, Portugal!
Lots of conversation, lots of catching up happened at the first live WordCamp in more than two years. Over the next several weeks, look for more discussions (and some proposals on doing things better) as they emerge from conversations that happened in Porto.
@matveb has been thinking about the Gutenberg 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/ roadmap. He posted this view of how that should affect planning for the next major release, which is version 6.1.
Gutenberg 13.4 has landed! (June 8, 2022)
What’s New in Gutenberg 13.4 – post published June 10, 2022
3. Blog (versus network, site) posts
Co-host @webcommsat shared these important posts for the community to digest:
A week in core, June 6, 2022 from @audrasjb
Editor chat summary, June 1, 2022
Gutenberg 13.4 Release Candidate 1 – June 1, 2022
4. Upcoming releases
Version 6.0 landed in late May 2022. The next major 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. will be 6.1.
The next minor 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. will be 6.0.1, and it needs release co-ordinators and a schedule.
Editor Chat Summary – June 8, 2022
6.0.1 Editor Tasks project board
@priethor sent the group the following updates:
- Gutenberg 13.4 stable has been released (the release post will be published later this week).
- In an effort to shorten cooldown periods that happen after each major release, Block 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 contributors have kept pushing forward bug 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 ever since the 6.0 feature freeze. Thanks to this, there is already a handful of patches ready for an early 6.0.1 release; nothing fixed is urgent, but all things combined can make for an impactful minor release.
- The first thing these minor releases need is people to run them – a Core tech lead and an editor lead. You can raise your hand in the core slack channel or contact @priethor, @annezazu (the release leads for 6.0) @audrasjb or @marybaum (the Core reps) privately.
- Last, but not least, I [@priethor] would like to remind folks that the 6.0 release retrospective will still be open until June 19, 2022. Please provide your feedback by filling out the survey or in a post comment.
Message from @jeffpaul:
With 6.0 behind us and 6.1 in the planning stages I had a question about things likely more in the 2023+ time frame that have been asked to me privately but that I have no answers for and am hoping folks in dev chat might be able to chime in. Specifically editor collaboration. Is there any update on the plans on that phase of Gutenberg (with https://github.com/WordPress/gutenberg/pull/23129 & https://www.multidots.com/multicollab-editing-commenting-plugin-for-wordpress-gutenberg/ being the only two examples I know of so far on that route)?
Early Bug Scrub schedule for 6.1 – thanks to everyone who has been contributing to and to @costdev and @audrasjb for leading these.
Link to Slack – info on 6.1 earlies bug scrub on June 8, 2022
5. Core contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org.
- Proposed: A sprint to help update the Core Contributor Handbook on Monday June 20, 2022. Save the date. More details in a P2 A free theme for WordPress, known for front-end posting, used by WordPress for development updates and project management. See our main development blog and other workgroup blogs. post and a spreadsheet to help async contribution to follow. If you would like to help with this, or you have a page of the handbook you would like to focus on, please contact @marybaum and @webcommsat who are pulling together some of the resources and links. Help for the sprint or preparing for it are welcome.
- WordCamp Europe contributor day update (more updates will to come; some people are still travelling from the event).
@webcommsat shared that lots of new people came to the core tables and to help work in cross-team areas. Thanks to @desrosj for organizing the core tables and all who helped lead areas of work or contributed. The group in Porto, and their online contingent, also did some cross-team work among core, documentation, training, community and marketing. More on this next week.
- Next new Core contributor meeting: if you’re new to the channel or you’re here from WCEU. @sergey talked a little about the New Contributors meeting that happens every two weeks in Core channel on Slack, before dev chat. The next one happens in two weeks, on June 15, at 10:00 UTC. A new contributor session an hour before the dev chat on June 8 (link to it on Slack), the next one will take place in two weeks, on June 22, 2022 at the same time (19:00 UTC).
WordPress Core Contributor Handbook FAQs to help new contributors to get started.
6. Open Floor
- @marybaum opened with a call to component maintainers.
- @sergeybiryukov highlighted tickets #55852, which makes
sanitize_url() the recommended function for sanitizing URLs instead of
esc_url_raw() , and #55194, which makes
wp_rand() work more like
mt_rand(). The full transcript of @sergey’s report.
- @sergeybiryukov invited anyone interested in making plugin 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 and theme updates in WordPress more reliable to test and leave feedback on the Rollbacks PR: https://github.com/WordPress/wordpress-develop/pull/2225.
- From next week, reaching out to component maintainers will restart to find out if there are any updates or blockages that can be raised in dev chat. Please do add to the weekly dev chat agenda too or message @marybaum and @audrasjb if you have a particular issue. If you are interested in helping with a component, you can also reach out to them.
Follow up on discussion started in the Core editor Slack channel, about how to land WordPress minor releases faster and more often. The full discussion.
@sergeybiryukov highlighted the feedback on these posts:
- Might be worth opening the discussion around minor release cadences to seek feedback on pain points and opportunities to potentially do a trial run.
- The minor release schedule is flexible and can happen quickly as needed. Having a Core + Editor representation on the minor release squad provides the balance to make the decisions to go fast when needed and slow when not needed.
- That mashup / pairing of Core and Editor leads leading the minor happened in the 5.9.x cycle. Might be worth doing it again in the 6.0.x cycle.
- I’m not aware of anything that slows dow or bottlenecks minor releases. My impression is the minor release squad makes those decisions.
Possibly an idea is to:
- monitor for pain points and bottlenecks during the 6.0.x minor cycles.
- then do a retro afterwards to gather feedback
- then refine the approach in the next cycle.
- The retrospective and refinement are not new. Done after each cycle. But in this cycle, it could be an underlying project (or whatever to call it) of seeking process improvements. (edited)
The next Dev Chat meeting will take place on June 15, 2022 at 20:00 UTC.
Props to @webcommsat for preparing the agenda and collating input,
to @marybaum and @webcommsat for leading the meeting,
to @marybaum for the summary, and to @webcommsat for reviewing.