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

 Can the title of this ticket/task be updated to "Ability to mark plugin as
 **__non-WP.org__** repo plugin"?

 With the introduction of auto-updates in 5.5 the need for a plugin header
 marking a plugin as non-wp.org will become relevant for custom plugins
 that __''ARE'' managed__ - just not managed on wp.org.
 The original wording of this ticket - to mark a plugin as "private" or
 "unmanaged" - no longer expresses the use of this feature correctly.

 I would also suggest opening a separate ticket for how the wp.org repo
 handles slugs for new plugin submissions. While these issues are related,
 they are "perpendicular" to each other. The resolution of one does not
 affect the resolution of the other.

 - The need of a plugin (especially a self-managed/self-updating plugin) to
 self-identify as non-wp.org. Allowing custom/private/in-the-wild plugin
 authors to safely turn-on auto-updates for their plugins without having to
 worry about a future naming conflict being introduced. (this ticket)
 - Updating the naming policy of wp.org plugin repo to alleviate such
 naming conflicts arising for new plugins added to the repo. (separate
 ticket)

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