Dev Chat Summary: October 31st (5.0 Week 5)

This post summarizes the dev chat meeting from October 31st 🎃 (agenda, Slack archive).

5.0 Planning and Updates

• We have a lot of PRs that need review, so please pick up one or two if that’s something you excel at. 🙂 A code review team is being create on GithubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ to help call these out.
• Bug scrubs are happening all week if you want to volunteer to help close a bugbug 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. or test to provide more information.
• 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. 2 came out last week and was accompanied by an update to the timeline that gives us more beta cycles.
• We have some back compat issues in the media component for 5.0 and could use more help there.
• Documentation has been split into two different tickets, one for User docs and Design/Dev docs.
• Gary posted some new dev notesdev 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, 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. about Block Editor Filters for this release. These filters exist to help transition to the blockBlock 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.

Component and Focus Updates

• The 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/ team released v4.2 which mostly includes performance enhancements and bug fixes. It also concludes the cycle for the formatting APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways..
• Core PHP is working on an updated roadmap for Servehappy, and shared a continued need for WSOD testing.
• Core Javascript is working on a plan to add End 2 End (E2E) tests for plugins and CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. as it is used in Gutenberg.

Announcements and Open Floor

• As mentioned last week, the AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) team wrote up a report on the accessibility of Gutenberg.
• Daniel Bachhuber wrote a post about Backwards Compatibility
• Josepha ended the meeting with some well-wishes to Jeff Paul & fam but also some lighthearted silliness.

Next meeting

The next meeting will take place on Wednesday, November 7 20:00 UTC 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 the upcoming agenda post so that we can take them into account.

#5-0, #a11y, #core, #core-editor, #core-js, #core-media, #core-php, #core-restapi, #dev-chat, #gutenberg, #summary, #team-reps