November 16th Support Team Meeting Summary

WordPress 4.9

WordPress 4.9 is out, and as is customary a new Master List has been put up on the forums.

As new bugs, gotcha’s and plugin/theme conflicts are discovered we’ll be updating the thread, so keep an eye on it for any new items.

Remember to keep general chatter in #forums on Slack to a minimum for the first 48 hours after a release, this is done to avoid missing information when it’s being shared at a critical point right after a new release.

Checking in with international liaisons

The Russian, Hindi, Italian, German and Spanish communities are having a good time.

Other topics

The next workshop is scheduled for January, more details to follow, but December is a very busy time for a lot of people so it makes sense for this to right over the new years hump.

Attendance

@anevins, @bcworkz, @bdbrown, @bethannon1, @clorith, @cristianozanca, @fierevere, @firoz2456, @geoffreyshilling, @hardeepasrani, @ipstenu, @jcastaneda, @josearcos, @lasacco, @macmanx, @numeeja, @pmfonseca, @stephencottontail, @sterndata, @t-p, @wido, @zodiac1978 and @zoonini attended.

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

 

Contributor tips
Bring that knowledge of yours to a local meetup, it’s a great way to share and learn among like-minded individuals!

#weekly-chat

Agenda for November 16th Support Meeting

  • WordPress 4.9 – How’s it going (if the release goes as planned)
  • Checking in with international liaisons
  • Time permitting: Open floor

Any other items that need addressing, please bring them up at the end of the meeting, or leave a comment below!

Take note of the meeting time, 17:00 UTC (as per the last two weeks votes, this is the most convenient time for the majority of us).

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

November 9th Support Team Meeting Summary

Announcements

Meeting Time!

The timing of this week’s meeting was a bit odd. No meeting was started at 16:00 UTC, though traditionally the meeting always followed the Daylight Saving Time switch in the US until the final vote, so we waited until 17:00 UTC and just started the meeting ourselves. This of course means that the votes were only received from folks who stayed the extra hour or who at least made their vote known in some other way prior to when we kicked things off, more on that later.

The time choices involved moving the meeting to 17:00 UTC (which will be an hour later for about half of us) or keeping it at 16:00 UTC (which will be an hour earlier for the other half).

The “final” votes for the meeting time are as follows:

  • Move to 17:00 UTC = 11
  • Keep at 16:00 UTC = 6

If you did not attend the meeting, but regularly attend and would like to have voted, please leave a comment with your vote. If we reach enough votes here to shift 16:00 UTC into the lead, we will call another vote during next week’s meeting at Thursday, November 16, 2017, 17:00 UTC, otherwise the time will stand at 17:00 UTC until the next cursed time change.

WordCamp US 2017

WordCamp US 2017 is fast approaching, so we just had a brief discussion about what’s being planned so far. It’s still a bit too soon to have solid plans, but so far we think it would be really cool to test out the Slack-based volunteer orientation we discussed at this year’s Community Summit. So far, the plan is to start it 30 minutes after Contributor Day starts and to announce it as many ways as possible far in advance so new volunteers at home can participate.

Checkin with International Support Liaisons

Attendance

@macmanx @firoz2456 @cristianozanca @kidsguide @bdbrown @jdembowski @liamdempsey @fierevere @keesiemeijer @zoonini @sterndata @sergeybiryukov @howdy_mcgee @geoffreyshilling @tobifjellner @bcworkz @wido @bethannon1 @danhgilmore @numeeja @anevins @hardeepasrani attended

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

Contributor tips
Did you know we have a few handy tools we consider must-haves for efficiently traversing the WordPress support world?

#weekly-chat

Agenda for November 9th Support Meeting

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

Remember that DST changes are in effect for everyone now, and we’ve kept the time at 16.00 UTC for now.

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

November 2nd Support Team Meeting Summary

General announcements

The WordPress 2017 survey is up, help us understand how WordPress is used so we can better align its direction by filling it out, it only takes a few minutes.

Time zones and daylight savings are again showing their faces, a quick tally shows that the current time of 16.00 UTC is still a favorable time for the majority of us, but we’ll do another check at the next gathering when the whole world has finished with these shenanigans.

WordPress 4.9

We’re getting very close to the 4.9 release date, and as such the draft for the master list has gone up as is customary, if there are core changes or gotchas we should prepare for, please provide them as comments on that post.

WordPress 4.9 Master List Draft

As mentioned, release date is growing ever closer, so if possible please help test. Release Candidate (RC) means it should be feature complete and all known bugs are taken care of, so it should be safe to test in any way you can think of at this point.

Checking in with international liaisons

The Russian, Swedish, Spanish, Portuguese and Italian communities stopped by for this weeks meeting. We love to hear feedback from the non-English parts of the community, so if you know someone who’s from a locale we don’t often hear from, feel free to invite them over, there’s value in sharing after all!

 

Attendance

@abletec, @anevins, @bcworkz, @bdbrown, @clorith, @cristianozanca, @fierevere, @firoz2456, @geoffreyshilling, @hardeepasrani, @howdy_mcgee, @jamiekennedy, @jdembowski, @josearcos, @keesiemeijer, @liamdempsey, @macmanx, @matheusfd, @pmfonseca, @sterndata, @t-p, @tobifjellner and @zodiac1978 attended.

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

 

Contributor tips
Some issues are mroe common than others, and you can save time by using one of our curated pre-defined replies.

#weekly-chat

WordPress 4.9 Master List Draft

