Media Meeting Recap – November 7, 2019

The following is a summary of the weekly media component meeting that occurred on Thursday, November 7, 2019. Weekly media meetings are held every Thursday at 14:00 UTC. A full transcript can be found here in the #core-media room in the Make WordPress Slack.

Attendees: @joemcgill , @mikeschroder, @afercia, @desrosj, @dinhtungdu, @karmatosed, @greglone, @azaozz

Meeting Time Discussion

It’s that time of year again (for some of us!) Fall Daylight Savings Time historically makes the meeting time move forward one hour. The next meeting will take place Thursday, November 14, at 14:00 UTC.

There was discussion in a group message consisting of meeting facilitators around potentially doing a rotation of one week at a convenient time for each side of the planet. The Hosting-Community room does this and it seems to work very well. This would allow for participation from groups outside of the normal hour that we hold the meeting while also allowing folks that have been stretching outside their normal work hours to catch the meeting async. Please let us know in the comments what you think about this! There was mention of potentially doing a few months on one schedule and a rotation after. Another suggestion was around doing many meetings instead of rotating meetings. This would entail two designated meeting times a week in an effort to encourage new participants. This topic will be discussed in the next Media Meeting. Any additional ideas would be appreciated.

WordPress 5.3 Tasks

There were three tickets discussed in the meeting.

  1. #48518 Inconsistent behavior when a registered image size is larger than the big image threshold – Testing is being done around this issue and should be ready for 5.3.
  2. #48451 Regression: wp_update_attachment_metadata filter now fires very often and without complete metadata – The Follow Up Post around this outlines a few areas to focus on with the recent uploads changes. Some discussion took place around whether or not a new hook would help folks adjust to the changes. This is still to be determined.
  3. #48522 Attachment size not generated when large images uploaded – A few more details about this issue can be found at this Slack Link. Testing would be appreciated on this ticket.

Feedback

If you have any feedback on the above, please feel free to leave a comment, join in #core-media for a chat, or attend the next meeting on November 14, 2019 at 14:00UTC!

#core, #core-accessibility, #core-media, #media, #summary

WP Notify – Meeting Recap – Oct 21, 2019

This is a recap of a meeting held October 21 for a Core project related to WordPress Admin Notifications. Meetings on this task are held every Monday at 14:00 UTC and 22:00 UTC respectively.

Related Links

Google Doc: WP Notify Project Requirements Document

Notes Per Agenda

Open Floor for Feedback

Our discussion this meeting further refined the focus of this project, to be a solution “… plugin and theme developers can leverage, again instead of using admin_notices.”

Present handling of admin_notices will require distinction between immediate (core) based notifications such as successful saves, and a queue of notifications to be followed up on at a later time.

This project seeks to pave the way so future projects can build upon the new notifications handling. Enhancement such as mail or push notifications handling, will be able to leverage the processing we create here.

Next Steps

We welcome feedback on the project either here in this post, or in the requirements (via Google Doc, comments). 

We invite you to attend our next meeting, held in Slack > #feature-notifications

  • Monday, October 28 2019 at 14:00 UTC 
  • Monday, October 28 2019 at 22:00 UTC

#summary

Dev Chat: 10/23/2019

The facilitator for this week’s chat was @audrasjb.

Announcements

WordPress version 5.3-RC2 was released on Tuesday. Everyone please help by testing out the RC.

The latest Dev Note published for 5.3 discuses “Noteworthy Admin CSS Changes in WordPress 5.3”.

Also, the official Field Guide for 5.3 was published!

@audrasjb called attention to the wonderful documentation work this cycle by @justinahinon and @jeffpaul. Thank you to both for their extraordinary efforts!

5.3 Updates

@azaozz Pointed out that there are only two tickets needing work after RC2, excluding the About Page. Follow the ticket progress in Trac here.

