The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: segaloco via TUHS <tuhs@tuhs.org>
To: Joseph Holsten <joseph@josephholsten.com>
Cc: Tautological Eunuch Horticultural Scythians <tuhs@tuhs.org>
Subject: [TUHS] Re: Collecting notes for future “historians” was: Earliest UNIX Workstations?
Date: Fri, 27 Jan 2023 00:34:48 +0000	[thread overview]
Message-ID: <wzLILyoOAS7e8Tp7ahmcvzTM4lmxeOTgkIFxngKLgEuuYXCgwgd3cY4iGVVShrXaHPFu3aJtl_tPlJmzJggwBTQkwYruJNULuzwTxxUG9Do=@protonmail.com> (raw)
In-Reply-To: <620c709c-e8bb-401c-a60d-8869457caacd@app.fastmail.com>

> Ah, I meant to ask: is there an existing wiki or repository? Or am I starting one?

https://wiki.tuhs.org/

I've discussed writing a few articles with Warren and it sounds like he's all for more folks producing content.  Ultimately it's Warren's call on that one, but I'm very interested in starting to produce some content.

> An appropriate way for us to do this sort of thing would be to create
> a repository where we can contribute to documents written in troff.

I've considered this exact thing save not for this project, but just as a way to approach collaborative writing.  I wouldn't have the attention span to admin such a repository, but would more than happily contribute to one, I love exposition and free access to knowledge.

- Matt G.

  reply	other threads:[~2023-01-27  0:35 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-26  0:31 [TUHS] " Joseph Holsten
2023-01-26  0:51 ` [TUHS] " segaloco via TUHS
2023-01-26  1:06   ` Luther Johnson
2023-01-26  1:15     ` Jon Steinhart
2023-01-26  1:01 ` Larry Stewart
2023-01-26 13:25   ` Marc Donner
2023-01-26 13:58     ` arnold
2023-01-31  2:03   ` Mary Ann Horton
2023-01-31 17:43     ` Marc Donner
2023-01-26  1:12 ` Tom Lyon
2023-01-26  1:47 ` Chris Hanson
2023-01-26  7:20   ` John Cowan
2023-01-26  7:33     ` Dave Horsfall
     [not found]     ` <CAD2gp_QtUPmd78yAixvKK1wzPX67HKZXzU5cJnVUbcWtMounGQ@mail.g mail.com>
2023-01-26 16:35       ` John Foust via TUHS
2023-01-26 17:58     ` Jon Forrest
2023-01-26 18:04     ` Jon Steinhart
2023-01-26 21:29       ` [TUHS] Collecting notes for future “historians” was: " Joseph Holsten
2023-01-26 21:38         ` [TUHS] " Jon Steinhart
2023-01-26 22:41           ` Joseph Holsten
2023-01-27  0:34             ` segaloco via TUHS [this message]
2023-01-27  0:36             ` G. Branden Robinson
2023-01-27  0:53               ` segaloco via TUHS
2023-01-27  1:28                 ` David Arnold
2023-01-27  1:35                   ` Warner Losh
2023-01-26  9:52 ` [TUHS] " emanuel stiebler
2023-01-26  9:58   ` Rob Pike
2023-01-26 10:09   ` Jaap Akkerhuis via TUHS
2023-01-26 15:14 ` Clem Cole
2023-01-28 21:16 [TUHS] Re: Collecting notes for future “historians” was: " Douglas McIlroy
2023-01-30  6:13 ` Phil Budne

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='wzLILyoOAS7e8Tp7ahmcvzTM4lmxeOTgkIFxngKLgEuuYXCgwgd3cY4iGVVShrXaHPFu3aJtl_tPlJmzJggwBTQkwYruJNULuzwTxxUG9Do=@protonmail.com' \
    --to=tuhs@tuhs.org \
    --cc=joseph@josephholsten.com \
    --cc=segaloco@protonmail.com \
    /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).