The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: grog@lemis.com (Greg 'groggy' Lehey)
Subject: [TUHS] Wikipedia for Unix?
Date: Sat, 6 Jun 2009 13:12:27 +1000	[thread overview]
Message-ID: <20090606031227.GC13220@dereel.lemis.com> (raw)
In-Reply-To: <20090605233040.GA35610@minnie.tuhs.org>

On Saturday,  6 June 2009 at  9:30:40 +1000, Warren Toomey wrote:
> On Fri, Jun 05, 2009 at 02:40:00PM -0400, Jason Stevens wrote:
>> I don't know I may be just dreaming in the sense I figure I'd probably
>> end up with something just as empty, but would people be willing to
>> put forth some kind of wiki of antidotes of their usage of various
>> Unix on platforms?
>
> Jason's e-mail gave me an idea. There's a website somewhere where some
> of the Mac developers captured anecdotes of the development of the Mac.
> How about a wiki-like website for Unix, which is a combination of an
> anecdote Wiki and a Wikipedia-for-Unix?

This is an excellent idea.  Count me in, and count a vote for
Mediawiki while you're at it.

> I'd suggest that editing isn't open to the general public, but
> either by invitation or vetting. A group of people would be needed
> to watch out for seriously bad articles/editing. At the same time,
> Unix history has been very diverse and there has always been lots of
> opposing sub-groups, so the site would need to be able to capture &
> deal with this diversity, as would the people overseeing the site.

I'm in two minds about this.  On the one hand, it makes perfect sense.
On the other, part of the advantage of things like Wikipedia is that
everything's in one place.  I honestly don't see the TUHS people being
active enough to produce anywhere like as much material as is already
present on Wikipedia.

Wikipedia has various "projects" which concern themselves with certain
subtopics (or they had them; looking at various pages, I can no longer
see any hints).  Does anybody know more details?  If we could find a
way to get a few knowledgeable, active people to ensure the
consistency and accuracy of UNIX-related articles, that could be a
better approach.

Greg
--
Finger grog at FreeBSD.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft MUA reports
problems, please read http://tinyurl.com/broken-mua
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20090606/2304bd97/attachment.sig>


  parent reply	other threads:[~2009-06-06  3:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-05  3:48 [TUHS] UNIX turns forty Brian S Walden
2009-06-05  4:18 ` Larry McVoy
2009-06-05 11:42   ` Jim Capp
2009-06-05 14:40 ` John Cowan
2009-06-05 16:06   ` Ian King
2009-06-05 18:29     ` John Cowan
2009-06-06  5:20       ` Ian King
2009-06-05 18:40 ` Jason Stevens
2009-06-05 23:30   ` [TUHS] Wikipedia for Unix? Warren Toomey
2009-06-05 23:39     ` John Cowan
2009-06-06  0:17       ` Larry McVoy
2009-07-05  9:25       ` [TUHS] www.tuhs.org now a MediaWiki Warren Toomey
2009-07-05 17:28         ` Jim Capp
2009-06-05 23:50     ` [TUHS] Wikipedia for Unix? Al Kossow
2009-06-06  1:29     ` Jim Capp
2009-06-06  3:12     ` Greg 'groggy' Lehey [this message]
2009-06-06  4:11       ` John Cowan

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=20090606031227.GC13220@dereel.lemis.com \
    --to=grog@lemis.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).