{"action":"created","issue":{"url":"https://api.github.com/repos/wp-cli/ideas/issues/84","repository_url":"https://api.github.com/repos/wp-cli/ideas","labels_url":"https://api.github.com/repos/wp-cli/ideas/issues/84/labels{/name}","comments_url":"https://api.github.com/repos/wp-cli/ideas/issues/84/comments","events_url":"https://api.github.com/repos/wp-cli/ideas/issues/84/events","html_url":"https://github.com/wp-cli/ideas/issues/84","id":297037179,"number":84,"title":"GDPR commands","user":{"login":"schlessera","id":83631,"avatar_url":"https://avatars1.githubusercontent.com/u/83631?v=4","gravatar_id":"","url":"https://api.github.com/users/schlessera","html_url":"https://github.com/schlessera","followers_url":"https://api.github.com/users/schlessera/followers","following_url":"https://api.github.com/users/schlessera/following{/other_user}","gists_url":"https://api.github.com/users/schlessera/gists{/gist_id}","starred_url":"https://api.github.com/users/schlessera/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/schlessera/subscriptions","organizations_url":"https://api.github.com/users/schlessera/orgs","repos_url":"https://api.github.com/users/schlessera/repos","events_url":"https://api.github.com/users/schlessera/events{/privacy}","received_events_url":"https://api.github.com/users/schlessera/received_events","type":"User","site_admin":false},"labels":[{"id":758404709,"url":"https://api.github.com/repos/wp-cli/ideas/labels/state:considering","name":"state:considering","color":"fbca04","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-02-14T10:06:04Z","updated_at":"2018-03-20T11:22:07Z","closed_at":null,"author_association":"OWNER","body":"WordPress is facing big issues with the rapidly approaching *[General Data Protection Regulation](https://en.wikipedia.org/wiki/General_Data_Protection_Regulation)* that will take effect starting from May 25th 2018.\r\n\r\nThere's a lot we could do using WP-CLI commands to give website owners the tools to comply with some of the regulations.\r\n\r\nSome preliminary thoughts:\r\n\r\n* WordPress Core will probably need some additional actions to allow for plugins to hook into those so that specific privacy-related tasks can be completed in a concerted manner across the entire WordPress site/application.\r\n* WP-CLI could start experimenting with such hooks, as it is fast and simple to iterate over functionality within the CLI. Any new tools don't need costly & time-consuming UI/UX to be usable.\r\n* Data  Controller tool: `wp user erase` could make sure that a user is deleted together with all of the privacy-related data that is attributed to this user. It could trigger a `wp_erase_user` hook to let plugins add their own data subsets to be erased.\r\n* Data Controller tool: `wp user anonymize` could render all data that belongs to a user into an anonymized form, like stripping part of the IP, replacing emails with a placeholder, etc... It could trigger a `wp_anonymize_user` hook to let plugins add their own data subsets to anonymize.\r\n* Data Controller tool: `wp user list-privacy-data` could generate a list (in several different formats, like CSV or JSON) of all the privacy-related information on a given user. It could trigger the `wp_user_privacy_data` filter so that plugins can add whatever personally identifiable information they have on a user.\r\n* Transition tool: `wp <entity> anonymize` could be used for specific entities like a comment or a post type, to remove all personally identifiable information from that entity. It could trigger a `wp_anonymize_$entity` hook to let plugins add their own data subsets to anonymize.\r\n* Transition tool: `wb db search --type=ip|email` could be used to search the database for specific personal information.\r\n\r\n(The above is only a collection of my very first thoughts, lots to discuss here)"},"comment":{"url":"https://api.github.com/repos/wp-cli/ideas/issues/comments/374562562","html_url":"https://github.com/wp-cli/ideas/issues/84#issuecomment-374562562","issue_url":"https://api.github.com/repos/wp-cli/ideas/issues/84","id":374562562,"user":{"login":"rosswintle","id":1532368,"avatar_url":"https://avatars2.githubusercontent.com/u/1532368?v=4","gravatar_id":"","url":"https://api.github.com/users/rosswintle","html_url":"https://github.com/rosswintle","followers_url":"https://api.github.com/users/rosswintle/followers","following_url":"https://api.github.com/users/rosswintle/following{/other_user}","gists_url":"https://api.github.com/users/rosswintle/gists{/gist_id}","starred_url":"https://api.github.com/users/rosswintle/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rosswintle/subscriptions","organizations_url":"https://api.github.com/users/rosswintle/orgs","repos_url":"https://api.github.com/users/rosswintle/repos","events_url":"https://api.github.com/users/rosswintle/events{/privacy}","received_events_url":"https://api.github.com/users/rosswintle/received_events","type":"User","site_admin":false},"created_at":"2018-03-20T11:22:07Z","updated_at":"2018-03-20T11:22:07Z","author_association":"NONE","body":"This is really good stuff.\r\n\r\nOne thing I've been talking about with another dev is anonymisation of data when taking a copy of a site. The use case for this is where I'm taking a copy of a client's site for local development work, and I don't want all their user data on my dev copy.\r\n\r\nIn this case being able to do `wp db export --anonymize` to get a dump of the database but with usernames and email addresses replaced by fake names (perhaps using something like Faker, if it's quick enough) would be awesome.  The flag could take a list of column names like `search-replace` does for excluding columns.\r\n\r\nI'm sure this needs more thought."}}
{"actor":{"display_login":"rosswintle"}}