1 |
>>>>> On Wed, 20 Jun 2018, Rich Freeman wrote: |
2 |
|
3 |
> The "underlying need" is what I'm getting at. Do we REALLY need to |
4 |
> track developers post-retirement? If we do, is DOB really the best |
5 |
> way to do this? |
6 |
|
7 |
I would presume that we do, if we need to clarify copyright or |
8 |
licensing of any files in our repositories. I could provide several |
9 |
examples where I had to contact retired devs because of license |
10 |
issues. |
11 |
|
12 |
But indeed, knowing their date of birth wouldn't have helped there. |
13 |
|
14 |
> And what are we going to do when some retired developer asks us to |
15 |
> forget about them? I don't think legally we need to go retract |
16 |
> published info, but that DOB seems very much the sort of thing that |
17 |
> would be risky to hold on to if somebody explicitly told us they don't |
18 |
> want us to retain it. We'd probably need justification to do so. |
19 |
|
20 |
The only justification I can think of is that we may need to know if |
21 |
a developer was of legal age when committing any code. But that seems |
22 |
very theoretical, since we don't even verify anybody's identity. |
23 |
|
24 |
Ulrich |