Mobile Team Update – November 19th

WordPress iOS and Android version 13.7 will be available for testing later today. Sign up here to join the beta program on iOS or follow this link on your Android device, tap on Become a beta tester.

Highlights for the last two weeks:

  • Block Editor: We added alignment options in paragraphs, block and Pexels support on iOS, fullscreen image preview on Android, and made improvements to unsupported blocks.
  • Full Site Editing: Spacer block is ready for shipping. Alignment options made available on Media & Text. Gallery, Group, and SPTs are in progress.
  • Other Projects: Work on dark mode continues for Android. We’re making progress on the Media Editing and Post Logic Improvements projects.
  • Infrastructure: Improvements to Sentry crash reporting.


Plugin Review Team: 18 Nov 2019

Plugin Status Change Stats

  • Plugins requested : 168
  • Plugins rejected : 17
  • Plugins closed : 27
  • Plugins approved : 69

Plugin Queue Stats (current)

  • Plugins in the queue (new and pending)* : 700
  • → (older than 7 days ago)** : 616
  • → (2019-11-11 – 2019-11-18) : 72
  • → (new; not processed or replied to yet)* : 9
  • → (pending; replied to)* : 691

HelpScout Stats

  • Total Conversations: 317 (+4%)
  • New Conversations: 225 (+6%)
  • Messages Received: 365 (+11%)
  • Customers: 278 (+1%)
  • Conversations per Day: 39 (+3%)
  • Busiest Day: Friday
  • Replies Sent: 437 (+3%)
  • Resolved on First Reply: 31% (+2%)
  • Resolved: 193 (+31%)
  • Resolution Time: 4d 7h (+21%)
  • Customers Helped: 261 (+5%)
  • Replies per Day: 62 (+3%)
  • Closed: 265 (+24%)


November 14th Support Team Meeting Summary

General announcements

bbPress 2.6 was released this week, and has been deployed to the various forums. Please note that an upgrade notice will show up in wp-admin if you have the appropriate access, don’t click this, the meta team will handle the upgrade routines accordingly once they’ve been tested in our large setup scenario.

WordPress 5.3

The new version of WordPress, version 5.3, was released this week.

As is customary after a major release, the WordPress 5.3 Master List has been published, and is a living document being updated with anything we find that breaks WordPress for users.

Discussion on linking to off-site support platforms

A hot topic this past week has been linking to support-topics that are outside of

Some good conversations were covered during the weekly meeting, and a make/support post has been published outlining what we discussed, and allowing for input from those unable to attend the weekly meeting.

Read the meeting transcript in the Slack archives. (A Slack account is required)


Design team update November 15th

Another week saw more exciting posts and activity in the design team.

Meetings and triage

On Wednesday the design team met at the usual time of 19:00 UTC. Monday and Tuesday saw triages run also in #design.

Calls for involvement

Here are some calls for involvement for the design team:

Posts this week

If you are having a WordCamp that has a design contribution table, please reach out in #design so you can be added in future updates.


November 7th Support Team Meeting Summary

We had our final call for changes to the WordPress 5.3 Master List, along with a call for testing of WordPress it self, as the next version of WordPress is scheduled for November 12th.

We discovered that there’s a need for a specific page for Twenty Twenty that the feature theme team has already finalized (teamwork makes the dream work!), which will be linked up properly after the upcoming release.

Fair warning as well, that next meeting we will be utilizing the meeting-opener used by many other teams. The support team in general doesn’t use the /here command, as we wish to avoid notification burnout, but we will be using it for the first meeting after a major release to make sure we can gather any important information that surfaces from users after a release.

Checking in with international liaisons

Members of our community from Sweden, Italy, Netherlands, India, Russia and Spain were part of this weeks meeting, with some new members from a few of them stopping by!

One of the contributors asked about information on highlighting topics to see which ones need addressing still, which the support team has a tool for at

Open floor

A request for more details for those running a contributor day was put forth. Turns out the existing page had been edited, and left in a state pending review. This has been re-published and is available at

We would like to improve the getting started documentation, so if you’ve ever held a contributor day and done support, input on what worked, what information you felt was missing, and what could be improved upon is very much welcome at any time.

