Dev Chat Summary: May 11, 2016

Update on WordPress 4.5.3

  • 8 tickets listed, 3 merged into trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision.
  • Both @adamsilverstein and @swissspidy were unavilable during chat

Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. 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 patchpatch 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. on #36492
  • A patch for #34391 was submitted this week. This patch also fixes #34344 and #35947 (both early tickets).

Feedback on bugbug 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/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.

CustomizerCustomizer 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. 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. a11yAccessibility 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), i18ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill., 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 APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways.

  • 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 metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. field to both the REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/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 makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility)./coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. about the changes in the Terms screens, see ticketticket Created for both bug reports and feature development on the bug tracker. #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 committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. to review the patch is the best thing to do. This should be updated in the Handbook.

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