WordPress.org

Making WordPress.org

Opened 6 months ago

Closed 6 months ago

Last modified 6 months ago

#5658 closed enhancement (wontfix)

Privacy is now a major subject

Reported by: arena Owned by:
Milestone: Priority: normal
Component: WordPress.org Site Keywords:
Cc:

Description

Privacy is now a major topic to choose a CMS.

Documentation related to privacy in wordpress is everywhere on the site (and also out of sight because out of site (slack)) and the latest roadmap (v2) is dated 14th february 2019.

Would be nice to reorganize all the usefull information related to privacy in one place with a chronology on what has been done (you know this accountability stuff from GDPR).

Regards

Attachments (1)

Privacy.png (81.4 KB) - added by arena 6 months ago.
Privacy

Download all attachments as: .zip

Change History (5)

@arena
6 months ago

Privacy

#1 @Otto42
6 months ago

  • Priority changed from high to normal

Unfortunately, we don't really have space on the page for another top level menu at present.

#2 @carike
6 months ago

  • Resolution set to wontfix
  • Status changed from new to closed

I disagree that Privacy is not at least as important as a top-level menu tab for Learn, @Otto42 :)
Having a top-level link to a privacy policy would help make .org more COPPA-friendly (this has been discussed on the Meta Make P2).

However, that having been said, we do not have a COPPA-friendly privacy policy at this point in time.
I do not believe that the roadmap would add significant value as a top-level menu item.

Going to close this ticket for now. It can be re-opened at a later time if needed.

#3 @arena
6 months ago

@Otto42, funny !

@carike, the screen is just a mockup using privacy roadmap v2 page ...

a) The global idea is to have a place where everything related to privacy in wp is documented.
I '"googled' "meta make P2" and "wordpress privacy meta make p2" and found nothing ...

b) Have no knowledge on any COPPA thing, i am a EU citizen.

c) I noticed that last theme twentytwentyone as a new section in readme.txt and i really appreciated it (privacy section should be a must do in plugins and themes as well as in wordpress readme.html)

<?php
== Privacy ==
Twenty Twenty-One uses LocalStorage to save the setting when Dark Mode support is turned on or off.
LocalStorage is necessary for the setting to work and is only used when a user clicks on the Dark Mode button.
No data is saved in the database or transferred.

d) Any chance to have an updated roadmap ?

Regards

#4 @carike
6 months ago

I am happy to hear that you noticed the privacy paragraph for Twenty Twenty-One, @arena :)

The Privacy team does not fall under Meta, it falls under Core.
So, if you would like to see information related to privacy, make.wordpress.org/core/tag/privacy/ would be the place to look.
That having been said, a lot of discussions happen on Slack and do not make it to P2, which is meant for discussing proposals before they become actionable as tickets.

An exception to that is this post: https://make.wordpress.org/meta/2021/01/03/protecting-childrens-privacy-on-wordpress-through-the-lens-of-coppa/, which is included on the Meta Make as it affects .org itself.

There are tickets for WordPress Core be able to process privacy related information from plugins and themes, with a JSON schema for plugins and themes to submit (and Core, at some point).
You can see that here: https://core.trac.wordpress.org/ticket/51092

As far as an updated Roadmap goes, that is possible, but I am not making any promises. :)

Privacy is a challenging component, in that it needs strong interdisciplinary collaboration.
While there is currently (only very recently, mind you) some sponsored dev hours for Privacy (not full time / enough to meet project demands like described above), there are no sponsored hours for the non-dev work.
Accountability reports aren't impossible, but someone actually has to do them. :)

I do still stand by my original assessment that a top-level menu item should only be reserved for an expanded Privacy Policy, which we currently do not have yet.

Note: See TracTickets for help on using tickets.