Dev Chat Summary: May 11, 2016

Update on WordPress 4.5.3

Triage of tickets with the “early”” keyword and “class tickets”

  • 9 tickets are still listed
  • @iseulde was unavailable for comment on #25387
  • @swissspidy is working on patches for WP_Post_Type and WP_Taxonomy.
  • @jeremyfelt is planning on commiting WP_Site_Query this week.
  • @boonebgorges will provide feedback for patch on #36492
  • A patch for #34391 was submitted this week. This patch also fixes #34344 and #35947 (both early tickets).

Feedback on bug scrubs/weekly chats/office hours

The general consensus is that having frequent meetings for each component is a positive thing that promotes contributions.

@helen: I don’t think having a lot of scheduled meetings is a problem when they’re not mandatory, it helps people schedule and structure their time.
@jorbin: It also helps people be involved since they have plenty of options for when they can interact live with others
@voldemortensen: Live feedback helped me a ton when starting with WordPress.

A link to https://make.wordpress.org/meetings will be added to the sidebar.

Feature project updates

Font Natively

  • There is a bug with MSEdge. @helen will try get in touch with them about it.

Customizer Transactions

  • Most of the work related to transactions has been on #34893 (Customize Setting Validation). Validation is needed in order to obtain a pass/fail green light to “commit” a transaction to the database. Further discussion can be found here: https://make.wordpress.org/core/2016/05/04/improving-setting-validation-in-the-customizer/

Customize Posts

  • @valendesigns has been improving the underlying framework for themes to add support for how they vary in how they use template parts to represent the various post fields (e.g. title, author, and content).
  • Also regarding #34923, @valendesigns has done an initial PR for adding the ability to create new posts/pages in the Customizer, with an Add New button appearing at the top of the panel for the given post type.
  • The Customize team will then be able to integrate this same button into the available nav menu items pane for menus in the Customizer.

Shiny Updates

  • @swissspidy continued working on update-core.php. See https://cloudup.com/cIh02KWWwey
  • @mapk conducted another user test (which went a lot smoother after we updated the test site to WP 4.5.1). That can be found here: https://cldup.com/yHfETI5gdE.mp4
  • All flow documentation for shiny updates can be found here: https://make.wordpress.org/flow/tag/shiny-updates/
  • The Shiny Updates team still needs reviews from various groups (i.e. a11y, i18n, etc).
  • So far the Shiny Updates team has done a total of five recorded user tests plus a few in-person ones at WordCamps. They’d like to do one more with themes install/update/delete to see if there are any quirks that have been missed.
  • @afercia would like a user review done with the tester using assistive technologies.

Fields API

  • The Fields API team is seeking feedback on an ongoing discussion surrounding #35658, where they’re proposing extending register_meta() to accept an $args array which would provide much needed information about the meta field to both the REST API and the Fields API.
  • The Fields API team and the REST API team are at odds about which schema should be used.
  • A explanation of the issue, as well as proposed solutions, can be found here: https://docs.google.com/document/d/1ZMKt_PIcy0fTTQAjE1THeG-MRPTUHVVSSyZs5dk7TIc/edit
  • Action items: Further define the pros/cons of each schema option and meet with REST API team to hash out an agreeable solution

Toolbar Experiments

  • No further progress.

Component updates

Please see: https://make.wordpress.org/core/tag/4-6/

Open discussion

  • @joemcgill would like to get another set of eyes on #36531, particularly as it relates to possibly fixing broken options via an upgrade routine.
  • @afercia would appreciate a review of the post draft for make/core about the changes in the Terms screens, see ticket #35664.
  • @brianvan would like a review of #27056
  • The workflow part of the Handbook isn’t clear on what to do after a ticket is tagged with “has-patch”. Getting another contributor or a committer to review the patch is the best thing to do. This should be updated in the Handbook.

#4-6, #dev-chat, #summary