Re: GDPR compliance best practices?

From: Theodore Y. Ts'o <tytso@mit.edu>
Date: Jun 10, 2018, 01:41 UTC
Message-ID: <20180610014133.GB5020@thunk.org>
In-Reply-To: <059CBAEFB9D945EE9D54BF515E963798@PhilipOakley>

On Sat, Jun 09, 2018 at 11:50:32PM +0100, Philip Oakley wrote:

Show 7 quoted lines

> I just want to remind folks that Gmane disappeared as a regular list because
> of a legal challenge, the SCO v IBM Unix court case keeps rumbling on, so
> clarifying the legal case for:
> a) holding the 'personal git meta data', and
> b) disclosing (publishing) 'personal git meta data'
> under various copyright and other legal issue scenarios relative to GDPR is
> worth clarifying.

And I suspect the best way of clarifying things is for laywers at the major corporations (e.g., Red Hat, Microsoft now that it owns github, Google since it publishes Android sources at sources.android.com, Canonical, etc.) to figure it out.

Those situations may very well differ depend on whether they have a CLA or Copyright Assignment Agreement which they require of contributors. But fortunately, those organizations are also best set up to send patches. :-)

If those organizations are not choosing to send patches, I suspect that might be a strong hint as to what those lawyers have concluded.

						- Ted