@ianbelanger informed the group that there are currently 0 tickets in the Bundled Themes component for Twenty Twenty. However, he added that an RC3 release would be helpful.

@audrasjb brought up ticket #48396 regarding @afercia‘s request to revert two lines of CSS to remove an unwanted changes on disabled buttons. @azaozz confirmed the revert to be a minor one and suggested that it move forward based on testing.

A pre-RC3 Bug Scrub in the #core channel was tentatively scheduled for Monday October 28, 2019 15:00 UTC. If there are no new tickets or regressions reported prior, the scrub will not take place.

@sergeybiryukov asked about branching for 5.3 this week. @peterwilsoncc suggested certainly branching before WordCamp US Contributor Day, as to allow for good-first-tickets to be committed for new contributors. @desrosj added that branching could be done at any time now that the dust has settled from RC2, but deferred to @azaozz‘s judgement as Core Tech Lead for 5.3. @azaozz suggested trying to resolve a couple of remaining issues in 5.3 prior to branching in the next few days, and a consensus was reached around this idea.

These notes were taking by @davidbaumwald and proofread by @audrasjb

#5-3, #dev-chat, #summary

Dev Chat: 10/9/2019

@davidbaumwald served as facilitator and note taker for this week’s chat held in the #core Slack channel. To view the chat from the beginning, click on this Slack Archive.

Announcements

WordPress version 5.3 Beta 3 was released on Tuesday. Congratulations to everyone involved in inching 5.3 closer to the finish line.

5.3 Updates

With 5.3 Beta 3 now release, focus turns to Release Candidate 1(RC1) is next on the schedule just a few days from now. A “soft string freeze” is now in effect.

@francina called for volunteers for next week’s RC1 release session. Both Mission Control(MC) and a Core Committer will be required. @azaozz and @sergeybiryukov raised their hands.

@karmatosed provided a quick update on 5.3’s About page, saying that everything is on track and copy is being finalized.

@jeffpaul inquired about the progress on compilation of Dev Notes for 5.3. @justinahinon pointed to a Google Sheet that he’s using to organize them and coordinate volunteer authors.

This discussion led to a call for more volunteers and ticket owners to draft Dev Notes. @desrosj mentioned that he’s “… started a page for the handbook collecting the learnings from the last three releases for this.”

@ianbelanger brought a Twenty Twenty update to the group. A PR has been opened to address WPCS violations in the Beta Twenty Twenty patch, and a call for testing was announced. @karmatosed added that testing on mobile is a great help to the team.

Open Floor

@azaozz mentioned that there are, as of writing, only 37 open tickets in the 5.3 milestone, and everything should be closed out as RC1 is released. This was a great reminder of the tremendous work done by Core Contributors during the course of the 5.3 cycle, as over 350 tickets were initially open when the cycle was kicked off!

These notes were drafted by @davidbaumwald and proofread by @justinahinon.

#5-3, #dev-chat, #summary

Editor chat summary: Wednesday, 9 October 2019

This post summarizes the weekly editor chat meeting on Wednesday, 9 October 2019, 14:00 WEST held in Slack.

Weekly Priorities

WordPress 5.3 is planned for next week, there are still some issues we need to fix before then:

Some of the priorities are being worked, but others are not taken yet. If you think you can help with some of these tasks, please leave a comment on the issue!

It is also essential to address some browser issues, namely on IE. People with a windows dev setup could be beneficial here.

We are getting close to the WordPress 5.3 release; testing is essential, namely on the mobile phone you use, given the wide variety of devices that exist.

Task coordination

Note: If you’re reading this summary outside of the meeting, please drop a comment if you can/want to help with something!

@youknowriad

  • Working on the Media Upload errors handling.
  • Working on a fix to the navigation mode.
  • Lots of reviews and coordination.
  • Exploring some improvements to Block nesting selection with a new Block Breadcrumb.

