[wp-trac] [WordPress Trac] #32101: Ability to mark plugin as unmanaged

[WordPress Trac]

#32101: Ability to mark plugin as unmanaged
-------------------------------------+----------------------------
 Reporter:  damonganto               |       Owner:  DrewAPicture
     Type:  task (blessed)           |      Status:  assigned
 Priority:  normal                   |   Milestone:  WordPress.org
Component:  Plugins                  |     Version:  4.1.2
 Severity:  major                    |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:
-------------------------------------+----------------------------

Comment (by Ipstenu):

 > While useful against someone poisoning the ecosystem with a plugin named
 'advanced-custom-fields-pro', that isn't the point of this ticket. This
 ticket is not about well know commercial plugins, it's about private
 plugins not "known to exist in the wild".

 Yeah, I'm not talking about well-known-commercial plugins either.

 The bar is super low (100 users at the moment) for 'is this a plugin known
 to .org?' and keep in mind, by that we mean "Is it a plugin that someone
 has installed on a WP site that's phoned home to momma for updates?"

 Which means ''all'' plugins on a site that contacts .org for any updates,
 which absolutely covers exactly who you're talking about.

 I do actually understand the ticket, and it's always going to be 'both'
 here. That's why I said 'somewhat' mitigated. It's not solved by any
 means, but we're doing our best outside this to make it less possible to
 damage sites.

 1. We don't want WP.org plugins to conflict with plugins not hosted here,
 regardless of how many users.

 2. We don't want plugins hosted here to accidentally hurt themselves and
 break updates.

 Basically? I don't want to hurt ANY users :) Thanks.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/32101#comment:69>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform