[wp-meta] [Making WordPress.org] #2627: Closed plugins should still have a public page

Making WordPress.org noreply at wordpress.org
Wed Mar 29 15:48:17 UTC 2017

#2627: Closed plugins should still have a public page
 Reporter:  tellyworth        |       Owner:
     Type:  enhancement       |      Status:  new
 Priority:  high              |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:  has-patch         |

Comment (by Ipstenu):

 Historically disabled and closed plugins have not been displayed because
 they're usually done so for pejorative reasons.

 Ill or nill, unless we're documenting WHY things are closed, I don't think
 it's wise to show closed plugins except to say "This plugin is closed..."
 as it would just cause the same FUD we have today (which I don't like, and
 yes, I'd like us to tackle in phase 2 :D )

 Instead of showing the readme, I would recommend we display a simple

 Closed: This plugin has been closed and is no longer available for

 Disabled: This plugin has been closed for new installs.

 In both cases for owner/admin: If you did not request this change, please
 contact plugins at wordpress.org for a status. All developers with commit
 access are contacted when a plugin is closed, with the reasons why, so
 check your spam email too.

 Then we can start considering how to properly flag things as 'closed by
 developer request' and 'closed for guideline infraction' (though I don't
 want to dog-shame developers and publicize their mistakes if I can help

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

More information about the wp-meta mailing list