Recently WordPress plugin review team write a reminder post “Please do not submit frameworks” (Ipstenu/Mika Epstein).
And the reason is:
We 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.
In a comment, Darrin, who had a framework plugin (Advanced Term Fields) submitted and approved last month asked:
Are you saying the best way to handle this scenario is to include the parent framework in each child plugin, as opposed to alerting the user that “This plugin requires XXX plugin in order to function properly”?
And Mika answered:
Currently, yes. That would have been the best way.
I don’t really agree with this.
I think it should go to the opposite direction. And this is why.