Working on WordPress.org’s GDPR compliance team is providing a good opportunity to look at other issues not necessarily related to one piece of legislation, but which impact the .org ecosystem all the same. Amongst other things, we are taking a look at the plugin developer guidelines to see where we can strengthen and clarify what they say about the ways data should be structured and protected. While we were thinking about the plugin guidelines, I took the opportunity to kill off a problem I have ranted against on conference stages for years. I worked with the .org plugin review team to have Section 9 of the plugin development guidelines, Developers and their plugins must not do anything illegal, dishonest, or morally offensive, amended with the following line:
implying that a plugin can create, provide, automate, or guarantee legal compliance
and with that, an issue which has always troubled me as a real risk to the integrity of the ecosystem has been shot down.
Going forward, plugins can, and certainly should, clarify that they can help a site administrator with aspects of a compliance issue, whether that is a front-end process or a back-end workflow. But claiming that a plugin
Source: https://managewp.org/articles/17340/pulling-the-plug-on-legal-compliance-plugins
source https://williechiu40.wordpress.com/2018/04/19/pulling-the-plug-on-legal-compliance-plugins/
No comments:
Post a Comment