Support Team Update – Novemebr 2nd

General announcements

The WordPress 2017 survey is up, help us understand how WordPress is used so we can better align its direction by filling it out, it only takes a few minutes.

Time zones and daylight savings are again showing their faces, a quick tally shows that the current time of 16.00 UTC is still a favorable time for the majority of us, but we’ll do another check at the next gathering when the whole world has finished with these shenanigans.

WordPress 4.9

We’re getting very close to the 4.9 release date, and as such the draft for the master list has gone up as is customary, if there are core changes or gotchas we should prepare for, please provide them as comments on that post.

WordPress 4.9 Master List Draft

As mentioned, release date is growing ever closer, so if possible please help test. Release Candidate (RC) means it should be feature complete and all known bugs are taken care of, so it should be safe to test in any way you can think of at this point.

Checking in with international liaisons

The Russian, Swedish, Spanish, Portuguese and Italian communities stopped by for this weeks meeting. We love to hear feedback from the non-English parts of the community, so if you know someone who’s from a locale we don’t often hear from, feel free to invite them over, there’s value in sharing after all!



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


Plugin Review Team Status – Nov 6 2017

The high number of rejected is due to end-of-month cleanup for plugins that were reviewed but had no reply within 6 months. Anyone who did reply to a review got a reminder email. Since they can’t submit another new plugin while the ones are pending, this is more of a hardship for them than us.

All plugins are reviewed within 7 business days of submission. If you didn’t get a review, check your spam.

Plugin Status Change Stats

  • Plugins requested : 124
  • Plugins rejected : 106
  • Plugins closed : N/A
  • Plugins approved : 106

Plugin Queue Stats (current)

  • Plugins in the queue (new and pending)* : 664
  • → (older than 7 days ago)** : 574
  • → (2017-10-30 – 2017-11-06) : 72
  • → (new; not processed or replied to yet)* : 54
  • → (pending; replied to)* : 610

SupportPress Queue Stats

  • Total open tickets* : 21
  • → (with no activity in last 7 days)** : 4
  • Within defined 7 day time window:
    • Total : 297
    • Closed : 296
    • Open : 1


Theme Review update for November 6, 2017


  • 247 new tickets are waiting for review.
    • 142 tickets are older than 4 weeks
    • 193 tickets are older than 2 weeks
    • 219 tickets are older than 1 week
    • 238 tickets are older than 3 days
  • 43 tickets are assigned to 22 reviewers.
    • 44 tickets are older than 4 weeks
    • 45 tickets are older than 2 weeks
    • 46 tickets are older than 1 week
    • 46 tickets are older than 3 days
  • 0 are approved but are waiting to be made live.

In the past 7 days

  • 220 tickets were opened
  • 221 tickets were closed:
    • 204 tickets were made live.
      • 18 new Themes were made live.
      • 186 Theme updates were made live.
      • 0 more were approved but are waiting to be made live.
    • 15 tickets were not-approved.
    • 2 tickets were closed-newer-version-uploaded.

#themes, #trt

CCOC project meeting notes – 17th & 31st October

17th October Notes:

A quick catch up on the meeting that happened on the 17th October

@mor10 and @morgankay were in attendance and shared the survey they have been working on.

They had it sent to an 3rd party survey expert to get feedback on the language and questions used in the survey.

31st October Meeting Notes:

The group met in the #community-team Slack.

Thanks to the people who participated: @sippis, @andreamiddleton, @morgankay, @mor10

The research CoC has a few more entries. The problem has been finding public articles about CoC situations that have been enforced and also articles against a CoC.

The CCoC survey has been reviewed by the survey expert and comments have been actioned.

The survey is now ready for review. The new questions are found under the Questions – Proposed header. Reasoning and discussion are found in the Questions – Draft header.

Please add comments to the survey document with anything you want to raise relating to the questions of the comments.

Next actions for the survey:

  • Put survey questions into a survey collection method.
  • Roll out the survey.
  • Publicise the survey.
  • Set a hard limit on return date

