REST API Meeting Agenda for March 14, 2019

The REST API weekly component chat will occur this week at March 14, 2019 18:00 UTC. If your country has recently adjusted for daylight savings time, please note that this may be a different hour than the past few months.

This week we will be continuing discussion from prior weeks around documentation needs, a canonical REST API authentication plugin, and 5.2 ticket priorities.

All agenda items are welcome, from all teams and contributors; please post them as suggestions on this document.

#agenda, #rest-api

Media Meeting Recap – March 7 2019


This post is a summary of the latest weekly Media component meeting, which took place in the #core-media Slack channel, on Thursday, March 7th, 2019. The purpose of these meetings are to move priority tasks forward, provide feedback on issues of interest, and review media focused issues. The focus of this meeting, was around the timing of our meeting going forward.

Attendees: @joemcgill @audrasjb @desrosj @antpb

Transcript: Read on Slack

Media Meeting Time Change

A time change has been discussed in the prior few Media meetings to better fit the schedules of folks all around the world. It was agreed that the time going forward would be Thursdays at 13:00-1400 UTC. We will be starting this schedule starting with the next meeting on Thursday, March 14th, 2019.

Next Meeting

The next #core-media meeting is set for Thursday, March 14, 2019 at 13:00UTC See you there!

#core-media, #media, #summary

Core Privacy’s 2019 Roadmap Published

We are super excited and proud to announce the #core-privacy team’s V2 Roadmap, which was published last week.

  • We’ve worked through the roadmap for the past few months, focusing on building for general privacy enhancements rather than specific legal obligations.
  • We intend to enhance our existing tools (the Privacy Policy generator, export tool, and the erasure tool we built for the V1 GDPR phase) while also developing extended support for things like Embed Privacy Controls and WP-CLI support. We are, of course, keeping an eye on legal developments in the privacy sphere to learn what tools and enhancements we’ll need to build a little later on as the needs change.
  • Where possible, we’ll work to build out plugins first, in order to make development easier for features, and then offer them as a merge to Core.

Let us know what you think of our roadmap! Share your feedback in the #core-privacy Slack channel.

As a friendly reminder, we are always looking for new contributors to our great little team. You can find our open Trac tickets here. We have bug scrubs on Mondays at 1600 UTC and we meet for office hours on Wednesdays at 19:00 UTC.


Dev Chat Agenda: March 13

Below is the agenda for the weekly devchat meeting on 2019-03-13 21:00:

  • Announcements
    • 5.1.1 is released!
    • 5.0 retrospective
  • 5.2 updates
    • Feature freeze in ~1 week (Mar 21)
    • Target release in ~7 weeks (April 30)
    • Task coordination
  • 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 in the Making WordPress Slack.

#5-2 #devchat #agenda

X-post: Strengths and Challenges: Organization

X-comment from Comment on Strengths and Challenges: Organization

JavaScript Chat Summary, March 12th, 2019

Below is a summary of this week’s JavaScript chat (agendaSlack Transcript). Have a topic for discussion for the next meeting? Leave a suggested edit on next week’s agenda.

Daylight savings time

Slack Conversation

@aduth proposed to not move the meeting time this instance, because for some people having the meeting an hour later means they can attend. If you have any feedback on this proposal, please leave a comment.

Default webpack configuration

Slack conversation

A default webpack configuration pull request has been merged to wp-scripts. So plugin authors can now do wp-scripts build and that will build their JavaScript into a bundle for the browser.

There was a brief discussion on whether or not the build command should accept a custom webpack configuration. For now this will stay possible. In the longer term the default configuration should be good enough for a lot of users and the Gutenberg webpack config should align with the default config as much as possible.

Pull request for typescript definitions

Slack conversation

The Gutenberg repository received a pull request with TypeScript definitions. This raised the broader question whether these pull requests should be accepted, because these definitions also need to be maintained.

In the chat the consensus was that it is only worth merging these kinds of PRs if the maintainability burden is very low. Given that is not the case it is probably better to not merge the given PR.

This will be decided on next week, please comment here with your ideas on this.

Removing grunt dependency from grunt-patch-wordpress

Slack conversation

@jorbin wants to make the grunt-patch-wordpress tool a general command-line utility that runs without a grunt dependency. Everyone agreed that this is a good idea. The new package will be located inside the monorepo like all other JavaScript packages.

#core-js, #javascript

Editor Chat Agenda: March 13th

This is the agenda for the weekly editor chat meeting on Wednesday, 13th March 2019, 14:00 GMT.

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

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


WordPress 5.1.1-RC1 is now available!

We need your help to test it! You can find the build here:

What’s in this release?

5.1.1 mostly addresses regressions introduced in 5.1. It also includes some changes designed to help hosts prepare users for the minimum PHP version bump coming in 5.2 (see #46074 and #46065).

You can browse the full list of changes on Trac.

What’s next?

Committers: Please consider the 5.1.1 milestone and the 5.1 branch frozen, barring any major issues with RC1.

The 5.1.1 release is scheduled for 2019-03-13 00:00 UTC.

Editor chat summary: 6 March 19

This post summarizes for the weekly editor chat meeting on Wednesday, 6th March 2019, 14:00 GMT.

Gutenberg 5.2

Gutenberg 5.2 was released today. It is a technical release essentially focused on building a generic block editor module. It is less about specific features and more about foundational work needed for the widget screen explorations.

Expect documentation (and dev note) about this new module in the upcoming weeks.


  • Our current roadmap priorities are the Block Management and Widgets Screen work.
  • The New workflow for releasing npm packages and synchronizing Gutenberg with WordPress Core is merged and a ticket to synchronize WordPress trunk is ready.

Focus for the week

  • @aduth and @mapk are continuing to work on the Block Management Features.

The a11y team is preparing a list of high-priority accessibility issues that we’re all encourage to help with.

Note: Anyone reading this summary outside of the meeting, please drop a comment if you can/want to help with something.

Open floor

The meeting archive is here.

The agenda for the next meeting is here, please add anything you want to discuss.

#meeting-notes, #core-editor, #editor, #gutenberg

JavaScript Chat Summary, March 5th, 2019

Below is a summary of this week’s JavaScript chat (agenda, Slack Transcript). Have a topic for discussion for the next meeting? Leave a suggested edit on next week’s agenda.

Slack Conversation

Following up from the previous week’s agenda item about the field in package.json file. @greatislander was successful in having his enhancement merged into the upstream npm-package-json-lint package. He also followed up with a pull request to use it in Gutenberg.

Npm package release process

Slack Conversation

Right now the timeline for publishing npm packages is strictly tied to WordPress releases. Moving forward, the idea is they would be published more frequently as proposed by @youknowriad in this pull request. It is expected to start using the revised workflow soon after Gutenberg 5.2 release is out which is planned for Wednesday.


Slack Conversation

@nosolosw merged a pull request with the first iteration of the @wordpress/docgen package, which will be used to auto-generate public API documentation from JSDoc comments. The idea is that the npm run docs:build command will re-generate the package’s README when something changes in the JSDoc comments. There is a master issue opened where follow-up tasks will be tracked. It’s expected to have a massive number of pull requests created which add public API documentation to most of the existing packages.

#core-js, #javascript