Agenda for February 23rd Support Meeting

  • General Announcements
  • WordPress 4.7.2
  • 2017 Community Summit
  • Checkin with International Support Liaisons

For any other items to discuss please add them in the comments below, or bring them up in the meeting.

The meeting will be Thursday, February 23, 2017, 17:00 UTC in #forums on Slack. (a Slack account is required)

February 16th Support Team Meeting Summary

Announcements

WordPress 4.7.2

We have nothing new to add to the known issues for 4.7 this week.

Checkin with International Support Liaisons

Attendance

@macmanx @t-p @numeeja @jcastaneda @kmessinger @hardeepasrani @lukecavanagh @jdembowski @sterndata @bdbrown @ipstenu @cristianozanca @kidsguide @prathameshp @lasacco @zoonini @stephencottontail @zodiac1978 @imazed @samuelsidler @geoffreyshilling @sergeybiryukov @pmfonseca attended

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

#weekly-chat

Agenda for February 16th Support Meeting

  • General Announcements
  • WordPress 4.7.2
  • Checkin with International Support Liaisons

For any other items to discuss please add them in the comments below, or bring them up in the meeting.

The meeting will be Thursday, February 16, 2017, 17:00 UTC in #forums on Slack. (a Slack account is required)

February 9th Support Team Meeting Summary

Announcements

  • The Theme Review Team is looking for FAQ suggestions.
  • If you have any topics or issues you’d like us to cover at this year’s Community Summit, please feel free to share those.
  • An exploit against WordPress 4.7.0 and 4.7.1 has been spotted in the wild. Please do your part to ensure that users are on 4.7.2, and that they know the importance of leaving auto-updates enabled, since this would have been pushed out two weeks ago via the auto-update system.

WordPress 4.7.2

We have nothing new to add to the known issues for 4.7 this week.

Support Team Short Description

A redesign is on the way for the overall Make site, requiring a shorter description. After a great discussion and a vote, we have settled on the following:

Help WordPress users around the world by answering support questions.

Letting Users Know When They’re Flagged

We have noticed that some folks are being flagged without any warning given. This leads to lots of duplicate attempts and overall confusion, as folks don’t know why their posts aren’t appearing. This also leads to a lot of your fellow moderators not knowing why someone was flagged and therefore removing their flag.

If someone is bad enough to flag, please leave a reply in the topic to let them know why.

If someone is spamming and you therefore don’t want them to know that they’re flagged, please just block them (or ask a Keymaster to do so).

If you feel someone is maybe bad enough to flag, but you don’t think they’ve broken any rules yet warranting a notification, please don’t flag them. In this case, I recommend bookmarking their profile and checking on them yourself once a day or so. They’ll either remain innocent long enough to take them off this sort of “personal probation” or they’ll prove themselves worthy of a flag with a notification.

If you don’t know why a flagged user is flagged, based on their previous interactions in the forums, please unflag them.

Checkin with International Support Liaisons

Attendance

@macmanx @hardeepasrani @sergeybiryukov @kmessinger @t-p @cristianozanca @lasacco @logankipp @jdembowski @sterndata @bdbrown @zoonini @clorith @liamdempsey @jmdodd @tacoverdo @lukecavanagh @numeeja @gagan0123 @dhoppe @ipstenu @tnash @otto42 @stephencottontail @hideokamoto @bethannon1 @keesiemeijer @zodiac1978 @jcastaneda @pmfonseca attended

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

#weekly-chat

Agenda for February 9th Support Meeting

  • General Announcements
  • WordPress 4.7.2
  • Support Team Short Description
  • Checkin with International Support Liaisons

For any other items to discuss please add them in the comments below, or bring them up in the meeting.

The meeting will be Thursday, February 9, 2017, 17:00 UTC in #forums on Slack. (a Slack account is required)

February 2nd Support Team Meeting Summary

Announcements

WordPress 4.7.2

We have nothing new to add to the known issues for 4.7 this week.

2017 Community Summit

The next Community Summit has been announced, and we are collecting support-related topics and issues for discussion in the comments of this post.

Checkin with International Support Liaisons

Attendance

@macmanx @clorith @bcworkz @sergeybiryukov @cristianozanca @kidsguide @lasacco @jmdodd @kmessinger @numeeja @t-p @zoonini @geoffreyshilling @stephencottontail @liamdempsey @wido @hideokamoto @bdbrown @ipstenu @bethannon1 @sterndata @voldemortensen @jdembowski @lukecavanagh @kenshino @prathameshp @zodiac1978 attended

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

#weekly-chat

Agenda for February 2nd Support Meeting

  • General Announcements
  • WordPress 4.7.2
  • 2017 Community Summit
  • Checkin with International Support Liaisons

For any other items to discuss please add them in the comments below, or bring them up in the meeting.

The meeting will be Thursday, February 2, 2017, 17:00 UTC in #forums on Slack. (a Slack account is required)

January 26th Support Team Meeting Summary

Announcements

WordPress 4.7.2

We have nothing new to add to the known issues for 4.7 this week.

New Forum Welcome (and link placement)

Thanks to @ipstenu, the Forum Welcome has officially moved to the Handbook, and after a great discussion on how to do it, a link to it has been added to the new forum theme.

Better “No Topics” Wording

When no topics are found, the forum currently reports “Oh bother! No topics were found here!” so we had a great discussion about how to improve that wording. Though we didn’t vote for anything specific, we rallied around something like “No topics found. Try a different search or start a new post.”

It gets the message across simply without any cultural limerick like “Oh bother!” (and is thus easier to translate), and offers two simple suggestions for what to do next.

2017 Community Summit

The next Community Summit has been announced, and we are collecting support-related topics and issues for discussion in the comments of this post.

Checkin with International Support Liaisons

Attendance

@macmanx @clorith @bcworkz @sergeybiryukov @bethannon1 @lasacco @sterndata @liamdempsey @wido @t-p @bdbrown @cristianozanca @fierevere @kmessinger @numeeja @jdembowski @stephencottontail @abletec @zoonini @keesiemeijer @kidsguide @lukecavanagh @hideokamoto @kenshino @pmfonseca @otto42 @samuelsidler @zodiac1978 @jcastaneda @danhgilmore attended

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

#weekly-chat

2017 Community Summit Support Topics/Issues

The next Community Summit has been announced, so let’s use the comments below to collect any support-related topics and issues you’d like to have discussed this year.

Here are a few to get the ball rolling:

  • Continue 2015’s discussion about making/keeping the support community welcoming and open, while at the same time encouraging quality replies.
  • Go through the remaining items on the lists of known issues and requested enhancements.

 

Agenda for January 26th Support Meeting

For any other items to discuss please add them in the comments below, or bring them up in the meeting.

The meeting will be Thursday, January 26, 2017, 17:00 UTC in #forums on Slack. (a Slack account is required)