There was a discussion on how to push the survey. The discussion included a debate on how much pushing did we want to do for the survey and the balance between getting large dataset and not having a skewed dataset based on one portion of the community.

The idea came to do two things:

  1. Email all meet up group organisers with information about the survey and ask them to share it with their meet up groups.
  2. Post on all Make P2s.

Some concerns include ensuring that there is clear communication about the intent of the project and the survey.

There was an idea to bundle some other Community related information in the same blast-out or if it was important to to have the message exclusively CoC-related. It would be good to know what potential information the bundle would include before making a decision.

There was also a lively debate over whether we should ask about any demographics of the survey responders.

Polldaddy records location and IP address by default. in the past the Community team has received a lot of pushback about asking demographic info in surveys. The outcome is that @mor10 is going to ask the survey expert how they do it to ensure it is far.

There was the question of whether we need the demographic information, because we shouldn’t be asking for information we don’t need. The thought behind the demographic data is that if marginalized people say we need a code of conduct and non-marginalized people don’t, then we need a code of conduct.

Group’s TODO:

Next Meeting:

Next meeting is on 14th November 2017 at 15:00UTC


Marketing Team Update – November 2, 2017

Hi everyone.

The Marketing Team has four subgroups, each of whom post updates on the Marketing Blog.

For consensus in our meetings, we’ve decided to work on one task and at the 45 minute mark take wish list items. This is helping with the overall flow of meetings.

Marketing the Community

This week the Community subgroup met. We published “What makes a WordPress Meetup Great?” and are working on a task list for Contributor Day at WCUS. It should also be noted that David Skarjune and the Agency and End Users subgroups have started to work on our own Handbook. Our meeting notes are here.

Marketing Team Published Content

It’s worth noting how much the Team has published in 2017. As the year comes to a close and we approach WCUS, I’d like to thank the Marketing Team for all of this great content.



Theme Review update for October 30, 2017


  • 235 new tickets are waiting for review.
    • 127 tickets are older than 4 weeks
    • 187 tickets are older than 2 weeks
    • 208 tickets are older than 1 week
    • 226 tickets are older than 3 days
  • 46 tickets are assigned to 29 reviewers.
    • 48 tickets are older than 4 weeks
    • 50 tickets are older than 2 weeks
    • 50 tickets are older than 1 week
    • 50 tickets are older than 3 days
  • 1 are approved but are waiting to be made live.

In the past 7 days

  • 146 tickets were opened
  • 145 tickets were closed:
    • 112 tickets were made live.
      • 16 new Themes were made live.
      • 96 Theme updates were made live.
      • 0 more were approved but are waiting to be made live.
    • 32 tickets were not-approved.
    • 1 tickets were closed-newer-version-uploaded.

#themes, #trt

Plugin Review Team Status – Oct 30 2017

Plugin Status Change Stats

  • Plugins requested : 138
  • Plugins rejected : 13
  • Plugins closed : N/A
  • Plugins approved : 74

Plugin Queue Stats (current)

  • Plugins in the queue (new and pending)* : 740
  • → (older than 7 days ago)** : 661
  • → (2017-10-23 – 2017-10-30) : 65
  • → (new; not processed or replied to yet)* : 40
  • → (pending; replied to)* : 700

SupportPress Queue Stats

  • Total open tickets* : 6
  • → (with no activity in last 7 days)** : 3
  • Within defined 7 day time window:
    • Total : 203
    • Closed : 201
    • Open : 2


Support Team Update – October 26th

WordPress 4.9

WordPress 4.9-beta4 is out, if you can please help with testing, the more bugs we can find before launch, the less work for us afterwards.

In similar news, Gutenberg (the new editing experience in WordPress) version 1.5.x is also out, with a first iteration of the meta box support, so if you wish ot help shape the future, that’s what you’ll want to get involved with at the time!

Checking in with international support liaisons

