The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: [TUHS] What UNIX Artifacts Are Still Missing?
Date: Thu,  7 Dec 2017 10:14:20 -0500 (EST)	[thread overview]
Message-ID: <20171207151420.3DB5D18C09E@mercury.lcs.mit.edu> (raw)

    > From: Larry McVoy

    > an altruistic person trying to make things better.  They aren't all bad.

I would echo that. During my time on the IESG, I'd say the vast majority of
the people in the IETF really did want to make things better for everyone.

Of course, that statement covers a vast range of subtle variations, from
people who had nothing at all to gain personally, and thus really were pushing
what they thought was best; through people who did stand to gain, but truly
thought that what they were advocating was in everyone's interest; etc.

But the people who I felt were deliberately and knowingly putting their own
interests before the community's, i.e. recommending something they knew to be
harmful because it was good for them - they were very rare.

My recollection is now somewhat dim (too much was happening, at too high a
pace) of the details of those later days (well, 'later' only in that they were
considerably later than the very early days :-), but my sense is that people
like that didn't last long in the community; I have the distinct impression
that people figured them out, and as an eventual result, they tended to fade
from the scene. The IETF culture was not welcoming to that kind of thinking.

I dunno, maybe I'm just being naive (and I would certainly welcome correction
if I'm wrong), but that's how I saw it.

   Noel


             reply	other threads:[~2017-12-07 15:14 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-07 15:14 Noel Chiappa [this message]
2017-12-07 15:36 ` Nevin Liber
  -- strict thread matches above, loose matches on Subject: below --
2017-12-06 17:59 Rudi Blom
     [not found] <mailman.400.1512518427.9955.tuhs@minnie.tuhs.org>
2017-12-06 11:25 ` Paul Ruizendaal
2017-12-06 12:58   ` Mutiny 
2017-12-06 14:33     ` Paul Ruizendaal
2017-12-06 17:13       ` Clem Cole
2017-12-06 19:27         ` Paul Ruizendaal
2017-12-07  6:14         ` Jason Stevens
2017-12-06 22:32       ` Dave Horsfall
2017-12-07  5:05         ` Jason Stevens
2017-12-07  5:46           ` Dave Horsfall
2017-12-07  5:40         ` Andy Kosela
2017-12-07  5:56         ` Robert Brockway
2017-12-07  6:07           ` Warner Losh
2017-12-07 17:47             ` Grant Taylor
2017-12-09  6:03               ` Nigel Williams
2017-12-07  6:14           ` Jon Steinhart
2017-12-07  7:02             ` Robert Brockway
2017-12-07 16:22               ` Jon Steinhart
2017-12-07 14:59             ` Larry McVoy
2017-12-07 15:40               ` Steve Simon
2017-12-07 15:42               ` Chet Ramey
2017-12-07 16:28             ` Clem Cole
2017-12-07 16:30               ` Clem Cole
2017-12-06 17:55   ` Warner Losh
     [not found] <mailman.398.1512513526.9955.tuhs@minnie.tuhs.org>
2017-12-06 11:22 ` Paul Ruizendaal
2017-12-05 22:45 Nelson H. F. Beebe
2017-12-05 22:21 Warren Toomey
2017-12-05 22:38 ` Robert Swierczek
2017-12-05 22:55 ` Angelo Papenhoff
2017-12-05 23:06   ` Warner Losh
2017-12-05 23:03 ` Dave Horsfall
2017-12-06  0:00 ` Robert Swierczek
2017-12-06  0:08   ` Grant Taylor
2017-12-06 15:23   ` Clem Cole
2017-12-06  5:54 ` arnold

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=20171207151420.3DB5D18C09E@mercury.lcs.mit.edu \
    --to=jnc@mercury.lcs.mit.edu \
    /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).