[wp-meta] [Making WordPress.org] #1560: Add "Delete this plugin" button on Admin page

Making WordPress.org noreply at wordpress.org
Mon Feb 8 20:26:33 UTC 2016


#1560: Add "Delete this plugin" button on Admin page
--------------------------+------------------------------
  Reporter:  Ipstenu      |      Owner:
      Type:  enhancement  |     Status:  new
  Priority:  normal       |  Component:  Plugin Directory
Resolution:               |   Keywords:
--------------------------+------------------------------

Comment (by coffee2code):

 I don't see a problem with giving the ability to close a plugin to any
 plugin committer. After all, each committer could delete all plugin files
 and pretty much do whatever is allowed by plugin owners if they wanted.
 Closing isn't any more dangerous of a capability for committers.

 Also, as @Ipstenu notes, the primary owner of the plugin is not an
 actively maintained field and may not accurately reflect the current owner
 (or even a committer). Singling out a sole owner runs counter to our
 desire to promote a more collaborative development culture around plugins.
 And it adds some unnecessary support for Plugin Directory admins in having
 to update and manage the primary owner field, answering why certain
 committers can't close the plugin, etc.

 In practice, yeah, it can be a little iffy because we don't currently have
 a functional role for plugins between no role and committers. Such an in-
 between role would accommodate those who have elevated privileges but not
 commit (as would be used to grant support forums privs for the plugin).
 See #1413. So some plugins do currently give commit access to their
 support forum staff. But that's never been an approach we've advocated,
 and what I propose below (and definitely if in conjunction with #1413, if
 we're too worried it'd be too easy to close a plugin) would address this
 use case.

 Here's what I'd suggest:

 * Add 'Close this plugin' button to the admin page as proposed ('Delete
 this plugin' is a bit misleading since we don't actually delete anything).
 * Above the button, add a descriptive paragraph/list explaining what
 happens when they click the button. (What "closing" a plugin means,
 reasons to close (and not to), the process involved for un-closing a
 plugin.)
 * When clicked:
   * Email all committers to let them know the plugin was closed by X user.
 (That way, like commits, they would get notified.)
   * Email plugins@ with a message indicating the plugin was closed by X
 user.
   * Directly close the plugin rather than it being a request submission.
 If we have adequate prefatory text, the author will just have to deal with
 any ramifications of doing so (e.g. having to submit a request to re-open
 with an explanation of why they want to have it re-opened, having to wait
 for a full review of the plugin, etc). And it saves Plugin Directory
 admins some effort.
 * For plugins that are already closed, replace the 'Close this plugin'
 button and text with an explanation about the plugin being closed and
 information about how to request re-opening the plugin (even if it's
 largely a link to plugin developers handbook).
 * (Possibly:) Provide a textarea for the user to supply a reason for
 closing the plugin. This would be included in the emails to all plugin
 committers, plugins@, and possibly logged as part of the plugin.

 Just to be clear, other than the button label change and allowing the use
 of the button by any committer, this list only differs from @Ipstenu's
 request in that the plugin would get immediately closed without needing
 Plugin Directory admin intervention. The other tasks outlined are simply
 laying out the implied and sensible requisite components of the request.

--
Ticket URL: <https://meta.trac.wordpress.org/ticket/1560#comment:3>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org


More information about the wp-meta mailing list