<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 6/26/24 4:57 PM, Warren Toomey via
TUHS wrote:<br>
</div>
<blockquote type="cite"
cite="mid:abdd62c3-9611-42eb-85ab-cda386ef2e80@tuhs.org">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<p><font face="Helvetica, Arial, sans-serif">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.</font></p>
<p><font face="Helvetica, Arial, sans-serif">The "assets" are
nearly all publicly available. The Unix archive can be easily
copied: see the end of <a class="moz-txt-link-freetext"
href="https://wiki.tuhs.org/doku.php?id=source:unix_archive"
moz-do-not-send="true">https://wiki.tuhs.org/doku.php?id=source:unix_archive</a></font></p>
<p><font face="Helvetica, Arial, sans-serif">The mailing list
contents can be downloaded from here as Zip files: <a
class="moz-txt-link-freetext"
href="https://www.tuhs.org/pipermail/tuhs/"
moz-do-not-send="true">https://www.tuhs.org/pipermail/tuhs/</a></font></p>
<p><font face="Helvetica, Arial, sans-serif">The actual list of
people on the list isn't available, although the TUHS team
could easily get a copy.</font></p>
<p><font face="Helvetica, Arial, sans-serif">The "tuhs.org" domain
I have registered until May 2030.</font></p>
<p><font face="Helvetica, Arial, sans-serif">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.</font></p>
<p><font face="Helvetica, Arial, sans-serif">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 :-)</font></p>
<p><font face="Helvetica, Arial, sans-serif">Cheers, Warren</font></p>
<p><font face="Helvetica, Arial, sans-serif">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.<br>
</font></p>
</blockquote>
<font face="Helvetica, Arial, sans-serif">Hi Warren,<br>
<br>
I didn't realize it was so easily mirrored. The instructions are
super clear and effective. This all sounds like a good approach to
providing for continuity over the long haul, even if it's not
super formal. <br>
<br>
It's interesting the perspectives gathering here - for some, it's
like a chat room to reminisce. For others, it's an information
source. For a few, it's a living history. What may not be apparent
to some of the folks who lived the history is that it is a fragile
thread and those who experienced its genesis firsthand are a
rapidly shrinking population. If we've seen misinformation
creeping into discussions of late, it's only going to get much
worse over the years. Particularly if we don't capture more of the
real story and keep that alive. TUHS is a great resource for folks
to turn to when they want to dig deeper into the origins of UNIX
or to learn more about the motivations for early decisions that
charted the course of it's descendants. The transition from
research unix to commercial and open source is becoming history
that fewer and fewer folks really know much about. All this to
say, TUHS is more than a chat platform for reminiscing and
clarifications of the record - it's a historical record of
important conversations that should be preserved and protected :).
<br>
<br>
Thanks,<br>
<br>
Will<br>
<br>
Thanks for the details!<br>
<br>
Will<br>
<br>
<br>
</font>
</body>
</html>