For plugins that do NOT contain any "high risk / high impact" functions, the Disclosure Tab would display that the plugin is not compatible.
For plugins that DO contain "high risk / high impact" functions, the Disclosure Tab would display a warning, in addition to a statement that the plugin is not compatible.
It is also recommended that the plugin's repository page on WordPress.org should display the warning in the latter case (possibly in a similar manner to the banner displayed if a plugin has not been tested with the last 3 major releases).
Although DPT could potentially reduce the risks associated with plugins in the WordPress.org repository to an acceptably low level, the risk associated with premium plugins could also potentially be reduced significantly.
We regard privacy as a strategic competitive advantage and believe that the market will eventually require compatibility, even if the WordPress.org Plugin Guidelines make compatibility voluntary. This is at the Plugin Team's discretion - they may or may not require compatibility before, at the time of, or after inclusion into core.
We would like to see plugins that do not use "high risk / high impact" functions / APIs, but who do not explicitly declare compatibility, reduced very quickly by making it very easy to declare compatibility. Discussion here: https://github.com/carike-codes/disclosures-and-permissions-tabs/issues/5
It is also recommended that the plugin's repository page on WordPress.org should display the warning in the latter case (possibly in a similar manner to the banner displayed if a plugin has not been tested with the last 3 major releases).
Although DPT could potentially reduce the risks associated with plugins in the WordPress.org repository to an acceptably low level, the risk associated with premium plugins could also potentially be reduced significantly.
We regard privacy as a strategic competitive advantage and believe that the market will eventually require compatibility, even if the WordPress.org Plugin Guidelines make compatibility voluntary. This is at the Plugin Team's discretion - they may or may not require compatibility before, at the time of, or after inclusion into core.
We would like to see plugins that do not use "high risk / high impact" functions / APIs, but who do not explicitly declare compatibility, reduced very quickly by making it very easy to declare compatibility. Discussion here: https://github.com/carike-codes/disclosures-and-permissions-tabs/issues/5