If you would be so kind, please leave a response to the annual WordPress user survey for 2019.

Read the meeting transcript in the Slack archives. (A Slack account is required)

🎉 With the influx of new users lately, we’ll revitalize the contributor tips, a crowd favorite.

Helping out is awesome, but be selfish now and then, take the time you need to relax and unwind.

Contributor Tips


Design team update November 8th

The past few weeks designers across WordPress were involved in multiple WordCamps, WC Tokyo and WordCamp US, to name but two of those. There was also a wide variety of work from 5.3 wrangling to Gutenberg and beyond.

The meeting times are changing with daylight saving in some countries.

  • Monday: 17:30 UTC – core/meta triage
  • Tuesday: 17:00 UTC – Gutenberg triage
  • Wednesday: 19:00 UTC – Design weekly team meeting

Weekly meeting

The design team held their weekly meeting at 18:00 UTC in #design. You can catch up on all the notes here:


The design team continues to have triages each week, one for core/meta and one for Gutenberg.

Calls for involvement

Here are some calls for involvement for the design team:

Interesting posts

If you are having a WordCamp that has a design contribution table, please reach out in #design so you can be added in future updates.


Mobile Team Update – November 5th

WordPress iOS and Android version 13.6 will be available for testing later today. Sign up here to join the beta program on iOS or follow this link on your Android device, tap on Become a beta tester.

Highlights for the last two weeks:

  • Block Editor: We added image alignment controls and also Pexels library support on Android.
  • Full Site Editing: Spacer block is merged. The team delivered fixes for beta requests and issues detected during tests. We also made progress in Gallery and SPTs.
  • Offline Support: Offline posting on iOS was merged to develop and high priority issues found in call for testing were fixed.
  • Other Projects: A rough version of dark mode is finished on Android.
  • Infrastructure: Finished configuring notifications for FluxC tests on API change.


Plugin Review Team: 04 November 2019

Following a day of travel, we have great news. The team has onboarded two new members to handle security and administrative details of the plugin team. We’re also working on how to properly separate reviews from ongoing security/behavioural issues.

Plugin Status Change Stats

  • Plugins requested : 159
  • Plugins rejected : 9
  • Plugins closed : 298
  • Plugins approved : 62

Plugin Queue Stats (current)

  • Plugins in the queue (new and pending)* : 700
  • → (older than 7 days ago)** : 595
  • → (2019-10-28 – 2019-11-04) : 70
  • → (new; not processed or replied to yet)* : 51
  • → (pending; replied to)* : 649

HelpScout Stats

  • Total Conversations: 456 (-67%)
  • New Conversations: 215 (-83%)
  • Messages Received: 400 (-72%)
  • Customers: 262 (-39%)
  • Conversations per Day: 57 (-67%)
  • Busiest Day: Tuesday
  • Replies Sent: 406 (-29%)
  • Resolved on First Reply: 34% (-6%)
  • Resolved: 182 (-29%)
  • Resolution Time: 3d 5h (-19%)
  • Customers Helped: 240 (-37%)
  • Replies per Day: 58 (-29%)
  • Closed: 425 (-35%)


WordCamp US Contributor Day 2019


  • Reviewed and commented on a draft document outlining criteria for inclusion of hosts on a new /hosting page on
  • Found a fix for WordPress Travis CI reporting
  • Got access to PHPUnit Plugin reporter used for showing hosting test results
  • Content review and edits to the Hosting Handbook – it had fallen a bit out of date


  • created a list of missing or incorrect information in the Gutenberg block documentation
  • Two reps designated for Gutenberg developer and user documentation
  • Migrated content from Codex to Devhub
  • Tidying up handbook issues
  • Tagging some articles as documentation


  • onboarded new contributors
  • New contributors helped get two new commits in: r46639 & r46640
  • set up and ran a unit test on a patch
  • agreed proposed direction for REST API core authentication support
  • Privacy – potentially displaying privacy info in plugin readme for hopeful adding to plugin repo
  • Roadmap for Site Health + action plan for v2
  • Solicited user feedback on Core 5.3
  • @TimothyBlynJacobs made his first commit to WordPress Core

