In a recent meeting with the Plugin 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, it became evident that there are gaps in our communication between the Plugin Review Team and the Meta 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, particularly concerning the addition of new features to the Plugin Directory.
While tracking existing Meta tickets is possible, the team generally isn’t informed in advance before new commits are added.
This can lead to problematic situations. We indirectly represent the directory — even if our focus is primarily on the review process — and people contact us with questions, relying on us to assist with such matters. It would be helpful for the Plugin Review team to have the opportunity to review, test, provide feedback, and (when appropriate) communicate this to plugin authors.
To improve this situation, we’d love help from the Meta team. Would the Meta team be able to adapt some workflows to facilitate better communication between our teams?
An example was the WordPress Playground preview ticket, which had to be reverted. I’m confident the situation would not have escalated as it did if a better process had been in place.
Some examples of things that could be done:
- Send a notification on the #pluginreview Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel or on our P2 a few hours before implementing changes (ideally at least 24 hours for major changes).
- If someone has the bandwidth to build a complete feedback process, we could create something to add a delay for new feature commits for a set period or maybe test beta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. versions of changes on a staging site.