Support Team Update – October 12th

WordPress 4.9 Beta

The WordPress 4.9 beta keeps updating weekly-ish, so if you can, please help by testing.

Focuses for this weeks testing from core are as follows:

1. The updates to the theme/plugin code editors
2. Scheduling and drafting in the Customizer
3. Locking in the Customizer (like post locking, but for your site changes)

Predefined replies

We’re seeing a few new faces every week, this is fantastic, and as such we’d like to share our predefined replies. The predefined replies list are answers to common questions that we can copy and paste into the forums, this allows us to be consistent in our replies, and saves us a lot of time in the long run.

You can find the replies in our handbook on under the Giving good support section.

Checking in with international liaisons

We had representatives form the Hindi, Italian, Brazilian, German, Spanish, Swedish and Portuguese communities stop by this week, multiple of which had WordCamps going off the previous week and introduced the wonderful world of support to new volunteers!

 

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

 

#support

Marketing Team Update – October 11, 2017

Hi everyone.

The Marketing Team has four subgroups, each of whom post updates on the Marketing Blog.

For consensus in our meetings, we’ve decided to work on one task and at the 45 minute mark take wish list items. This is helping with the overall flow of meetings.

Marketing to End-Users

This week the Marketing to End-Users Subgroup met and primarily discussed writing a persona doc to guide our internal and external marketing.

#marketing-team

Plugin Review Team Update – October 16

Plugin Status Change Stats

  • Plugins requested : 127
  • Plugins rejected : 8
  • Plugins closed : N/A
  • Plugins approved : 119

Plugin Queue Stats (current)

  • Plugins in the queue (new and pending)* : 730
  • → (older than 7 days ago)** : 620
  • → (2017-10-09 – 2017-10-16) : 104
  • → (new; not processed or replied to yet)* : 67
  • → (pending; replied to)* : 663

SupportPress Queue Stats

  • Total open tickets* : 29
  • → (with no activity in last 7 days)** : 2
  • Within defined 7 day time window:
    • Total : 233
    • Closed : 232
    • Open : 1

#plugins

Theme Review update for October 16, 2017

Currently

  • 215 new tickets are waiting for review.
    • 101 tickets are older than 4 weeks
    • 151 tickets are older than 2 weeks
    • 181 tickets are older than 1 week
    • 207 tickets are older than 3 days
  • 51 tickets are assigned to 36 reviewers.
    • 45 tickets are older than 4 weeks
    • 46 tickets are older than 2 weeks
    • 48 tickets are older than 1 week
    • 51 tickets are older than 3 days
  • 15 are approved but are waiting to be made live.

In the past 7 days

  • 248 tickets were opened
  • 250 tickets were closed:
    • 212 tickets were made live.
      • 24 new Themes were made live.
      • 188 Theme updates were made live.
      • 10 more were approved but are waiting to be made live.
    • 32 tickets were not-approved.
    • 6 tickets were closed-newer-version-uploaded.

Our last meeting topics were:

  • Use of Pixabay images
  • Appropriate images
  • Theme Sniffer
  • New experiments

#themes, #trt

WordPress.tv Moderator Update October 12, 2017

“Things don’t just happen, they are made to happen.”
John F. Kennedy


WordCamps submitting videos for modding or editing:

WC DenverWC Rhode IslandWC Los Angeles –  WC NijmegenWC ChiclanaWC Moscow –  WC Toronto WC Varna – WC  Tokyo  – WC  SeattleWC  Montreal


The Modchat on Slack


Anyone anytime can take a video to edit.
Post-Production Videos-to-Edit


In The Last 7 Days
71 videos were published from
12 WordCamps and WordPress Related Events around the world


WordPress Community Interview Series

with Michele Butcher-Jones


The Top Most Viewed WordCamp Videos Last Week

Marija Zaric: The Creation Of Small Business Websites In WordPress – My Process

Thomas Deneulin, Romain Lefort, Thierry Le Moulec, Benjamin Lupu: Table ronde: La planète WordPress doit apprendre le JavaScript. Mais… pourquoi ? Et comment ?

