From: Raymond Jennings <shentino@gmail.com>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Date-of-birth in developer applications
Date: Wed, 20 Jun 2018 13:47:30 -0700 [thread overview]
Message-ID: <CAGDaZ_rRcTuYvenNho5HGs14QpWD17PQbCFF14dJ_nw4yrTkkw@mail.gmail.com> (raw)
In-Reply-To: <1529483543.2506.23.camel@gentoo.org>
On Wed, Jun 20, 2018 at 1:32 AM Michał Górny <mgorny@gentoo.org> wrote:
>
> W dniu śro, 20.06.2018 o godzinie 10∶24 +0200, użytkownik Kristian
> Fiskerstrand napisał:
> > On 06/20/2018 10:16 AM, Michał Górny wrote:
> > > However, I'm not aware of any good
> > > justification for collecting this kind of personal information.
> >
> > 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? Even if we ever have to do that, do you
> really think we'd use one's birthday all over the place?
>
> > (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'.
>
> c. We don't even have any clue what to do if someone is *not* of 'legal
> age'.
As a logical issue, I will point out that point a, legal age differing
per country, directly contradicts point b, using a simple boolean.
The fact that there are multiple countries with possible disparate
concepts of "legal age" preempts the usefulness of a simple boolean,
and in my observation actually *increases* the viability of using DOB
as legal age.
Quite simply, if we WERE to use a single boolean the first question
we'd have on our hands when answering "is this developer of legal age"
is first to ask "of what country?"
>
> --
> Best regards,
> Michał Górny
next prev parent reply other threads:[~2018-06-20 20:48 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-20 8:16 [gentoo-project] Date-of-birth in developer applications Michał Górny
2018-06-20 8:24 ` Kristian Fiskerstrand
2018-06-20 8:32 ` Michał Górny
2018-06-20 8:53 ` Kristian Fiskerstrand
2018-06-20 8:55 ` Dale
2018-06-20 8:56 ` Kristian Fiskerstrand
2018-06-20 11:09 ` Rich Freeman
2018-06-20 11:14 ` Kristian Fiskerstrand
2018-06-20 11:23 ` Rich Freeman
2018-06-20 11:26 ` Kristian Fiskerstrand
2018-06-20 9:04 ` Ulrich Mueller
2018-06-20 9:16 ` Michał Górny
2018-06-20 10:52 ` Rich Freeman
2018-06-20 11:12 ` Kristian Fiskerstrand
2018-06-20 11:41 ` Rich Freeman
2018-06-20 13:06 ` Ulrich Mueller
2018-06-20 13:10 ` Kristian Fiskerstrand
2018-06-20 13:50 ` Rich Freeman
2018-06-20 14:19 ` Ulrich Mueller
2018-06-20 15:00 ` R0b0t1
2018-06-20 20:47 ` Raymond Jennings [this message]
2018-06-20 8:33 ` Marek Szuba
2018-06-20 8:47 ` Ulrich Mueller
2018-06-20 9:12 ` Michał Górny
2018-06-20 9:38 ` Ulrich Mueller
2018-06-20 15:06 ` Matthew Thode
2018-06-20 15:20 ` Matthew Thode
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGDaZ_rRcTuYvenNho5HGs14QpWD17PQbCFF14dJ_nw4yrTkkw@mail.gmail.com \
--to=shentino@gmail.com \
--cc=gentoo-project@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox