Open bugfolder opened 2 years ago
No need, it's already in the repo. Just needs to be enabled.
Reopening because there may need to be some discussion about it. The description of the extension (at https://beta.backdropcms.org/civicrm/admin/extensions?reset=1) includes a supposed link to documentation, which the https version of has a bad cert, and the http version of leads to a 404. And the main website of the organization (https://vedaconsulting.co.uk) does not seem to have any information about this extension.
Some of it is clear from the settings page: https://beta.backdropcms.org/civicrm/gdpr/settings
In looking at filling out b.org's GDPR settings page, the stuff to be filled in are things like official points of contact and things that depend on official organizational policies, most of which I would, if I encountered the question in the wild, would punt over to @jenlampton. So I'll do that here (and I'm going to deassign myself from the task). Jen, if you're not the right person to provide the information for this page, can you suggest who would be?
Good question! I took a first pass at updating the GDPR settings, but I think the contact should be conduct@backdropcms.org (or maybe we create a new privacy@backdropcms.org for this purpose?) rather than an individual. And maybe we can punt questions like this to that email (and thus people in some kind of privacy group) next time :)
Per meeting notes from CiviCRM meeting on 2022/03/14, add the CIviCRM GDPR extension to the codebase (download the extension locally, then commit it to the repo and git pull to the server).