From: Joe Perches <joe@perches.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Theodore Ts'o <tytso@mit.edu>,
linux-kernel@vger.kernel.org
Subject: Re: PSA: Do not use "Reported-By" without reporter's approval
Date: Fri, 24 May 2019 08:06:49 -0700 [thread overview]
Message-ID: <ee5c9928d7193436735bf766fb3c1fce81241bf5.camel@perches.com> (raw)
In-Reply-To: <20190524125402.GA616@chatter.i7.local>
On Fri, 2019-05-24 at 08:54 -0400, Konstantin Ryabitsev wrote:
> On Fri, May 24, 2019 at 12:57:08AM -0400, Theodore Ts'o wrote:
> > > I'm perfectly fine with Link:, however Reported-By: usually has the
> > > person's
> > > name and email address (i.e. PII data per GDPR definition). If that pehrson
> > > submitted the bug report via bugzilla.kernel.org or a similar resource,
> > > their expectation is that they can delete their account should they choose
> > > to to do so. However, if the patch containing Reported-By is committed to
> > > git, their PII becomes permanently and immutably recorded for any reasonable
> > > meaning of the word "forever."
> >
> > Many (most?) bugzilla.kernel.org components result in e-mail getting
> > sent to vger.kernel.org mailing lists. So even if they delete the
> > bugzilla account, there e-mail will be immortalized in lore.kernel.org
> > and their associated git repositories.
>
> I wouldn't say that most -- to my knowledge, it's only about 5-6
> components of the 50+. It's hard to tell how much that is by volume,
> though, because certainly not all components see much activity.
>
> We *can* excise things on lore.kernel.org. It's a massive pain, since
> message archive is a git repository itself, so will need to be rebased,
> reindexed and remirrored -- but it *is* possible.
It's likely not a worthwhile pain to self-inflict because
lore.kernel.org is not the only public vger mailing list archive.
https://lkml.org/
https://www.spinics.net/lists/kernel/
http://lkml.iu.edu/hypermail/linux/kernel/
https://marc.info/?l=linux-kernel
etc...
next prev parent reply other threads:[~2019-05-24 15:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 19:30 Konstantin Ryabitsev
2019-05-22 19:45 ` Joe Perches
2019-05-22 19:58 ` Konstantin Ryabitsev
2019-05-22 20:00 ` Joe Perches
2019-05-24 4:57 ` Theodore Ts'o
2019-05-24 12:54 ` Konstantin Ryabitsev
2019-05-24 15:06 ` Joe Perches [this message]
2019-05-23 5:53 ` Bhaskar Chowdhury
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=ee5c9928d7193436735bf766fb3c1fce81241bf5.camel@perches.com \
--to=joe@perches.com \
--cc=konstantin@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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
all inboxes | Powered by JetHome®