From: Warren Toomey via TUHS <tuhs@tuhs.org>
To: tuhs@tuhs.org
Subject: [TUHS] Re: Planning for the future
Date: Thu, 27 Jun 2024 07:57:58 +1000 [thread overview]
Message-ID: <abdd62c3-9611-42eb-85ab-cda386ef2e80@tuhs.org> (raw)
In-Reply-To: <3d1cbccf-e4c5-47bb-8ad9-81079b53d9b0@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1524 bytes --]
On 27/6/24 00:30, Will Senn wrote:
>
> Which brings me to my topic - how is TUHS set up for the future?
> Is TUHS set up in such a way as to weather the sands of time or do we
> need to do something to ensure its sustainability (similarly
> bitsavers/gunkies/beebe's bib/etc).
>
Good question. There isn't a real succession plan. We do have a handful
of people behind the scenes (the TUHS team) who have access to the
server and who could take over the care and feeding if required. The
regular operations are mostly documented but, as always, could be
improved upon.
The "assets" are nearly all publicly available. The Unix archive can be
easily copied: see the end of
https://wiki.tuhs.org/doku.php?id=source:unix_archive
The mailing list contents can be downloaded from here as Zip files:
https://www.tuhs.org/pipermail/tuhs/
The actual list of people on the list isn't available, although the TUHS
team could easily get a copy.
The "tuhs.org" domain I have registered until May 2030.
What I should probably do is to ask one of the TUHS team to volunteer to
a) put their credit card up as a secondary for my cloud provider in case
my card stops working and b) give them access to the cloud provider so
they can make their card the primary one.
I did try to float the idea of a more formalised TUHS structure a while
back but there was not much enthusiasm at the time :-)
Cheers, Warren
P.S. And I should set up a "dead man's hand" script to tell the list if
I have been 'inactive' for a few weeks.
[-- Attachment #2: Type: text/html, Size: 2804 bytes --]
next prev parent reply other threads:[~2024-06-26 21:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 18:17 [TUHS] Sad but not unexpected news about the LCM-L Clem Cole
2024-06-26 0:56 ` [TUHS] " Aron Insinga
2024-06-26 1:29 ` Larry McVoy
2024-06-26 3:34 ` [TUHS] Re: Trust stuff, " John Levine
2024-06-26 9:22 ` [TUHS] Wills. (Was: Sad but not unexpected news about the LCM-L) Ralph Corderoy
2024-06-26 1:42 ` [TUHS] Re: Sad but not unexpected news about the LCM-L George Michaelson
2024-06-26 17:22 ` aki
2024-06-26 1:44 ` Paul Guertin
2024-06-26 1:46 ` Dan Cross
2024-06-26 2:46 ` Paul Guertin
2024-06-26 5:36 ` Lars Brinkhoff
2024-06-26 14:30 ` [TUHS] Planning for the future was " Will Senn
2024-06-26 15:18 ` [TUHS] " Al Kossow
2024-06-26 21:57 ` Warren Toomey via TUHS [this message]
2024-06-30 13:05 ` [TUHS] Re: Planning for the future Will Senn
2024-06-26 16:56 ` [TUHS] Re: Sad but not unexpected news about the LCM-L aki
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=abdd62c3-9611-42eb-85ab-cda386ef2e80@tuhs.org \
--to=tuhs@tuhs.org \
--cc=wkt@tuhs.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;
as well as URLs for NNTP newsgroup(s).