August 11th Support Team Meeting Summary

Attendance

@macmanx @clorith @kidsguide @bethannon1 @jmdodd @vitormadeira @quitevisible @geoffreyshilling @justingreerbbi @numeeja @cristianozanca @tnash @ipstenu @girlieworks @danhgilmore @jcastaneda @abletec @dimitris33 @gmosso @stevesterndatacom @voldemortensen @pmfonseca @hardeepasrani @kenshino @samuelsidler @stephencottontail @songdogtech @kmessinger @tabakisp @sergeybiryukov attended.

Announcements

• The 4.6 Field Guide is up. Please review this, as it’s a great high-level overview of what’s changing.
• The Rosetta Forum upgrades are underway, and you can watch the progress at Make/Meta.
• Please leave feedback on the wireframes for the upcoming forum redesign.
• And, of course, please consider sharing this awesome post on leaving and replying to reviews.

WordPress 4.6 RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. 2

WordPress 4.6 RC 2 is here. This is the second Release CandidateRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge., meaning that the developers are reasonably sure this could be the final release, so please make sure you’re testing. Less bugs in the final release = less threads in the forums.

Varying Vagrant Vagrants is a simple way to run local WordPress sites for testing, though there are others, and of course you could always just install the betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. on a subdomain on your own hosting provider/VPS/dedicated/cloud/etc, and don’t forget about the Beta Tester plugin.

4.6 OMGWTFBBQ Draft

The 4.6 OMGWTFBBQ Draft is up and open to feedback in its comments section.

The draft continues to be improved, and we’d especially appreciate suggestions for the “Not a Bug” section (these are items which are intentional changes, but may seem like a bug or glitch to users offhand, like Dashboard fonts being different).

Support Badge Automation

After a good discussion, we’ll be proceeding towards a final vote with the following general approach for automating badges:

Support Contributor = [x] replies. (tentative 400, pending more data from MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. Team)

Support Team = Moderator. (adjustments to the Moderator expectations will be discussed next week, for example we’ll likely be decreasing the inactivity threshold for demotion to less than 10 replies in 6 months)

This will likely apply across all languages, as the goal is to be to establish a standard of automation across all communities.

Next week, we’ll discuss exactly how we’re merging the Support Team and Moderator expectations, and we’ll vote to officially adopt the approach to automation. By delaying the vote, we hope to draw in more attendees and votes from interested parties and affected volunteers.

Gentle Reminder about Deleting Threads from Spammers

This is a gentle reminder to please delete spam threads after (or before) blocking the spammer.

Checkin with International Support Liaisons

• The Italian support community has received a few useful upgrades, like additional translations and being able to mark threads as Resolved (for Moderators and OPs).

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

#weekly-chat