January 4th Support Team Meeting Summary

General announcements

First up a reminder for our upcoming workshop on January 22nd.

Scaling Support: Dip the Data Bucket Every Day – Workshop on January 22, 2018


We’ve also added the first copy of our “how to troubleshoot” for our Health Check plugin, as it includes tools to hep users troubleshoot common issues without affecting site visitors.

Troubleshooting using the Health Check


In February we’ll be continuing our on-boarding experiment, to help get users, old and new, situated and familiarized with the support process. This is a great way to get involved, or to get a refresher. It covers how to find topics to contribute to, tools to help you, and proper etiquette (how to respond and react). It’s also a great chance to get to know others who are interested in the support aspect of open source!


Lastly, a reminder that calling out users in public channels can be misinterpreted by onlookers, and although there is likely no ill intent behind it, avoiding to call out and name individuals is appreciated. Instead consider linking to threads asking for input on threads rather than users. This also helps us jump into a thread without any bias, as we’ve not been inadvertently drawn towards any one individual.


WordPress 4.9.1

There have been no new recurring issues with WordPress 4.9/4.9.1 that aren’t already tracked either in our Master List, or in a core ticket.


Checking in with international liaisons

Representatives from the Swedish, Italian, Portuguese, Russian and German communities stopped by during this weeks meeting to give an update on how things are going, Sweden mentions increased activity and is very pleased with this!



@anevins, @bcworkz, @bdbrown, @bemdesign, @bethannon1, @clorith, @contentiskey, @cristianozanca, @e_baker, @fierevere, @firoz2456, @geoffreyshilling, @howdy_mcgee, @jcastaneda, @kimwhite, @macmanx, @numeeja, @pmfonseca, @ramthas, @sergeybiryukov, @stephencottontail, @sterndata, @t-p, @tobifjellner, @voldemortensen and @zoonini attended.

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


Contributor tip
Did someone mark their topic as resolved without getting any replies? Why not reply asking them how they solved their problem? This helps users who may arrive at their topic in the future from search engines having the same question.