Today’s chat did not really happen, for the best of reasons, since most of the regular contributors are currently making their way to the massive WordCamp Europe 2015. The good news is that many Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. UI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. related chats are expected to take place there, as many gather in person.
Since I ran the meeting for similar reasons last week, I figured I’d post a quick summary of what happened since then in Core UI Land instead.
Tickets with notable UI-related commits
#28820, #32213, #32015, #32325, #21845, #30157, #31336, and #31216
Some active tickets
- #32346 is being discussed
- #29906 is alive and well, nearing commit state (needs testing)
- #32395 got a brand new patch, needs testing
- #16434 is seeing some patches and chatter
- #30902 is on fire!
- #19257 was set to fixed; #30729 got punted to a future release, and #31240 looks like it might as well
Looking stalled, could use some help, with beta 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. 1 approaching
#31654, #32398, #26550, #29958, #32152, #32493, #29158, #30154, and #31655
Main recommendations for commits this week
I’ve chatted with 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) group about a series of List Table and accessibility ticket they have, and I’ve recommended they tag them as commit ASAP. They are all, IMHO, in good shape to be considered. They’ve also clearly been abundantly discussed, iterated upon, etc. Some commit-time tweaks might be required, but nothing I’d consider related to the actual functionality.