Sandra Boulou: Les 5 clés d’un e-commerce gagnant

Tammie Lister: Know Your Users

Shanta Nathwani: Everything I Needed To Know About Life, I Learned At Coding School.

#wordpress-tv

Theme Review update for October 9, 2017

Currently

  • 202 new tickets are waiting for review.
    • 97 tickets are older than 4 weeks
    • 144 tickets are older than 2 weeks
    • 166 tickets are older than 1 week
    • 187 tickets are older than 3 days
  • 58 tickets are assigned.
    • 52 tickets are older than 4 weeks
    • 55 tickets are older than 2 weeks
    • 55 tickets are older than 1 week
    • 58 tickets are older than 3 days
  • 17 are approved but are waiting to be made live.

In the past 7 days

  • 211 tickets were opened
  • 235 tickets were closed:
    • 174 tickets were made live.
      • 22 new Themes were made live.
      • 152 Theme updates were made live.
      • 7 more were approved but are waiting to be made live.
    • 54 tickets were not-approved.
    • 7 tickets were closed-newer-version-uploaded.

Our open floor meeting is tomorrow at 1700UTC.

#themes, #trt

Plugin Review Team Status – Oct 9

Before anyone panics, the reason there are 70 rejected plugin is that 60 were rejected from April due to no responses in six months. Any plugin with at least one reply to indicate the review was being worked on is still pending.

In order to reduce the pending number, we are planing to restrict the number of plugins you can have in progress at a time. Since the average turn-around for a review is 7 days, we feel this is not an imposition.

Plugin Status Change Stats

  • Plugins requested : 81
  • Plugins rejected : 70
  • Plugins closed : N/A
  • Plugins approved : 37

Plugin Queue Stats (current)

  • Plugins in the queue (new and pending) : 683
  • → (older than 7 days ago): 593
  • → (2017-10-02 – 2017-10-09) : 70
  • → (new; not processed or replied to yet) : 20
  • → (pending; replied to) : 663

SupportPress Queue Stats

  • Total open tickets : 33
  • → (with no activity in last 7 days) : 2
  • Within defined 7 day time window:
    • Total : 265
    • Closed : 264
    • Open : 1

#plugins

CCOC project meeting notes – 3rd October

The group met in the #community-team Slack at its new time of 15:00 UTC.

There were no objections on the previous meetings workflow and flowchart proposals. We have made PDF format of the workflow and flowchart and uploaded them onto this site so that they are stored for clarity.

We then reviewed the amount of research the group had found so far on COCs inside and outside of technology. We have found there are many examples of COC documents but not so many exampels of published enforcement reports or articles or information on why people find COCs problematic.

We agreed that it would be benefitcal to find more informaion to why and how people find COCs problematic and add them to the spreadsheet. We have also done a public call for examples of such articles on twitter to see if we can find where these articles are. @danieltj has kindly offered to concentrate on the task.

@mor10 and @morgankay have yet to sync up to do a first draft of the COC survey. The survey was originally thought of as a survey for WordCamp and Meetup organisers and attendees, but agreement has been foudn to boarden the target audience of the survey to be all WordPress community members.

@mor10 asked what questions and topics we are hoping to get from the survey.
As a starting point the survey will include the following:

a) whether people know the event CoC at all
b) whether they have experienced a CoC violation
c) whether it was reported
d) whether it was handled
e) whether they think handling was successful

We have agreed before the survey is published and circulated that htere should be a chance for the ccoc group to review the survey and give feedback.

We also discussed how we will be make sure the survey reaches the community. There was the idea of emailing all wordcamp andmeetup organisers via the WP.org Community Team. We would have to see if the Community Team felt comfortable emailing everyone about the survey. Other options will include reaching out to WordPress related news outlets.

There was also a post-meeting discussion, about whether the CCOC project is to update the WordCamp Code of Conduct and expand its scope to become a WordPress Community Code of Conduct (CCoC) adhere to.