@get_dave

  • Continues the work on DimensionControl https://github.com/WordPress/gutenberg/pull/16791, and ResponsiveBlockControls https://github.com/WordPress/gutenberg/pull/16790 PRs.
  • Started on the implementation of a potential new Link insert/edit interface as per https://github.com/WordPress/gutenberg/issues/17557

@gziolo

  • Helped @epiqueras to land the initial version of the Components Storybook.
  • Is focused on some optimizations related to eliminating dead code (mostly for experimental features) from WordPress 5.3 release.

@jorgefilipecosta

  • Worked on some changes to the custom gradient picker. Now, it is possible to move the control points using arrow keys, and the code was reorganized. It should be ready for a more in-depth review; a11y feedback would also be valuable.
  • Focused on some 5.3 must-haves.
  • Helped (reviewed tested, or suggested commits) in navigation block (related PR’s), DimensionControl, ResponsiveBlockControl, and other smaller PR’s.
  • Will continue the work on must-haves, apply a refactor that makes media&text work on IE, and fix some generic block editor issues.

@karmatosed

@brentswisher

  • Hoping to revisit displaying a notice of some kind in the inserter when there are disabled blocks (https://github.com/WordPress/gutenberg/pull/17338).
  • Help out with any 5.3 issues that he can.
  • Will try to help get through some of the new issues, label them, and get additional attention to them if he thinks they are WordPress 5.3 must-haves.

Open floor

@jeffreycarandang asked for an updated to PR https://github.com/WordPress/gutenberg/pull/17617 and to issue https://github.com/WordPress/gutenberg/issues/17809.

Regarding PR https://github.com/WordPress/gutenberg/pull/17617 @youknowriad and @jorgefilipecosta both had some comments on the problem the PR faces. The basic idea is that when a format is applied to a rich text, the focus goes back to the rich text (e.g., when we press a “bold button” it is expected I can continue typing) this behavior was always present. Some time ago, mainly because of accessibility reasons, a change was applied to popovers that automatically closes them when the focus is outside. The two previous behaviors together have some impact on formats that are applied in a popover (the popover may close in an unexpected situation). This is a high priority very complex problem, and a solution is being worked.

Regarding issue https://github.com/WordPress/gutenberg/issues/17809, @youknowriad pointed $wp_version variable as a possible solution and provided a way to make it available in JavaScript.

@welcher asked more detailed feedback on https://github.com/WordPress/gutenberg/pull/16384 which adds a priority mechanism to the Slot&Fill pattern.

@mcsf and @youknowriad shared strong reservations.

It seems that priority and order are very visually focused, in stark contrast with how Gutenberg has tried to use SlotFill so far.

In Gutenberg, we talk about advanced settingsinspector, etc., instead of the visual element sidebar. Coming back to priority, what does it mean for SlotFill as far as selective rendering goes? how is a sequence determined semantically? etc.Why does this matter? Well, the bridging of different platforms and environments under Gutenberg is an important factor. If a codebase needs to work transparently across Web and Mobile, for example, its semantics needs to be clear and independent of a particular visual expression (e.g. Web on Desktop)

@mcsf

@mkaz had a docs related question:

How do y’ll feel about ES5 support in documentation? Most of the code and package docs are ESNext, but we show ES5 examples first in docs. I don’t have a proposal together yet, but I feel we should move people quicker to ESNext since it is what they most likely will experience everywhere.

People agreed that the default docs should be ESNext but ES5 examples should still be present.

#core-editor, #editor-chat, #meeting, #summary

WP Notify Meeting Recap – October 7 , 2019

This is a recap of a meeting held October 7 for a Core project related to WordPress Admin Notifications. Meetings on this task are held every Monday at 14:00 UTC and 22:00 UTC respectively.

Related Links

Google Doc: WP Notify Project Requirements Document

Notes Per Agenda

Proposal to continue merging recap and agenda into one post

@hrmervin: Volunteered to prepare the weekly recap following Eastern US time meeting

We have an open `call for scribes` if anyone is interested in volunteering alongside Mervin to take notes and/or prepare a recap.

Update on requirements gathering document

@hrmervin: Created a visual representation of the present hook workflow. As we continue to write the details of this project, we will create diagrams to illustrate A) The feature’s (feature plugin) hooks, B) the Data being managed and how it will flow, and C) the user(s) views and endpoints (how the notifications will be consumed)

  • We discussed adding names for our target users.
    • Site Admins (non-technical)
    • Site Admins (Technical)
    • Product Authors (Plugin and Theme authors)

