August 22nd Support Team Meeting Summary

General announcements

The Site Health Team did the suggested upgrade version bump for PHP in core this week, and over the next week users will start seeing a dashboard widget if they are using PHP 5.6 or lower, guiding them towards upgrading.

A reminder that when flagging users, a moderation action limiting public display of posts until approved by a moderator, always educate the users on why this was done and what this means, there will also be more direct guidelines on when to flag users coming in the future, as the use of flags is becoming a bit too liberal, at least on the international forums.

And when writing notes on users, make sure to be descriptive enough, as they are available across all rosetta sites, and not everyone can read an archived post for example.

In other news, there’s a lively conversation going on at relating to WordPress profiles here on dotorg.

Increased use of the topic report feature by authors for invalid reasons

There has lately been an uptick in incorrect use of the report topic feature by plugin and theme authors, primarily because they don’t like getting negative feedback from users.

This has started to become a nuisance to the volunteers, and we would like to reiterate that the report feature is for forum guideline violations only. Continued misuse of the feature will lead to us reporting things to the theme or plugin teams respectively.

WordPress Core Timeline Update

WordPress 5.2.3 is scheduled for release on September 4th.

WordPress 5.3 is tentatively scheduled for release on November 12th.

Checking in with international liaisons

Members from our Russian, Swedish, Brazilian and Dutch communities took place in this weeks discussions.

If you are a part of a non-English speaking part of our community, we invite you to join our weekly meetings (if you can), as we would love to get ot know you!

Open floor

Some questions are going unanswered, notably relating to the new block editor. Although it’s a shame when someone doesn’t get helped, we’re all volunteers on a community forum, and it’s perfectly fine for some questions to not be answered, we’re all human, and we do what we can when we can, but nobody should feel obligated here.

The Health Check plugin was updated last week, and some of the more notable changes include:

  • Changes to the grading indicator in the header (no longer uses a numeric value, instead it’s an indicator with a string for clarity)
  • A new dashboard widget when you login to give you the site health at a glance
  • A new PHP compatibility checker for plugins in the Tools section

For more changes, the full list is available at, and yes, some of the changes in the plugin relating to the grading indicator and Site Health Checks are being tested out and intended for a core release.

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


August 15th Support Team Meeting Summary

General announcements

The Health Check Plugin has received an update which went live over the weekend between the meeting and this summary going out.

Useful new features are primarily related to the PHP Compatibility Checker, found under the Tools tab.

The suggested PHP version in core is scheduled to go live on August 20th (this is for showing the dashboard widget encouraging users to update their PHP version if they are using version 5.6 or lower).

The docs team is looking for input on what documentation is often needed, but is either missing or incomplete.

So far we’ve informed them that documentation on the new Site Health features (both checker, and fatal error protection) are desired, and that the block documentation needs to be surfaced better as many did not know we had any.

Core updates

5.3 is tentatively scheduled to release mid-November, and a 5.2.3 release has been tentatively scheduled for early next month in the interrim.

Checking in with international liaisons

Members from Sweden, Brazil, Portugal, Netherlands and India provided updates on how things are going in their regions.

Open floor

The plugins team gave a heads up that there’s a lot of trademark strikes being handled as companies are becoming more aggressive in what they do and don’t allow, which may cause some noise.


Support Team Meeting Updates for July 18th

Items covered at today’s Support Team Meeting:

  • Helper Scripts
  • Breakfix Lessons

Read the Make/Support blog post for more details.


July 11th Support Team Meeting Summary

General announcements

As you may know, we’ve got a couple tools we use here in support, which are linked to from the handbook, and have been sitting neatly in my GitHub account, which felt… a little bit wrong, so has been set up, and the various tools will be migrated over there one by one as they receive changes. If you’re already using existing versions, do not worry, they will automatically update to the new location (you may be prompted to accept the update, but that’s it)

The first tool to be ported is the simple Topic Highlighter, as it needed some bugfixes, and accessibility improvements in the first place, anyone using that userscript will likely have received the update notification about 2 weeks ago, but I thought I should mention it any way to make sure everyone is in the loop

WordPress Core status

