Title: Team Coordination for Plugin Directory Updates Author: Felipe Velzani Published: October 20, 2023 --- [ ](https://profiles.wordpress.org/felipevelzani/) [Felipe Velzani](https://profiles.wordpress.org/felipevelzani/) 1:42 am _on_ October 20, 2023 Tags: pluginreview    # Team Coordination for Plugin Directory Updates In a recent meeting with 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/](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 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, particularly concerning the addition of new features to the Plugin Directory. While [tracking existing Meta tickets is possible](https://meta.trac.wordpress.org/query?status=!closed&component=Plugin+Directory), 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](https://meta.trac.wordpress.org/ticket/7251), 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](https://make.wordpress.org/meta/tag/pluginreview/) SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/) channel or on [our P2](https://make.wordpress.org/plugins/) 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 betaBeta 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. +make.wordpress.org/plugins/ ### Share this: * [ Threads ](https://make.wordpress.org/meta/2023/10/20/team-coordination-for-plugin-directory-updates/?share=threads) * [ Mastodon ](https://make.wordpress.org/meta/2023/10/20/team-coordination-for-plugin-directory-updates/?share=mastodon) * [ Bluesky ](https://make.wordpress.org/meta/2023/10/20/team-coordination-for-plugin-directory-updates/?share=bluesky) * [ X ](https://make.wordpress.org/meta/2023/10/20/team-coordination-for-plugin-directory-updates/?share=x) * [ Facebook ](https://make.wordpress.org/meta/2023/10/20/team-coordination-for-plugin-directory-updates/?share=facebook) * [ LinkedIn ](https://make.wordpress.org/meta/2023/10/20/team-coordination-for-plugin-directory-updates/?share=linkedin) * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2023%2F10%2F20%2Fteam-coordination-for-plugin-directory-updates%2F%23respond&locale=en_US) 1. ![](https://secure.gravatar.com/avatar/e7b27b178ff5a141aa26976d2f17272a6483508f92d4fc6a210bcf8df560921f? s=32&d=mm&r=g) 2. [Courtney Robertson](https://profiles.wordpress.org/courane01/) 9:12 pm _on_ October 20, 2023 3. This is very encouraging. 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. meeting facilitators are also aiming to have the weekly agenda out 24 – 48hrs before the meeting. Feel free to add comments to the agenda posts for topics to be included at Meta meetings. 4. Likewise, traditionally in Meta, other teams come ot the Meta team meeting. Even if one cannot attend in real time, we encourage async communications. We allot a day or two after meetings before publishing recap notes. 5. The agendas and recaps are also relatively new for Meta. At this time, I have been facilitating these with Sé. Noting that our presence is solely as facilitators, while others contribute to the DevOps nature of the team. ### Leave a Reply 󠀁[Cancel reply](https://make.wordpress.org/meta/2023/10/20/team-coordination-for-plugin-directory-updates/?output_format=md#respond)󠁿 You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2023%2F10%2F20%2Fteam-coordination-for-plugin-directory-updates%2F&locale=en_US) to post a comment. # Post navigation [← Meeting Recap for October 18, 2023](https://make.wordpress.org/meta/2023/10/19/meeting-recap-for-october-18-2023/) [Meeting Agenda for November 1, 2023 →](https://make.wordpress.org/meta/2023/10/31/meeting-agenda-for-november-1-2023/)