I would like to take a moment to make it clear, that this project is currently all research driven. Our interest in the COC that in-person events ( such as WordCamps and meetups ) use, is to see if there is anything the whole project could learn from and whether what was written a few moons ago, still holds up in the WordPress.org landscape today.

The outcome of the research may or may not include recommendations to the WordCamp COC but will always be a recommodation that the community as a whole will need to decide to accept or reject.

I would like to thank @andreamiddleton for asking the question and if there is anything that is unclear, please do pipe up.

### Get involved
If you have any questions or topics that you think teh survey should include, please share them in the comments below.

We have a shortage of `anti-coc concerns articles/ posts` or ` COC Issues/ incident reports or stories`. If anyone knows of any links to any published articles or posts on either topic, please add thenm to the relevent tab in the CCOC Research spreadsheet or post links as a comment to this post and i’ll add them in.

### Personal Note:
I will be in transit for the next meeting. If i have timed my flights correctly, I should be in a location with WIFI and therefore can chair the meeting.

If I am not available, I would appreciate it if someone else could chair the meeting. I will be looking for a backup chair over the next week. Any one who would like to do it please just let me know.

#ccoc

Support Team Update – October 5th

General announcements

We’ve put some effort into the proposed `info.php` lately, we’ve now merged this into the Health Check plugin, and may revisit the core inclusion at a later date. Keeping it in the plugin for now means we can more easily iterate and find needs in a more efficient manner. As such, we recommend using the plugin for troubleshooting where getting information about a setup is required, if we all stick to using one tool we’ll get a much clearer picture of its usefulness. The plugin is already starting to get translations from the various languages around our lovely support community, which is amazing!

In other news, WordPress 4.9-beta1 is now available. If you can, please give it a try, our primary concern is still the file editing in core getting revamped,let’s make sure it’s as hard as possible to break things (there are enhancements to this that didn’t make it into beta1 as well, so beta2 should be a really good experience we hope).

Our second workshop was had this week, it went off without a hitch, and we seem to be finding our footing around conducting them, a huge thanks to @tacoverdo for doing this one! The recording from the session is available in the post as well for those interested who weren’t able to make it live. Input on topics of interest are welcome, if there’s a particular topic or presenter that would be of interest, let us know.

Checking in with international liaisons

The Portuguese, Swedish, Italian, Russian, Hindi, Brazilian, Spanish and Greek communities are looking fine and dropped by for the conversations.

Other items

At-mentions in the forums

We’ve noticed a starting trend of directly pinging people in support topics to bring attention to issues faster, in an attempt to “cut the line” so to speak.

Pings should be used to bring a topic to someones attention, for example if you are stuck, but know another volunteer knows a fair bit about a topic, this is a good use. It can also be used to guarantee a notification is sent out, in the case of moderators we might use this to ensure someone gets a notice about doing something that is frowned upon, before we archive our own message. We archive our own messages to avoid friction in these situations, as they often require jumping into some other users topic.

To help give people a place to reference, we’ve updated the international forum guidelines, we don’t want our volunteers to feel forced to answering anything, and if they have an official place to reference about this being frowned upon, it’s easier for them to say no.

Contributor badges

We had some questions about how badges work, so here’s a quick coverage of how the support ones work.

The badges are manually assigned for now, each international community has one or more liaisons that provide the profiles of members who should be given either a contributor or a team badge. If you are the administrator of an international forum and don’t have this ability please reach out and we’ll get you sorted out with this ability.

The criteria for the badges are fairly simple:

  • Support team: You are a moderator or an administrator on your support forums
  • Support contributor: You have 400 or more posts on the forums

The badges will eventually be automated, and we may also revise our criteria, but those are the current ones.

 

 

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

#support

Design team weekly update October 7th

The design team are now posting individual updates each week, this post is a summary of the updates from there. If any other teams have design they need help with, please also let us know. You can either add as a comment to the post on make/design, add a comment here, or you can ask directly in #design on Slack.

Worked on/released this week:

Currently working on:

Need help with:

Full update post here.

+make.wordpress.org/core +make.wordpress.org/design