The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: scj@yaccman.com (scj@yaccman.com)
Subject: [TUHS] A repository with 44 years of Unix evolution gets the MSR '15 Best Data Showcase Award
Date: Thu, 21 May 2015 12:54:06 -0700	[thread overview]
Message-ID: <f0b9d6259465611cc4b3a0e6730da45b.squirrel@webmail.yaccman.com> (raw)
In-Reply-To: <555A4699.5060107@aueb.gr>

My contribution to the author attribution is to point out that, at least
in the Research Bell Labs days, there was a unique but very effective
rule--if you touch it, you own it!  People were encouraged to hack the
code rather than complain to the previous authors.  But when they did,
they owned the result, bugs and all.

For example, I invented the first "at" command.  My contribution was
primarily the name and some of the syntax.  My implementation was as a
shell script, which absolutely revolted Dennis.  Within a couple of days
he had replaced it with a jewel that not only ran the command at the
correct time, but from the correct directory and with the correct
permissions.  I never touched it again...

I've never again worked with a group that took such an approach to
ownership, and I have frequently missed it...

Steve

> The most useful
> community contribution would be to increase the coverage of imported
> snapshot files that are attributed to a specific author. Currently,
> about 90 thousand files (out of a total of 160 thousand) are getting
> assigned an author through a default rule. Similarly, there are about
> 250 authors (primarily early FreeBSD ones) for which only the identifier
> is known. Both are listed in the build repository's unmatched directory
> [6], and contributions are welcomed (start with early editions; I can
> propagate from there). Most importantly, more branches of open source
> systems can be added, such as NetBSD OpenBSD, DragonFlyBSD, and illumos.
> Ideally, current right holders of other important historical Unix
> releases, such as System III, System V, NeXTSTEP, and SunOS, will
> release their systems under a license that would allow their
> incorporation into this repository.  If you know people who can help in
> this, please nudge them.
>
> --Diomidis
>





  parent reply	other threads:[~2015-05-21 19:54 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-18 20:07 Diomidis Spinellis
2015-05-19  9:24 ` Tom Ivar Helbekkmo
2015-05-19 10:04   ` Erik E. Fair
2015-05-19 13:19     ` Jacob Goense
2015-05-19 13:48       ` Steffen Nurpmeso
2015-05-19 14:36         ` SPC
2015-05-19 15:55   ` Warner Losh
2015-05-19 16:48     ` Tom Ivar Helbekkmo
2015-05-19 17:30       ` Clem Cole
2015-05-19 18:06         ` Tom Ivar Helbekkmo
2015-05-19 18:55         ` cowan
2015-05-20  3:07           ` Andy Kosela
2015-05-19 14:53 ` Clem Cole
2015-05-21  1:42 ` Derrik Walker v2.0
2015-05-21 11:50   ` Diomidis Spinellis
2015-05-21 15:09     ` cowan
2015-05-21 15:49       ` Clem Cole
2015-05-21 17:03         ` Jacob Ritorto
2015-05-21 18:04           ` Clem Cole
2015-05-25 16:46             ` Mary Ann Horton
2015-05-25 17:21               ` John Cowan
2015-05-25 21:15               ` Cory Smelosky
2015-05-26 17:55               ` Scot Jenkins
2015-05-29 14:14                 ` Mary Ann Horton
2015-05-22  0:17         ` John Cowan
2015-05-26 19:12   ` Doug McIntyre
2015-05-21 19:54 ` scj [this message]
2015-05-19 15:40 Doug McIlroy
2015-05-19 16:26 ` cowan
2015-05-19 17:29   ` Doug McIlroy
2015-05-21 19:41     ` scj
2015-05-25 19:05 Noel Chiappa
2015-05-26 10:07 Berny Goodheart

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=f0b9d6259465611cc4b3a0e6730da45b.squirrel@webmail.yaccman.com \
    --to=scj@yaccman.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).