Privacy Office Hours Agenda: Wednesday September 18th, 2019

The following is the agenda for the privacy weekly office hours meeting. The meeting is held every Wednesday at 19:00 UTC in the #core-privacy room of the Making WordPress Slack.

  • Announcements / Housekeeping
  • Upcoming Release (5.3) Discussion & Planning
    Note: We have 6 enhancements pending for 5.3, they will need to be committed or punted by Sept. 23rd, 2019.
    • #43890 – Allow Admin to Skip e-mail confirmation for Export/Anonymization.
    • #44133 – Should the Data Export indicate when we have no information on the user.
    • #44135 – Have Erasure button workflow follow Export button workflow replacing with static link.
    • #44588 – Denote the Copy action is complete by updating the Copy button to state ‘Copied’.
    • #46303 – Update wp_privacy_send_personal_data_export_email to provide the same filters as _wp_privacy_send_erasure_fulfillment_notification.
    • #46895 – Personal Data Export Report: A way to display the group count.
  • Feature Plugin Proposal: Privacy Data Request Form
  • Feature Plugin Discussion: Consent and Logging Mechanism for User Privacy
  • Discussion / Open Floor

If you have anything to propose for the agenda or specific items related to those listed above, please leave a comment below.

#core-privacy, #privacy

Editor Chat Agenda: September 18th

Note taker: @mikeschroder.

This is the agenda for the weekly editor chat scheduled for September 18, 2019 at 1300 UTC.

This meeting is held in the #core-editor channel in the Making WordPress Slack.

  • Gutenberg 6.5 Release
  • Weekly Priorities
  • Task Coordination
  • Open Floor

If you have anything to share for the Task Coordination section, please leave it as a comment on this post.

As always, if you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below.

#agenda, #core-editor, #editor-chat

JavaScript chat summary, Sept. 10th, 2019

Below is a summary of the discussion from this week’s JavaScript chat (agenda, Slack Transcript). Thanks to @cbravobernal for putting these notes together.

Agenda: Upgrading jQuery when user on the front end.

@adamsilverstein comment the idea of upgrading jQuery on the front end, due to the crashes that appear if you try to update the wp-admin part. There was discussion about removing jQuery from all WP, but is a hard task to do and we have still to be compatible with old browsers like IE11.


Anything new should either not use jQuery or at the very least work with the current version correctly.

Keep the discussion going in the ticket and hopefully we can arrive at a way forward.

Out of agenda: jQuery dependency on admin bar

@williampatton raised this Issue regarding the jQuery dependency of the admin bar.

The main discussion is what to do, use a temporary patch (for 2020 theme we are considering just enqueueing jQuery) or try to completely remove the jQuery dependency of that admin bar.

Seems that a “hoverintent” is the main problem of removing jQuery there, also other keyboard actions should be checked before removing it.


Keep tracking the issue

#core-js, #javascript, #meeting-notes

WP Notify weekly meeting agenda for 16 September 2019

Here is the agenda for the weekly meeting happening later today, Monday, September 16, 2019, 14:00 UTC and Monday, September 16, 2019, 22:00 UTC.

We were unable to meet last week, so this meeting will be follow up from the last meeting held on the 2nd of September, and will probably be a lot shorter.

  • Project contributors document
  • Follow up on project naming
  • Follow up on requirements gathering
  • Meeting host availability and contingency plans
  • Open Floor

If you have anything to propose for the agenda or specific items related to those listed above, please leave a comment below.

This meeting is held in the #feature-notifications channel , to join the meeting, you’ll need an account on the Making WordPress Slack.

#agenda, #feature-notifications

Dev chat summary: September 11


@Francina asked the group for announcements, and @jbaudras highlighted this Make/Design post:
There are 3 tickets waiting for final decision in order to land in WP 5.3

Then she added two more:

Make WordPress Core
Introducing Twenty Twenty
The Block Editor will soon celebrate its first birthday in Core and with every update it grows more capable. The promise of the block editor is to give users the freedom to design and structure the…

Make WordPress Core
Defining Content–Block Areas
One of the major projects from this year’s focuses is to expand the block editor beyond the content area and into other parts of the site. This included, so far, explorations to bring blocks into o…
Sep 5th

