The meeting was facilitated by @thewebprincess while @thelmachido took notes. Full meeting transcript on slack. 

Both groups followed the pre-prepared agenda and started the chat by celebrating the release of WordPress 5.6 Beta 2, please test and review the BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. version and share any bugs/issues.

Announcements

WP Version 5.5.2 is scheduled for release on October 29th

Highlighted Posts

@helen is running code review/commit office hours for 5.6, you can get more information about it here.

@chanthaboune outlined the rationale behind dropping the Widgets screen from 5.6 catch up on that and the plan going forward here.

Dark Mode for Twenty Twenty-One
Discussions are ongoing and the team has outlined some options that your input could help narrow down.

Calls for maintainers and focus leads

PHP 8 call for testing
@sergeybiryukov highlighted again that there is need for more testing on PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8, we have to expand test coverage and creat tickets for any issues found. A thorough report has been written by @omarreiss, @jrff, and @herregroen about the current state of PHP 8 and its compatibility with WP.

Build/Test Tools
Docker environment was updated to allow for using multiple PHP Unit versions, get more details on that here. (Note: this is currently temporarily reverted to investigate test failures) Also, some changes were made to account for the recently released Composer 2.0.

Upgrade/Install Component Update
@audrasjb is drafting on a dev notedev note 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 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. for #50907. It should be ready for review by the Docs lead/cohort/mentor.

Open Floor

Take part in the 2020 WP English Survey, if you are interested to see 2019 survey results, or get links to the 2020 survey in French, German, Japanese, Russian, or Spanish, you can find all that here!

Block Pattern Directory Ideas and Discussion
@daisyo surfaced the post for feedback.

@audrasjb is working on a technical proposal for dropping support/security backports for very old versions of WordPress. He is going to publish a Make CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. post and open a ticketticket Created for both bug reports and feature development on the bug tracker. with a patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. proposal very soon. The topic should be ready for discussion during the next dev chat. Comments are welcome here. Follow the conversation on slack

Join the team for the next bug scrub on Friday

WP 5.6 Beta 3 is Scheduled for next Monday.

Next Dev Chat meetings

The next meetings will take place on Wednesday, November 4, 2020, 07:00 AM GMT+2 and Wednesday, November 4, 2020, 10:00 PM GMT+2 in the #core 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/. channel. Please feel free to drop in with any updates or questions. If you have items to discuss but cannot make the meeting, please leave a comment on this post so that we can take them into account. 

#5-5, #5-5-1, #core, #dev-chat, #summary