Plugin Review Team: 17 February 2025

PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party Status Change Stats

  • Plugins requested : 207
  • Plugins rejected : 103
  • Plugins closed : 18
  • Plugins approved : 96

Plugin Queue Stats (current)

  • Plugins in the queue (new and pending)* : 1403
    • (older than 7 days ago)** : 1154
    • (2025-02-10 – 2025-02-16) : 165
    • (new; not processed or replied to yet)* : 246
    • (pending; replied to)* : 1157
    • (pending; waiting on author)* : 991
    • (pending; waiting on reviewer)* : 155
    • (pending; waiting on reviewer, email not yet sent)* : 11

Help Scout Queue Stats

  • Total Conversations: 761
  • New Conversations: 409
  • Customers: 548
  • Conversations per Day: 95
  • Busiest Day: Sunday
  • Messages Received: 552
  • Replies Sent: 1019
  • Emails Created: 216

* : 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

#plugins

Our Strengths and Challenges

Hello all, and thanks for welcoming me so warmly. I’m new to this role of Executive Director, but this is my third year helping our wonderful community work together. During that time, I’ve worked with a lot of teams and have been able to see what seems to be working well for most of us.

For the most part, the WordPress contributors excel at:

  1. Sharing knowledge freely, for the common good
  2. Seeking efficient and effective solutions to complex problems
  3. Communicating courteously in our shared public spaces
  4. Pointing out exceptions and possible risks in implementation
  5. Raising concerns about fairness and possible conflicts of interest
  6. Jumping in to help when the need is great

Working with multiple teams across the project has also given me the chance to identify some things we all struggle with. I’ve received feedback from contributors, too, about where they feel more support is needed. Here are some of the places where I see we (contributors of all types) can have the most impact over the course of the year.

For the most part, WordPress contributors need help with:

  1. Coordinating on collaborative work between teams
  2. Aligning our work better to project goals/values
  3. Understanding team roles, leadership structures, and decision making
  4. Clarifying the differences between open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. and open commit
  5. Tracking conversations and progress across the project
  6. Raising project-wide concerns more easily
  7. Improving how we recognize and celebrate success

We can start solving some of these things right away (please join me in using this P2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org/. for talking about project-wide work for starters). Others will take some exploration and planning.

What is missing from this list? What kind of support do you need to do your best work? Which of the above do you think is most urgent? Share your thoughts in a comment on this post

After people have had a chance to weigh in, I’ll follow up with some next steps!

Addressing Overlapping Initiatives and Improving Collaboration Across Teams

An in-person meeting during WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe was convened to address the overlapping initiatives among various WordPress contributor groups and explore ways to enhance collaboration and streamline efforts. The primary goal was to avoid duplication of work and ensure that all teams were aligned and working efficiently towards shared objectives.

Meeting Subject: Addressing Overlapping Initiatives and Improving Collaboration Across Teams
Teams/Groups Involved: Sustainability Team, DEIB Working Group, Five for the Future Working Group, Contributor Mentorship Working Group, Community Team, MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. Team, Dashboards Working Group
Facilitator: Angela Jin – Head of Programs & Contributor Experience
Attendees:

  • Josepha Haden Chomphosy @chanthaboune – Executive Director of the WordPress project
  • Chloe Brinkmann @cbringmann – Operations/Communication
  • Naoko Takano @naoOpen SourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. Project Manager / Five for the Future initiative
  • Patricia Brun Torre @patricia70 – Facilitator of the Contributor Mentorship Group
  • Courtney Robertson @courane01 – Meta Team and Project Health Working Group
  • Isotta Peira @peiraisotta – Community Team RepTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts.
  • Nora Ferreirós @noradriana, Nahuai Badiola @nahuai, Thijs Buijs @yellowlime – Sustainability Team
  • Birgit Olzem @coachbirgit – DEIB Working Group

The meeting took place in person during WordCamp Europe on June 14th, 2024.

Key Discussions

Introduction and Purpose

Angela Jin opened the meeting by expressing excitement about the gathering and emphasizing the importance of understanding each group’s focus areas to prevent duplication of efforts and improve collaboration.

Team Introductions and Project Overviews

Sustainability Team

The Sustainability Team, represented by Nora Ferreirós, Nahuai Badiola, and Thijs Buijs, has focused primarily on environmental projects like the WP Sustainability Plugin, and the Sustainable Events Handbook due to time constraints. They aim to expand their work to include socio-economic and environmental pillars, with ongoing projects like making WordPress events more sustainable and developing a pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party to measure website environmental impact.

Project Health Dashboard