Discussion on overlap of TRT Admin Notices package

@aristath: Spoke on an admin notice package developed to help theme authors manage notices.

“The WPTRT package is a simple wrapper for the core functions to make it easier for theme-devs to add admin-notices in a consistent manner, avoiding all the issues we’ve had in the past with theme-reviews. It’s pretty simple if you look at its code, simply sanitizing/escaping, and handling the notices dismissing.”

  • We may incorporate aspects of this package into the front-end parts of our end solution.

Open floor

  • One recommendation for future technical implementation was made by @ediamin “fetch the notifications with REST API and show them with Gutenberg Notice and/or Snackbar components”

Next Steps

We welcome feedback on the project either here in this post, or in the requirements (via Google Doc, comments). 

We invite you to attend our next meeting, held in Slack > #feature-notifications

  • Monday, October 14 2019 at 14:00 UTC 
  • Monday, October 14 2019 at 22:00 UTC

#summary

WP Notify Meeting Recap – September 30, 2019 & Weekly Agenda

This post summarises the weekly WP Notify chat meeting from September 30th 2019.

For the sake of efficiency, it also includes the weekly meeting agenda for the meeting to be held later today (October 7th, 2019)

Weekly WP Notify meetings are held every Monday at 14:00 UTC and 22:00 UTC respectively.

Feedback on requirements gathering

Document link

Last week, we built a basic requirements table of content for the requirements. @dinhtungdu started filling it with the data collected from the Trac ticket and proposal document.

We still need to add more content from the conversations took place on the Trac ticket and the Proposal.

What we archived last week is a skeleton which is ready to add more content to. This does however make it easier for new contributors to get up to speed on the focus of the project

@karmatosed raised a concern that on reading the doc, it seems to be going to technical requirements first and asked whether explorations in user flows/experience been thought about yet.

@hrmervin has offered to start to piece something together for the flow of information.

@ediamin inquired about whether there any plan to include any background processor into WP core, to facilitate WP Notify using WP Cron to dispatch the notifications. They also pointed out that WooCommerce uses this and it’s very efficient.

@daniloercoli asked that we take the mobile apps in the consideration. Right now the apps “talk” with the backend via XML-RPC. There is a plan to upgrade the communication layer to the REST API, but it’s still not there due to the “missing” authentication part.

Agenda for next meeting

  • Proposal to continue merging recap and agenda into one post
  • Update on requirements gathering
  • Discussion on overlap of TRT Admin Notices package
  • Open floor

Comments/suggestions are encouraged and welcome. If you want to add any agenda topics, please also comment on this post.

#feature-notifications, #summary

Dev Chat summary: October 2

The 5.3 Release Coordinator, @francina, led the chat (full transcript). For the record, here was the agenda for the meeting.

Announcements and highlighted posts

@francina made some announcements and pointed out highlighted posts from Make/Core blog:

Feel free to browse through these posts and add comments or thoughts.

@youknowriad mentioned Gutenberg 6.6 recap post. This version focused on stability for the editor and performance for WordPress.

Upcoming Releases

Gutenberg team lead @youknowriad said they welcome any testing to detect bugs and regressions before 5.3 release. You can see what’s happening with the editor on this GitHub board.

Site Health component maintainer @clorith reported that desired changes are on track and should be ready for the Release Candidate, currently scheduled for October 15.

