@marybaum and @webcommsat facilitated the WordPress Developers Chat on this agenda. You can o read the full meeting on the Make WordPress Slack.
Announcements
WordPress 6.0 Beta 1 landed on Tuesday, April 12. Please download and test!
Blog (versus network, site) posts of note
Followup on WebP by default proposal (April 12, 2022): The Performance Team will be reassessing this proposal to consider the feedback.
A Week in Core (April 11, 2022) – thanks to @audrasjb
Help wanted: Test WordPress 6.0 (April 12, 2022) – thanks @ironprogrammer
Help test the comments blocks for 6.0 – thanks @juanmaguitar
More answers to round four of questions on the Full Site Editing (FSE) program. You can find answers from all the question rounds at fse-answers, from @annezazu
A new post on Core styles and customizations: the next steps, from @ramonopoly
Upcoming releases: 6.0
(Ed. note: 5.9.3 was the last maintenance update for 5.9, and there will likely only be security updates from here out. The Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team only talks about those after the fact.)
@annezazu reported in with a list of highlights:
- Backporting PHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher changes is complete: https://github.com/WordPress/gutenberg/issues/39889
- There are loads of experimental APIs to address: https://github.com/WordPress/gutenberg/issues/40316
- 15 out of 42 dev notes Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. are drafted: https://github.com/WordPress/gutenberg/issues/39654
Anne also highlighted the WebP project post above.
@webcommsat reported in for Docs and the About page:
The three Release Documentation Leads are working closely with Learn WordPress to find places to collaborate, so users hear similar terms and get the idea that they mean somewhat similar things.
On the About page, the component scrub on the next several Mondays (Help/About, 20:00 UTC in the Core 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/. channel) will focus almost exclusively on that task. You can follow the action asynchronously on the ticket; to join the fun, come to the Monday scrubs!
6.0 walkthrough on April 7. If you missed this, the walkthrough itself is now up on WordPress TV.
6.0 bug-scrubs schedule.
(Note from core team 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: The triage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. leads for 6.0 are @costdev and @chaion07, but you, dear reader, can lead a 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. scrub, too, and scrub only the tickets you care about. You don’t need any special privileges or standing — just contact the leads to get on the schedule. Once you’ve held your scrub, you will have earned a mention in the 6.0 credits.
Open Floor
@annezazu reminded the group of the latest FSE Program Outreach call, which is due April 21, 2022.
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 2022
@webcommsat asked if anyone was working on items for the Core tables at WordCamp Europe Contributor Day, June 2, 2022
@adamsilverstein raised that volunteers were still needed to facilitate the Core table(s) at WordCamp Europe’s 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/..
After some discussion, @desrosj volunteered to organize tables for Core and Core-JS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors., and to get together with the Getting-Started folks, if any, on a table where attendees can learn to set up a local WordPress environment. @marybaum volunteered to help with collateral materials, and @annezazu volunteered to add some FSE content.
Props to: @webcommsat for the agenda, @marybaum and @webcommsat for leading the meeting, @marybaum for writing the summary, and @webcommsat and release squad members for review.
#6-0, #dev-chat, #summary
