November 1st Support Team Meeting Summary

General announcements

We’re still working on the update to the Support Guidelines, we’re working on them over at GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. and feedback on issues/suggestions and Pull Requests are encouraged, as we don’t want this to be a one horse show, and the more participation, the broader an audience we hope will be able to digest the guidelines.

On the mention of time, last year we chose not to change our meeting time when daylight savings ended, and we’ve stuck with it when they began again. In light of this we plan on keeping the weekly meetings at 17:00 UTC.

The agenda post will be able to translate the time into your local time when you view it, so we hope this won’t be a major issue.

Checking in with international liaisons

Representatives of the Brazilian, Swedish, Urdu, Russian, Dutch, Serbian and German communities took part in this weeks discussions.


At-mentions trigger notifications on the forum (as the network wide notification system for The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. parses posts), and not everyone is a fan of this.

That’s perfectly fine, but they do serve a purpose to identify which user you may be interacting with in a topic if there’s more than two users speaking. It is also a common pattern of internet use these days to use @<user>when addressing someone, popularized by services such as twitter etc. Because of this, completely removing them isn’t a likely option, and hiding usernames means users will end up using display names instead, inadvertently pinging unrelated third parties.

If you wish, you can control what notifications you get, and where they are delivered, at

There’s also a Meta ticket set up for this at with some proposed changes.

Please give the ticket a read, and think over potential pros and cons of various changes here, and we’ll have a quick re-visit at our next gathering.


@abdullahramzan, @amboutwe, @bcworkz, @benlumia007, @bethannon1, @binarywc, @bph, @cleancoded, @clorith, @contentiskey, @felipeelia, @fierevere, @jcastaneda, @kenshino, @nikolam, @numeeja, @presstigers, @raduconstantin, @RDD, @stephencottontail, @t-p, @tobifjellner, @zodiac1978 and @zoonini attended

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