How should we shape the future of the Plugin Review team?

The deadline has been extended from June 17 to July 2 due to several contributors being occupied with 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 and unable to provide feedback on this post within the initial deadline.

Since we began restructuring the 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 Review team with our advisors and new team members, we’ve had to make some tough collective decisions. These decisions, while based on strong intuition from our contributions, could have more alignment with the whole community.

This post aims to discuss and explore some important goals to improve our effectiveness and efficiency. This is a proposal, not a final set of goals.

We hope to receive community feedback, which will help us reach a general understanding. If possible, when commenting and adding suggestions around specific goals, please also provide the reasons behind your suggestions.

Comments will be open for feedback until July 2, 2024. Thank you for your contribution to the Plugin Review team!

1. Review timeframes

The plugin review process consists of two main queues (not including the security queues). First, we have an initial review queue, during which we check the issues and assign a specific reviewer to the plugin review. Then, if everything is good, we will approve the plugin, or it will go to a subsequent review queue assigned to the initial reviewer to continue the conversation until it reaches a satisfactory level.

We need to have different timeline goals for each of these steps.

  • For the initial reply to plugin submissions, it would likely make sense to happen within seven days. This timeframe can be considered at three levels: the regular level would be up to 7 days, the warning level would be between 7 and 14 days, and the critical level for more than 14 days. The idea behind the regular level being up to one week is that some team members contribute more during weekends, and we need to allow enough time for this to compensate for the increase in submissions during the week.
  • If the plugin is not initially approved, we propose that the assigned team member have a follow-up reply within 10 days as a goal on the subsequent review queue. We need to consider that some team members are distributing their pledged time over one day per week, so it might not be viable to lower this number as we try to keep the same reviewer handling the entire review process for a specific plugin.

If we can’t meet the expected timeframes, we must implement contingency plans. When we reach the warning level, we will ask team members who are involved in other team projects to reprioritize and focus on reviews as much as possible. If the situation worsens and we reach a critical level, we propose to create urgent calls to add new team members and explore even deeper actions to reverse this as soon as possible. We would love suggestions on other contingency plans.

Suggested monthly goal: 95% of initial reviews completed within 7 days and 90% of subsequent reviews completed within 10 days.

2. Improving initial submission quality

The team’s work is primarily focused on providing a safe and reliable experience while following some basic standards and guidelines. 

One of the team goals is to make Plugin Check (also known as PCP) a big part of the submission process, and we expect this to improve the quality (and speed) of the whole process. Having more AI-based tools also has some potential, even if we don’t yet know exactly how, but we’re open to suggestions.

Apart from that, we would like to improve our interactions with plugin authors by consolidating information and providing practical tips through small videos (like Instagram/TikTok) on common issues such as sanitizing and escaping.

This means that part of our goal is to invest in this direction and ask some of our contributors to dedicate time to it.

Right now, it takes an average of about three interactions per review when looking at the last six months, so it would be ideal to change that closer to two interactions per review.

Suggested monthly goal: Improve the quality of applications so that there are only two interactions (one initial review and one subsequent follow-up review) as average per application.

3. Keeping track of popular plugins

The team has historically only reviewed the initial version of plugins by default, then only checked based on specific reports or specific cases.

This means some plugins with many active installations haven’t had a full review from our team in a really long time. 

The team would like to start dedicating resources to scheduled reviews whenever a plugin achieves 20k active installations. Of course, this is more challenging while there is still a backlog, but it is one of the plans we consider throughout a plugin’s journey on the WP.org directory.

Suggested monthly goal: Complete scheduled additional reviews for all of the plugins with over 20k active installations at least once every two years.

4. Distribution of contribution

Ideally, no single person should be responsible for the majority of active reviews. We need to avoid overloading a few individuals and relying on only a few people to keep the work going. 

A health number might be not more than 25% of reviews, as this distribution ensures consistency and protects us if someone steps out temporarily or permanently.

This means we will explore internally (and even add new team members if needed) until we accomplish this goal.

Suggested monthly goal: Ensure no team member handles more than 25% of active reviews at any time.

X-post: Recognizing Contributions and Acknowledging Challenges

X-comment from +make.wordpress.org/sustainability: Comment on Recognizing Contributions and Acknowledging Challenges

X-post: The Plugin Directory gets a refresh

X-post from +make.wordpress.org/meta: The Plugin Directory gets a refresh

WordCamp Asia 2024: Plugin’s team table on contributor day

