Timeline for Does GDPR affect individual contributor license agreements for opensource projects?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 7, 2018 at 22:59 | comment | added | Shinrai | Again it depends on the exact CLA which was signed. The GDPR isn't invalidating the CLA itself it's invalidating the ability to maintain the data subject's personal data. The best, and probably safest option, would to claim Article 6 section 1b. As the CLA itself is a contract in itself. | |
| Jun 1, 2018 at 16:26 | comment | added | carlspring | "Consent must be informed per Recital 32 of the GDPR" means what exactly? Just sending them an e-mail informing them what their contact details will be kept for, or asking them all to re-sign the agreements with this amendment? (I find it hard to believe that it's the latter, as it would also invalidate all sorts of other legally binding signed contracts). Please, advise! | |
| Jun 1, 2018 at 15:25 | comment | added | carlspring | These details provided by the contributor are solely for identifying them as having agreed (in signed form) with the project's license. | |
| Jun 1, 2018 at 15:21 | comment | added | carlspring | Are you sure about the part requiring the re-signing of the CLA for older signed agreements? So far, I haven't seen any OSS projects chasing contributors to do so. I mean -- if this were so, it would open a door to a whole world of cases where developers would be granted a chance to revoke their permission, (if, for example, a project has become quite successful) and potentially want compensation for this. I believe the information collected for the sake of the agreement (name, address, e-mail, phone) is required as legally binding and fits the "special circumstances" clause. | |
| May 28, 2018 at 8:31 | history | answered | Shinrai | CC BY-SA 4.0 |