Closed MiquelRForgeFlow closed 6 years ago
Some questions about module naming:
dp_
, or privacy_
?gdpr_
prefix. Just to put an example, in Spain we had LOPD, then RGPD, then now GDPR. Naming the addon after each acronym would have been a nightmare, and narrowing its reach to just one jurisdiction also seems innecesary (think of those outside UE that want to use it). Isn't it better to stick with the prefix we choose at point 1?Yeah. No problem with renaming, but I want maximum consensus before doing it. I don't want to change the name four times 😏
My vote for privacy_
. We don't want more initials to get confused (dp: decimal precision? :laughing: )
It seems it's most accepted in the google doc; let's use privacy_
then.
I'll do further review after rename, or GH will trash all comments
I don't know what fails in Travis, but Runbot is :green_apple: 😎
As you see in the Readme, the xlsx report doesn't work because the pending fix in the odoo.
When https://github.com/OCA/data-protection/pull/2 gets merged, then I will open a new PR for the partner report.
@mreficent no point in waiting, please go ahead asap. You can fix the dependency name for the base module once #1 is sorted out.
This PR adds:
.gitignore
and.travis.yml
files.data_protection_base
module andgdpr_base
modules (Enable menus).gdpr_partner_report
module.GDPR Partner Report
This module helps a company to identify all the transactions that a specific partner is involved in, with the possibility to export the associated data.