[wp-meta] [Making WordPress.org] #6921: Prepare for Plugin Dependencies

[Making WordPress.org]

#6921: Prepare for Plugin Dependencies
------------------------------+---------------------
 Reporter:  dd32              |       Owner:  (none)
     Type:  defect (bug)      |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:  needs-patch       |
------------------------------+---------------------

Comment (by afragen):

 @dd32 to answer the these questions directly.

 > To prepare for this, we could:
 >
 > - Block plugin submissions and updates which reference dependencies
 which are not valid

 I think we need to discuss what it means to have a valid dependency. My
 opinion is that if the dependency exists somewhere that the user can
 install it, it is valid. It may take the user purchasing and installing a
 premium plugin but this is no different for add-ons for Gravity Forms or
 WPML that currently exist.

 > - Block plugin submissions which use the Dependencies feature but are
 not Requires WP >= 6.3

 Plugins can still use the Plugin Dependencies feature plugin for
 compatibility. But certainly a response from the plugin review team
 indicating this would be in order with a recommendation to update to
 `Requires at least: 6.3`.

 > - Potentially delist existing plugins when the dependencies become
 unavailable (ie. Required plugin is removed from the directory, a plugin
 which requires that plugin should not be installable)

 I don't think a plugin should be delisted. If a plugin dependency is not
 available and not installed/active, the dependent plugin will
 automatically be deactivated and will not be able to be activated until
 the dependency is met. Again, as long as the dependency exists and is
 installable by the user the dependent plugin is usable.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/6921#comment:18>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org