Plugin Directory Update – Feb 12

Due to ongoing .org migrations we’ve had some fun glitches. Like stats being broken. Still. Yaaaay.

#plugins

Support Team Update – February 8th

General announcements

We had our first online-only volunteer orientation this week on February 6th.

Our next workshop is scheduled for March 16th, and will cover how to deal with angry users:

Dealing with Angry Users – Workshop on March 16, 2018

 

First iteration of the Upgrade PHP page is now live and sits under the Support site on WordPress.org for now.

 

WordPress 4.9.4

WordPress 4.9.3 and 4.9.4 were released this week, 4.9.4 fixes a bug that was accidentally introduced in 4.9.3 which prevents automated security updates.

If someone is on 4.9.3 when asking for help, give the ma friendly nudge to hit that update button 🙂

 

Checking in with international liaisons

The Italian, Russian, Hindi, Portuguese, Greek, Spanish and Swedish communities had representatives present during this weeks meeting, saying hi!

 

Open floor

The Stack Exchange community are looking for new community spotlights to feature. It’s something that should be brought up with the community team though, but would be a nice way to cross-reference our different support communities.

 

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

#support

Design team monthly recap January 2018

January 2018 has been pretty good for the Design Team, with new team reps. This is what we’ve been focussing on:

Weekly meetings

Our weekly meetings occur on two days:

  • Ticket triage Monday’s from 17.30-18.00 UTC
  • Weekly Meeting from 18.00-19.00 UTC

The weekly meeting agenda and meeting notes are published on our team page for more detailed insights on our activity.

Gutenberg

Designers continue to be involved in this project, with two design leading and many more contributing.

Calls for design

We’re actively reaching out to the other teams for calls for design, which resulted in:

Ticket triage

On a weekly basis, we go over the oldest tickets that need UX/UI feedback to catch up. The goal of these is to look at each one and see if we can progress the issue in some way. Tickets that were discussed this month are: #22579, #28232, #34281, #39624, #19912, #40432,  #33148, #40123, #33627. #18402, #38869, #25219
We’re now pretty much caught up and the oldest tickets are less than 9 months old.

Overall improvement of communication and structure

To make it easier for new contributors to find out what’s going on, we’ve started improving our overall structure and communication.

Team reps

We have three new team reps on the design team. Besides sitting team reps @Karmatosed and @Melchoyce, we now have @Joshuawold, @Boemedia and @Mizejewski added as new team reps.

#design-team

Marketing Team Update – February 7, 2018

Our vision for the Marketing Team is to be the go-to resource on strategy and content for other WordPress teams  — that means you.

Today’s Meeting

The Marketing team used today’s slack meeting to focused on updates to the tasks that exist in Trello currently. It’s our intention to move away from the working meeting and move toward this update model. So big shoutout to @mcdwayne for that suggestion.

It’s good to remember that everyone that contributes on this team are volunteers. We discussed our in-progress tasks including WCUS Gutenberg User Testing Testimonial Videos, WP Jargon glossary, prioritizing our own Handbook, finalizing the WP Press Kit, and suggesting revisions to the Contributor Day Handbook.

You can read more here.

#marketing-team

Code of Conduct Team Update

On January 23, the Code of Conduct team had our first meeting of the new year.

Update on project status

We have mostly finished the survey that we want to send to the community, but are still hung up on the conversation about whether to ask for demographic information.

Discussion of demographic data

Jenny provided a summary of all conversations about demographics here: https://docs.google.com/document/d/1Yu35nO7B-op51i5v6_wE5p_EmHjb4uacbkjK9UPvms0/edit#

Our conclusions: if we are going to collect demographic data, we need to have a clear reason for doing so. In this case, we need to understand the characteristics of the people who answer the survey, and understand the reach of the survey within the WP community.

To understand who answered the survey, we agreed that it would be easy to collect gender information, but gathering information about race in an international survey is extremely complicated. So we will ask about gender and country. We are also asking where people found out about the survey.

The survey answers will be anonymized. The CoC team (Morten Rand-Hendriksen, Jenny Wong, Morgan Kay, Andrea Middleton) will make sure that all identifying data is removed, and then the survey results will be released to the public.

