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=-0.5 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: from minnie.tuhs.org (minnie.tuhs.org [50.116.15.146]) by inbox.vuxu.org (Postfix) with ESMTP id BF595236D2 for ; Sun, 30 Jun 2024 15:06:08 +0200 (CEST) Received: from minnie.tuhs.org (localhost [IPv6:::1]) by minnie.tuhs.org (Postfix) with ESMTP id 943A5436CD; Sun, 30 Jun 2024 23:06:02 +1000 (AEST) Received: from mail-oa1-x30.google.com (mail-oa1-x30.google.com [IPv6:2001:4860:4864:20::30]) by minnie.tuhs.org (Postfix) with ESMTPS id B1F9D436C2; Sun, 30 Jun 2024 23:05:56 +1000 (AEST) Received: by mail-oa1-x30.google.com with SMTP id 586e51a60fabf-25d5333989dso1221987fac.1; Sun, 30 Jun 2024 06:05:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1719752755; x=1720357555; darn=tuhs.org; h=in-reply-to:from:content-language:references:to:subject:user-agent :mime-version:date:message-id:from:to:cc:subject:date:message-id :reply-to; bh=ucHxDeafr3BsbXhcP0sR5E7GllcIRESTg/jBuOwEKyk=; b=YdjH4RIiO7svIZQHR8pjSULfmIzwQtmAlqa/36pTC6kE5YsEDRq5nkb2Hc+29nYehD jzsUcJaEsRvgJHdB6+CLnxwasEsPFI68bHSgWjTcuKbFSpU/fbz5WFMnfhbvEhcayj07 JpiYKQDxlIQ9rkkIY/3bjtI0X7NsrXZ5pesj643YkKGY3iPVHQ4EPNfK8k2SFXp1f+53 G1ZqH0FLOlgJ9ly5JYbjyT5Z1+3Scsec9sdrqe6hFkPlubZSSTiekE54Esy/1b1MvOo0 PHWx+N+eeEu8AJ6slYYdkqYVO6pC4ZgP0IhfcQONxwmklxTE31NSPpTh5/kizposDuRL TZsg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1719752755; x=1720357555; h=in-reply-to:from:content-language:references:to:subject:user-agent :mime-version:date:message-id:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=ucHxDeafr3BsbXhcP0sR5E7GllcIRESTg/jBuOwEKyk=; b=fxyS2Zd8KZqRpG+M7GqQZNa7ufH2PAPEyTGvgW0iEaftveJBQ9dwaFfx8DK8pQIwjk cik9u6HWNosq+nr3IACEZUHTnl5TeNLYAI7/XtjFDhZLlBhAdMB5MzJHecVtdjmM99Uq p3DFMm6Ir2DCM11YFtpmIGnLLZc8Itn7gVf/irILR/j/xrPrx4kC6EscTC1Qyh4aX4CT HCucVfJ4CS8fCFrKrd/uYktekz4uaXlfz2sELpdDP8IyC9JASwvjNIQuzOE7ak99VbG/ 2Abcp6LPxmFJGjk0c8O+U+Zn2DRgfBM5heVxZizKJs63lIeDAnLQ8eSybGyECQEDCnsf E4qQ== X-Forwarded-Encrypted: i=1; AJvYcCUGD0htwpPr630/k+dSU/hiSAeaRSDHIGxYXVatcwBqi+BrDVKjfHY+JRu8m7NGZ/cS0zNTwo0kmziiKIrh X-Gm-Message-State: AOJu0YznqHQdQpx8P/P27mrQX5UUKSNdU6qQ2bRc3J8Bdn3HkYOM51gh MaV5s8zmkSdD4cSGyoX+EUHFLLe6kcKWzq99WCTHKMyTYjLUpZWCjPS51g== X-Google-Smtp-Source: AGHT+IGJMKqhVV/XkMEH1XexUcLM3WVe5KtHYWL9DPdhn4ePa8KMr9c0GIVkETDkVQEjEYQAE4gILw== X-Received: by 2002:a05:6871:3423:b0:254:a2c2:d3c1 with SMTP id 586e51a60fabf-25db337900emr3388968fac.2.1719752754761; Sun, 30 Jun 2024 06:05:54 -0700 (PDT) Received: from [192.168.1.13] (h246.146.40.69.dynamic.ip.windstream.net. [69.40.146.246]) by smtp.gmail.com with ESMTPSA id 586e51a60fabf-25d8e33b73esm1304296fac.37.2024.06.30.06.05.53 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 30 Jun 2024 06:05:53 -0700 (PDT) Content-Type: multipart/alternative; boundary="------------qjtwGQa0zXGnLm6njckNr0fU" Message-ID: <7a561e22-30b4-4dc2-afc1-5d3e6e967d5e@gmail.com> Date: Sun, 30 Jun 2024 08:05:53 -0500 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: Warren Toomey , 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 From: Will Senn In-Reply-To: Message-ID-Hash: GBCPDADF7CJUFSIPQZAMTVOI64275G7U X-Message-ID-Hash: GBCPDADF7CJUFSIPQZAMTVOI64275G7U X-MailFrom: will.senn@gmail.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tuhs.tuhs.org-0; 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: This is a multi-part message in MIME format. --------------qjtwGQa0zXGnLm6njckNr0fU Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 6/26/24 4:57 PM, Warren Toomey via TUHS wrote: > > 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. > Hi Warren, 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. 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 :). Thanks, Will Thanks for the details! Will --------------qjtwGQa0zXGnLm6njckNr0fU Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit
On 6/26/24 4:57 PM, Warren Toomey via TUHS wrote:

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.

Hi Warren,

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.

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

Thanks,

Will

Thanks for the details!

Will


 --------------qjtwGQa0zXGnLm6njckNr0fU--