This post summarizes the weekly dev chat meeting from August 28th 2019 (agenda / Slack Archive).
Announcements
@chanthaboune mentioned a Make/Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. post about using SSL for auto-updates.
@francina mentioned the recently created WP-Notify working group. They had their first meeting and they have two weekly meeting so people from different timezones can attend. If you are interested, join #feature-notifications dedicated 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.
WP-Notify was also added to the features list page on Make/Core.
@francina also mentioned there is a new time slot for Core tickets/Gutenberg issues triage and bug-scrubs. If you are in the APAC timezone feel free to take part into the 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. scrubs, they are great to get started in understanding how WordPress is made.
Upcoming Releases
5.2.3
5.2.3 RC 1 is available for testing.
Release lead The community member ultimately responsible for the Release. @whyisjake mentioned they are skipping RC2 for 5.2.3 as there are no new commits since RC1 and no regression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. was reported against RC1. The final release is scheduled for this coming Wednesday.
Please continue testing, and provide feedback. If you are new to testing Core releases, there is a guide to get started. Getting involved in testing WordPress means you will be directly involved in raising the quality of the WordPress user experience.
5.3
@francina announced that @audrasjb is joining the Release Team as focus lead for the accessibility 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) part.
@davidbaumwald ran the first bug scrub of the release cycle, focused on tickets that are milestoned for 5.3, but haven’t see any movement in some time.
@johnbillion: “We need more people attending bug scrubs and scrubbing bugs. Tell all your friends.”. @davidbaumwald added that’s being added for the 5.3 cycle to give props for those running scrubs.
If you want lead a scrub, please get in touch with @davidbaumwald and it will be added to the official schedule to spread the word.
@azaozz mentioned it would also be great if component maintainers could help triage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. their components.
@audrasjb mentioned the accessibility team will run two additional bug scrubs dedicated to 5.3.
@karmatosed mentioned the design team also runs weekly bug scrubs.
@davidbaumwald is maintaining the list of 5.3 bug scrubs. There was a discussion about having it as a sticky post to see if it helps to increase the number of people attending bug scrubs.
@karmatosed published a post concerning the design of WP core About Page. The post is to start a discussion about what could be easier about this screen. It has a few of the current problems around it and then leads into some potential ideas. Any input on this is welcome.
Call for component maintainers
As per today, there is 6 components without maintainer. Any interested contributors is welcome to help maintain components.
@justinahinon mentioned his interest for the Site Health component.
@francina asked if all the components who seem to have a maintainer really maintained.
@jeffpaul did one component maintainers audit this year and one last year, so the current listing is nearly almost folks who committed to maintaining as best they can.
#5-2-3, #5-3, #bug-scrub, #components, #feature-plugins
