Theme Review update for February 19, 2018

Currently

  • 211 new tickets are waiting for review.
    • 91 tickets are older than 4 weeks
    • 159 tickets are older than 2 weeks
    • 188 tickets are older than 1 week
    • 204 tickets are older than 3 days
  • 53 tickets are assigned to 38 reviewers.
    • 49 tickets are older than 4 weeks
    • 51 tickets are older than 2 weeks
    • 53 tickets are older than 1 week
    • 54 tickets are older than 3 days
  • 17 are approved but are waiting to be made live.

In the past 7 days

  • 285 tickets were opened
  • 308 tickets were closed:
    • 258 tickets were made live.
      • 12 new Themes were made live.
      • 246 Theme updates were made live.
      • 12 more were approved but are waiting to be made live.
    • 50 tickets were not-approved.
    • 0 tickets were closed-newer-version-uploaded.

The last meeting was an open floor meeting with notes posted here.

#themes, #trt

Plugin Directory Update – Feb 19

Stats are still broke.

https://meta.trac.wordpress.org/ticket/3447

#plugins

Accessibility team update, February 12, 2018

This week in WordPress Accessibility, February 12, 2018

Marketing Team Update – February 14, 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, revisions to the Contributor Day Handbook, and more.

Also of note is ensuring the Marketing Slack Channel is manned during Contributor Days. @bridgetwillard is reaching out to camps individually and keeping track on a Google Sheet. WC Bangkok is this weekend and @bridgetwillard will be on Slack from 6:30pm to 8:30 PST. A volunteer is needed to cover the WC Prague time period. That Google Sheet is here.

You can read more here.

Titles and Meta Descriptions – Request from Meta

Of note is we also were asked to work with Meta on an SEO project which began last night. See Trello for more details.

Feel free to reach out to me (@gidgey on slack) or @mcdwayne if you have a project for Marketing. We will set up a Trello card and rally our team in Slack.

#marketing-team

Support Team Update – February 15th

General announcements

HelpHub work has started back up, this will see a change to the front page of WordPress.org/support, and we’ll introduce some editors as well to handle articles that will be published there.

 

WordPress 4.9.4

No new issues have been discovered for WordPress 4.9.4 that aren’t already tracked on Trac.

 

Checking in with international liaisons

The Russian, Italian, Portuguese, Brazilian, Swedish and German representatives were in attendance this week.

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

#support

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