Dev Chat Summary: January 10th (4.9.2 week 6)

This post summarizes the dev chat meeting from January 10th (agenda, Slack archive).

4.9.2 planning

  • Tentative release timing of 1/16 for beta, 1/23 for RC, and 1/30 for release
  • 57 tickets currently on the milestone, @sergey will be reviewing them during a bug scrub on Friday (Jan 12th) at 19:00 UTC
  • Bug scrubs for future weeks will be scheduled around 19:00 UTC on Mondays, Wednesdays, and/or Fridays by @sergey and @desrosj

Updates from focus leads and component maintainers

  • Design team would like to check in with the other teams and see if anyone has projects they need designers for in the next couple months. If you have needs then please reach out in the #design channel.
  • REST API team would like to know if your work would be aided by API improvements or is blocked by API issues; if so, please come see them in #core-restapi.
  • Media and PHP teams have posted their meeting recaps from the past week for review.

Servehappy project

  • @schlessera: posted a Servehappy project overview
  • Our goal is to have a positive impact on PHP version distributions, to get a higher percentage of servers to run on supported PHP versions.
  • We have 3 main building blocks right now:
    • 1. information page about PHP, its versions, and upgrading them (see: draft)
    • 2. admin notices letting site owners know they run an old version
    • 3. plugin/theme requirements that prevent installation/updates when PHP version requirements are not met
  • @flixos90: Regarding #1, we have a Trac ticket in place. The page itself has two goals: Convince site owners that it's worth their time to take action, and then explain how they can proceed.
  • How and who do we approach to get it on wordpress.org infrastructure? Should it be hosted as an area inside .org or as a separate site with separate domain (if yes, which one)?
  • Plan to collaborate with Tide, in terms of preparing the PHP upgrade as users could check for their plugins and themes compatibility.
  • @stevenkword: We are also considering making the PHP Compatibility Checker plugin a consumer of Tide when it's production ready. Leveraging the cached results would really speed it up. We're pushing an update for 5.2 support this afternoon, and it will contain 7.1 and 7.2 checks
  • Anyone who's interested in helping out, please join our weekly meetings on Monday 16:00 UTC, and of course feel free to review what we currently have.

General announcements

  • @jorbin: I want to draw some early attention to a ticket that has the potential to impact all core contributions, especially related to JavaScript. Please take a read of #43055 and after reading it all, comment with any thoughts or concerns.
  • @audrasjb: when will we have a chance to know WP 5.0 delivery roadmap?
    • @jbpaul17: I’m not aware of any pending updates, so I’d suggest for now joining the conversation in #core-editor and helping with Gutenberg as any roadmap or timeline will come from the progress of development there.

Next meeting

The next meeting will take place on January 17, 2018 at 21:00 UTC / January 17, 2018 at 21:00 UTC in the #core Slack channel. Please feel free to drop in with any updates or questions. If you have items to discuss but cannot make the meeting, please leave a comment on this post so that we can take them into account.

Media meeting recap – January 4, 2018

Happy new year!

Overview

This post is a summary of the latest weekly Media component meeting, which took place in the #core-media Slack channel, on Thursday, January 4, 2018 at 1900 UTC. The purpose of these meetings are to move priority tasks forward, provide feedback on issues of interest, and review media focused tickets on Trac.

Attendees:
@blobfolio, @clorith, @desrosj, @joemcgill, @karmatosed, @mikeschroder

Transcript: Read on Slack

4.9.2 Review

The following tickets assigned to the upcoming 4.9.2 milestone were reviewed:

  • #39859wp.media.view.Modal jumps when you open it
  • #42225 – Whitelist Flac Files
  • #42447 – Mark test_remove_orientation_data_on_rotate as skipped when exif_read_data isn't available
  • #42480 – Consistent suppression of getimagesize() errors
  • #42643 – FLV video format not playing

#39859 and #42447 appear to be on track for commit.

If the small enhancement #42225 is allowed to land at the dot-dot, @desrosj and @blobfolio think #42919 should be retargeted for inclusion as well. The latter could also be argued to be a bug fix rather than just an enhancement as full aac support is already present in the Core; it is only files literally named *.aac (versus using the AAC codec inside some other container) which cannot be uploaded.

#42480 has a patch that addresses the stated issue. @blobfolio suggested that a better long-term approach might be to remap getimagesize() calls to a wrapper function, which would allow WP to deliver more robust responses (the native PHP function is inconsistent across versions). Such a wrapper was introduced to the patch under #35725, but further discussion is needed.

#42643 might be limited by upstream support, however @adamsilverstein and @clorith are working on it.

Gutenberg

@karmatosed led a discussion of outstanding Gutenberg tickets. It was decided that the next weekly meeting should designate 15-30 minutes to discussing high-priority items to help get the media team connected with Gutenberg development.

Other Tickets

