- Issue created by @w01f
- π©πͺGermany jurgenhaas Gottmadingen
I'd say, that doesn't help much. People who find the Klaro module have already found what they need. It's more like the other modules should point to Klaro with a recommendation to use this instead.
The EU Cookie Compliance module already has that recommendation in bold at the top of their project page.
And the GDPR module makes one assume it does the same, but it has no consent management whatsoever. And the module itself doesn't seem to be much maintained these days.
- πΊπΈUnited States w01f
Ahh, I had missed the bold message on the EU Cookie Compliance page (that's the one we use). If that's the case and they all tackle the same problem, so that Klaro is the obvious, de facto best option - then I agree and we can close this.
- π©πͺGermany jurgenhaas Gottmadingen
Yeah, it really sounds like the community is comming together behind this Klaro module. That's what I was told all over DrupalCon last week.
Here is also a link to our ADR on how the decision came together that Drupal CMS goes with Klaro: https://git.drupalcode.org/project/drupal_cms/-/wikis/Architecture-Decis...
- π©πͺGermany jan kellermann
Thank your for discussing.
Do you have some additions for the README or documentation?
Else I would like to close this issue.
- πΊπΈUnited States w01f
Only if you and Jurgen think something along the lines of:
"This module is the recommended replacement in Drupal 11 for sites previously using the EU Cookie Compliance and General Data Protection Regulation (GDPR) modules."
Otherwise, I agree and think it can be closed.
- π³π΄Norway svenryen
Just confirming what @jurgenhaas mentions in Comment 2: The "General Data Protection Regulation (GDPR)" module really handles other aspects of data protection than EU Cookie Compliance, and I think for some use cases the GDPR module is still useful even when Klaro! is being used. I wouldn't recommend saying that Klaro! replaces the GDPR module.
When it comes to EU COokie Compliance, we are doing what we can to deprecate it, but we have to do it the right way, and that takes time. Hopefully, by the end of May we should have reached a final conclusion about the fate of the EU Cookie Compliance module.
I have started today by posting that the EU Cookie Compliance module is looking for a new maintainer π¬ Seeking new maintainer for EU Cookie Compliance Active . I have read the docs on drupal.org quite in detail this morning, and it seems that making the announcement is the best practice and first step. If nobody shows interest, we're prepared to mark EU Cookie Compliance as Unsupported by the end of May.
- π©πͺGermany jurgenhaas Gottmadingen
@svenryen when it comes to the GDPR module, there is a lot of stuff included which is just confusing users. And things are extremely complex and linked into each other.
The good news is, that we found the maintainer of the important things in that module, which is identifying the PII fields and the reporting and deleting data on request handling. Together with him, we're in the process of refactoring that and moving his code into a new suite of modules that covers those areas, for details see π [Meta] PII module suite Active .
- π©πͺGermany Anybody Porta Westfalica