Next ticket scrub on January 17th, 2019

This ticket scrub will happen on 2019-01-17 17:00 UTC in the #meta-wordcamp channel.

The focus is on Meta tickets with the WordCamp Site & Plugins component.

Comment below if there’s a specific ticket or topic you’d like to discuss.

#agenda #ticket-scrub #wordcamp

WordCamp US Contributor Day: What Should We Work On?

It looks like we’ve got about a dozen people so far who have listed the Meta team as their preference for WCUS Contributor Day (Sunday, December 9th). How best can we spend our time together?

Here are a few ideas:

  • A scrub for tickets that have patches and need a little jumpstart
  • Work on a tough bug that has been lingering a long time, like #703
  • Improvements to the Meta Environment

Other ideas?

We’ll also have thumb drives available pre-loaded with the Meta Environment to help with onboarding new contributors.

cc @RMarks @nvwd @metalandcoffee @iandunn @julienmelissas @obenland @icaleb @drewapicture @jonoalderson @otto42 @hiddenpearls @joostdevalk

WordCamp Bug Scrub – October 24th

The next bug scrub will be Wednesday, October 24th at 4pm UTC in the #meta-wordcamp channel on Slack.

Come join us if you need any feedback on a patch, are looking for a ticket to contribute to, etc.

Revised Gutenberg Landing Page

Hi everyone! I’m working on a refresh of the current Gutenberg landing page at The goal is to have a new version of this up by the time the Try Gutenberg callout lands. I’d like to share with you an early draft of the design and content.

Here’s a little background on the goals and intent:

  • The current page is very text-heavy, but this new exercise turns it into more of a “product” page (along the lines of these examples). It’s meant to be a quick, simple way to get up to speed on what Gutenberg is. It’s primarily aimed at all the new visitors that’ll show up via the Try Gutenberg callout, but would contain some external links for people who want to get more in-depth. 
  • The current page discusses much of the background/process behind Gutenberg. It also spends a lot of time aiming to allay the concerns of developers. While the page still needs to do that, it primarily needs to introduce new people to Gutenberg. We can likely move any in-depth content into the handbook or elsewhere.
  • This has all been built using default Gutenberg blocks/styles.

You can check out a live draft of the revised page here:

Gutenberg Landing Page Draft 

Here are some screenshots as well:

So far, the general structure of the page is:

  1. Basic Introduction to Gutenberg (It’s my hope that the image at the very top of the page would be replaced by a video introduction to Gutenberg, but that would likely occur later on.)
  2. Introduction to Blocks
  3. Combining Blocks
  4. Developer Resources
  5. The Future of Gutenberg
  6. Additional Resources

I’d appreciate any initial impressions and feedback on this draft. Thanks!

Thanks @karmatosed for help with this, and @michelleweber for copywriting. 

Google Tag Manager Hangout

We got started using GTM on in #1017-meta. To discuss our next steps there let’s get together on a Zoom hangout on July 5 2018, 15:00 UTC. Everyone with an opinion is invited! I’ll post the link in the #meta Slack channel.


GDPR and privacy improvements to

As you might know, GDPR is coming, and the Meta team has been hard at work ensuring,, and other hosted community sites are compliant with the new privacy and data handling requirements. We’re also making an effort to ensure that we go beyond the minimum standard set by GDPR, and ensure our retention of data and handling of privacy is in line with the expectations of the WordPress community.
Here’s a broad outline of what we’re planning on rolling out:

1. Subject Access Requests (SAR).

By filling in a form and authenticating your email address, you will be able to download a copy of all of the relevant data has stored about you. That will include things like:

  • The contents of your user profile.
  • Your favourites, ratings, and reviews.
  • Support forum activity.
  • SupportPress activity.
  • activity, including attendance at WordCamps.
  • Submissions to other sites such as Rosetta, Showcase, etc.

2. Erasure.

