Agenda, Slack log.
Editor (#)
@azaozz, @iseulde
Spent last week to go over the things they want to work on. @iseulde will work on the mobile editor toolbar first. They’ll milestone tickets as they get patches. For posterity and everyone who wants to follow up, the Editor game plan for 4.3 can be found here: https://make.wordpress.org/core/2015/05/01/editor-wish-list-for-4-3/
Admin (and super admin) UI User interface (#)
@helen
Not much to talk about yet as @helen was out last week and will be out for the next few days. She will schedule a meeting for next week, likely May 14 17:00 UTC. location to be determined.
Network (versus site, blog) Admin UI (#)
@jeremyfelt
There was a good chat about NA UI on Tuesday. First steps are documenting pain points now and move forward with tickets, etc. Multisite chat summary: https://make.wordpress.org/core/2015/05/06/multisite-office-hours-recap-may-5-2015/
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. (#)
@westonruter
Noteworthy from Monday’s chat is that Menu Customizer was added to the 4.3 roadmap for the Customizer, while Transactions were taken off it. No other news besides that: https://make.wordpress.org/core/2015/05/04/customizer-chat-summary/
Better Passwords (#)
@markjaquith
Weekly meetings are on Monday 17:00 UTC in #core-passwords. Right now they’re throwing ideas around, by Monday @markjaquith wants to have gone through that and have a make/core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. post that outlines the major goals for this release, so they can get to work.
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 (#)
@joedolson
The accessibility team has spent a lot of time generating tickets for tabular data, based on user feedback gathered during the 4.2 cycle. It’s about 8 tickets right now, all prefixed with “List Table:”. They have also been focusing on establishing a new heading hierarchy for the admin. Resolving the H1 issue is fairly simple, but has broad impact across the admin; should probably get this in ASAP. It shouldn’t have much impact in normal usage, but e team is unsure what kinds of edge cases might be out there. There are two separate issues: implementing H1 across pages and addressing the hierarchy within pages; @joedolson suggested to handle just the primary H1 to start, then start looking at the internal issues.
Build tools component update (#)
@jorbin
Started upgrading dev dependencies and our version of QUnit. @jorbin will finish those updates this week. People will likely need to do some npm installs to ensure they have the up to date versions.
Next chat will be on May 13, 20:00UTC
#4-3, #meeting
