From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id B2925138334 for ; Wed, 20 Jun 2018 09:05:03 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id EC8C9E0A8C; Wed, 20 Jun 2018 09:05:02 +0000 (UTC) Received: from smtp.gentoo.org (dev.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id B0375E0A8B for ; Wed, 20 Jun 2018 09:05:02 +0000 (UTC) Received: from a1i15.kph.uni-mainz.de (host2092.kph.uni-mainz.de [134.93.134.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: ulm) by smtp.gentoo.org (Postfix) with ESMTPSA id 71613335CA5; Wed, 20 Jun 2018 09:05:00 +0000 (UTC) Message-ID: <23338.6328.533219.212459@a1i15.kph.uni-mainz.de> Date: Wed, 20 Jun 2018 11:04:56 +0200 To: gentoo-project@lists.gentoo.org Subject: Re: [gentoo-project] Date-of-birth in developer applications In-Reply-To: <1529483543.2506.23.camel@gentoo.org> References: <1529482561.2506.17.camel@gentoo.org> <756a345e-0209-9643-c94f-1cf94321eb2a@gentoo.org> <1529483543.2506.23.camel@gentoo.org> X-Mailer: VM 8.2.0b under 24.3.1 (x86_64-pc-linux-gnu) From: Ulrich Mueller Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Project discussion list X-BeenThere: gentoo-project@lists.gentoo.org Reply-To: gentoo-project@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="pgp+signed+OGP7ezbGZI1b8mq"; micalg=pgp-sha256; protocol="application/pgp-signature" X-Archives-Salt: 61438abe-1058-489f-91eb-3fe963b1db59 X-Archives-Hash: 8a0bbc1d4c035d8e318078a23d3aaf26 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --pgp+signed+OGP7ezbGZI1b8mq Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable >>>>> On Wed, 20 Jun 2018, Micha=C5=82 G=C3=B3rny wrote: > W dniu =C5=9Bro, 20.06.2018 o godzinie 10=E2=88=B624=E2=80=89+0200, u= =C5=BCytkownik Kristian > Fiskerstrand napisa=C5=82: >> Immediately I can think of two good reasons for this information, >> (i) as a disambiguifier for matching names, at least across europe >> it is common to refer to an individual "A born DD.MM.YYYY", > Please tell me, how many times did we have to disambiguate two > developers using the same name=3F Even if we ever have to do that, do= > you really think we'd use one's birthday all over the place=3F At least once. While we researched the copyright forms, we wondered why there were two entries in LDAP with a different nick, but with the same name and approximately the same location. >> (ii) verify legal age for entering into agreements. One can argue >> that without further verification of (ii) it has less value, but at >> least that would be a misrepresentation so shifting the question a >> bit if it ever becomes an issue with FLA/DCO etc. > a. 'Legal age' may differ per country, so birth date alone is not > very useful. > b. There is no reason to store the full birth date if all we need is > a boolean whether someone is of 'legal age'. How would you determine when to flip that bit=3F > c. We don't even have any clue what to do if someone is *not* of > 'legal age'. And closing our eyes would improve that situation=3F Ulrich --pgp+signed+OGP7ezbGZI1b8mq Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBCAAGBQJbKhi0AAoJEMMJBoUcYcJz0VwIAJDtZywSbrcDo7TNmBaR7nvK 3/AhuCG4UG1HZASCSe+cE+3caQUhLNflRKuXNf53N/r95R4BCmzT+YrexbcYE9AQ rm8OepFCsY9Gh5x+5h0//x8UpnTVvEzgskl7hecCfvkS//N9/jZv0x/KYhlpuxWp 00/kWt9guXPXTmfoV3Dz8UNt4SImnOTw8FwYDEMqSBOQ37hyTODRiR/r8iSadDqL ClpwB0s+vg5zCv7yYEo58IHMMXzNZPW6x8qVyrbwbJuJqmhO4+IoJSPb7Eg6L3/N U7bWChlzAKwjubPuYxJMA5LWYCEpPfgryYQedV3+5wreuPNgHpqhNVDGPwsHa7A= =5hWj -----END PGP SIGNATURE----- --pgp+signed+OGP7ezbGZI1b8mq--