#4694 closed defect (bug) (fixed)
Plugin Directory: More userfriendly language regarding plugin closures
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Milestone: | Priority: | normal | |
| Component: | Plugin Directory | Keywords: | has-patch dev-feedback |
| Cc: |
Description
In the interests of reducing FUD with regards to plugin closures, we should soften the language of the closing and make it clear that the closure is temporary.
Attachments (2)
Change History (12)
#2
@
5 years ago
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.
@
5 years ago
More complex version of the first patch, NOT fully tested with regards to checking the contributors
Attachment 4694-1
The patch adds to the 60 day check. That is, if a plugin is closed less than 60 days, the message includes that the closure is temporary, pending review. If it's closed more than 60 days, that message is removed as the odds are pretty small.
This also contains a change to merge closed and disabled notifications. From an end user perspective, they're the same. The same checks for admins exists so they can see why.