With WordCamp Asia 2024 coming soon, we need to get ready for contributor dayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/.!

To ensure a smooth experience on the day, we recommend installing a local development environment on your laptop in advance. The conference venue’s Wi-Fi may not always be optimal, especially when many people are using it simultaneously. Achieving this prerequisite over a stable and fast connection is much simpler.

Here’s the checklist:

  1. Latest Local WordPress Setup: You can use tools like MAMP, XAMPP, Local by Flywheel, Docker, or WP-Now.
  2. Latest Stable Version of Node.js and npm: You can find it here: Node.js (LTS version is the one used by coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and 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/).
  3. Code Editor: Consider using VSCode or Sublime.4. 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/.: its optional but good to have

We eagerly anticipate your presence at the event!

Thanks to @kafleg for your help drafting this post.

X-post: Guideline change: Reviews of Commercial/Pro Plugins

X-comment from +make.wordpress.org/support: Comment on Guideline change: Reviews of Commercial/Pro Plugins

X-post: Suggestion for a change in the guidelines:

X-comment from +make.wordpress.org/support: Comment on Suggestion for a change in the guidelines:

X-post: Incident Response Team: Call for Nominations

X-comment from +make.wordpress.org/project: Comment on Incident Response Team: Call for Nominations

X-post: Developer Resources gets a refresh

X-post from +make.wordpress.org/meta: Developer Resources gets a refresh

X-post: Update on Matrix Migration: Pausing the Transition

X-comment from +make.wordpress.org/project: Comment on Update on Matrix Migration: Pausing the Transition

Join the Plugin Review team!

The application period is now closed. We appreciate the interest of everyone who applied. Expect to hear from our team by January 31, 2024 February 17, 2024.

Edit: We had more than 70 applications, which delayed the whole process, so we will publish the announcement in a few weeks.

We’re happy to announce the reopening of applications for the 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 Review team!

Our team is looking for new members who believe in our mission of guiding plugin authors in responsibly transforming their innovative ideas into reality and ensuring a great WordPress plugin experience for end users.

Given the significant level of access and responsibility within the community, we plan to add only three new members in this round. This path helps us address long-term challenges associated with team expansion.

Our goals

The primary goal of adding new members is really to improve the state of our plugin review queue — our hiring and onboarding procedures have been undergoing restructuring, and we had to finish the onboarding for new team members before restarting the process.

Besides improving the queue, we’re focused on creating a diverse and inclusive team. If you feel underrepresented in the community, we want you to know that we not only accept you, we embrace you!

We believe that having a team with different experiences and backgrounds is important for more creativity and inclusivity in the WordPress world. If you belong to a group that’s not well-represented in tech, your unique view is really important and wanted in our team.

Main tasks and expectations

Your tasks would look like this:

  • Dive into plugin reviews, ensuring they meet our high standards. This is crucial for maintaining the quality and security of WordPress plugins.
  • Review the mailbox for questions and requests from plugin authors and users.
  • Work with the team on process improvement — we’re always looking to do things better.
  • Get involved in developing tools that help us and the WordPress community, like the Plugin Check Plugin (PCP).

We also expect you to pledge at least 4 hours per week to be part of the team.

We would like team members to have a deep understanding of PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. https://www.php.net/manual/en/preface.php., JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/./ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. (for the blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor), a solid understanding of the WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress./plugin architecture, and skills in SQL/database management. We have some folks focused on security issues, but general web security practices are relevant as well.

However, it’s important to highlight that the ability to contribute to the team in different ways is valued, so not having a specific skill shouldn’t be a blocker.

Timeline

Our onboarding timeline:

  • November 2023: Finalization of new aspects of our process.
  • December 2023: The application form reopens for 30 days.
  • January 2024: Announcement of three new team members, chosen for their alignment with our team’s needs.

We plan to close the application form on 31 December 2023.

Apply now

You can apply using the button below:

[The application form is now closed.]

PS: If you have already applied in the last 12 months and would like to apply again, please share any new relevant skills and contributions to the community that make you a better fit now.

Questions or Feedback

Feel free to ask questions or share any feedback in the comments or email plugins at 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/.


Special thanks to @annezazu, @coachbirgit, @chanthaboune, @properlypurple, @jordesign, the DEIB working group, and all the members of our team — we appreciate the great feedback on restructuring our hiring and onboarding.

Edit: We clarified the technical expectations a bit more.