The current patch for #35725 (Add mime-type for Webp) tackles both the file type whitelisting — allowing .webp files to be uploaded — and full image integration for e.g. thumbnails, media insertion into posts, theme screenshots, etc. @mikeschroder suggested separating out the more in-depth handling functionality, while @blobfolio felt it important the two halves merge together since the Core does not provide a native way to retroactively generate thumbnails.

As there is a growing number of new and exciting image formats, many of which might be better left to plugins and themes, @blobfolio started a new enhancement ticket #43023 outlining the Core areas that would need to be rewritten to allow for such extensibility.

Next Meeting

The next #core-media Slack channel meeting will be held Thursday, January 11, 2018 at 1900 UTC. See you there!

Dev Chat Agenda: January 10th (4.9.2 week 6)

This is the agenda for the weekly dev meeting on January 10, 2018 at 21:00 UTC / January 10, 2018 at 21:00 UTC:

  • 4.9.2 planning
  • Updates from focus leads and component maintainers
  • Servehappy project
  • General announcements

If you have anything to propose to add to the agenda or specific items related to the above, please leave a comment below. See you there!

PHP Meeting Recap – January 8th

This recap is a summary of our previous PHP meeting. It highlights the ideas and decisions which came up during that meeting, both as a means of documenting and to provide a quick overview for those who were unable to attend.

You can find this meeting’s chat log here.

Chat Summary

The primary focus of this chat was strategizing about our opportunity on January 10th to discuss the servehappy project during the devchat. We discussed a potential roadmap with estimated timeline so that there’s specific information to offer at the devchat.

Decisions arrived at for rough ETA’s on Roadmap

  • 1st Quarter 2018 is target for servehappy page on wp.org
  • 2nd Quarter 2018 is target for core integration (admin notice etc). See Core integration doc recently published.
  • 3rd Quarter 2018 possible target for plugin requirements work.

Other discussion

  • README.md was updated on the servehappy repository. Pull requests are welcome for keeping it up to date and adding any missing info (such as PHP Compatability Checker mentioned during the meeting)
  • For admin notice initial work will be done in the trac ticket (and that will be the source for initial wire-framing/discussion) and then we’ll do a feature plugin (possibly WordPress/servehappy-admin-notice) for iterating on implementation and easier user/usability testing.
  • Some discussion around Tide and any potential impact on the servehappy project. General consensus is that Tide doesn’t block anything but communication should be kept open between the two teams to be aware of any overlap of documentation or user facing things between the two projects.
  • @schlessera will be preparing a blog post outlining a more detailed roadmap that will be published within two days, the intent being using it as a resource ahead of the general WP core dev-chat meeting.

Next Meeting

The next meeting will take place on Monday January 15, 16:00 UTC as always in #core-php.  The agenda will likely cover the results from servehappy presentation at the dev chat meeting and the next steps from that. See you next week!

#core-php, #php, #summary

No Dev Chat This Week (4.9.2 week 5)

A reminder that there will be no devchat this week as we are on hiatus over the holidays.

 

The next devchat will be on January 10, 2018 at 21:00 UTC / January 10, 2018 at 21:00 UTC.

Dev Chat Summary: December 20th (4.9.2 week 3)

This post summarizes the dev chat meeting from December 20th (agenda, Slack archive).

4.9.2 planning

  • @sergey to be release lead, @williampatton to be deputy release lead
  • @desrosj able to help with bug scrubs
  • Tentative release timing of 1/16 for beta, 1/23 for RC, and 1/30 for release

Confirm definition of "minor release"

  • Confirmed definition: Bugfixes and enhancements that do not add new deployed files and are at the discretion of the release lead with suggestions/input from component maintainers and committers.
  • @jbpaul17 added that definition to the handbook for future reference (see here, here, and here)

Updates from focus leads and component maintainers

  • Team Editor (Gutenberg): They have no more meetings until January 3rd in #core-editor. The channel is of course open all the time, but meetings will resume then. They also have a request for assistance on video processing of the usability videos from WCUS. Please check the post if you’re available / have interest.
  • Teams Customize and REST API are both on hiatus through the holidays and have no updates this week.
  • Multisite published a post about their roadmap

Meeting hiatus over holidays

  • There will be a two week hiatus for devchat, final meeting for 2017 is today (December 20th). First meeting for 2018 will be January 10th.

General announcements

  • @presskopp looking for advice on getting patches reviewed. Advice given is to ping component maintainers, mention it during devchat's General announcements section, or mention it during a bug scrub.
  • @schlessera looking for advice on getting something on the devchat agenda for January 10th. Advice given is to ping @jbpaul17, mention it during devchat's General announcements section, or add it as a comment to the agenda post. Also noted that Make/Core posts can be a good idea for things that need some discussion and can happen at any time.
  • @schlessera to work on a Make/Core post around the topic of "Servehappy project – current status and how to proceed to have the effort blessed"

#4-9-2, #core, #core-multisite, #dev-chat, #gutenberg, #summary

Media meeting recap – December 14, 2017

