[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 apedog):

 I think actually the onus shouldn't be on WP.org plugins repo. Regardless
 of the naming policy WP.org repo adopts.

 If someone wants to upload a generic {{{google-tag-manager}}} utility
 plugin to WP.org, she shouldn't be blocked from using that generic name
 just because another {{{google-tag-manager}}} plugin already exists "in
 the wild".

 This is a WP core issue. Not a WP.org plugins-repo issue.
 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.__"

 The point of adding this as a header (and not a hook) is so the plugin can
 communicate this to core even when deactivated.

 This reduces the onus on the plugins repository to manage plugin naming
 conventions. And it affords plugin authors better control of their
 plugins. Be they publicly-available plugins (used by 100 installations) or
 a tailor-made plugin (used by a single website). I can write a small
 {{{google-tag-manager}}} plugin with hard-coded ID for a client and never
 worry about a potential future conflict when someone adds a similar plugin
 to the WP.org repo.

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