Support Team Meeting Updates for June 28th

General announcements

In light of the past days events, just a re-iteration that security things pop up now and then, please practice responsible disclosure by reporting incidents to, such topics are always touchy and emotions are easily mixed in so just refer to that site and avoid any public discussions about unpatched issues

Google Chrome’s July update will be rolling out soon, and it will mark any website not served over HTTPSHTTPS HTTPS is an acronym for Hyper Text Transfer Protocol Secure. HTTPS is the secure version of HTTP, the protocol over which data is sent between your browser and the website that you are connected to. The 'S' at the end of HTTPS stands for 'Secure'. It means all communications between your browser and the website are encrypted. This is especially helpful for protecting sensitive data like banking information. as “Not secure” in the address bar. We may see some questions pop up from users who are unfamiliar with https and wants to know why their site is suddenly no longer secure. We can educating them on the benefits of a secure website, and that the message is not necessarily dangerous, but more of a push towards a safer browsing experience. We’ll link to whatever resource Google provides when this change comes, but until they have one our user manual page on https is a good start.

WordPress 4.9.6 (and beyond!)

There’s no new incidents for 4.9.6, and leads for 4.9.7 have been picked. This means we’ll likely get a release date for the next WordPress release some time in the next week.

Checking in with international liaisons

Representatives from RussiaItalySerbiaGreeceUrduBrazilianSpanishGerman and Swedish communities joined in, it was a grand gathering this week, and some new information was shared with the new Urdu forums!

Open floor

With HelpHub (our new user documentation project) not far away, some pre-defined replies are likely to change, as we refer users to articles there instead of the Codex (don’t worry, we will be redirecting codex pages, so existing links will keep working).


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