Opened 3 years ago
Last modified 11 months ago
#5653 new enhancement
Plugin Directory: Track reasons for Rejection
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Component: | Plugin Directory | Keywords: | has-patch |
Cc: |
Description
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.
Change History (3)
This ticket was mentioned in PR #107 on WordPress/wordpress.org by @dd32.
11 months ago
#1
- Keywords has-patch added
#2
@
11 months ago
@Ipstenu It might be nearly two years later, but I made a start on this.
I haven't yet got to the Bulk rejection, but I'm assuming I'll just add the dropdown again for Bulk actions, although you'd suggested defaulting to 6-month, I'd rather have an explicit choice (even if it's all you use it for, I'm hopeful others might have a reason to use it for other things in the future).
Does the above list need any updates at all?
The rejection email can be customized in a followup change.
#3
@
11 months ago
From the list, there's on change:
-> 6 months without completion (default)
Change to 3 months.
The 'select all posts' works to reject like it does for a normal 'change the status of these posts' selector. I wouldn't mind integrating a 'why reject?' requirement but I cannot think of how that UX would work.
Now _automating_ rejections fully at 3 months... Is another thing all together :D
Trac Ticket: https://meta.trac.wordpress.org/ticket/5653