Docs coordinator @justinahinon said 5.3 dev notes include some for major changes/enhancements, plus many others. Check out all the dev notes here.

@earnjam reminded the group that each published dev note on Make/Core sends an email to ~4000 newsletter subscribers. He suggested authors limit each dev note to a single topic so people can find things in the index.

@francina shared WordPress 5.3: Accessibility focus progress report.

WordPress project Executive Director @chanthaboune brought up changes that are coming to the admin interface. She stated that the focus leads have been discussing whether to keep the changes or allow extra exploration time for them, as suggested in this post.

Here are the key stances she noted from the various discussions so far:

  • There are some concerns about how quickly the changes were decided on and then implemented from design.
  • There are some concerns raised about the process overall, and whether there’s enough time for testing. Josepha and a few core committers share this concern.
  • There are concerns that further delays will result in loss of momentum from accessibility as well as confidence in an iterative process.

Josepha said she’s doing her best to balance progress with caution, and that she has gotten a lot of feedback from the release focus leads.

Here are the different opinions that have been shared by people regarding this:

  • @garrett-eclipse said that when the changes landed in trunk with several bugs popping up all over, he was leaning towards the pull, but now that the team seems to have addressed and crushed the majority of them, he’s more in favor in keeping the changes.
  • @clorith reminded that while they are worth doing, he agrees on the fact that the changes may have come a bit late in the cycle with limited time for testing and exposure.
  • @mapk asked if the a11y improvements at the cost of design worth immediate and rapid merging, or if we can take the time we need to fully test and address issues?
  • @samuelsidler asked about the items of concerns/tasks that can not or will not be fixed before 5.3 Release Candidate.
  • @melchoyce answered @samuelsidler about tasks that can’t/won’t be fixed before 5.3 RC:
    • Wider design changes to account for the shift in the hierarchy; because the new form fields are so much darker than the list tables, any page where both exist is thrown off a little.
  • @mapk answered @samuelsidler saying that he believes there are other design explorations to address and a committed testing cycle for a large release.
  • @karmatosed shared some worries she has about this:
    • Documentation: those that write tutorials and might find their screenshots out of date.
    • Testing: A longer testing phase for her would be better just like during mp6 project. She thinks that 5.4 should be a focused release, with testing, time and iteration feel safer.
  • @joemcgill said that since he has not been part of the discussions, he would be more concerned by process problems keeping a11y improvements from shipping rather than shipping changes that improve a11y and then iterating on the design.
  • @afercia clarified that most of the design changes come from design and were implemented on top of the a11y improvements. He also mentioned that from an a11y perspective all the matters are:
    • Removing the fixed heights from the input fields etc.
    • Improving contrast
  • He also said that all the other changes are unrelated to a11y and came from design feedback.
  • @samuelsidler asked @melchoyce if there is a plan in place to fix/iterate on those visual issues for the future? If yes, when in the future? He also asked if those improvements happen in 5.3.x or they would need to be in 5.4 or later?
  • @melchoyce replied to @samuelsidler and said that he thinks they would be wide-reaching enough that the design team would need to ship them in 5.4.
  • @earnjam expressed that he would personally lean toward a more cautious approach and allowing further iterating as a feature plugin with an earlier merge in a release cycle to allow more time to catch/fix the bugs. He also feels like we’re trading one set of bugs/issues for a different set and doing it during the beta period.

This discussion has continued with different arguments from design and a11y team members and with other contributors as well. You can read the discussion in its entirety here.

Calls for components maintainers have been skipped for this chat.

Open Floor

@azaozz noted that he’s started to get concerned by the 100+ tickets that are still open for 5.3. He invited maintainers and committers to review and comment on tickets that must be in the release and move the rest to the Future Release milestone.

@afercia said that while the a11y team is committing a lot of things, they will need urgent feedback on #47069 and #43037. @ryokuhi gave a brief explanation about the last ticket.