Media component maintainer Anthony Burchell told the group he’s been sharing that link around and getting great feedback.
@francina praised the video in the post. She added, “Personally I’m looking forward to seeing all the possibilities that blocks are giving us!”
After @afercia mentioned some accessibility feedback, @francina moved the discussion forward, inviting everyone (you too, dear reader!) to leave comments on the relevant posts.

Upcoming releases: 5.3

Bugscrubs: @davidb opened with this news: we still had 314 tickets milestoned for 5.3.

The discussion that followed surfaced a general preference to focus on enhancements and features between now and Beta 1, when features freeze, and on bug fixes between Beta 1 and release.

As of devchat, 120 features and enhancements are milestoned for 5.3 on Trac.

@davidb and the focus leads will do a bit of promoting to get more folks to come to bugscrubs.
(Ed. note: Beta 1 should land September 23; final release is slated for November 12.

Default theme focus lead @ianbelanger reported in on the next default theme, Twenty Twenty. has a weekly meeting, on Mondays at 19:00 UTC, and has opened its Github repo to contributors.

Marketing has nominated @miker as its focus lead for the release. It’s started meeting on Fridays at 16:00 in the Marketing channel, to work on copy for the About page. @marybaum and @miker asked for input from maintainers on enhancements they think are important.

In Docs, we have one dev note published and two more under review. Lead @justinahinon is going to all the component meetings, to let their teams know the Docs team is around to help with their notes.

Media: @mikeschroder is the 5.3 focus lead.

Next bugscrub is Thursday at 05:00 UTC. Check the rest of the schedule at


@antpb reported in on Media, which is also taking the lead on APAC-friendly meeting times. As he said:

“This devchat does not align with normal hours for him, so I will help with updates here. Discussion about the scope of the 5.3 Media will take place tomorrow at 13:00 UTC (agenda to come soon in the #core-media room). I anticipate the scope to largely focus on a11y and image handling improvements. I know of a few on my plate currently that will also fit in line with the release focus of UI improvements.”

@clorith and @jeffpaul will work to get scrubs posted on WordPress 5.3 Development Cycle – Make WordPress Core.

@pierregordon volunteered to become a maintainer for the External Libraries component.

And there was more discussion on getting people to come to bugscrubs.


As we hit the hour, folks who needed to do other things (like sleep, eat or work) signed off. But the chat was still lively enough that several people stayed on tolerant more about exactly what a component maintainer’s role includes.

@jbaudras referred to this post:

These maintainers are vital to keeping WordPress development running as smoothly as possible. They triage new tickets, look after existing ones, spearhead or mentor tasks, pitch new ideas, curate roadmaps, and provide feedback to other contributors. Longtime maintainers with a deep understanding of particular areas of core are always seeking to mentor others to impart their knowledge.

From (edited)

Devchat ended at ten minutes past the hour.

#5-3, #core, #devchat, #twenty-twenty

Core editor chat summary September 11th, 2019

This post summarizes the weekly editor chat meeting agenda here. Held on Wednesday, 11th September 2019 held in Slack. Moderated by @youknowriad.

Weekly Priorities

Gutenberg 6.4 and WordPress 5.3

The upcoming Gutenberg release next week (Monday 16th September) is going to be the last one that is backported completely to Core for 5.3. WordPress 5.3-beta is due on 23 September.

By this time, all the features that are meant to go into WP 5.3 should already be merged, so it is a matter of getting in the last few features. After the beta1, we’ll have more time to polish/fix bugs.
@gziolo is working on the WordPress Core Patch. It needs more testing and approval.
@jorgefilipecosta added some backport of PHP API for block styles registration from Gutenberg.

Task Coordination

@jorgefilipecostaLast week:
Continued the iterations on the Gradient mechanism, proposed a buttons block and submitted some bug fixes and regression fixes.
– Refactored the cover min-height resizing to use a true min-height on the editor (instead of height).
– Helped the core update patch (reviewed and ported the block styles server functions).
Next week I will less available time, I will try to help some PR’s arrive at the finish line, namely the color formats, gradients and continue to help some core tickets.

@gzioloLast week:
– Updated the WordPress Packages to the ones used in the Gutenberg 6.4 release.
– Generated asset file in PHP format with the list dependencies to use with plugins and core.
– Added new Babel macro (or plugin) which handles block.json file transformation with 18n support.
Next week:
Whatever is necessary to have Gutenberg 6.5 ready and integrated with WordPress 5.3.

@youknowriad – Worked a little bit on a reusable blocks refactor which hopefully solves a bunch of related issues.
This week.
– I’ll be totally focused on WordPress 5.3 on the next days/weeks.
– I want to add a small friendly reminder note about the “Dev Notes” for WordPress 5.3.
– If you worked on these PR’s that require Dev Notes, it’s a good time to start writing these. I will write some of these and I’m available to help others too.

@paaljoachim – I have focused on older PR’s asking about status updates and how we could move them onward. This also means there seems to be a few PR’s that are it seems stuck and need some last adjustments, final code reviews and merging.

Open Floor

@yannicki – As already discussed in the previous meeting, a padding option for group block would be a much needed feature for 5.3.
Adds basic dimension controls to Group Block
Add DimensionControl component
@youknowriad Yes, that’s a great feature. Thought at this point, It does seem that it’s probably too late for this to land in a good state.
@paaljoachim Btw @get_dave has been very busy for a while now so that he has not had the opportunity to continue work lately on the padding/margin PR’s.

@afercia – To my understanding RichText is now split in two RichText components.
– “wrapping” RichText and “bare” RichText.
On the other hand, we’re also getting warning for the deprecated wp.editor.RichText which is now wp.blockEditor.RichText
I can’t figure out how to make the custom blocks work and make them compatible with WP 5.1 / 5.0, described here: RichText changes and custom blocks backwards compatibility for WP 5.3
Deprecations warnings are totally fine and we are going to support both ways to use RIchText through wp global.
We should provide a backword compatible support for removed props if they were removed. – See the Slack discussion for more information.

Would working with floats become easier, when this PR is merged?
Fix: Clear floats on specific successive blocks that use alignment tool
I feel “floats” are intrinsically complex and it will always be the case. I’d love if we could actually remove them entirely. It’s not going to happen, don’t worry, but things like columns, grids… make floats less necessary.
UI consistency in regards to the heading should be merged and land in core:
Heading block: move alignment controls to toolbar
Yes, this one is a good quick win, I’ll see if we can land it this week. Might need to work with @andraganescu on it.
Some links might be embedded while others are not.
Option to use text link instead of auto embed.
It looks like the solution here is a block transform from embed blocks to paragraphs which is arguably easy to add. If there’s any new contributor that would want something to try, this seems like a good opportunity.
@desaiuditd Volunteered to work on the issue. Here is the PR.

I was hoping for feedback/direction on SlotFill sorting with a priority property if possible.
To be honest, I’m not entirely sold on this because it’s very tied to the implementation of the Slot. (not a fully semantic API). I don’t have a better alternative at the moment. I know @matias have some thoughts about that as well.

Had specific questions for Introduce a filter to override Document label in Document Settings Header. See the Slack discussion for more information.

Dev Chat Agenda for September 11th 2019 (5.3 week 4)

Here is the agenda for the weekly meeting happening later today: Wednesday, September 11, 2019, 11:00 PM GMT+3. Please share any items you’d like to include in the comments below!

  • Announcements and highlighted posts
  • Upcoming Release Discussions
  • Calls from component maintainers
  • Open Floor

If you have anything to propose for the agenda or specific items related to those listed above, please leave a comment below.

This meeting is held in the #core channel. To join the meeting, you’ll need an account on the Making WordPress Slack.

#5-3, #agenda, #devchat

Editor Chat Agenda: September 11th

This is the agenda for the weekly editor chat scheduled for Wednesday, September 11, 2019, 03:00 PM GMT+2.

This meeting is held in the #core-editor channel in the Making WordPress Slack.

  • Weekly Priorities
  • Tasks Coordination
  • Open Floor

If you have anything to share for the Tasks Coordination section, please leave it as a comment on this post.

If you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below.


Core themes chat summary for September 4, 2019

These are the notes for the weekly Twenty Twenty meeting which takes place on Mondays. You can read the full transcript on the core-themes Slack channel (archive link) and find the meeting’s agenda here (also on Slack, for this first one).


Thanks all around

The Twenty Twenty GitHub repo was made public on Friday, and there’s been a flurry of activity over the weekend with numerous issues posted and Pull Requests created. We’ll be working through them and will try to address all of them in time.


It’s a tight deadline, with just two weeks left until Beta 1, so major topics other than those alredy in the agenda were encouraged to be kept to GitHub.

Discussion Topics


Non-latin font fallbacks

A ”Support for non-latin font fallbacks” issue (#118) has been created, with calls for suggestions on which font fallbacks to include for each alphabet. There are lots of alphabets yet to be added, so suggestions are welcome. The issue could also use suggestions on how to best include the CSS for the different alphabets. @nielslange offered to take a closer look at that.

Whether to bundle a font

One proposed solution was to limit the font-family setting to serif and sans-serif. That led to a bigger discussion about whether a bundled font should be used, or if we should rely on a stack of system fonts like Twenty Nineteen. The arguments for using system fonts were that it reduces the size of the theme, and the page size of sites using it. The argument against is the user experience being uneven depending on which system the visitor uses. The discussion will be continued on GitHub.

Build Tools

Due to the tight deadline, the team has decided not to go overboard with using build tools for the theme.


The structure of the header menu locations was brought up by @joyously. Currently, the theme is intended to use three menu locations for the header. One for mobile, and two for desktop: a horizontal, traditional one, and one hidden behind a toggle. The arguments against the structure is that it could be confusing to the user, for two reasons:

  • The distinction between the two different desktop menus would not be clear
  • Users might not set a menu to the mobile menu location, and not understand why a menu is not displayed on mobile

A suggestion was made that the mobile menu can fall back to either the horizontal menu or the modal menu, if the mobile menu has not been set. The discussion will continue in a GitHub issue (#164).

Migration from jQuery to Vanilla JS

@fabiankaegy has created a PR for converting the currently jQuery based construct.js file to a Vanilla JavaScript one, using @wordpress/scripts. The discussion around it centered on whether @wordpress/scripts was needed. It was argued that including it adds a barrier of entry to new contributors, and that given the small amount of JavaScript needed to replicate the current jQuery functionality, @wordpress/scripts wasn’t needed. @fabiankaegy has since added a new PR without the build tooling, which can be found here: #163.

@audrasjb also raised concerns about removing the jQuery from the theme entirely, as the admin bar doesn’t function correctly when jQuery is not enqueued by the theme. This is described more in detail in an issue for Twenty Nineteen. @williampatton will try to look at the issue in Core and check if a fix is doable by 5.3. If a fix is not included in 5.3, it was decided that Twenty Twenty will enqueue jQuery when the admin bar is displayed, same as Twenty Nineteen.

Open floor

Due to the meeting already running 30 minutes long at this point, the open floor was skipped.


Media Meeting Recap – September 5, 2019

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

Attendees: @anevins, @sergeybiryukov, @pstonier , @afercia, @francina, @mikeschroder

Media Focus Lead for 5.3

Much like the 5.0 release, 5.3 will have many designated release leads around each focus/component in the project. 5.3 is right around the corner and now is the time for a decision to be made on a release lead representing the Media component. Previously @antpb had offered to take on the role if no others were interested. In this weeks Media meeting, a volunteer emerged! @mikeschroder has graciously offered to take on this role. Thanks Mike! Mike is in the JST time zone. This brings an awesome opportunity to have global representation in the team. @antpb has offered to help with relaying information or representing where time zones do not conveniently meet for Mike.

5.3 Ticket Triage

#47135 – Drag and drop functionality unavailable to keyboard or touchscreen — It was determined by the team that this issue exists more globally in meta boxes. It was deemed appropriate to document the information from the Media focused instance of this in an existing ticket on the issue: #39074 No method to move meta boxes using keyboard which was also given the keyword wpcampus-report for tracking purposes.

#47137 Insuficient form semantics – @anevins asked “Is there a technical reason why there isn’t a form element being used around that attachments browser code? That would defeat all of the remediation advice.” @afercia had these recommendations: “Ideally it should be a form because that helps in establishing semantic relationships. However, the sidebar is not rendered in all the views, so including the select area, the attachments list and the sidebar within one form might be a bit complicated.
The list of attachments is perceived as a list of checkboxes so it makes sense to wrap it within a fieldset + legend. I’d tend to think it would need more work in the future because yes, it’s a group of checkboxes but it actually works like a mini-application with custom interaction. I’d say fieldset + legend would help, for now.”

Triage on unanswered tickets continued after the meeting closed, and can be followed here.


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 September 12, 2019 at 1300UTC!

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