From: wkt@tuhs.org (Warren Toomey)
Subject: [TUHS] Reorganising the Unix Archive?
Date: Sat, 18 Feb 2017 11:09:40 +1000 [thread overview]
Message-ID: <20170218010940.GA24036@minnie.tuhs.org> (raw)
In-Reply-To: <CAC20D2O7FWLZe9XvB+h3Zo2_jE6ui7Xso4gGyKpB6Q3Cze70gQ@mail.gmail.com>
On Fri, Feb 17, 2017 at 07:40:16PM -0500, Clem Cole wrote:
> Sounds good, although I might offer one slight twist. I think
> organizations should be the higher bit not systems, doc etc....
I'll disagree, mainly because of what we have currently in terms of
applications and documentation.
At present, in these categories we have:
- Circuit_Design Festoon Portable_CC Shoppa_Tapes Usenix_77
Early_C_Compilers Macro-11 README Software_Tools Algol68
Em_Editor OpenLook Ritter_Vi Spencer_Tapes
- AUUGN Books Emails OralHistory PUPS Papers TUHS Unix_Review
- various system setup docs
Except for the last category, all the existing applications and documentation
are not easily classifiable into <organisation>. So I think it would be
better to have a generic top-level Applications and Documentation directories.
We can move the system setup docs into specific system areas.
I don't mind having <organisation> top-level directories, but I fear that
in the long term there will be lots of them. So it's a question: do we clutter
up the top level with a heap of <organisation> directories, or do we
have a heap of Systems/<organisation> directories. I'd prefer the latter.
> I also feel that Year of Distribution probably needs to be in the
> name if possible (certainly in metadata or at least an explanatory
> README). For things like the USENIX tapes that's easier - because they
> were done by year.
My preference is to keep date details in metadata and not in directory names.
There will be some things which are hard to date or whose date is in dispute,
and there may be things which are aggregates of work done over several years.
But I'll admit that there is not enough metadata and little consistency in
the metadata (e.g. Readme files) that are currently in the Archive.
Cheers & thanks for the feedback, Warren
next prev parent reply other threads:[~2017-02-18 1:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-18 0:12 Warren Toomey
2017-02-18 0:21 ` Warren Toomey
2017-02-18 0:40 ` Clem Cole
2017-02-18 1:09 ` Warren Toomey [this message]
2017-02-18 17:17 ` Random832
2017-02-18 3:30 Doug McIlroy
2017-02-18 4:40 ` Warren Toomey
2017-02-18 17:19 ` Random832
2017-02-18 18:49 Doug McIlroy
2017-02-19 0:12 Doug McIlroy
2017-02-20 1:48 ` William Corcoran
2017-02-20 2:33 ` Doug McIlroy
2017-02-20 2:52 ` Larry McVoy
2017-02-20 18:06 ` Joerg Schilling
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=20170218010940.GA24036@minnie.tuhs.org \
--to=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).