You may submit your work to OpenStore for approval. Every submission will be considered and either approved or rejected. We would love to feature any plugin and theme created for OpenWack but we set the priority on quality and user safety first. Here is the list of reasons why your plugin/theme can be rejected:
This means that your plugin employs its own tools for interaction with core and other plugins ignoring the programming guidelines and existing tools for your tasks. Even if your plugin may work fine with the given version of OpenWack it may be incompatible with future updates and may grow the system unstable whenever your plugin or other plugins are used not the way you originally intended.
OpenWack is written the way that you can take off really quickly writing your own classes and standard components. This approach is too often employed because of the lack of understanding of what OpenWack core already has. It makes sense to create plugins that way only if you don't intend to share them with anyone and absolutely need to trade quality, compatibility and everything else for development speed. In all other cases this is unacceptable.
Your plugin employs parts of code of vague and unclear purposes. That may be intended to cause harm to the host site.
Your plugin introduces little to no value over what already is in the OpenStore. It may duplicate the existing functionality of other plugins and/or OpenWack core. Although this is a very vague wording this clause has to be there. Of course the burden of deciding the amount of value (or fact of duplication) lies on us.