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

 Replying to [comment:73 Ipstenu]:
 > I'm disagreeing that they're ''entirely'' separate. I think they're
 running in parallel right here. Agree to disagree :)

 I _know_ your intentions are good, but I really do disagree.  These issues
 are entirely separate.

 The core issue in this ticket isn't a plugin with 100 users gotten from
 some other source conflicting with .org.  It's that a plugin with one
 user, who chose to name their private custom plugin "seed-core" and is in
 use on one site has to jump through hoops "just in case" some day someone
 submits a plugin to .org with the slug "seed-core".

 The cleanest simplest solution is above, add a line to the header block to
 declare its a `private`.  I really don't get how that one patch takes over
 5 years to get into core. It's exactly these sorts of tickets that sapped
 all interest I ever had in trac and core myself.

 Now, again, per above, it _could_ be a simple start to something so much
 better that just a private flag. That header line could declare an
 alternative source for updates. Imagine the utility in that just for
 testing beta versions before release to .org?  Imagine the utility in that
 to developers with private plugins like many of mine that are used across
 dozens of sites.

 WP's power comes from its flexibility and extensibility, and giving
 alternative sources core support would be FANTASTIC help to those needing
 that sort of flexibility.  Yes, they can write their own, but why should
 they when they could still make use of core tooling for secure, fail-safe,
 auto-updates of our private plugins which we are use across a few, or even
 hundreds of sites... instead of home-brewed updaters far more likely to
 have security and reliability issues than core's.

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