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?



Theme Review update for January 29, 2018


  • 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…


Support Team Update – January 25th

General announcements

We updated the Health Check plugin to v0.9 last night, primarily focusing on user experience, translation fixes bug-squatting.

WordPress 4.9.3-beta1 is out, please test if you can!

A reminder to avoid name-dropping in the #forums Slack room. We are in many ways the public face of WordPress, and perception is a fickle beast. It’s hard to properly convey intentions via text on the internet, and what we say can lose context or be misinterpreted. Let’s help each other to remember not to drop names/usernames in the channel moving forward.

WordPress 4.9.2

No new issues have arisen for 4.9.2 (thankfully, with 4.9.3 on the horizon).

Checking in with international liaisons

The Italian, Greek, Swedish, Portuguese, Russian, German and Hindi communities had representatives present providing feedback and input during this weeks meeting.

Open floor

Our January workshop was this week, check out the recap if you’re interested!

Next workshop will be in March, and our new Contributor Orientation is set for February, announcements for both to follow shortly!



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


Marketing Team Update – January 24, 2018

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

Getting Involved

All are welcome and encouraged to join in, comment on posts, and participate in meetings and on projects:

Today’s Meeting

We ran through our in-progress tasks, managed with cards in Trello.

We focused the bulk of our time on the quick start guide for Trac. This should help onboarding new users both during the year and at individual Contributor Days.

Read the entire update on our blog.

Published This Week

This week we published the following:

Social shares are welcomed. 😉


The Marketing Team




Community Team Chats – January 18, 2018

The Community Team meets twice a month, first and third Thursday, at two different times to cover different timezones.
Slack logs from December 7th: 8:00 UTC and 20:00 UTC

We always kick things off with a deputy check-in: everything is going smoothly for everyone around the world. We have new deputies and more people are interested in joining the program. No roadblocks right now.

Our main focus at the moment is making a list of 2018 goals: everyone is invited to share their suggestions in this post.
Some ideas were mentioned during the chat:

  • General growth in numbers
  • Improvements in our communication channels
  • Streamlining the deputy programme
  • Improvements to financially support events
  • Improvements to WordCamp websites

We had two other items in the agenda:

  1. Global Community Team Limited Availability: the Automatticians team won’t be available between January 21st and 26th. Have a great team retreat folks!
  2. Calling European WordPress Communities: this is a project from the fine people of the WordCamp Europe organising team, we are spreading the voice!

Finally, the open floor of the second chat brought out an interesting topic: raising the number of sponsored volunteers involvement in the project. Andrea Middleton is working on a cross-team proposal and she will post it here when it’s ready.

We have a very long list of applications, so if you are a deputy please see if you can land a hand in HelpScout.

Next chat will be Thursday, February 1st 2018.

2018 first #ccoc project meeting

After WCUS and the festive holidays of Decemeber, we’re going to get back on our #CCOC meetings at 23rd January 2018 16:30 UTC, in the #community-team slack channel.

The agenda will include:

  • An update on the project situation
  • Review of all discussions of collection demographic data
  • Outline a road map to getting the survey shipped.

Theme Review update for January 22, 2018


  • 214 new tickets are waiting for review.
    • 120 tickets are older than 4 weeks
    • 158 tickets are older than 2 weeks
    • 180 tickets are older than 1 week
    • 194 tickets are older than 3 days
  • 59 tickets are assigned to 40 reviewers.
    • 59 tickets are older than 4 weeks
    • 60 tickets are older than 2 weeks
    • 61 tickets are older than 1 week
    • 61 tickets are older than 3 days
  • 1 are approved but are waiting to be made live.

In the past 7 days

  • 195 tickets were opened
  • 229 tickets were closed:
    • 166 tickets were made live.
      • 25 new Themes were made live.
      • 141 Theme updates were made live.
      • 1 more were approved but are waiting to be made live.
    • 58 tickets were not-approved.
    • 5 tickets were closed-newer-version-uploaded.

The next meeting is January 23.

#themes, #trt

Plugin Review Team – 22 January 2018

Plugin Status Change Stats

  • Plugins requested : 103
  • Plugins rejected : 2
  • Plugins closed : N/A
  • Plugins approved : 77

Plugin Queue Stats (current)

  • Plugins in the queue (new and pending)* : 706
  • → (older than 7 days ago)** : 621
  • → (2018-01-15 – 2018-01-22) : 53
  • → (new; not processed or replied to yet)* : 32
  • → (pending; replied to)* : 674

SupportPress Queue Stats

  • Total open tickets* : 21
  • → (with no activity in last 7 days)** : 2
  • Within defined 7 day time window:
    • Total : 204
    • Closed : 204
    • Open : 0
  • * : Stat reflects current size of queue and does not take into account ‘date’ or ‘day’ interval
  • ** : Stat reflects activity only within the ‘recentdays’ from today


Support Team Update – January 18th

General announcements

Monday January 22nd we’ll have our next support workshop.

WordPress 4.9.2

WordPress 4.9.2 was released last week, primarily to address security patches.
WordPress 4.9.3 is now tentatively scheduled for the end of January, but this date may still change.

We’re looking into reports of site slowdowns after the 4.9.2 release.

Checking in with international liaisons

The Russian, Spanish, GreekGerman and Portuguese communities came by, some are seeing still increased activity which is great!

Open floor

As discussed last week, some image embeds were lost in the migration to the new bbPress forums, so far the CloudUp service works (for those who have accounts there), but we’ll be looking to re-introduce imgur. Feel free to follow the Meta ticket.

Some links in the various forums are becoming un-clickable after, it seems that a browser restart solves it in most (all?) cases until a fix can be implemented.


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