Courtney Robertson discussed the Project Health Working Group’s involvement in exploring dashboard options to gather better statistics and metrics for contributors and the need for better documentation to support team reps during turnover. They are considering whether to build their systems or use SaaS solutions.

DEIB Working Group

Birgit Olzem highlighted the DEIB Working Group’s focus for 2024 on extending the contributor handbook to be more inclusive and accessible. They are conducting surveys to assess DEIB status within the WordPress community at both local and international levels. The intended purpose of the DEIB working group is to be a shared resource for all contributor teams on how to apply the DEIB principles into their daily routines.

Contributor Mentorship Program

Patricia Brun Torre explained the mentorship program’s evolution from earlier contributor working groups. The program aims to improve onboarding and create closer connections with initiatives like Five for the Future.

Overlapping Projects and Communication

The attendees recognized significant overlaps in their projects, especially concerning contributor onboarding and sustainability. Discussions highlighted the need for better coordination and communication among teams. There was a consensus on the value of regular cross-team check-ins and hangouts to share current projects and focus areas.

Challenges and Solutions

Several challenges were identified, including the perception of the sustainability team’s role and the need for clear documentation processes within Meta. The group discussed potential solutions like forming a central team for culture and sustainability, while maintaining specific focus areas under this umbrella. Concerns were raised because of the community’s perception of the term “Sustainability.” This term is often perceived as focusing only on environmental sustainability.

Proposed next steps

Forming a Singular Team

The attendees agreed on the potential benefits of forming a singular team to address contributor culture, sustainability, and onboarding comprehensively. This new team would focus on integrating efforts and providing clear resources for new and existing contributors.

Enhanced Communication

To improve communication and avoid duplication, the group proposed regular cross-team hangouts and using existing channels like the Team Reps channel and P2s for updates and collaboration.

Documentation and Awareness

Emphasizing the importance of documentation, the group suggested creating detailed guides and resources to help team reps and contributors navigate their roles and projects effectively. Additionally, raising awareness about each team’s efforts within the community was seen as crucial for fostering a cohesive and informed contributor base.

Conclusion

The meeting concluded with a commitment to continue discussions and refine the proposed collaboration structure. A follow-up meeting will be scheduled to finalize details and ensure all teams are aligned on the next steps.

Rough dates to follow-up with next steps:

  • Follow-up meeting via Zoom Call: mid-July
  • Singular team decision (structure, collaboration protocol, and name/identity): early August

Please leave your thoughts and feedback to this discussion here as a comment before July 12, 2024

Props

Thanks to @nao, @courane01, @cbringmann, @peiraisotta for reviewing and leaving feedback on this post. Thanks also to @patricia70, @noradriana, @nahuai for giving your blessing after reviewing. A special thanks to @courane01 for recording (with consent of all participants) and providing the transcription of the meeting.

Big Picture Goals 2021

During 2020’s State of the Word, Matt reminded us of our overall roadmap for GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/. Much of that roadmap is on a multi-year timeline, and it can be hard to know what’s next with such a distant North Star. This post contains some near-stars for the year, but there are some things you should know before you read them.

These are intentionally broad

There is more to WordPress’ success than the code we write, or the open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. freedoms we share. While the goals below are focused on shippable projects, I understand that there are supporting contributions (translations, testing/triage, accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility), support, etc) that are part of these project goals.

These are intentionally incomplete

There are always small projects that arise over the course of our year. And there are big projects that we move forward in pieces over the course of multiple years. This project is too big for me to see everything all the time, and I rely on the information from team reps and the vision from project leadership to help navigate any surprises.

Just because a project isn’t written here, doesn’t mean it is forgotten or has no value to our overall success.

The Big Picture

  1. Full site editing: Bring into the Gutenberg pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party, and subsequently WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., the ability to edit all elements of a site using Gutenberg blocks. This will include all in-progress features designed to help existing users transition to Gutenberg as well. Scope/Timeline: MVPMinimum Viable Product "A minimum viable product (MVP) is a product with just enough features to satisfy early customers, and to provide feedback for future product development." - WikiPedia in the plugin by April 2021, v1 in Core by WordPress 5.8.
  2. LearnWP: Enable WordPress skills-leveling by providing workshops, pre-recorded trainings, and self-serve learning opportunities on learn.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/Scope/Timeline: regularly publish new workshops and lesson plans, maintain a high pass rate on workshop quizzes to establish learner success and comprehension.
  3. Contributor tools: Decrease the manual overhead of maintenance work for teams through better tooling. Scope/Timeline: Varied, and pending additional testing.

