[wp-trac] [WordPress Trac] #43750: Establish a standard means of core reading privacy declarations from plugins' headers

[WordPress Trac]

#43750: Establish a standard means of core reading privacy declarations from
plugins' headers
-------------------------------------------------+-------------------------
 Reporter:  allendav                             |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  Privacy                              |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  gdpr has-patch needs-refresh needs-  |     Focuses:
  unit-tests                                     |  administration
-------------------------------------------------+-------------------------
Changes (by desrosj):

 * keywords:  gdpr needs-patch close => gdpr has-patch needs-refresh needs-
     unit-tests
 * focuses:   => administration
 * milestone:  Awaiting Review => Future Release


Comment:

 There will likely be something required on the w.org side to note privacy
 feature support directly on plugin pages eventually. But for now, let's
 focus on within WordPress. The main goal is to allow a plugin to declare
 that it integrates with a privacy feature to help site owners be aware of
 potential privacy issues on their site. Like declaring WordPress or PHP
 version support, it's a bit of an honor system.

 [attachment:43750.diff] is a start by adding support for a `Privacy:`
 header of the plugin. Eventually, the value should be transformed from
 comma separated list to an array.

 I like @allendav's suggestions in [ticket:43750#comment:10] as a starting
 point, but not sure those are worded the best, or that it covers all of
 the scenarios.

 The second part of this ticket would be the functions that interpret the
 values specified. `wp_plugin_has_privacy_support( 'feature' )`,
 `wp_privacy_plugin_supports_personal_data_export( $plugin )`, are a few
 examples @allendav and I were kicking around.

 After #43938 receives some UX feedback, the functionality needs will be
 clearer, but we can start to draw up the basics.

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