[wp-trac] [WordPress Trac] #22316: Plugin Dependencies (Yet Another Plugin Dependencies Ticket)

[WordPress Trac]

#22316: Plugin Dependencies (Yet Another Plugin Dependencies Ticket)
------------------------------------------+---------------------
 Reporter:  Viper007Bond                  |       Owner:  (none)
     Type:  enhancement                   |      Status:  new
 Priority:  normal                        |   Milestone:  5.9
Component:  Upgrade/Install               |     Version:  3.4.2
 Severity:  normal                        |  Resolution:
 Keywords:  dev-feedback has-patch early  |     Focuses:
------------------------------------------+---------------------
Changes (by peterwilsoncc):

 * keywords:  dev-feedback has-patch => dev-feedback has-patch early


Comment:

 As the code stands, I think it's a good proof of concept but I don't think
 this is ready to be considered for 5.9. The discussion on the approach has
 been sporadic for the last four years so moving from proof of concept PR
 to core seems a little rushed.

 This is what I would like to see happen before this is considered for
 merge:

 * Feature discussion on this ticket rather than a PR. The code has come
 before a revised discussion on the feature so getting the architecture
 down before the proof-of-concept moves forward will help.

 * Agenda a discussion on the feature in a Core dev-chat. The only
 discussion I've seen is an announcement of the PR rather than discussing
 the feature

 * A feature plugin: this is a problem WP has been sitting on for nine
 years, so there's no need to get it in to Core in the next three months.

 During manual testing of the feature branch, I've found a few things that
 will need a decision:

 * should the bootstrapping of WP take in to account dependency order for
 the `require`-ing of plugins
 * how should external/commercial plugin repositories be accounted for
 (there's a suggestion above of a `provider:` prefix)
 * if a namespace prefix is used, should wordpress.org's plugin repo use
 one too

 It would also be good to get further design team involvement in the
 notifications. My testing threw three dependency notifications and an
 activation notification which was already becoming a little overwhelming.

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