Kids Camp

  • Started first ever kids camp at a WordCamp US!
  • Scavenger hunt where kids took selfies with people from each contributor team to use in the creation of their WordPress sites!


  • A couple usability testing scripts have been written.
  • Going through all Gutenberg issues labelled as “needs testing” – over 15 tested
  • Helping other contributors get their testing environments set up


  • Translated 5.3 for Dutch


  • Subtitling videos to use for marketing purposes
  • Updates to example sites on
  • Interviewing other teams and working up a recap post


  • Fire, forage, and treasure exercise with post-its
  • Working on Author block
  • Working on processes for product design for WordPress


  • Testing
  • Environment setup
  • Updating new contributor onboarding documentation
  • Regression testing on iOS beta release


  • We’ve gotten everyone acquainted with the accessibility team, how to contribute and where to find important team info
  • We split the group into two: those who are new to a11y and want to go over 101 basics and those more familiar with it and want to learn how to get started contributing
  • We went over Trac and GitHub and learned how to create and give feedback on tickets and issues
  • We discussed the many different ways in which people can contribute, wether that’s with code, design, testing or feedback, everyone can participate
  • Working through Trac tickets
  • Testing, giving feedback, and opening issues for new stuff
  • After lunch we all paired and started diving into Trac. The team is already helping move tickets forward by testing, suggesting solutions and submitting patches.


  • Onboard 4-5 new people to the team
  • Discussing what the causes may be of fewer unanswered issues than normal
  • “No reply” topics down to 4


  • Working on updating Lando testing system
  • Closed several existing issues
  • Work on docker environment to make running tests more reliable


  • Got Aaron access to make this post!
  • Onboarded 4 people
  • Fixed 4 issues
  • Fixes 2 issued for Five for the Future
  • Fixed 1 issue for


  • Onboarding
  • Iterations on Make.WP site
  • Forms, new page templates, and taxonomies for lesson plans
  • Working on lesson plans for:
    • Getting started with CSS
    • Installing plugins
    • What you can do with WordPress
  • 3 new prs for meta site
  • 3 lesson plans were instructionally reviewed.


  • New meetup organizer orientation
  • Documentation for reaching out to prior WordCamp sponsors
  • WC Asia budget review
  • Going through WCUS 2019 photos
  • Working on messaging and benefits around speaker diversity training
  • Onboarding checklists
  • New WordCamp organizer orientation
  • New meetup chapter vetted and ready to launch
  • Diverse Speaker Training Team: Marketing text for promoting our workshop to meetups
  • Diverse Speaker Training Team: Edited training videos
  • Diverse Speaker Training Team: Started creating diverse events self-guided training


  • Teaching people how to access videos from WordCamp that need to be edited.
  • Several people are modding and editing videos from:
    • WCEU
    • Jacksonville
    • Birmingham
  • Two people submitted their first video to wptv
  • Published State of the Word 2019!
  • Onboarded people for moderating and editing


  • Lots of progress planning the WPGraphQL v1.0 Roadmap
  • Onboarded two new volunteers
  • Streamlined flows


  • Working on rate limiting issue

#contributor-day, #wordcamp-us

Five for the Future: Open for Pledges

I’m very proud to announce that the first iteration of the Five for the Future pledge program is open for pledges! Individuals and organizations can now publicly pledge their time to contribute to WordPress in a centralized place that is public and transparent.

The intent of this program is to acknowledge the organizations and individuals who contribute regularly to WordPress, helping to sustain the project and work on ongoing initiatives. My hope is that this will encourage contributions from the wider WordPress community. Naturally, the same expectations for promotion on also applies to this program.

This program wouldn’t have been possible without the dedication and hard work of some amazing contributors! Props to all the people who designed, developed, gave feedback, and tested:

@ryelle, @mrwweb,@miss_jwo, @melchoyce, @liljimmi, @jorbin, @jeffpaul, @imath, @iandunn, @hristo-sg, @hlashbrooke, @earnjam, @courtneypk, @coreymckrill, @clorith, @chanthaboune, @camikaos, @angelasjin, @andreamiddleton, @adityakane, @aaroncampbell, @_dorsvenabili

If you have questions, find issues, have suggestions for future iterations, or think of improvements we could make to the program in the coming months, please comment on this post!