From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Joe Perches <joe@perches.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PSA: Do not use "Reported-By" without reporter's approval
Date: Wed, 22 May 2019 15:58:04 -0400 [thread overview]
Message-ID: <20190522195804.GC21412@chatter.i7.local> (raw)
In-Reply-To: <7b7287463e830fa8d981dc440f8165622cbc628e.camel@perches.com>
On Wed, May 22, 2019 at 12:45:06PM -0700, Joe Perches wrote:
>> It is common courtesy to include this tagline when submitting
>> patches:
>>
>> Reported-By: J. Doe <jdoe@example.com>
>>
>> Please ask the reporter's permission before doing so (even if they'd
>> submitted a public bugzilla report or sent a report to the mailing
>> list).
>
>I disagree with this.
>
>If the report is public, and lists like vger are public,
>then using a Reported-by: and/or a Link: are simply useful
>history and tracking information.
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 person 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."
Now, I'm pretty sure that a request to rebase git history to edit a
commit message would be considered "unreasonable" under GDPR provisions,
but a) it still eats up valuable time handling such requests and b) it's
a consequence reporters are not aware of when they submit bug reports.
So, my request to ask for permission before using "Reported-By" is not
coming from any legal position, but from the perspective of courtesy to
people submitting those reports.
-K
next prev parent reply other threads:[~2019-05-22 19:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 19:30 PSA: Do not use "Reported-By" without reporter's approval Konstantin Ryabitsev
2019-05-22 19:45 ` Joe Perches
2019-05-22 19:58 ` Konstantin Ryabitsev [this message]
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
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=20190522195804.GC21412@chatter.i7.local \
--to=konstantin@linuxfoundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.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