From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: meta@public-inbox.org, a.fatoum@pengutronix.de
Subject: Re: Indicating the mirror's origin
Date: Wed, 14 Jun 2023 16:56:52 -0400 [thread overview]
Message-ID: <20230614-storage-plutonium-a7df9d@meerkat> (raw)
In-Reply-To: <20230614201857.imjpysjbu4mrxa35@pengutronix.de>
On Wed, Jun 14, 2023 at 10:18:57PM +0200, Uwe Kleine-König wrote:
> Hello Konstantin,
>
> On Wed, Jun 14, 2023 at 02:42:15PM -0400, Konstantin Ryabitsev wrote:
> > We've had a few requests to mirror public-inbox archives that originate on
> > other systems so they can also be searchable and viewable via lore.kernel.org.
> > I've been dragging my feet on these requests, because they are a potential
> > liability in terms of GDPR compliance.
>
> What is the relevant GDPR liability here? I assume someone who sent a
> mail to (say) barebox@lists.infradead.org can request that you remove
> your copy of that mail?!
It feels stupid to subscribe an archiver agent to the list when a public-inbox
repository is conveniently available for cloning. However, if we just clone
the repository over and integrate it into lore, we need to indicate that we're
just copying bits over from some other location -- I cannot delete things from
the archive on my own any more.
> (I wonder what should be the effect on lore.kernel.org if
> lore.barebox.org removes a mail. Should it disappear from the former,
> too?)
Yes, if we are mirroring the underlying archive git repositories, any deletes
you make on your end will propagate to us.
-K
next prev parent reply other threads:[~2023-06-14 20:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 18:42 Indicating the mirror's origin Konstantin Ryabitsev
2023-06-14 20:18 ` Uwe Kleine-König
2023-06-14 20:56 ` Konstantin Ryabitsev [this message]
2023-06-14 23:50 ` Eric Wong
2023-06-15 14:47 ` Konstantin Ryabitsev
2023-06-19 6:09 ` Uwe Kleine-König
2023-06-20 2:37 ` [RFC] support publicinbox.$FOO.appendHeader in read-only endpoints Eric Wong
2023-07-05 14:27 ` Ahmad Fatoum
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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230614-storage-plutonium-a7df9d@meerkat \
--to=konstantin@linuxfoundation.org \
--cc=a.fatoum@pengutronix.de \
--cc=meta@public-inbox.org \
--cc=u.kleine-koenig@pengutronix.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).