user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <>
To: Konstantin Ryabitsev <>
Subject: Re: Recording archiver origins in git
Date: Tue, 29 Jun 2021 19:59:57 +0000	[thread overview]
Message-ID: <20210629195957.GA12571@dcvr> (raw)
In-Reply-To: <20210629125626.c5e6ianh6yilbakp@nitro.local>

Konstantin Ryabitsev <> wrote:
> On Mon, Jun 28, 2021 at 10:12:36PM +0000, Eric Wong wrote:
> Hope you're finding ways of staying cool and sane. It's hot here on the East
> coast, but a) we're used to it, and b) it's not yikes degrees.

Bugs are crazy invasive, again :<

> > > Imaginary code snippet:
> > > 
> > > $ git show refs/meta/origins:i
> > > [metadata]
> > > source = smtp
> > 
> > Is "source" necessary?  It seems like something that could be
> > in the "description" file or noted in the contents of
> > publicinbox.$NAME.infourl.
> I wasn't sure what infourl was used for. :) Is it supposed to contain
> structured data, or is it more of a "click here for more info" kind of thing?

It's "click here for more info", so freeform.  It should
probably be added to the footer of every HTML page.

> > > listaddress =
> > > listid =
> > > archive-url =
> > > archive-contact =
> > 
> > I think the keys should match what we use in the config file, at
> > least.  So s/listaddress/address/ and s/archive-url/url/
> Okay.
> > I'm not sure if "contact" is necessary if the aforementioned
> > "infourl" exists.
> My thinking is that with mirrors of mirrors of mirrors, if someone submits a
> GDPR removal request, then there should be an easy way of figuring out where
> these requests should actually go. Maybe infourl can cover this, but it's less
> likely to be set up than an email address like postmaster@. So, I'm in favour
> of keeping that in the info record.

I'm a little worried about it having too many directions
(e.g. webmaster vs postmaster) and something freeform like
infourl can cover it.  Or we maybe something with user-defined
labels would work:

	contact = postmaster
	contact = GPDR
	contact = webmaster

> > > Does that sound sane?
> > 
> > I think so.  Only the latest epoch would be taken into account,
> > I suppose.
> I'm actually thinking the other way around -- only the 0.git (or whatever is
> the lowest number), simply because it's more likely to have that record. That
> is, unless you want to add functionality to automatically copy these from
> previous epochs on auto-rotation events.

It should be easy to change this info down-the-line in case of
project name/hosting changes, forks, etc.  So whatever's latest
should supercede the older.  It would also allow partial mirrors
to work with only the latest epoch(s) (I expect a partial
mirrors of recent epochs to be more useful than mirrors with
only old epochs).

  reply	other threads:[~2021-06-29 19:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-28 21:26 Konstantin Ryabitsev
2021-06-28 22:12 ` Eric Wong
2021-06-29 12:56   ` Konstantin Ryabitsev
2021-06-29 19:59     ` Eric Wong [this message]
2021-06-29 20:10       ` Konstantin Ryabitsev

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210629195957.GA12571@dcvr \ \ \ \
    --subject='Re: Recording archiver origins in git' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this inbox:

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).