Overview

This post is a summary of the latest weekly Media component meeting, which took place in the #core-media Slack channel, on Thursday, December 14, 2017 at 1800 UTC. The purpose of these meetings are to move priority tasks forward, provide feedback on issues of interest, and review media focused tickets on Trac.

Attendees:
@sergey @desrosj @blobfolio @adamsilverstein @mikeschroder

Transcript: Read on Slack

4.9.2 review

The following tickets assigned to the upcoming 4.9.2 milestone were reviewed:

  • #39859 – wp.media.view.Modal jumps when you open it
  • #42225 – Whitelist Flac Files

Both tickets are looking to be in good shape for commit. Because #42225 is an enhancement, whether it ships in 4.9.2 will be up to the lead.

Media Formats

The majority of this meeting focused on various media and file-type expansions for WordPress.

#42775 – Support uploading files in HEIF and HEVC formats

Browser and PHP support for these new formats does not yet exist. There was disagreement as to whether the file types should be added to upload_mimes, and discussion will continue in the ticket.

#42017 – Parse the creation date out of uploaded audio files

@desrosj noticed that aac is not part of the upload_mimes list, though many additional media types which make use of aac are.  Opened #42919 to address this.

#35725 – Add mime-type for Webp

@blobfolio uploaded a more comprehensive patch that adds full backend support for WebP images, including GD and ImageMagick integration.

<PICTURE> Support

There was discussion on how fallback support could be handled if WordPress supported media types with less browser support, like `HEVC` or `WebP`. The HTML5 <picture> element could be used for this task, however to avoid unintended compatibility issues with existing themes, @desrosj suggested this be hidden behind add_theme_support()

Other Tickets

@mikeschroder and @adamsilverstein to review #30155 (Fix crop image functionality within edit flow) and potentially retarget for 4.9.2.

Holiday Schedule

In anticipation of busy travel schedules, the next core-media meeting is set for Thursday, January 4, 2018 at 1800 UTC. Please join us then for discussion!

Thanks much to @blobfolio for writing up the meeting notes!

#core-media, #summary

Dev Chat Agenda: December 20th (4.9.2 week 3)

This is the agenda for the weekly dev meeting on December 20, 2017 at 21:00 UTC / December 20, 2017 at 21:00 UTC:

  • 4.9.2 planning: release lead, bug scrubs, timing
  • Confirm definition of "minor enhancements/features"
  • Updates from focus leads and component maintainers
  • Meeting hiatus over holidays
  • General announcements

If you have anything to propose to add to the agenda or specific items related to the above, please leave a comment below. See you there!

#4-9-2, #agenda, #core, #dev-chat

Multisite Roadmap Published

Over the past year, the multisite team has been looking at possible features to add or improve support for, what some of the pain points are and last but not least how to align with the core focuses for this year, which for multisite scope basically means working on REST API support and usage.

The result of those long discussions is a clearly defined roadmap, describing what the priorities will be over the next couple months or generally the near future. It should be clarified that this is a living document that will see updates from time to time as tasks get completed or new decisions are made.

The roadmap document lives on a separate page to be easily accessible outside of the blog, and also to allow other component teams to possibly follow with their own roadmaps.

Here is what the roadmap focuses on at this point of publication:

  • REST API support for users, sites and networks
  • new internal APIs for sites and networks
  • introduction of site metadata
  • internal usage of the Meta API for network options
  • file organization improvements

All the above will set a solid foundation to after their completion finally focus on some long-needed more user-centric enhancements, particularly to the administration panels. Other long-term changes include improving test coverage and global context support. Those areas are also described a little more broadly in separate sections towards the end of the roadmap.

Please refer to the roadmap document for a full and current overview of multisite priorities.

#core-multisite

Dev Chat Summary: December 13th (4.9.2 week 2)

This post summarizes the dev chat meeting from December 13th (Slack archive).

4.9.2 planning

  • @obenland available to volunteer as release lead, offline until January 8th
  • @westonruter planning to start committing fixes in January after reviewing patches in the 4.9.2 milestone
  • Potential release timing of 1/16 for beta, 1/23 for RC, and 1/30 for release could work

Devchat coordination

  • There will be a two week hiatus for devchat, final meeting for 2017 will be December 20th
  • First meeting for 2018 will be January 10th

General announcements

  • @paaljoachim asks if there is someone who has interest in helping lead work on the exporter / importer
    • @rmccue also started a similar project
    • project not likely to see significant progress until its made a focus
    • revamping the import/export workflow is a huge, not unrisky lift
    • the import/export work is a continuation of the previous work already done on the Export-API #22435
  • @paragoninitiativeenterprises noted plugin breakage concern with #42439 plus 4.9.2 release note recommendation
  • @paaljoachim asks if there is someone who has interest in helping lead work on the admin bar (#32678)
    • @danieltj is component maintainer, will look into it

#4-9-2, #core, #dev-chat, #summary