Closed folbert closed 8 years ago
wordpress.org did not accept Fewbricks for its Plugins Directory.
Pasted below is the rejection e-mail which holds some valid points that I am totally fine with (at least the part on updating plugin/framework). My guess is that they exist mainly to protect users that are not developers and who updates plugins using WP Admin. So it probably makes more sense to keep Fewbricks as a Composer package which gives some control as to which versions are installed.
If you don't want to use Composer, it will of course still be possible to install everything manually.
At this time, we are not accepting this sort of plugin as we don’t feel frameworks, boilerplates, and libraries are appropriate for the Plugins Directory.
We do generally require that plugins be useful in and of themselves (even if only being a portal to an external service). And while there are many benefits to frameworks and libraries, without plugin dependency support in core or the directory, it becomes another level of hassle for users.
The parade of likely support issues:
And bearing in mind that the framework and plugin developers are different people, that’s another level of coordination/compatibility issues.
Frameworks and libraries should be packaged with each plugin (hopefully in a way that doesn’t conflict with other plugins using the framework or libraries). At least until core supports plugin dependencies.
If you feel this was in error, please reply to this email with your plugin attached as a zip and explain why you feel your plugin should be an exception.
Request for a review sent to WordPress. Now we wait...