@azurecurve should we include trialware plugins in the guidelines? I saw HappyFiles was delisted from WP repository because the plugin reviewer labeled it as trialware because it has a 10 folder limit. This is probably a mistake because it sounds more like a freemium plugin, but that did make me think about trialware plugins that would stop working after X amount of time.
For reference, here’s an email the HappyFiles developer sent about delisting:
Shortly after the last release (version 1.5.1) the WordPress repository team delisted the free version of HappyFiles on wordpress/org.
No warning, no heads-up, nothing. Straight-up delisted the best-rated media manager plugin for WordPress without me ever having violated anything on wordpress/org before.
All other WordPress media manager plugins that had the same folder restriction as HappyFiles received an email warning upfront about this “violation”. So much for treating everyone equally.
The (anonymous) reviewer labeled HappyFiles as “trialware” due to its 10 folder limit. Which violates the repository guidelines. That is the sole reason it got delisted. Security-wise, etc., everything was fine.
I, every HappyFiles user that I talked to, and the dictionary disagree.
Trialware is defined as: “… computer software that can be used free of charge for a limited evaluation period.”.
That definition does not apply to the free version of HappyFiles.
Thousands of plugins in the WP repository provide a limited, free version, which can be unlocked by purchasing the paid version.
The 10 folder limit has also always been clearly stated upfront and all users of the free version were happy with it.
This so-called “freemium” model is most often the only viable & sustainable way to ensure the people behind any project have the required resources to build, maintain & support their software.
As it stands right now HappyFiles will continue to be delisted on wordpress/org
And this also brings up a question, should we outline a process that ClassicPress will take to suspend a plugin to give developers an idea of what happens and when.
For example, something like this:
- When plugin guidelines are breached, the plugin developer will receive an email with details of the breach. The developer will have 7 days to reply and/or update the plugin to correct the issue.
- Failure to respond or correct the issue within 7 days will result in suspension.
- Ensure you have a valid, frequently monitored email listed on your developer’s profile.
- ClassicPress reserves the right to suspend a plugin with a serious vulnerability and/or security issue without prior notice to prevent users from downloading a vulnerable plugin.
If we don’t put specific timeframes, then it becomes open to interpretation.