[wp-trac] [WordPress Trac] #43750: Establish a standard means of core reading privacy declarations from a plugins' headers (was: Establish a standard means of core reading privacy declarations from plugins’ readme.txt)

[WordPress Trac]

#43750: Establish a standard means of core reading privacy declarations from a
plugins' headers
------------------------------------+------------------------------
 Reporter:  allendav                |       Owner:  (none)
     Type:  enhancement             |      Status:  new
 Priority:  normal                  |   Milestone:  Awaiting Review
Component:  Privacy                 |     Version:  trunk
 Severity:  normal                  |  Resolution:
 Keywords:  gdpr needs-patch close  |     Focuses:
------------------------------------+------------------------------

Comment (by allendav):

 Replying to [comment:14 Otto42]:
 > Just for informational purposes, core currently has no way to read or
 parse the readme.txt at all. That has always been an exclusive thing to
 the org site. So, from a purist point of view, as well as an
 implementation one, -1.
 >
 > You'd be better off to find a way for a plugin to declare that, yes, it
 does a thing, using the plugin header only. That's easier, more likely to
 gain traction, and doesn't run into myriad problems with translations.

 You're absolutely right @Otto42 - I was thinking plugin header and then
 didn't catch that we started talking about readme.txt

 The title of this issue doesn't help either :) I'll fix that next.

 So, to clarify, I'm talking about adding tags to the plugin header for
 privacy - not to a plugins' readme.txt.

 @azaozz - I'm renaming this issue to "Establish a standard means of core
 reading privacy declarations from a plugins' headers" - feel free to push
 back if that's a bad move.

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