The Italian, German, Russian, Swedish and Brazilian communities had representatives stop by and take part in this weeks discussions. If you’re doing support in a any other local communities we would love to have you join our weekly meetings so please stop by! It doesn’t have to be a forum, as we understand that various locales function differently!

We’ve enabled the user watch plugin on some more locales, if your forum doesn’t have access to the “Flag Author” link on posts (it should be next to the user notes link) and would like this, please let us know!

A flagged user will have their posts held in the Pending queue until a moderator manually approves them, this is intended for use with users who have misbehaved and we want to ensure they can play nice with others before we let them post without supervision again.

Flagging users

A bit of a followup on the previous lines, when a user is flagged it’s important to follow some fixed procedures to keep track of what is going on.

As such, when a user gets flagged, one should always add a user note, explaining why you’ve flagged the user, this is so that other moderators know why a user was flagged.

When a flag is issued, also always make a reply to the user explaining why they are flagged ,and what this means for them. If the user doesn’t know why they were selected, or that they are in that user classification at all, they won’t learn from their mistakes.

But before flagging a user, try educating them, we’re very trigger happy with flagging accounts at the moment (at least on the international forums), and educating them and adding a user note without flagging them may be more appropriate in many situations (basically don’t punish them for not knowing).

Moderator attendance

This is more a reminder that we expect a certain level of involvement from our moderators, at least on the international forums. We ask that they come by our weekly meetings at least somewhat-regularly or interact with the make/support articles that go up at the very least (we understand that meetings are not always timed well for every participant). This is to avoid having any unused privileged accounts hanging around.


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

#support Moderator Update October 26, 2017

“What do such machines really do? They increase the number of things we can do without thinking.
Things we do without thinking — there’s the real danger.”
Frank Herbert (God Emperor of Dune)

WordCamps submitting videos for modding or editing:

WC  Los Angeles – WC Bogotá –  WC Porto Alegre – WC PittsgurghWC Wilmington – WC Baltimore –  WC Toronto – WC  Bratislava

The Modchat on Slack

Anyone anytime can take a video to edit.
Post-Production Videos-to-Edit

In The Last 7 Days
90 videos were published from
12 WordCamps and WordPress Related Events around the world

WordPress Community Interview Series

with Sandro Gilando

The Top Most Viewed WordCamp Videos Last Week

Amar Trivedi: Designing for Accessibility Will Improve User Experience

Marija Zaric: The Creation Of Small Business Websites In WordPress – My Process

Joe Howard: Scaling to 10,000 Unique Visitors / Month

Kristina Romero: The Low Stress/Low Risk Way To Update WordPress

Interview and QandA With Matt Mullenweg

Alain Schlesser: OOP Plugin Development Basics


Accessibility update for October 23, 2017

Transcript in Slack

Please note: the times of our meetings have changed.


Because of work and holidays, the last month not much work was done on the handbook. But as from now we will pick up writing again. The goal still is to have the handbook finished mid March 2018 (with all the text ready for review around mid January).

Tickets/Issues for contributor days

We need a page to refer to on contributor days with a list of tickets and issues to work on. Preferable tickets without a long history of discussion. Like “good-first-bugs” or keyword related tickets or Gutenberg “Good first issue”. @afrecia provided a list and Rian will create the page.

Our focus for 5.0

For the WordPress 5.0 release we will focus on the accessibility of Gutenberg. There are still a lot of Gutenberg a11y tickets open and discussions to be held and testing to be done.

HTML5 landmarks

Marco Zehe published recently: Firefox 57 will be less chatty to screen readers in some situations. FireFox will treat HTML5 landmarks differently. This has implications for the changes just made in the Underscores theme. @samikeijonen is researching this.

Also Apple VoiceOver doesn’t announce the footer if no role="contentinfo" is added. This seems like a bug.

We will wait until FireFox 57 is officially out and will test this with FF/NVDA and Safari/Voiceover.