From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.2 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,DKIM_VALID_EF,HTML_MESSAGE,MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: from minnie.tuhs.org (minnie.tuhs.org [IPv6:2600:3c01:e000:146::1]) by inbox.vuxu.org (Postfix) with ESMTP id 3AF2022FC2 for ; Wed, 26 Jun 2024 23:58:09 +0200 (CEST) Received: from minnie.tuhs.org (localhost [IPv6:::1]) by minnie.tuhs.org (Postfix) with ESMTP id 4837743691; Thu, 27 Jun 2024 07:58:06 +1000 (AEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tuhs.org; s=dkim; t=1719439086; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:list-id:list-help:list-owner:list-unsubscribe: list-subscribe:list-post; bh=/k9pmEyrzMbyjLhQQphyM7Ldv9zw/GTaDGhqFtgtIgk=; b=k/qzpz0szFhcdxFui/alA2Odkykj/2ysMxufNGLM/fX17cx9v7AstCjg00rYh+Pii/Y5dC WWCNvagiQXIxaRu8Lr63zCWcBotPtv98pXBLPd8gi69sraICvtARVl2G4igIrWZzr5Mzcg LvixmoovdBgC/Cz6AEhL5HLCMPYMej0= Received: from [10.10.1.45] (unknown [58.161.103.106]) by minnie.tuhs.org (Postfix) with ESMTPSA id 74B934368F for ; Thu, 27 Jun 2024 07:58:01 +1000 (AEST) Content-Type: multipart/alternative; boundary="------------Xh0n5ESjk3UkN5RD6BzW1OBl" Message-ID: Date: Thu, 27 Jun 2024 07:57:58 +1000 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: tuhs@tuhs.org References: <43c3bd5e-b0cf-42ed-a9b3-0c222f801a75@guertin.net> <7wikxwb6zl.fsf@junk.nocrew.org> <3d1cbccf-e4c5-47bb-8ad9-81079b53d9b0@gmail.com> Content-Language: en-US In-Reply-To: <3d1cbccf-e4c5-47bb-8ad9-81079b53d9b0@gmail.com> Message-ID-Hash: C5RQOJFVD72Y5W6WB5CXMT5R7QFNXNE7 X-Message-ID-Hash: C5RQOJFVD72Y5W6WB5CXMT5R7QFNXNE7 X-MailFrom: wkt@tuhs.org X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.6b1 Precedence: list Subject: [TUHS] Re: Planning for the future List-Id: The Unix Heritage Society mailing list Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: From: Warren Toomey via TUHS Reply-To: Warren Toomey This is a multi-part message in MIME format. --------------Xh0n5ESjk3UkN5RD6BzW1OBl Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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. --------------Xh0n5ESjk3UkN5RD6BzW1OBl Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit
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.

--------------Xh0n5ESjk3UkN5RD6BzW1OBl--