How can you help?

As I mentioned above, I know that our code isn’t the only measure of our success. If you already know what sort of contribution you’d like to make, you can check out this list of teams (with links to their community sites) and team reps. If you’re not yet sure, here are the areas that each team falls into:

  • Development, Technology, Code: Core/Editor, Mobile, CLICLI Command Line Interface. Terminal (Bash) in Mac, Command Prompt in Windows, or WP-CLI for WordPress./Tide, Security
  • Design, Product, UXUX UX is an acronym for User Experience - the way the user uses the UI. Think ‘what they are doing’ and less about how they do it./UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing.: Design, Accessibility, Test, Triage
  • Community, Extending WP, Education: Community, Themes, Plugins, Polyglots, Training
  • Contributor Experience: MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress., Docs, Hosting, Privacy
  • Communications: Marketing, Support, WPTV

A Note on Specialized Groups

There are a couple of coordinated efforts that provide essential support to the progress of multiple teams.

  • Triage: The triage effort happens across multiple teams and has two purposes. One purpose is to make sure tickets are sorted and have all the elements needed for someone to work on them. The second purpose is to determine priority. Not everyone has the information to set priority, but anyone can help sort and replicate reported bugs!
  • Test: The testing effort also happens across multiple teams and has two purposes. One purpose is to try out features before they get to our users. The second purpose is to bring high quality feedback into our process early. A lot of that coordination happens on make.wordpress.org/test, but there are also frequently calls to participate on make.wordpress.org/core.

#goals

Test Team Update: 2 December 2024

Test Ticket Queue 🎟

 👉🏻 “(change: N)” represents changes from prior week (unless noted).

 📊 Current totals (since Nov 25, 2024):

  • Need testing info: 19 (change: 0)
  • Need reproduce issue: 2029 (change: +2)
  • Need patch testing: 219 (change: 0)
  • Need unit tests: 106 (change: 0)
  • Need review (have patch and unit tests): 245 (change: +3)

🟢 New/Changed last week:

  • Need testing info: 0 (change: 0)
  • Need reproduce issue: 13 (change: -15)
  • Need patch testing: 7 (change: -4)
  • Need unit tests: 0 (change: 0)
  • Need review (have patch and unit tests): 7 (change: +1)

 🟣 Closed last week:

  • Need testing info: 0 (change: 0)
  • Need reproduce issue: 4 (change: -4)
  • Need patch testing: 1 (change: 0)
  • Need unit tests: 0 (change: 0)
  • Need review (have patch and unit tests): 9 (change: +2)

To discuss queries used in this report, please comment below, or connect with the Test Team over in #core-test.

+make.wordpress.org/test/

#test

Test Team Update: 25 November 2024

Test Ticket Queue 🎟

 👉🏻 “(change: N)” represents changes from prior week (unless noted).

 📊 Current totals (since Nov 18, 2024):

  • Need testing info: 19 (change: 0)
  • Need reproduce issue: 2027 (change: +11)
  • Need patch testing: 219 (change: +3)
  • Need unit tests: 106 (change: -1)
  • Need review (have patch and unit tests): 242 (change: -1)

🟢 New/Changed last week:

  • Need testing info: 0 (change: -1)
  • Need reproduce issue: 28 (change: +22)
  • Need patch testing: 11 (change: +7)
  • Need unit tests: 0 (change: -1)
  • Need review (have patch and unit tests): 6 (change: -5)

 🟣 Closed last week:

  • Need testing info: 0 (change: 0)
  • Need reproduce issue: 8 (change: +6)
  • Need patch testing: 1 (change: 0)
  • Need unit tests: 0 (change: -1)
  • Need review (have patch and unit tests): 7 (change: -2)

To discuss queries used in this report, please comment below, or connect with the Test Team over in #core-test.

+make.wordpress.org/test/

#test

Test Team Update: 18 November 2024

Test Ticket Queue 🎟

 👉🏻 “(change: N)” represents changes from prior week (unless noted).

 📊 Current totals (since Nov 11, 2024):

  • Need testing info: 19 (change: 0)
  • Need reproduce issue: 2016 (change: +5)
  • Need patch testing: 216 (change: 0)
  • Need unit tests: 107 (change: 0)
  • Need review (have patch and unit tests): 243 (change: +3)

