To keep everyone aware of big projects and efforts across WordPress contributor teams, I’ve reached out to each team’s listed representatives. I asked each of them to share their Top Priority (and when they hope for it to be completed), as well as their biggest Wins and Worries. Have questions? I’ve included a link to each team’s site in the headings.

Accessibility

  • Contacted: @joedolson, @audrasjb, @arush
  • Priority: Work on authoring a manual for assistive technology users on Gutenberg, led by Claire Brotherton (@abrightclearweb). Continue to work on improving the overall user experience in Gutenberg. Update and organize the WP A11y handbook.
  • Struggle: Lack of developers and accessibility experts to help test and code the milestone issues. Still over 100 outstanding issues, and developing the Gutenberg AT manual helps expose additional issues. The announcement of an accessibility focus on 4.9.9 derailed our planning for Gutenberg in September with minimal productivity, as that goal was quickly withdrawn from the schedule.
  • Big Win: Getting focus constraint implemented in popovers and similar components in Gutenberg.

CLI

  • Contacted: @danielbachhuber, @schlessera
  • Priority: Current priority is v2.1.0 of WP-CLI, to polish the major refactoring v2.0.0 introduced. You can join in or follow progress on their site.
  • Struggle: Getting enough contributors to make peer-review possible/manageable.
  • Big Win: The major refactoring of v2 was mostly without any negative impacts on existing installs. It provided substantial improvements to maintainability including: faster and more reliable testing, more straight-forward changes to individual packages, and simpler contributor on-boarding.

Community

Core

  • Contacted: @jeffpaul
  • Priority: Continued preparation for the 5.0 release cycle and Gutenberg.
  • Struggle: Identifying tasks for first time contributors, as well as for new-to-JS contributors.

Design

  • Contacted: @melchoyce, @karmatosed, @boemedia, @joshuawold, @mizejewski
  • Priority: Preparing for WordPress 5.0 and continuing to work on better onboarding practices.
  • Struggle: Identifying tasks for contributor days, especially for small- to medium-sized tasks that can be fit into a single day.
  • Big Win: Regular contributions are starting to build up.

Documentation

  • Contacted: @kenshino
  • Priority: Getting HelpHub out before WordPress 5.0’s launch to make sure Gutenberg User Docs have a permanent position to reside
  • Struggle: Getting the documentation from HelpHub into WordPress.org/support is more manual than initially anticipated.
  • Big Win: Had a good discussion with the Gutenberg team about their docs and how WordPress.org expects documentation to be distributed (via DevHub, Make and HelpHub). Getting past the code blocks to release HelpHub (soon)

Hosting

  • Contacted: @mikeschroder, @jadonn
  • Priority: Helping Gutenberg land well at hosts for users in 5.0.
  • Struggle: Short time frame with few resources to accomplish priority items.
  • Big Win: Preparing Try Gutenberg support guide for hosts during the rollout and good reception from users following it.

Marketing

  • Contacted: @bridgetwillard
  • Priority: Continuing to write and publish case studies from the community.
  • Big Win: Onboarding guide is going well and is currently being translated.

Meta (WordPress.org Site)

  • Contacted: @tellyworth, @coffee2code
  • Priority: Support for other teams in the lead up to, and the follow-up of, the release of WP 5.0. ETA is the WP 5.0 release date (Nov 19) and thereafter, unless it gets bumped to next quarter.
  • Struggle: Maintaining momentum on tickets (still).
  • Big Win: Launch of front-end demo of Gutenberg on https://wordpress.org/gutenberg/

Mobile

  • Contacted: @elibud
  • Priority: Have an alpha version of Gutenberg in the WordPress apps, ETA end of year 2018.
  • Struggle: Unfamiliar tech stack and the goal of reusing as much of Gutenberg-web’s code as possible.
  • Big Win: Running mobile tests on web’s PRs.

Plugins

  • Contacted: @ipstenu
  • Priority: Cleaning up ‘inactive’ users, which was supposed to be complete but some work preparing for 5.0 was necessary.
  • Struggles: Devnotes are lacking for the upcoming release which slows progress.
  • Big Win: No backlog even though a lot were out!

Polyglots

Support

  • Contacted: @clorith
  • Priority: Preparing for the upcoming 5.0 release
  • Struggle: Finding a good balance between how much we want to help people and how much we are able to help people. Also, contributor recruitment (always a crowd favorite!)
  • Big Win: How well the team, on a global level, has managed to maintain a good flow of user engagement through support.

Theme Review

  • Contacted: @acosmin, @rabmalin, @thinkupthemes, @williampatton
  • Priority: Implementing the Theme Sniffer plugin on WordPress.org which is one step forward towards automation. ETA early 2019
  • Struggle: Not having so many contributors/reviewers.
  • Big Win: Implementing multiple requirements into our review flow, like screenshots and readme.txt requirements.