By filling in a form and authenticating, regular users will be able to delete their accounts and all of the private data associated with it, with a few exceptions necessary for the ongoing stability of WordPress as a community project. Data deleted will include:

  • The contents of your user profile.
  • Favourites, ratings, and reviews.
  • Personal data held by, such as shirt size and meal preference.
  • Personal data such as email addresses stored generally in non-critical tables such as comments.

Things not deleted will include:

  • Public posts and comments on, and support forums. Your email address will be removed, but public content will remain.
  • Subversion commits, Trac tickets, and Trac comments.
  • Administrative records from which must be retained for legal and financial reasons.
  • Themes, plugins, and showcase submissions. Your email address and any other personal details will be removed where possible.
  • Generally, content that has been made freely available to the public.

Deletion for most users will be self-service, with the final erasure and permanent account closure happening automatically a day or so after the request.

Significant users will not be able to delete their accounts and data without manual intervention. That means accounts with special access privileges, Subversion committers, plugin and theme authors, authors of Make WordPress blog posts and other content. These users will be asked to pass additional authentication steps, and confirm exactly what data they’re requesting to have deleted. Data that is necessary to the archives or historical records of the WordPress open source project will not be available for erasure.

3. Data retention.

We’re in the process of eliminating the storage and tracking of unnecessary data through a combination of means:

  • Erasing old and unnecessary data.
  • Anonymizing sensitive data.
  • Reducing the amount of data that we retain.

As part of this, we’re developing a new stats system that can record usage stats without storing any identifiable user data.

4. A new privacy policy.

The policy will describe what we do and don’t retain, and help ensure we’re meeting expectations. Users will be advised of cookie usage and changes to the privacy policy.

We’ve done our best to make sure that all Meta sites will be compliant with the GDPR. You can help us to make sure we’re keeping up with community expectations.

New About pages on all Rosetta sites

Thanks to the hard work of many contributors, the new About page is now available across the Rosetta network. This means the content is consistent, easily translatable and updateable – all local sites will have current content and information. Many thanks to the Polyglots who have been busy translating all the content.

We’ll be bringing further enhancements to all local sites soon.

Two Factor Authentication on

(Beta1). Based on the Two Factor plugin, a feature project for WordPress Core, a first trial version of 2FA is now available on While it’s not in a state yet suitable for rollout across the network, it is ready to be tested by a subset of users—based on ease of segmentation that’s Core Committers and users that are Super Admins. During the testing period it is only in place on and does not yet protect other parts of the network such as SVN or Trac.

Since 2FA is part of account security, the UI to enable it will live in the support forum’s profile page. From there, users can enable and disable it, as well as generate backup codes (alongside updating their password to a more secure one, generated by their favorite password manager).

Two Factor Authentication on will use a Time-based One-time Password Algorithm as the primary authentication method. Popular apps for that method are Authy or Google Authenticator, which make it easy to manage multiple accounts that are 2FA enabled. Secondary methods (in case users don’t have access to their phone) will be via email, Slack (if 2FA is enabled there too), or printable backup codes.

All code is open-sourced and the work on this feature is trac’d in #77-meta, where you can follow along with the latest updates to this feature. In case there are not too many bugs uncovered during this first trial period, the current plan is to improve this enhancement over the next few weeks, and make it available to all users eventually.

New About page

@tellyworth, @dd32, and I compiled a list of the remaining tasks for #3046. To help with transparency and community feedback, I’ll repost those here as well.

  • New logo page redesign – implementation done this week (@obenland)
  • Navigation – decide on the design and implement (@obenland)
  • Enable main theme on (@dd32)
  • Replace prefixed translation strings (@dd32)
  • Decide how to keep new pages in sync, and implement (@dd32)
  • Write a script to add pages to Rosetta sites (@dd32)
  • Back up old About page images (@dd32)
  • Find a way to add links to About page into main Rosetta navigation (@dd32)
  • Make sure navigation works for extra child pages on Rosetta sites (@dd32)
  • Decide on how to handle translated slugs, and implement (@dd32)

X-post: Potential addition of a new Onboarding Team

X-comment from Comment on Potential addition of a new Onboarding Team