Title: plugin support – Make WordPress.org

---

#  Tag Archives: plugin support

 [  ](https://profiles.wordpress.org/iandunn/) [Ian Dunn](https://profiles.wordpress.org/iandunn/)
2:56 am _on_ September 17, 2013     
Tags: [plugin directory ( 45 )](https://make.wordpress.org/meta/tag/plugin-directory/),
plugin support   

# 󠀁[Support Expectations for Meta Plugins in the WordPress.org Repository](https://make.wordpress.org/meta/2013/09/17/support-expectations-for-meta-plugins-in-the-wordpress-org-repository/)󠁿

For plugins that we release into the WordPress.orgWordPress.org The community site
where WordPress code is created and shared by the users. This is where you can download
the source code for WordPress core, plugins and themes as well as the central location
for community conversations and organization. [https://wordpress.org/](https://wordpress.org/)
repository (like CampTix and Tagregator), what should our support policy be?

Since we have a lot of things we want to accomplish, and a limited set of resources,
my opinion is that we should provide _product support_, but not _user support_. 
i.e., we should fix bugs and security vulnerabilities, but not help people who are
having trouble using the pluginPlugin A plugin is a piece of software containing
a group of functions that can be added to a WordPress website. They can extend functionality
or add new features to your WordPress websites. WordPress plugins are written in
the PHP programming language and integrate seamlessly with WordPress. These can 
be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
or can be cost-based plugin from a third-party., or who want to customize it to 
fit their specific needs.

The would ensure that the quality remains high, but would avoid us getting bogged
down with doing other people’s work for them.

We could manage expectations by having something like this in plugin description:

>  Support Expectations:
> We created this plugin to scratch our own itch, and are happy to offer the code
> to the community in the spirit of open sourceOpen Source Open Source denotes software
> for which the original source code is made freely available and may be redistributed
> and modified. Open Source **must be** delivered via a licensing model, see GPL..
> We are only able to provide limited support, however. If you find a legitimate
> bug or security vulnerability∗, please let us know; we take those seriously and
> will fix them.
> On the other hand, if you’re just having trouble using the plugin, or making it
> fit your specific needs, then you’ll need to solve the problem yourself, hire 
> a developer, or get help from the community.
> ∗ If you do find a security issue, please disclose it to us privately by sending
> an e-mail to security@wordpress.org, so that we can release a fix for it before
> you publish your findings.

What are everyone’s thoughts on that?

[#plugin-directory](https://make.wordpress.org/meta/tag/plugin-directory/), [#plugin-support](https://make.wordpress.org/meta/tag/plugin-support/)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fmeta%2F2013%2F09%2F17%2Fsupport-expectations-for-meta-plugins-in-the-wordpress-org-repository%2F%23respond&locale=en_US)