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

WordPress Trac noreply at wordpress.org
Thu Apr 30 18:06:14 UTC 2020


#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):

 Besides the fact that 'google-tag-manager' is disallowed for trademark
 reasons (unless you're Google), I disagree. Partly. I don't think the sole
 responsibility is (nor should be) on the plugin review team. But I do
 think we need to make sure we don't make things worse.

 The issue isn't just if YOU, who owns apedog-tag-manager and has it
 installed somewhere wants to now host on .org, damn the consequences. It's
 what if someone ''else'' does it? A real-world example for you: End users
 upload other people's plugins to .org semi-regularly. I assume it's
 because they think it's uploading to their site, but none of those people
 have replied so I don't know for sure.

 There's more layers to "We need to make sure plugin X in the wild doesn't
 get broadsided by a new plugin on .org" and having multiple checks and
 balances will help us prevent the damage.

 > The idea is to allow any plugin with any name to tell WP core: "I am not
 a WP.org plugin. I update from X" or "I am not a WP.org plugin. And I
 don't update at all. Leave me alone."

 Sure. And by blocking people from using those names, we prevent someone
 from installing a plugin that already exists and breaking their site.
 (i.e. you have apedog-tag-manager as a non-org plugin AND as a .org
 plugin, and someone tries to install both... What happens?)

 We want to prevent that too, at least as much as we can :)

 We're never going to prevent every possible permutation of errors, but
 that's not a reason not to stop what we know we can.

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


More information about the wp-trac mailing list