From: Jonathan Corbet <corbet@lwn.net>
To: Thorsten Leemhuis <linux@leemhuis.info>
Cc: workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Simona Vetter <simona.vetter@ffwll.ch>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v4] docs: clarify rules wrt tagging other people
Date: Mon, 10 Feb 2025 11:12:33 -0700 [thread overview]
Message-ID: <87y0ydzn1q.fsf@trenco.lwn.net> (raw)
In-Reply-To: <588cf2763baa8fea1f4825f4eaa7023fe88bb6c1.1738852082.git.linux@leemhuis.info>
Thorsten Leemhuis <linux@leemhuis.info> writes:
> Point out that explicit permission is usually needed to tag other people
> in changes, but mention that implicit permission can be sufficient in
> certain cases. This fixes slight inconsistencies between Reported-by:
> and Suggested-by: and makes the usage more intuitive.
>
> While at it, explicitly mention the dangers of our bugzilla instance, as
> it makes it easy to forget that email addresses visible there are only
> shown to logged-in users.
>
> The latter is not a theoretical issue, as one maintainer mentioned that
> his employer received a EU GDPR (general data protection regulation)
> complaint after exposing a email address used in bugzilla through a tag
> in a patch description.
>
> Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> Cc: Simona Vetter <simona.vetter@ffwll.ch>
> Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Reviewed-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> Reviewed-by: Shuah Khan <skhan@linuxfoundation.org>
> Signed-off-by: Thorsten Leemhuis <linux@leemhuis.info>
> ---
>
> Jonathan, what do you think of this? I felt somewhat unsure about this a
> few weeks ago, but I guess I was overly careful. If you think this
> change is fine and shouldn't cause any trouble for anyone, feel free to
> merge this. And if not, please speak up.
I have a couple of thoughts, neither of which is sufficient for me to
oppose the change if there is consensus for it:
- You're saying that people need to grep email addresses out of the git
history before crediting them in a tag; that's not a step we have
required of people before and seems like a bit much..?
- It would be awfully nice if we could provide this advice in exactly
one place in the document. This is one of our most important docs,
and it is far too long to expect new contributors to read through and
absorb. Avoiding making it longer and more repetitive would be
better, if we can.
- I wonder if it would make sense to say that, if an implicit-permission
tag has been added, the person named in it should get at least one
copy of the change before it is merged?
OK, three thoughts, you know what they say about off-by-one errors :)
Thanks,
jon
next prev parent reply other threads:[~2025-02-10 18:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 14:30 [PATCH v4] docs: clarify rules wrt tagging other people Thorsten Leemhuis
2025-02-07 1:42 ` Bagas Sanjaya
2025-02-07 8:24 ` Thorsten Leemhuis
2025-02-10 16:16 ` Mauro Carvalho Chehab
2025-02-11 8:45 ` Thorsten Leemhuis
2025-02-07 9:05 ` Laurent Pinchart
2025-02-08 15:36 ` Thorsten Leemhuis
2025-02-10 11:15 ` Laurent Pinchart
2025-02-11 8:43 ` Thorsten Leemhuis
2025-02-10 18:12 ` Jonathan Corbet [this message]
2025-02-11 8:48 ` Thorsten Leemhuis
2025-02-18 20:42 ` Jonathan Corbet
2025-03-06 13:31 ` Thorsten Leemhuis
2025-03-12 22:39 ` Jonathan Corbet
2025-03-17 22:49 ` Jonathan Corbet
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=87y0ydzn1q.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=mchehab+huawei@kernel.org \
--cc=simona.vetter@ffwll.ch \
--cc=skhan@linuxfoundation.org \
--cc=workflows@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