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

[WordPress Trac]

#32101: Ability to mark plugin as unmanaged
-------------------------+------------------------------
 Reporter:  damonganto   |       Owner:
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Plugins      |     Version:  4.1.2
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:
-------------------------+------------------------------

Comment (by Otto42):

 I like [attachment:32101.diff] from @markjaquith adding the "Private"
 header. Not sure about the use of "true" here, but it's fine.

 Regarding the suggestions after it, about allowing updates from elsewhere,
 I think that while those topics are related, they're separate ideas.

 Allowing for updates from other APIs: #25314
 - Note that this would be something we would have to police for in the
 plugin and themes directory. WordPress.org directories are hosting sites,
 not listing sites. We don't allow code there to update from elsewhere.
 However, what your non-free plugin hosted from your own site does is not
 our concern so making that simpler is fine by me. Probably should be more
 than a header though, maybe a better filter or action. But that's
 discussion for over there.

 Using unique ID headers to identify plugins and prevent mismatching:
 #23318
 - Big +1 to this. Almost all the work for this is in the API though, not
 much to do in core.

 Having the private header do special things in the repos: (part of this
 ticket, mentioned by @ipstenu and @georgestephanis)
 - Not necessary, because we would actively block plugins and themes in the
 WordPress.org repository from having this header at all. It doesn't work
 that way, because obviously if we send a Private plugin to a system, it
 will never check for updates for that plugin ever again. So we'd prevent
 it entirely. Such a patch would be made to theme-check to prevent the
 theme from being uploaded, and to the plugin pre-commit scripts to prevent
 such a change from being committed, even by accident. Somebody
 accidentally makes it private, we send that ZIP to their users, they're
 now locked out of updates for it forever without manually editing the
 field.

 Usefulness of this by non-free plugins:
 - High at first, less so after #23318 goes in and gets widespread.

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