Media Meeting Recap – November 14, 2019

The following is a summary of the weekly media component meeting that occurred on Thursday, November 14, 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: @sergeybiryukov , @pbiron, @spacedmonkey, @afercia, @dinhtungdu, @azaozz

Post 5.3 Triage

There were a few issues that came to light after folks updated to the 5.3 release.

Issues discussed:

  • #48632 : Cannot upload images directly from blogpost – Meeting participants attempted to replicate but were unable. Related issues were #48620 and #48604 in which one of the issues were due to a plugin.

That’s all that was reported as of meeting time last week! Thank you to everyone that contributed to WordPress 5.3! It really is a great update.

Meeting Scheduling Discussion

As you may have noticed, the time for the meeting was adjusted for Daylight Savings Time and moved later by one hour. There was some discussion in the meeting around adding a second meeting to the week allowing folks from both sides of the planet to participate. If you are in the AMEA region, please leave your thoughts on when the day and time of the week that works best. This topic will be revisited in the next meeting on Thursday, November 21, at 14:00 UTC

It was also mentioned that in this new scheduling model, it would be desired to move the currently scheduled meeting later one hour. This is of course only if there is another AMEA friendly meeting scheduled.

New Issues Triage

The meeting transitioned to a bug scrub after discussion about scheduling.

  • #48562 : Audio keeps playing on closing of media/attachment details popup in WP Admin – This was reproducible via the Media Library page in grid view. This issue has been around since 5.2 also so this is not a regression. Work is happening in the ticket to fix it up. The remainder of the meeting was filled with bunnies and discussion around a fix for the issue.

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 21, 2019 at 14:00UTC!

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

Core Editor Summary for November 20

This post summarises the weekly editor chat meeting (agenda), held on Wednesday, November 20, 2019, 14:00 UTC in core-editor Slack channel.

Weekly Priorities

Slack transcript.

See November Priorities post. Good to focus on these things as the month wraps to an end and start thinking on next steps.

  • Block Content Areas: expected to still be a focus for a while.
  • Navigation block (board): is close to get out of the experimental phase into the plugin.
  • Tightening up (board):
    • Polish to blocks and different parts of the UI is continuing.
    • Gradients are coming along nicely.
    • Some progress is being made to the Block Selection Tools.
    • Add color to specific text inside RichText (16014) is blocked by 17617 It’d be good to unblock those.

Triage role for GitHub

Slack Transcript.

GitHub has recently created a few new roles with more fine-grained permissions. One of those is the Triage Role that enables people to manage issues and pull request, and well as other actions. There was a consensus that this new role could help onboard new contributors and less technical folks who are not part of the Gutenberg group already.

Tasks:

If you’re interested in joining the Triage group, please, leave a comment in the agenda or the GitHub issue.

Task Coordination

Slack Transcript.

If you’re reading this asynchronously, please, add your notes as comments.

Open Floor

Slack Transcript.

Welcome feedback on this exploration of hover/selection states for Full Site Editing concepts by @shaunandrews

Request For Comments experiment. A few months ago Gutenberg started doing a RFC for major features following this post. @youknowriad noted that it didn’t get as much traction as expected. Many agreed. To close this experiment and the open RFCs is being considered.

If you have any feedback about the RFC experiment, please, comment on this post or reach out to people involved. Feedback channels will be opened until next week when a decission will be made.

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

Dev Chat Summary: November 20, 2019

Here’s a summary of the November 20 Dev Chat (agenda / Slack archive).

Announcements

The 5.3 Retrospective – Call for Feedback post.

@clorith asked, “Would it be an idea to also allow for an anonymous form to submit to that? I know some folks may not be comfortable with the potential for conflict, and may feel safer giving an honest feedback if it wasn’t all public under their name? Then the feedback could be provided by the leads under a followup post, with no relation to individuals.”

@francina said she’d change the post to mention that anyone who’d like to give feedback privately is welcome to do so. 5.3 release leads @davidbaumwald, @youknowriad, @justinahinon, @audrasjb also committed to offering the same.

Upcoming Releases

5.3.1

@whyisjake offered the current list of tickets in the milestone at https://core.trac.wordpress.org/query?group=status&milestone=5.3.1

After a quick discussion of potential release dates, December 11, 2019 came out a potential winner. It’s pretty soon, but it still gives us time to triage 5.3 regressions and bugfixes. That decision is not final – it’s pending more discussion in the comments.

Got thoughts on timing? Please leave them in the comments – the sooner the better.

While we see how those conversations shake out, @audrasjb graciously offered to lead the first 5.3.1 bug scrub on Thursday November 21, 2019 18:00 UTC

Next up: a call for volunteers to lead the release.

@sergeybiryukov, @audrasjb, @amykamala, @marybaum, and @whyisjake all raised their hands. Everyone expressed great confidence in the potential candidates.

Want to be part of the 5.3.1 release squad? Please leave a comment.

Open floor

@youknowriad brought up a discrepancy in the release cadence between WordPress Core and Gutenberg:

By December 11, the date proposed for a 5.3.12 release, Gutenberg will be ahead of Core with about 5 releases and this is a problem. 12 Gutenberg releases shipped into 5.3 . This is too much for a single WordPress release and with the current schedule, it’s seems like this is going to be similar for 5.4. This is not tenable for the future. It’s hard to stabilize and ship, it’s hard to summarize the changes for third-party [developers] and users, it’s more scary to ship and people were recommending the plugin to be installed for their clients (and it’s risky since the plugin is a development plugin). So how to reduce that gap is a big issue that needs solving IMO.Ideally I do think a shorter release cycle for majors is better. (Why not just a 5.4 in like end of January). [O]therwise we’ll have to include enhancements in minors.

This generated a long discussion that continued well past the end of the Dev Chat. See the full conversation starting here.

@davidbaumwald led the chat and wrote these notes. @marybaum did some editing.

#5-3, #devchat, #summary

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