I know, it got quiet. There were things.
They’ll be picking back up next month though! Come with your thinking hats on. Can’t make it? Leave comments on the above post 😁
Welcome to the official blog for the Plugin Review Team.
If you have a problem with your hosted plugin, or have found an issue with a plugin hosted here, please read our post on reporting plugin issues first.
We do not provide help with using, debugging, or developing plugins. We act as gate-keepers and fresh eyes on newly submitted plugins, as well as reviewing any reported security or guideline violations.
Currently we have neither meetings nor office hours.
As of Sept 2016, we are not able to accept new team members due to technical issues.
We can be reached by email at plugins AT wordpress.org, or you can join us in the #pluginreview channel on Slack.
Subscriptions should be working again.
Feeds have _moved_ and I’m really sorry about that. Hopefully we’ll get an nginx redirect in there sooner rather than later but basically it’s this:
We’re using WordPress now, so any time you see a view you want to follow in RSS, slap `/feed/` on the end and it will probably work.
There’s also this URL:
https://wordpress.org/support/plugin/akismet/active however, as you will notice, there is no ‘feed’ for it. Those are custom (non default WP) views and are all support threads with Closed
and Resolvedt filtered out, then sorted by last reply. We’re working on feeds for those and the old plugin committer feeds. I want that back too. Right now, I suggest you use the per-plugin feed to get a list of your new bugs etc, and then subscribe to the post (or add it to favorites).
Sadly, ‘cost overruns’ have been the story of this migration. We had hoped to be done with everything by the 5th, but that proved a gross underestimate.
We know there are a lot of ‘smaller’ features everyone loves and have gotten used to making their lives easier that we’re now doing without. It sucks. Trust me here, the mods have ‘lost’ more tools than anyone else. This upgrade had to happen, though.
Also the reason I’m closing these posts to comments when I make them is I have no additional information to provide. Historically, if I leave them open people will posts complaints and rants (which I can do nothing about save sympathize), bug report (which we either already know about, or should have been posted elsewhere), or ‘thanks’ (which we all appreciate, but get spammy). And pinging me on Slack won’t get you any answers more than I’ve posted. This is what I know as I know it.
All I have for you now is a plea to be patient. This is a massive undertaking that for a long time was deemed impossible. But slowly, as we clean up the mess, things will get better and the pros of the move will reveal themselves. Like having Akismet actually catch spam for a change.
Please check Support Forums: Meta Trac before filing a bug report/complaint. And if you have suggestions for fixes, jump in and let us know! The bonus of being on bbPress now is that if there are plugins that can do what we need, we can actually use them!
WordPress 4.7 will contain a significant re-architecture of how hooks work. Please read the post on make/core for the full details, and test your plugins!
Happy 4.6.1 day.
The direct urls to your reviews will be
https://wordpress.org/support/plugin/akismet/reviews/#new-post — I don’t know if that’s forever.
The amount of data being imported is causing everything to take longer than expected, in order to do this without crashing the servers. Which would be bad. That’s also why some posts are showing out of order. This is the biggest bbPress install ever, I suspect…
ETA on everything? We don’t know. It’s all taking longer than we hoped.
Akismet has also been acting a prat and spamming people so if that happens, swing by the #forums slack and ask if they can have a look for you 🙂 Please ask nicely and offer coffee.
Summary: A great many things have been improved. Paramount was getting the data over (done!), syncing review stars with their new post IDs (done), and making the forums run faster (in progress).
Please note: There was no way to actually test this properly before moving over, so while this is frustrating for everyone, the moderators have had to be quite aggressive in deleting repetitive reports of what’s broken. If you’ve found something that isn’t on the bugs and broken things list, please leave a reply there. Otherwise the answer is “As soon as we can get it done, it’ll be done.”
If you want to be super helpful, please make sure your fellow developers read the posts 🙂
This is directly related to the support forum maintenance.
We’ll do our best to keep this window short, but for now the choice was between closing reviews for 4 days or closing all of the support forums for 24 to 48 hours.
The Meta team felt (and I personally agree) that it is far more important to have support forums than the reviews. And the support forums were unsustainable. So while this is a wrench in your plugins, it’s far far better than no forums at all for Labor Day Weekend.
Updated Sept 2 0233
Consider this an announcement: all plugin/theme connections to the forums are currently considered broken. We expected that. It will take a few days to restore this, and that’s considered acceptable losses, for now. We will be working to fix these issues over the next few days, and it will be corrected as we get to it. In other words, we are aware of the issues and working to fix them.
Updated Sept 2 1628
You may have noticed you can’t do some things in the forums anymore. This is known. Please read Forum Bugs and Broken Things before you complain. Here’s a list of what you’re probably trying to figure out. ALL of these are being working on. Don’t fret. Enjoy your weekend.
Thank you everyone for being patient about this.
This summer was spent re-writing and editing and tweaking the guidelines. I ripped them down, sat and spelled out what they meant, then I rewrote them to be more clear. Then I got the plugin review team to review the changes. Then I had a group of people at WCNYC Contributor Day review them.
Finally, I moved it all to a GitHub repo and started to ask smaller groups to review it. Then we had a quick rebranding and that all brings us here.
I would like everyone in the community to read these proposed updates to the Plugin Directory Guidelines.
At the risk of sounding trite, pull requests and issues are welcome.
If you feel a guideline’s explanation is unclear, please create an issue or a pull request with what you feel should be changed and why. All grammar/spelling corrections are greatly welcome. We’re trying to write these for all levels of developers, as well as people who may not speak English proficiently. Using words like ‘obsequious’ should be avoided (nb: That’s mostly to me who uses those words regularly).
All feedback should be opened as issues in the tracker.
Let the games begin!
Hello plugin authors!
We will have a maintenance window for the plugins SVN repository from August 31, 20:30 UTC through September 01, 00:30 UTC (four hours total). During this time, plugin authors will not be able to commit to the SVN repository.
This post on the WordPress.org status page will be updated when the maintenance window is complete.
Edit: Maintenance has been completed, and the plugins SVN is available for commit once again.
The WordPress Plugin Repository is rebranding as the WordPress Plugin Directory.
As “directory” refers to the entire plugin hosting service (the site, VCS, etc) and “repository” conventionally refers more specifically to just a VCS (such as GitHub, SVN, etc), we feel this will be less confusing and more in-line with the other aspects of WordPress.org.
We’re in the process of updating all our documentation. I believe I’ve updated all the documentation. Can I nap now?
Today, Facebook released version 2.7 of their API and changed the manner in which shared posts are counted.
That would have been okay, except they also turned off the part of the 1.0 API (the one that didn’t use versions in their URLs because who needed that?) and blindsided everyone. Reading the Facebook Dev Changelog didn’t make that any more sensible to me either. But what I can tell you is here are some affected plugins/services:
Anyone who has a plugin (or theme) with sharing buttons that count MAY be affected. If someone can come up with a way to scan the repository for impacted plugins, let me know and I’ll be happy to do that and email as many of them directly as we can.