Agenda, Slack log.
@azaozz has been looking at the “WordPress integration” parts the last couple of days, a lot of things that can be improved there. It removes some of the oddities, like running the post content through wpautop() before outputting it in the textarea, but only when TinyMCE is expected to be loaded, etc. @iseulde is working on the mobile toolbar and is hopeful she can get a patch 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. ready this week. By next week’s meeting they want to have the mobile toolbar working (except in iOS The operating system used on iPhones and iPads.), as well as #31655, #30949, and maybe #31441 in.
Admin (and super admin) UI User interface (#)
@helen has largely been working on prepping things (tickets, examples, links, etc.) for Thursday’s UI meeting. More about the meeting (including agenda) can be found here: https://make.wordpress.org/core/2015/05/11/weekly-core-ui-meetings-for-4-3/
Network (versus site, blog) Admin UI (#)
Recap of Multisite office hours: https://make.wordpress.org/core/2015/05/12/multisite-office-hours-recap-may-12-2015/
Things they want to have done by next week:
- Mockups for the Edit Site / Add New Site improvements by @hugobaeta.
- Having more flows posted to Make Flow for the network admin, via @sofiarose @kraft, and @ubernaut.
- Get some decent progress on `WP_Site` and `WP_Network` with @jjj.
Partial Refresh (#)
Weston hopes to add initial integration between Menu Customizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. and Partial Refresh this weekend. Due to client projects he’ll have to work on Concurrency _concurrently_ with Partial Refresh so he doesn’t hold up Menu Customizer. By next week Partial Refresh should be abstracted enough for the Menu Customizer to work with.
Menu Customizer (#)
Now that it’s object-oriented they’re ready to start ramping up work. They’ll be going through github GitHub is a website that offers online implementation of git repositories that can 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/ issues and come up with the next milestone for possibly the end of the week. By next week they’re planning on getting lazy-loading of both all menu item controls and the add-menu-item panel done, as well as better error handling for duplicate menu names and the like.
Better Passwords (#)
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) component update (#)
There’s been a ton of work done on the List Table class and associated areas. Joe has a set of 10 tickets with patches that he’d like to see committed by next week: #32150, #32254, #32255, #32028, #32152, #32147, #32189, #31654, #32253, #32170.
Build tools component update (#)
QUnit update seems to have gone off without a hitch. There are 7 npm dependencies that need to be updated. 6 are ready to go. grunt-sass needs a bit more digging in. This week, @jorbin is going to update the build tools roadmap he wrote up after WCSF and then pester a lead (likely @helen) to give it a read so that it can finally be published.
Not exactly build related, but test related: Bug scrub identified that we don’t have any tests for nav menus, especially around the classes we add. @johnbillion has agreed to write some tests there so that we can fix all the bugs around that.
Support for managing favicons seems like a rudimentary thing, and its absence in core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. does seem odd to some. We still need plugins to handle favicon and other media icons in the admin, there is currently no good way for users to do that. We’ve been talking about adding support for a favicon manager for a long time ( #16434 ), let’s make 4.3 the release that finally adds it. @johnbillion volunteered to lead the feature for 4.3, with help from @brandondove, @kraftbj, @sofiarose, and possibly @dh-shredder.
Next chat will be on May 20, 2000 UTC