[wp-meta] [Making WordPress.org] #4694: Plugin Directory: More userfriendly language regarding plugin closures

[Making WordPress.org]

#4694: Plugin Directory: More userfriendly language regarding plugin closures
-----------------------+---------------------
 Reporter:  Ipstenu    |       Owner:  (none)
     Type:  defect     |      Status:  new
 Priority:  normal     |   Milestone:
Component:  General    |  Resolution:
 Keywords:  has-patch  |
-----------------------+---------------------

Comment (by Ipstenu):

 I'm tossing around a second patch which is not fully tested yet.

 The idea is that if an author asks for a plugin to be closed, it's meant
 to be permanent, and if there are no committers, then it's because the
 users were banned. The ACTUAL reason (author req or guidelines) will be
 displayed after 60 days. This should give users enough information to not
 panic so much without putting them at more risk by unintentionally
 disclosing privileged information.

 That said, I'm not entirely sure WHERE to put the check and I've ended up
 doing a double look up.

 If it's permanent, say so from the start. If it's not, do the 60 day
 check.

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