WordPress.org

Making WordPress.org

Opened 5 weeks ago

Closed 4 weeks ago

Last modified 2 weeks ago

#4694 closed defect (fixed)

Plugin Directory: More userfriendly language regarding plugin closures

Reported by: Ipstenu Owned by: tellyworth
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)

4694-1.diff (2.4 KB) - added by Ipstenu 5 weeks ago.
4694-2-UNTESTED.diff (3.1 KB) - added by Ipstenu 5 weeks ago.
More complex version of the first patch, NOT fully tested with regards to checking the contributors

Download all attachments as: .zip

Change History (12)

@Ipstenu
5 weeks ago

#1 @Ipstenu
5 weeks ago

  • Keywords has-patch added

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.

#2 @Ipstenu
5 weeks 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.

@Ipstenu
5 weeks ago

More complex version of the first patch, NOT fully tested with regards to checking the contributors

#3 @Ipstenu
5 weeks ago

Pinging @otto42 and @dd32 for eyes on this please.

#4 @SergeyBiryukov
5 weeks ago

  • Component changed from General to Plugin Directory

#5 @Ipstenu
5 weeks ago

  • Component changed from Plugin Directory to General
  • Keywords dev-feedback added

OH and this should be PROPS to jb510 no matter which way we go.

#6 @Ipstenu
5 weeks ago

  • Component changed from General to Plugin Directory

#7 @tellyworth
5 weeks ago

  • Owner set to tellyworth
  • Status changed from new to reviewing

#8 @SergeyBiryukov
4 weeks ago

  • Resolution set to fixed
  • Status changed from reviewing to closed

In 9116:

Plugin Directory Theme: Make plugin closure messages more user-friendly; make it clear when the closure is temporary.

Props Ipstenu, jb510, SergeyBiryukov.
Fixes #4694.

#9 @SergeyBiryukov
2 weeks ago

In 9128:

Plugin Directory Theme: When determining the permanence of plugin closure, check if the plugin has committers.

Props Ipstenu.
See #4718, #4694.

#10 @SergeyBiryukov
2 weeks ago

In 9129:

Plugin Directory Theme: Correct the close reason check when determining the permanence of plugin closure.

See #4718, #4694.

Note: See TracTickets for help on using tickets.