May 31st Support Team Meeting Summary

WordPress 4.9.6

No unexpected issues with the new release, that aren’t already tracked, have been noticed in our regular places this week.


Checking in with international liaisons

We had people joining us from the Pakistani, Serbian, Russian, Brazilian, Italian, Swedish communities during this weeks gathering.


On topics of GDPR

As always, we can’t give legal advise but we do see users be confused, especially when it comes to externally loaded assets (such as Google Fonts for example).

As WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. doesn’t use a CDN for regular assets, we can inform users of this. We do use it for one case though, emoji, and we can inform them of this exception and that there are plugins available to disable this behavior if they so desire.

Our general stance on GDPR topics is still to not offer any official advise on what users need to be compliant, because our volunteers shouldn’t be held accountable for anything that may relate to legal matters. The general information topic that was posted last week covers this and can be a good asset also for rosetta sites (or for translating if they so desire).



@abdullahramzan, @abletec, @amboutwe, @anevins, @bcworkz, @bemdesign, @clorith, @contentiskey, @cristianozanca, @felipeelia, @fierevere, @joyously, @lasacco, @nikolam, @numeeja, @presstigers, @stephencottontail, @sterndata, @t-p and @tobifjellner attended.


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


Contributor tips
Remember that you can walk away from a support request at any time. Tempers run hot under the summer sun, and users may be a bit on edge, you’re not forced to help them, and should always think of your self first.