Re: [Tools-implementation] Organization of the mail archives

[Ryan Cross <[e-mail]>]

Inline

> On Sep 15, 2020, at 9:58 AM, Robert Sparks <[e-mail]> wrote:
> 
> Continuing this in the context of today's conversation.
> 
> After the cleanup described below, we are/will-be left with:
> 
> 
> /a/mailarch/data/archive as the _authoritative_ store. 
> 
> /a/mailarch/data/mbox_archive/public as an automatically generated set of mbox files generated from the authoritative store. 
> 
> Should we plan to move the first to be under /doc and the second to be under /derived?
> 
> 
Do you mean

/a/mailarch/data/doc/[list name]

/a/mailarch/data/derived/[list name]

Or something else?
> RjS
> 
> 
> 
> -------- Forwarded Message --------
> Subject:	Organization of the mail archives
> Date:	Tue, 1 Sep 2020 12:30:56 -0500
> From:	Robert Sparks <[e-mail]> <mailto:[e-mail]>
> To:	Ryan Cross <[e-mail]> <mailto:[e-mail]>, [e-mail] <mailto:[e-mail]> <[e-mail]> <mailto:[e-mail]>
> 
> After consulting with Ryan, I propose this disposition for the following email archive related directories:
> 
> 
>>> Legacy Mailarchive /a/ietf A few very old mail archive scripts
> This can simply be removed. The scripts are no longer used.
>>> Email Mailarchive /a/isode ISODE IMAP server data store
>>> Email Mailarchive /a/mailarch Mail Archive operations
> 
> These should stay where they are.
> 
> /a/mailarch/data/archive is the _authoritative_ store.
> 
> /a/mailarch/data/mbox_archive/public is an automatically generated set of mbox files generated from the authoritative store. That should be used to replace several things below.
> 
>>> Email Mailman /a/mailman Mailman operations
> That has to remain (though we should consider what to do with it when we bring in Mailman3
>>> Email Mailman /a/mailman/archives Mailman Legacy Archives
> This has to remain - it is where mailman's internal archiving takes place - any lists using pipermail are kept here, so Legacy isn't really accurate above
>>> 
>>> Email Postfix /a/postfix Postfix operations
> This remains
>>> FTP FTP/Website combined /a/www/ietf-ftp/concluded-wg-ietf-mail-archive ftp, rsync none NOT exposed by http
>>> 
> These have all been imported, and are served through the mailarchive. These should be stashed. I personally don't think we should serve them in any way since they are available through the mailarchive. If they are served, they should clearly be in something I'd like to start calling the "museum".
>> 
>>> FTP FTP/Website combined /a/www/ietf-ftp/ietf-mail-archive Contains text versions of mail archive ftp, rsync night-runner All web access is to the /a/www/ietf-mail-archive tree, which this is a copy of
> This should go away as soon as ftp stops depending on it (and we had another conversation about removing it already).
>>> Email Mailarchive /a/www/ietf-mail-archive Legacy mail archive
>>> Email Mailarchive /a/www/ietf-mail-archive/text
>>> Email Mailarchive /a/www/ietf-mail-archive/text-secure
>>> Email Mailarchive /a/www/ietf-mail-archive/web
>>> Email Mailarchive /a/www/ietf-mail-archive/web-old
>>> Email Mailarchive /a/www/ietf-mail-archive/web-secure
>>> 
>>> Again, has all of that been imported, and can all of this simply be removed (or stashed offline)?
> All of this should be stashed. Everything here, with the possible exception of things in web-old have been imported into mailarchive. Ryan is looking at making sure those get imported. Once that's done, all of these should either be taken offline or put in the museum.
> 
> Are there any other puddles of email-archive related things that aren't in those directories?
>