Add a mechanism allowing project admins to "delete" a user #2445
Conversation
This leaves the user record and host records in the DB to avoid dangling references from the result table. It: - changes the user name, email addr, and auth to "deleted_xxx" - removes the user from team - removes posts by the user - removes PMs by the user - removes friend connection - removes profile - "anonymizes" the hosts (erase IP addr and domain name) Note 1: this is accessed by admins using a script in ops/; It's not available to users. Note 2: this may not satisfy the requirements of EU-GDPR since it doesn't delete the user and host records.
|
David - do you mind if we hold on reviewing this to see how the discussion in #2447 goes? Since there might be a lot of overlap between the two it would be good to have one implementation if that will meet the needs that led to this pull request as well as GDPR? |
|
ok
…On Tue, Apr 3, 2018 at 3:12 PM, Kevin Reed ***@***.***> wrote:
David - do you mind if we hold on reviewing this to see how the discussion
in #2447 <#2447> goes? Since there
might be a lot of overlap between the two it would be good to have one
implementation if that will meet the needs that led to this pull request as
well as GDPR?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2445 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AA8KgWzJvttsIoRaIuak-C_EKS88C4aPks5tk_O4gaJpZM4TF04J>
.
|
|
@davidpanderson - as I think through #2447 - what was the driver for this pull request? I.e. I'd like to understand what are the needs that led to the creation of this pull request so that I can understand what other steps might be needed as I implement the other issue. |
|
There was a very strong request by one particular user to be erased from the BOINC-site, and potentially from project sites as well. Obviously I can't identify the user here, but they are known to me personally, and I can brief you privately if you wish. |
|
I don't need the details - just a general idea which you provided. It sounds like whatever we implement for GDPR will have satisified that request as well. Let me know if you agree. |
|
I would agree with that. I don't think the user concerned was consciously requesting a dummy run for GDPR, and I don't think that David was consciously operating GDPR, but in effect that's what happened. If you follow the current path of merging your legal advice with David's PR, the final result should have the best of both. |
|
I'm going to merge this to master and use it in pull request #2472 |
This leaves the user record and host records in the DB
to avoid dangling references from the result table.
It:
Note 1: this is accessed by admins using a script in ops/;
It's not available to users.
Note 2: this may not satisfy the requirements of EU-GDPR
since it doesn't delete the user and host records.