[wp-meta] [Making WordPress.org] #1602: Kill switch

[Making WordPress.org]

#1602: Kill switch
------------------------------+------------------
 Reporter:  obenland          |       Owner:
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+------------------

Comment (by dd32):

 I'm not entirely sure what's being proposed here, so I'm going to offer up
 two thoughts:

 1. Anything "kill switch"able is not something that can be done in the
 Plugin Directory, that's up to the plugin to include appropriate flags
 that stops the plugin from doing something after it's merged.

 2. We currently close feature plugins on WordPress.org after they're
 merged, which means we loose a tiny-tiny bit of history and links from
 older blog posts.[[BR]]
  It'd be great if we could keep the plugin open, but add a note that the
 plugin was merged into WordPress X.[[BR]]
  Normally I'd say this is something that should be in the plugin readme,
 but we'd also want to exclude it from search results.[[BR]] It seems like
 what we need here is a Status of some kind that leaves a plugin public,
 but excludes it from search results.[[BR]] It's possible that we could
 have a note in the readme, and a way to exclude items from search results.

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