There’s no immediate plan for a WordPress 5.2.3 release, although we may see one depending on when the 5.3 release gets scheduled for (there’s no direct plan for that either at this time, but will keep you all posted as soon as there’s any information on either of these).

The most prominent thing for 5.2.3 would be a backport of a fix to the plugin details, which require a bit of scrolling to read if you are using 5.2.2, as they got pushed down about 1-2 viewport heights

PHP Version requirements and recommendations in core

Of interest to the support crew is our PHP version progression roadmap, well I say roadmap but it’s out on a call for input right now at

This is for the widget in the dashboard recommending users upgrade, and not the hard minimum requirement to use WordPress, just so that’s mentioned, and it’ll be up for comment until at least this coming Monday, where we’ll look to make a call on what version we will recommend next. Once that call is made it’ll be put up and signal boosted so everyone is aware for a bit before we do the recommendation bump, but currently it looks like we’ll be aiming for PHP 7.1

Open floor

HelpHub i18n: The docs team will be picking two new locales to enable it on, judging by how those two progress, it’ll get enabled for the rest. They will announce what locales and such on when things are ready

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


July 4th Support Team Meeting Summary

We’ve had a bit of a break, due to WordCamp travels, but are back with a 💥, on the 4th of July no less.

Please also remember to take some time off as the summer starts rolling in, stay hydrated, and enjoy the sun when you can, take some “me” time.

Checking in with international liaisons

Representatives from the communities in Italy, Russia, Netherlands, Spain, India, Brazil and Urdu took part in this weeks discussions.

Toxic users and impacts on smaller parts of our community

We had good discussions on how best to approach toxic users who may provide a negative first impression to new users, as well as existing users.

Although no one solution to end it all was found, it’s an important conversation to have, even if it’s a difficult one to summarize due to context awareness, but we’ll try it any way and encourage looking at the transcript when possible for the full context.

Give warnings for bad behavior, it may be a misunderstanding of expectations or guidelines.
Don’t give too many warnings without acting on them, as the concept of the warning is lost if they’re just repeated.

Although not something we discussed, but rather an afterthought that’s good to share, I’d also say that if anyone is uncomfortable with the interactions of addressing problematic users, they can always escalate the matter. We’re here to help each other, and can step in for such situations so that anyone can avoid putting them selves in situations they’re not comfortable with, or that may lead to bad blood.

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


June 6th Support Team Meeting Summary

