public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-project <gentoo-project@lists.gentoo.org>
Subject: Re: [gentoo-project] Date-of-birth in developer applications
Date: Wed, 20 Jun 2018 06:52:29 -0400	[thread overview]
Message-ID: <CAGfcS_m0MZsqPTEH87mnP4f8ACgyUoOU5_C5modaUd5UwHbbWA@mail.gmail.com> (raw)
In-Reply-To: <1529483543.2506.23.camel@gentoo.org>

On Wed, Jun 20, 2018 at 4:32 AM Michał Górny <mgorny@gentoo.org> wrote:
>
> 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?

Even if we've had two people from the same location with the same
name, WHY would we ever have to use their date of birth to identify
them?  We already have their nicks which is what we use internally,
and those are always unique.

And if we DID have to identify a specific individual legally, then why
aren't we collecting government ID numbers, which actually do the job
a LOT better than DOB?

As far as I'm aware, under most privacy laws and policies I've seen,
name+DOB is just as sensitive as a government ID number.  If
collecting the latter makes you recoil in horror, then you should be
just as concerned about DOB collection.

I don't see the need to collect either for legal identification
purposes, so why do it?

> b. There is no reason to store the full birth date if all we need is
> a boolean whether someone is of 'legal age'.

++

Just ask put on the dev application a certification that they are
legally allowed to sign agreements.  That depends on more than just
age anyway.

Could somebody lie?  Sure, just as they can lie today about their DOB.

This is just reasonable care.  I don't think there is any expectation
by anybody that we have a higher level of certainty that our
developers are able to sign things (DCOs or otherwise - which are also
just reasonable care, unless we intend to start doing in-depth reviews
of every commit).

If we did need a higher level of certainty, then just asking for DOB
won't cut it.  We'd need to verify IDs, take at least some level of
care that they aren't mentally incapacitated, and know the local age
of being able to sign such agreements.

I think we need to take a step back and consider the threat model
here.  What is the threat we need to protect against?  Is collecting
DOB an effective but least-intrusive way of mitigating that threat?

-- 
Rich


  parent reply	other threads:[~2018-06-20 10:52 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 [this message]
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
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=CAGfcS_m0MZsqPTEH87mnP4f8ACgyUoOU5_C5modaUd5UwHbbWA@mail.gmail.com \
    --to=rich0@gentoo.org \
    --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