Re: Is git compliant with GDPR?

From: demerphq <demerphq@gmail.com>
Date: Jul 3, 2020, 06:29 UTC
Message-ID: <CANgJU+X2C157XCxbcdrGf1rRWY10o9UGtXMaqafgJBLORucEkw@mail.gmail.com>
In-Reply-To: <0f0e01d650a6$9a5b5b80$cf121280$@pdinc.us>

On Thu, 2 Jul 2020 at 21:27, Jason Pyeron <jpyeron@pdinc.us> wrote:

Show 10 quoted lines

> > On Sun, Jun 03, 2018 at 04:28:31PM +0100, Philip Oakley wrote:
> <snip/>
> > You provide a lot of arguments about why it is not a necessity to have
> > this, but let's assume it is; is there any actual problem you see with
> > the proposal, except that someone would have to implement it?
>
> It's the strawman problem. If it was a real 'real issue' then it would have
> already shown up with companies clamouring to pay folk to fix our (git's)
> latest problem. But the haven't, so I think it's a much more balanced issue.
>

I don't agree. These things tend to come in waves. Just because the first wave hasnt hit yet doesn't mean it wont come. GDPR is still super new, people are still coming to understand it. Over time this understanding will lead to more people exercising the right to be forgotten.

cheers, Yves

-- 
perl -Mre=debug -e "/just|another|perl|hacker/"