Action Items

  • Draft a canonical post that describes the goal of the CoC initiative and contextualizes this survey, including information on who will have access to the survey.
  • Provide an email address within the survey in case people want to report an incident.
  • Review the survey to make sure it is ready to send out

Plugin Review Team Status

The status tool is broken.

Plugin Status Change Stats

  • Plugins requested : Unknown
  • Plugins rejected : 10
  • Plugins closed : N/A
  • Plugins approved : Unknown

Plugin Queue Stats (current)

  • Plugins in the queue (new and pending) : 656
  • → (older than 7 days ago): 577
  • → (2018-01-29 – 2018-02-05) : 55
  • → (new; not processed or replied to yet): 26
  • → (pending; replied to): 630

SupportPress Queue Stats

  • Total open tickets: 28
  • → (with no activity in last 7 days): 1
  • Within defined 7 day time window:
    • Total : 338
    • Closed : 334
    • Open : 4

#plugins

Support Team Update – February 1st

General announcements

Out first online-only contributor orientation will be held next week.

Support Volunteers Orientation, Tues, Feb 6, 17UTC

 

Also a reminder to moderators: When making edits make sure the post hasn’t somehow been converted to a draft. This appears to happen when editing things in the back-end when they aren’t yet published (spam or pending posts). If you make edits, take responsibility for your edit and make sure it goes live.

 

WordPress 4.9.2

(Thankfully) no new major items have been trending for 4.9.2, the release of 4.9.3 has been postponed until next week to avoid doing any automated updates right before the weekend.

 

Checking in with international liaisons

The Italian, Russian, Swedish, PortugueseGerman and Hindi communities had someone in attendance this week

 

Open floor

The 500 errors when moving posts or topics is identified as being caused by a counting mechanic in bbPress that does… crazy counting. For now making the move from the back-end in wp-admin is the way to go, as the counts only run when using bbPress on the front end.

If you’d like to help shape the future of our support plugin, head on over to the GitHub project page to add issues, and provide feedback on existing ones!

Some improvements are being made to the child theme documentation after seeing a fair amount of confusion about best practices, and will be seeking some cross-team efforts from the Theme Review Team.

If, as a volunteer, you feel users demand too much of you in a manner that feels like you were an employee, reach out and we’ll assign you a custom title to denote that you are in fact a volunteer 🙂

 

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

#support

Marketing Team Update – January 31, 2018

Our vision for the Marketing Team is to be the go-to resource on strategy and content for other WordPress teams.

Getting Involved

Everyone is welcome and encouraged to join in, comment on posts, and participate in meetings and on projects. And, yes, you can add yourself to any Trello Card you’d like to work on.

Today’s Meeting

The Marketing team used today’s slack meeting to focused on updates to the tasks that exist in Trello currently, including an About WordPress Press Kit, Why Use WordPress Blog Post, and a Jargon Glossary.

You can read more here.

We’d love your help promoting our latest blog post, too.

So, Why Should You Use WordPress to Publish?

Thanks.

<3

Theme Review update for January 29, 2018

Currently

  • 228 new tickets are waiting for review.
    • 133 tickets are older than 4 weeks
    • 167 tickets are older than 2 weeks
    • 192 tickets are older than 1 week
    • 213 tickets are older than 3 days
  • 41 tickets are assigned to 24 reviewers.
    • 40 tickets are older than 4 weeks
    • 42 tickets are older than 2 weeks
    • 44 tickets are older than 1 week
    • 45 tickets are older than 3 days
  • 3 are approved but are waiting to be made live.

In the past 7 days

  • 232 tickets were opened
  • 239 tickets were closed:
    • 204 tickets were made live.
      • 30 new Themes were made live.
      • 174 Theme updates were made live.
      • 3 more were approved but are waiting to be made live.
    • 31 tickets were not-approved.
    • 4 tickets were closed-newer-version-uploaded.

#themes, #trt

Plugin Review Team – 29 Jan 2018

Stats are reporting bad numbers right now (claiming only 20 plugins were requested last week, which is totes wrong).

There will be a supplemental post when we sort this out…

#plugins