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

 Replying to [comment:87 apedog]:
 > Replying to [comment:86 afragen]:
 > > I’ve always thought something like this was plugin territory, so I
 wrote one.
 > >
 > > https://github.com/afragen/skip-updates
 > >
 > > It will skip any updates only for plugins or themes hosted on dot org.
 >
 > This ticket is about allowing a custom plugin to self-dis-associated
 from wp.org repo. Not neccessarily disabling its updates altogether. The
 plugin might still have its own update routine from another repo (eg.
 using https://github.com/afragen/github-updater). It's more about
 "namespacing". Allowing plugin authors to confidently create custom
 plugins without having to worry about a same-name plugin later being added
 to the wp.org repo and messing with the current plugin's functionality.
 >
 > This is not plugin territory. It's very much a wp-core issue.

 All this plugin does is dis-associate other plugins or themes from dot
 org.

 It really does work flawlessly with GitHub Updater or likely any other
 custom updater.

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