Core Dev Chat Notes for Jan 20

Announcements

• Week in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. is started up again!  Thanks @ebinnion, @adamsilverstein, and @morganestes for the effort. Help is needed!  Please join the SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. #core-weekly-update to volunteer.
• There will be another feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins. meeting next Tuesday, January 26, 2016, 2100 UTC (normal dev chat time). More details coming soon.

Focus Status Updates

• 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.: @westonruter, @celloexpressions
  • Good progress has happened for selective refresh, with good feedback and an architectural direction #27355.
  • A responsive preview feature has been getting good feedback and is nearing a committable 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. #31195.
  • Update make/core post coming soon.
• HTTPSHTTPS HTTPS is an acronym for Hyper Text Transfer Protocol Secure. HTTPS is the secure version of HTTP, the protocol over which data is sent between your browser and the website that you are connected to. The 'S' at the end of HTTPS stands for 'Secure'. It means all communications between your browser and the website are encrypted. This is especially helpful for protecting sensitive data like banking information. Improvements: @johnbillion
  • Nothing specific to report about the HTTPS work, there will be a meeting next week about ‘force ssl’ which he will post about in make/core tomorrow morning for those who want to get involved.
• Image Improvements: @joemcgill
  • Improving Imagick compression settings #33642 is still a priority.
  • Looking into options for #28474 (better animated GIF handling).
  • Longer term effort: what can be done to improve some of the core 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. for working with images
• Multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site/WP_Site: @jeremyfelt
  • Several things assigned to the 4.5 milestone
  • A reorg of filters for networknetwork (versus site, blog) allowed themes went in today.
  • Working at the latest <code>WP_Site</code> patch now with the intent of putting it in today or tomorrow.
  • Office hours on Tuesdays at 21:00 UTC in #core-multisite; bring your bugs.
• Post New: @michaelarestad
  • @karmatosed is going to be leading a team focused on improving the RevisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. UIUI User interface
  • @hugobaeta is going to be leading the Toolbar Remix team
  • @michaelarestad working on improving the Publishing UXUX User experience and Metaboxes
  • @michaelarestad made a Sketch template for wp-adminadmin (and super admin) that’s accurate and will be published later this week.
  • Update posts coming soon
  • Join the effort: comment on the original post and join the Slack #design channel.
• Editor: @azaozz, @iseulde
  • @iseulde is working on the inline link dialog
  • @azaozz just upgraded TinyMCE
  • They posted a wishlist for 4.5, comment there for feedback

Open Floor

• @ipstenu brought up #35429; @michaelarestad going to review from UX perspective, discussion
• @azaozz brought up inline link dialog autocomplete, extend suggest.js or use another library (typeahead, select2)? what is the use case? discussion in #core-editor. @sheri offered to help with user testing to determine the best UX.
• Meeting ended, ticketticket Created for both bug reports and feature development on the bug tracker. conversation continued…

View the full logs on Slack.

#4-5, #dev-chat, #meeting-notes