As 4.9 nears it’s release, and we’ve now entered the Release Candidate stage, it is safe to say that the next version of WordPress is feature-ready. This means we need ot start thinking of what items need to go into our Master List for this release (popularly referred to as the OMGWTFBBQ post).

For those unfamiliar, the support team publishes a master list with potential got’chas users may experience when using a new version of WordPress, be it changed interfaces, new headlined features, or removed features. It’s important to keep in mind that this is a draft post, and not the final product, the finished result will be posted on the forums after the new release is out.

The fixed data will be gathered from our handbook pages about the master list, and variable, version specific, changes will be supplemented from the list below.


Core Changes

 

Not a Bug

  • <List of things perceived as a bug, but aren’t>

 

Known Issues

  • <Populated as issues arise in the forums>

 

Reported Bugs

  • <Populated as issues arise in the forums>

 

Agenda for November 2nd Support Meeting

  • WordPress 4.9 RC
  • 4.9 Master List
  • Checking in with international liaisons
  • Time permitting: Open floor

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

Remember that Europe had their DST change the past week, so remember to double check the meeting time for you!

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

October 26th Support Team Meeting Summary

WordPress 4.9

WordPress 4.9-beta4 is out, if you can please help with testing, the more bugs we can find before launch, the less work for us afterwards.

In similar news, Gutenberg (the new editing experience in WordPress) version 1.5.x is also out, with a first iteration of the meta box support, so if you wish ot help shape the future, that’s what you’ll want to get involved with at the time!

Checking in with international support liaisons

The Italian, German, Russian, Swedish and Brazilian communities had representatives stop by and take part in this weeks discussions. If you’re doing support in a any other local communities we would love to have you join our weekly meetings so please stop by! It doesn’t have to be a WordPress.org forum, as we understand that various locales function differently!

We’ve enabled the user watch plugin on some more locales, if your WordPress.org forum doesn’t have access to the “Flag Author” link on posts (it should be next to the user notes link) and would like this, please let us know!

A flagged user will have their posts held in the Pending queue until a moderator manually approves them, this is intended for use with users who have misbehaved and we want to ensure they can play nice with others before we let them post without supervision again.

Flagging users

A bit of a followup on the previous lines, when a user is flagged it’s important to follow some fixed procedures to keep track of what is going on.

As such, when a user gets flagged, one should always add a user note, explaining why you’ve flagged the user, this is so that other moderators know why a user was flagged.

When a flag is issued, also always make a reply to the user explaining why they are flagged ,and what this means for them. If the user doesn’t know why they were selected, or that they are in that user classification at all, they won’t learn from their mistakes.

But before flagging a user, try educating them, we’re very trigger happy with flagging accounts at the moment (at least on the international forums), and educating them and adding a user note without flagging them may be more appropriate in many situations (basically don’t punish them for not knowing).

Moderator attendance

This is more a reminder that we expect a certain level of involvement from our moderators, at least on the international forums. We ask that they come by our weekly meetings at least somewhat-regularly or interact with the make/support articles that go up at the very least (we understand that meetings are not always timed well for every participant). This is to avoid having any unused privileged accounts hanging around.

Attendance

@anevins, @bcworkz, @bdbrown, @berksted, @bethannon1, @clorith, @contentiskey, @cristianozanca, @felipeelia, @fevered, @fierevere, @firoz2456, @geoffreyshilling, @howdy_mcgee, @jdembowski, @justingreerbbi, @macmanx, @numeeja, @otto42, @sergeybiryukov, @stephencottontail, @sterndata, @t-p, @tobifjellner, @voldemortensen and @zodiac1978 attended.

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

New contributor tips
If you are looking for a place to start, or have some free time to kill, why not check the list of topics without any replies?

#weekly-chat

Agenda for October 26th Support Meeting

  • General announcements
  • WordPress 4.9 Beta
  • Checking in with international liaisons
  • Time permitting: Open floor

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, October 26, 2017, 16:00 UTC in #forums on Slack. (a Slack account is required)

October 19th Support Team Meeting Summary

General announcements

The plugins team has requested we stop reporting crypto currency miners unless they actually violate the forum guidelines. Things such as not informing site visitors that a miner is running isn’t considered a plugin directory violation as that’s up to site owners and not us to police.

We also had a lengthy discussion regarding the new Gutenberg callout added for WordPress 4.9, where the concerns that were discussed were added to the ticket for consideration and further discussion. (It has since been decided to revert the callout for now).

Open floor

A question regarding screenshot sharing was brought up, and how to point users at where to put them as we don’t have (nor do we want to have, that’s a whole new beast of legal concerns) any upload capabilities on the forums.

Should a new section be added to the help text before you make a post concerning screenshots, what possible issues could arise from this, let’s get some feedback on this one.

Initial concerns are that the blob of text before making a post grows even more, by a substantial amount as screenshot explanations are wordy and vary by platform. We already know that users do not like to read a lot of text like that, they wish to make their post and get on with things.

Checking in with international liaisons

The Portuguese, German, Russian and Swedish community representatives dropped by for this weeks meeting, reporting no issues at this time.

Attendance

@anevins, @bcworkz, @bethannon1, @clorith, @danhgilmore, @fierevere, @firoz2456, @geoffreyshilling, @hardeepasrani, @ipstenu, @jdembowski, @keesiemeijer, @liamdempsey, @macmanx, @numeeja, @pmfonseca, @sergeybiryukov, @stephencottontail, @sterndata, @t-p, @tobifjellner and @zodiac1978 attended.

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

 

New contributor tips
If you find a topic you don’t know much about, but you find it interesting, subscribe to the topic and be notified when someone else answers it!

#weekly-chat