@davidbaumwald said he’s planning a last-minute scrub due to the high number of tickets that are remaining for 5.3. The schedule for 5.3 scrubs can be found here. Again, everyone is welcomed to attend scrubs and also to organize them.

@justinahinon shared a “Special interest” he has about developer documentation, dev-notes, and WordPress codebase. You can read about it on the chat agenda comments.

@davidbaumwald reminded that they will be doing a lot of punting at the end of the week, so two things:

  • If you have a ticket you absolutely want in 5.3, get moving.
  • If not, at least leave a comment on feasibility for 5.4, or he’ll be moving everything to Future Release if they haven’t seen any movement in a while.

@desrosj clarified that the tickets owned by committers and maintainers have largely been left in the 5.3 milestone to allow those owners to make the decisions they feel are appropriate. If those tickets are not gardened in the next few days they will be punted.

Finally, @azaozz added that the best would be the component maintainers to decide what is good to be in 5.3 and what is going to be in 5.4 of future releases.

That’s the end for this long, lively and important devchat.


#5-3, #dev-chat, #summary

Editor Chat Summary: October 2nd, 2019

This post summarizes the weekly editor chat meeting on 13:00 UTC, October 2nd, 2019 held in Slack.

The agenda can be found here.

WordPress 5.3

Slack transcript.

Gutenberg 6.6 was released and has been included in WordPress 5.3 beta 2.

Weekly Priorities

Slack Transcript.

The main current focus is still WordPress 5.3. Tasks are being tracked in this Github board. Starting work towards the content-block areas.

Task Coordination

Slack Transcript.

Open Floor

Slack Transcript.

@mikeschroder raised that WordPress 5.3 comes with an update to image uploads: if the server sends a HTTP 500 error (for example, because it couldn’t finish the thumbnail resizing) the process will be retried. This is implemented in the Media Library and Media Modal, but not in the REST API and Gutenberg yet.

@maximeculea mentioned that the mobile team is running an experiment with styled components (CSS in JS) as a way to learn whether styles can be shared between web and mobile.

@paaljoachim brough up that there is a PR that address some of Gutenberg float issues. @youknowriad and @joen noted that, currently, this falls in theme-land. We should make progress on some refactorings to the block list that are a better approach, leaving the current behavior as it is.

#core-editor, #editor-chat, #summary

Dev Chat summary: September 25

As our Release Coordinator @francina was not available yesterday, @mapk led this chat. Thanks to all the attendees.

Announcements and highlighted posts

First announcement was Beta 1 of WordPress 5.3 that went out earlier this week. Every one is invited to help test it and report bugs and unexpected behaviors. The Beta includes the first iteration of Twenty Twenty, the new default theme which development is ongoing on GitHub.

Here are some highlighted posts shared by @mapk:

@antpb also shared the Media component weekly report.

Upcoming Release Discussions

@mapk said Gutenberg team started a project board in the editor Github for the issues and pull requests that they’re hoping to get in or at least backport into 5.3.

Twenty Twenty lead @ianbelanger said the team is particularly looking for help on this issue.

@audrasjb made a post-Beta1 Accessibility update focus. 6 important tickets for the focus where committed just before the release. They are still 33 open tickets in the milestone. Everyone is invited to help tackle them and join the focus weekly bug scrub every Friday at 2 PM GMT+3.

@davidbaumwald remembered that there are dedicated bug scrubs for 5.3 with the schedule here which Beta 2 is scheduled for next Monday.

@desrosj noted that 5.3 Release Candidate 1 is scheduled for October 15, and that the list of remaining tickets in the milestone needs to be empty by this date.

Calls from component maintainers

@audrasjb pointed out the 15 ready to be committed tickets in 5.3 milestone and asked for available committers attention on them.

Open Floor was quiet yesterday. And the chat ended up under one hour at 9:40 PM.

#5-3, #devchat, #summary