Training

  • Contacted: @bethsoderberg, @juliek
  • Priority: Getting the learn.wordpress.org site designed, developed, and being able to publish lesson plans to it.
  • Struggle: Getting contributors onboard and continually contributing. Part of that is related to the learn.wordpress.org site. People like to see their contributions.
  • Big Win: We have our new workflow and tools in place. We are also streamlining that process to help things go from idea to publication more quickly.

Interested in updates from the last quarter? You can find those here: https://wordpress.org/news/2018/07/quarterly-updates-q2-2018/

To keep everyone aware of big projects and efforts across WordPress contributor teams, I’ve reached out to each team’s listed representatives. I asked each of them to share their Top Priority (and when they hope for it to be completed), as well as their biggest Wins and Worries. Have questions? I’ve included a link to each team’s site in the headings.

Accessibility

  • Contacted: @rianrietveld, @joedolson, @afercia
  • Priority: Working to make sure that Gutenberg is reasonably accessible prior to merge. ETA is before 5.0
  • Struggle: Lack of developers and accessibility experts to help test and code the milestone issues. The team is doing outreach to help solve this problem.
  • Big Win: Interest from companies like The Paciello Group and Tenon.io to help out with Gutenberg code review and testing tools.

CLI

  • Contacted: @danielbachhuber, @schlessera
  • Priority: Very first global Hack Day is coming up July 20. Version 2.0.0 is still in progress (new ETA is end of July).
  • Struggle: The team continues to need new contributors. The current team is tiny but tough.
  • Big Win: WP-CLI is currently one of the project’s four main focuses, as mentioned in the Summer Update at WordCamp Europe.

Community

  • Contacted: @francina, @hlashbrooke
  • Priority: Focusing on smoothing out the processes in our community management by building up our team of volunteers and establishing what tools we need to keep things running well. ETA is ongoing.
  • Struggle: Our two biggest struggles at the moment are tracking what we need to get done, and making final decisions on things. There is current work on the tools available to assist with tracking progress.
  • Big Win: After making a concerted effort to get more contributors on the Community Team, we now have a much larger group of volunteers working as deputies and WordCamp mentors

Core

  • Contacted: @jeffpaul
  • Priority: Following the WordCamp Europe summer update (and the companion post here), the team is getting Gutenberg (the new WordPress editing experience) into a strong state for the 5.0 release. Potential ETA as soon as August.
  • Struggle: Coordinating momentum and direction as we start seeing more contributors offering their time. Still working our way through open issues. The team is starting multiple bug scrubs each week to work through these more quickly and transparently.
  • Big Win: Had a sizable release in 4.9.6 which featured major updates around privacy tools and functionality in Core.

Design

  • Contacted: @melchoyce, @karmatosed, @boemedia, @joshuawold, @mizejewski
  • Priority: Better on-boarding of new contributors, especially creating better documentation. ETA is end of July.
  • Struggle: It’s hard to identify reasonably small tasks for first-time contributors.
  • Big Win: The team is much more organized now which has helped clear out the design backlog, bring in new contributors, and also keep current contributors coming back. Bonus: Joshua Wold will co-lead the upcoming release.

Documentation

  • Contacted: @kenshino
  • Priority: Opening up the work on HelpHub to new contributors and easing the onboarding process. No ETA.
  • Struggle: Some blockers with making sure the code and database can be ready to launch on https://wordpress.org/support/
  • Big Win: The first phase of HelpHub creation is complete, which means content updates (current info, more readable, easier discovery), internal search, design improvements, and REST API endpoints.

Hosting

  • Contacted: @mikeschroder, @jadonn
  • Priority: Preparing hosts for supporting Gutenberg, especially support questions they’re likely to see when the “Try Gutenberg” callout is released. ETA July 31st, then before WordPress 5.0
  • Struggle: Most contributions are still made a by a small team of volunteers. Seeing a few more people join, but progress is slow.
  • Big Win: New team members and hosting companies have joined the #hosting-community team and have started contributing.

Marketing

  • Contacted: @bridgetwillard
  • Priority: Continuing to write and publish case studies from the community. ETA is ongoing.
  • Struggle: No current team struggles.
  • Big Win: Wrote and designed a short Contributor Day onboarding card. It was used at Contributor Day at WCEU and onboarding time went down to 1 hour instead of 3 hours.

Meta (WordPress.org Site)

  • Contacted: @tellyworth, @coffee2code
  • Priority: Reducing manual work around the contributor space (theme review, GDPR/privacy, plugin review). ETA for small wins is end of quarter, larger efforts after that.
  • Struggle: Maintaining momentum on tickets. There are also some discussions about updating the ticket management process across teams that use the Meta trac system.
  • Big Win: The new About page launched and has been translated across most locale sites.