🟢 New/Changed last week:

  • Need testing info: 1 (change: 0)
  • Need reproduce issue: 6 (change: -2)
  • Need patch testing: 4 (change: +2)
  • Need unit tests: 1 (change: -1)
  • Need review (have patch and unit tests): 11 (change: +4)

 🟣 Closed last week:

  • Need testing info: 0 (change: 0)
  • Need reproduce issue: 2 (change: -1)
  • Need patch testing: 1 (change: -1)
  • Need unit tests: 1 (change: +1)
  • Need review (have patch and unit tests): 9 (change: +6)

To discuss queries used in this report, please comment below, or connect with the Test Team over in #core-test.

+make.wordpress.org/test/

#test

Test Team Update: 11 November 2024

Test Ticket Queue 🎟

 👉🏻 “(change: N)” represents changes from prior week (unless noted).

 📊 Current totals (since Nov 4, 2024):

  • Need testing info: 19 (change: 0)
  • Need reproduce issue: 2011 (change: -2)
  • Need patch testing: 216 (change: 0)
  • Need unit tests: 107 (change: 0)
  • Need review (have patch and unit tests): 240 (change: +3)

🟢 New/Changed last week:

  • Need testing info: 1 (change: +1)
  • Need reproduce issue: 8 (change: +5)
  • Need patch testing: 2 (change: -2)
  • Need unit tests: 2 (change: 0)
  • Need review (have patch and unit tests): 7 (change: +2)

 🟣 Closed last week:

  • Need testing info: 0 (change: 0)
  • Need reproduce issue: 3 (change: 0)
  • Need patch testing: 2 (change: 0)
  • Need unit tests: 0 (change: -1)
  • Need review (have patch and unit tests): 3 (change: -1)

To discuss queries used in this report, please comment below, or connect with the Test Team over in #core-test.

+make.wordpress.org/test/

#test

Test Team Update: 4 November 2024

Test Ticket Queue 🎟

 👉🏻 “(change: N)” represents changes from prior week (unless noted).

 📊 Current totals (since Oct 28, 2024):

  • Need testing info: 19 (change: 0)
  • Need reproduce issue: 2013 (change: +5)
  • Need patch testing: 216 (change: +1)
  • Need unit tests: 107 (change: -2)
  • Need review (have patch and unit tests): 237 (change: +2)

🟢 New/Changed last week:

  • Need testing info: 0 (change: -2)
  • Need reproduce issue: 3 (change: -6)
  • Need patch testing: 4 (change: -12)
  • Need unit tests: 2 (change: -1)
  • Need review (have patch and unit tests): 5 (change: -16)

 🟣 Closed last week:

  • Need testing info: 0 (change: 0)
  • Need reproduce issue: 3 (change: 0)
  • Need patch testing: 2 (change: -1)
  • Need unit tests: 1 (change: +1)
  • Need review (have patch and unit tests): 4 (change: -8)

To discuss queries used in this report, please comment below, or connect with the Test Team over in #core-test.

+make.wordpress.org/test/

#test

Training Team Updates – November 2024

This post reports on the Training Team’s progress with projects. For a detailed list of new content recently published on Learn WordPress, see the latest edition of the Learn WordPress Newsletter: Learn WordPress Newsletter – November 2024


Content Creation on Learn WordPress

Learning Pathways

Other Projects and News

The team is considering ways to introduce Learn resources in the wp-admin dashboard. Join the discussion in Brainstorm: Introducing Learning Pathways to users during onboarding.

See this month’s Contributor Spotlight: Margherita Pelonara.

The third Learn WordPress Course Cohort received many applications. The cohort is starting on Monday, November 4th.

Nomination for 2025 Training Team Reps has closed. Voting will open on November 5th once responses from nominees have been confirmed.


Learn GitHub Repository Status

Reporting period: 2024-10-01 to 2024-10-31
(Figures in parentheses show change from previous month.)

Issues and Pull Requests

  • Issues created: 95 (+32)
  • Issues closed: 48 (+22)
  • Issues open: 468 (-92)
  • Pull requests created: 3 (+1)
  • Pull requests closed: 2 (+1)
  • Pull requests open: 15 (+-0)

Issue activity increased in the buildup to the relaunch of https://learn.wordpress.org/ in August this year. Post-launch, issue activity has gone back to normal.

Weekly number of issues closed and opened from November 1, 2023 to October 31, 2024

Active Members

  • GitGit Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. Git is easy to learn and has a tiny footprint with lightning fast performance. Most modern plugin and theme development is being done with this version control system. https://git-scm.com/. authors: 4 (+4)
  • Issue authors: 21 (+-0)
  • PR submitters: 3 (+1)

Of these, 1 Git author, 7 issue authors, and 1 PR submitter made their first contribution last month 🎉

Weekly number of issue submitters from November 1, 2023 to October 31, 2024