[wp-meta] [Making WordPress.org] #5653: Plugin Directory: Track reasons for Rejection

Making WordPress.org noreply at wordpress.org
Tue Mar 9 17:51:09 UTC 2021


#5653: Plugin Directory: Track reasons for Rejection
------------------------------+--------------------
 Reporter:  Ipstenu           |      Owner:  (none)
     Type:  enhancement       |     Status:  new
 Priority:  normal            |  Milestone:
Component:  Plugin Directory  |   Keywords:
------------------------------+--------------------
 This came up in the conversation about making statistics boards for teams.

 One of the things we don't do is track WHY something was rejected, so I
 came up with a list of why plugin submissions are rejected:

 * 6 months without completion (default)
 * Code is already in core
 * Duplicate (copy) of another plugin
 * Framework or Library Plugins
 * Generic for plugins we're just not hosting
 * New/renamed version of their own plugin
 * WP-CLI Only Plugins
 * Storefronts
 * Not Your Plugin (submitter tried to upload here instead of their own
 site)
 * Script Insertion Plugins are Dangerous
 * Test/Demo plugin (non functional)
 * Translation of existing plugin
 * Banned developer trying to sneak back in
 * OTHER (needs a followup to explain why)

 That's actually the list of pre-defined emails we use, so it's pretty
 accurate.

 Having this would allow us to customize the rejection email and obviate
 (or minimize) the need to re-send a 'why you were rejected'. Bonus, it can
 auto-update the plugin notes, so we have the history without having to
 spend more time copy/pastaing.

 With the 6-months be default (in theory at least) we would still be able
 to bulk reject.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5653>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org


More information about the wp-meta mailing list