First up, our weekly call to see if there’s anyone new around who’d like to help lead the support group at WordCamp Europe during their Contributor Day (

It’s a great way to start getting more involved, the tasks are mainly helping get new folks situated and familiarized with the tools we use and how to navigate the places we help users. Feel free to send @clorith a DM if this sounds like it might be interesting, or you just want more details.

On the note of leadership, if that’s something you’re interested in, we’re looking to do some leadership training within the WordPress community, we’re currently taking input on the documentation and processes, and judging interest, you can find more about that at

Checking in with international liaisons

Members from our Swedish, Russian, Dutch, Italian, Indian, Spanish and Greek communities were present for this weeks chats.

Open floor

Awhile back there was talk of a support appreciation day or something of the sort. Did that ever go anywhere outside of the idea phase?

Just an idea phase for now, although it’s been mentioned a few times since and if anyone wants to help put together a plan here, the support team is looking for volunteers. A Google Docs has been made public to help with collaboration on this.

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


May 23rd Support Team Meeting Summary

General announcements

WordPress 5.2.1 is out, so keep an eye out for any recurring issues that may pop up, if any.

Notable fixes are the cryptography library now working better on 32bit systems.

Checking in with international liaisons

Members of the Italian, Serbian, Dutch, Russian, Indian,. Swedish and Greek communities had representatives present for our weekly chats. If there’s anyone from other non-English communities that would like to take part, feel free to join in and let us know, we love to hear from other parts of our community to build bridges!

Open floor

First a reminder that support volunteering shouldn’t be a chore. Please don’t be afraid to take breaks, we’ll all be here when you return, stay healthy.

A question on how to find the support guidelines was brought forth, they’re currently linked to from the Forum Welcome page, which you can find at the top of the form for submitting new topics on all forums. If we find this to need better surfacing a meta ticket will be opened.

It was also brought up that sites with lower activity often forget to check for false-positives in their spam queues, this is an understandable scenario, and will hopefully be remedied by #meta-3954.

A quick note, not mentioned in the meeting, but we would still love to hear from any volunteers attending contributor day at WordCamp Europe 2019, that would be interested in helping lead the support group. No prior experience is required, and it is a nice way of getting experience with both the team in general, and also taking part in a smaller introductory leadership position. If this is you, let @clorith know.

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


May 16th Support Team Meeting Summary

General announcements

WordPress 5.2.1 is likely looking at a release early next week (the week of May 20th), to address some of the more time critical items (and any other items that are already done and patched) for 5.2.0

WordPress 5.2.0

We’re not seeing any new trending issues that haven’t already been tracked this past week, smooth sailing is the best sailing!

Checking in with international liaisons

Representatives from the Dutch, Swedish, Italian, Russian, Indian, Urdu and Spanish communities took part in this weeks discussions, and we had some exciting input on the reception of 5.2!

Open floor

A custom page is being created to cover the various Site Health elements (WSOD protection, the health checker and such), which will ive under

The site will feature custom design elements for user consumption, and be made available for rosetta site translations.

The Italian community have started a collaboration with the local polyglots team to translate the handbooks.

WordCamp Bristol will be having their Contributor Day tomorrow (May 17th), remember to he kind and helpful as new users with little experience may show up throughout the day!

We’re also still hoping to plan a Support (Appreciation) Day, if you’re interested in taking the reins on this, please let us know in the comment section below, as we would love help with this.

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


May 9th Support Team Meeting Summary

WordPress 5.2 was released, and so far a few recurring issues have popped up, but a relatively quiet release so far. The recurring issues have all been added to the core Trac, and will be tackled in an upcoming release of WordPress.

The Master List has also been updated with any relevant steps for users to follow.

As we like numbers, we can tell that it’s been fairly quiet on the forums in terms of new topics, despite the new release, the graph below shows the progression of topics created since March 1st until March 16th.

Graphs can be hard to interpret though, although a visible but vague jump, so here’s the number values:

The week before release we saw 5,178 new topics, with 10,699 replies.
The week following the release, we saw 7,884 new topics, with 17,235 replies.

Checking in with international liaisons

Members of the Swedish, Russian, Dutch, Indian, Italian, Spanish, Greek and Urdu communities were taking part in the post-update chatting.

Some are also translating the master list into the various languages, which is a huge benefit, and we thank them for their efforts!

Open floor

@tobifjellner had a trick for any translators working on the health check plugin

If anyone wants to catch up with translations of Health-Check, note that you get a lot of strings for free if you export WP/dev/admin as mo-file and then import into the Health Check plugin.


May 2nd Support Team Meeting Summary

General announcements

The WordPress 5.0 release retrospective has been published, and is available for all to read and comment on.

With WordPress 5.2 nearing completion, the Master List draft has been put up in a Google Docs where anyone can provide comments on modifications to improve the look of the initial post. Of course it will be a living post and will be updated as we negotiate the input from users throughout the weeks following the release.

Moderator rulings

If a moderator makes a ruling on the forums, others should not overturning those rulings. It makes it seem like an unorganized mess, and doesn’t leave much trust in moderator decisions when this happens.

If there are disagreements in how a ruling should be made in a particular case, an open discussion about it so we can provide a unified reaction to them in the future is the best way forward.

Checking in with international liaisons

We had members from the Italian, Russian, Swedish, Portuguese, Dutch, Indian and Greek communities take part in our weekly chat and give input on the various discussions at hand.

Open floor

If there’s anyone representing a support group at a local WordCamp, please feel free to reach out to @clorith on Slack in a DM with participants and what camp you are at and we will sort out custom titles for your forum profiles. This is something we’ve been doing for a while now, and is a tiny way of giving a bit of recognition to these wonderful volunteers.

On the notion of WordCamps and contributor days, a brainstorming session should be planned in the future to properly flesh out tasks and goals that can be used for the support team at these, beyond the normal approach of answering forums questions. There are other support outlets we are represented at, and we may find a wider audience this way.

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