Mobile

  • Contacted: @elibud
  • Priority: Getting Gutenberg in the mobile applications. ETA is late December.
  • Struggle: Consuming the Gutenberg source in the ReactNative app directly. More info can be found here: https://make.wordpress.org/mobile/2018/07/09/next-steps-for-gutenberg-mobile/
  • Big Win: The WordPress mobile applications now fully support right-to-left languages and are compliant with the latest standards for accessibility.

Plugins

  • Contacted: @ipstenu
  • Priority: Clearing ~8,000 unused plugins from the queues. Likely ETA is September.
  • Struggles: Had to triage a lot of false claims around plugins offering GDPR compliance.
  • Big Win: Released 4.9.6 and updated expectations with plugin authors. Huge thanks to the Core Privacy team for their hard work on this.

Polyglots

  • Contacted: @petya, @ocean90, @nao, @chantalc, @deconf, @casiepa
  • Priority: Keep WordPress releases translated to 100% and then concentrate on the top 100 plugins and themes. ETA is ongoing.
  • Struggle: Getting new PTEs fast enough, and complex tools/systems. Overall, the volume of strings awaiting approval.

Support

  • Contacted: @clorith
  • Priority: Getting ready for the Gutenberg callout (it got pushed last quarter). Needing a better presence on the official support forums, and outreach for that is underway, ETA end of July. 
  • Struggle: Keeping contributors participating post-contributor days/drives. Considering the creation of a dedicated post-contributor day survey to get some insight here.
  • Big Win: The increase in international liaisons joining for weekly meetings, helping bring the wider support community together.

Theme Review

Tide

  • Contacted: @valendesigns (but usually @jeffpaul)
  • Priority: Storing PHPCompatibilty results inside the WordPress.org API and building a UI to display those results, an endpoint to request an audit is required for this work to continue.
  • Struggle: Development has dramatically slowed down while team members are on leave or pulled into internal client work.
  • Big Win: Migration to Google Cloud Platform (GCP) from Amazon Web Services (AWS) is complete and the audit servers have all been rewritten in Go. (This allows us to be faster with greater capacity and less cost.)

Training

  • Contacted: @bethsoderberg, @juliek
  • Priority: Lesson plan production. ETA is ongoing.
  • Struggle: The workflow is a little complex, so recruiting and training enough contributors to keep the process moving is a struggle.
  • Big Win: WordCamp Europe’s Contributor Day was very productive. New tools/workflow are in place and two team representatives were there to lead and help.

Interested in updates from the first quarter of this year? You can find those here: https://make.wordpress.org/updates/2018/04/24/quarterly-updates-q1-2018/

It’s time for the annual WordPress user and developer survey! If you’re a WordPress user, developer, or business owner, then we want your feedback. Just like previous years, we’ll share the data at the upcoming WordCamp US (WCUS).

It only takes a few minutes to fill out the survey, which will provide an overview of how people use WordPress. 

WordCamp US in Nashville

The State of the Word includes stats and an overview of what's new in WordPress and is given every year at WCUS. Don't forget that tickets are available now so you can join the excitement in Nashville this year!

Global WordPress Translation Day is a one-day contributor initiative organised by the WordPress project’s Polyglots team that is dedicated to helping new contributors who would like to translate WordPress in one of the 160 languages WordPress is available in.

Global WordPress Translation Day will be on Sunday, April 24th, starting at 0:00 UTC and will go on for 24 hours covering all time zones.

What are we doing?

  • Live training: A 24h live streaming of tutorials about translating WordPress in different languages and making your code translatable (30min/1h sessions in different languages including a general instruction and specifics for that particular language). The internationalization sessions will be in English. The sessions will be presented by some of the most experienced WordPress translators and internationalization experts. The Schedule can be found on the website.
  • Local translation contributor days: Groups of contributors gather at different locations and work face to face.
  • Local remote translation contributor days: Current translation teams dedicate time and get involved remotely to do orientation for their potential contributors or work with their current translation teams on translating as many strings as they can.

If you organise a local meetup, why not organise a contributor day for translating in your language?

Join us! Read about the initiative and sign up as an organiser.

Can I get involved if I only speak English?

Yes! Even if you only speak English, it would be great to get involved and check out some of the English locale variants – English as spoken in the United Kingdom, Canada, New Zealand, Australia, South Africa. English has many variants across the globe and you can learn about the differences and why it’s important that users have the option to choose a variant during some of our sessions. And if you’re in a funky mood, you can give translating the interface into Emoji a try! Yes, we have a WordPress in Emoji locale!

Questions?

The polyglots team and the event organisers hang out in #Polyglots in Slack. They will gladly help you out.