From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, HTML_FONT_LOW_CONTRAST,HTML_MESSAGE,MAILING_LIST_MULTI, RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 6249 invoked from network); 5 Apr 2021 19:31:59 -0000 Received: from minnie.tuhs.org (45.79.103.53) by inbox.vuxu.org with ESMTPUTF8; 5 Apr 2021 19:31:59 -0000 Received: by minnie.tuhs.org (Postfix, from userid 112) id C198D9CA99; Tue, 6 Apr 2021 05:31:58 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id DD8D29C883; Tue, 6 Apr 2021 05:30:58 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=fail reason="signature verification failed" (1024-bit key; unprotected) header.d=ccc.com header.i=@ccc.com header.b="an5SL8YW"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id 486F19C883; Tue, 6 Apr 2021 05:30:54 +1000 (AEST) Received: from mail-qv1-f53.google.com (mail-qv1-f53.google.com [209.85.219.53]) by minnie.tuhs.org (Postfix) with ESMTPS id CAFFE9C83D for ; Tue, 6 Apr 2021 05:30:52 +1000 (AEST) Received: by mail-qv1-f53.google.com with SMTP id x16so5960145qvk.3 for ; Mon, 05 Apr 2021 12:30:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ccc.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=7g3/9KxPOfrhaks7Mkc056dCBMbAGOt3padZMtTeVDY=; b=an5SL8YWrxns0Ga9q/+702Xj6sm8uT9cN4gud8/+m2vTWtwB7rgy6B7Pvrceab7zoC r+Ak2MpUWOhAqJUrXYZCNCHfibqOGNaBkVJZ6oQizju7uGPYAKgXT1arihtgGr3ceTzK 4Siz4uIelG2wcG3+cSzQvnZEszcy/bueqegNA= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=7g3/9KxPOfrhaks7Mkc056dCBMbAGOt3padZMtTeVDY=; b=Y+ksg9/Y/TiTjYwGCZEs+I/RimSoX47Jgn3vLEwA8mKFfu3QyXpMP4bxcoiwLHPNUI +k/diOb0oqKMLxli+gakqRuiO9kIqUSbh8kg2YWpWDm/Lx32keGZv/Pepqb8RuVHKdeU b4DFXdKyCQt2sSzmUI0WYqgNCreasBDAxp1p01dBjSbbE1S3CrIh3lT+D9xA1sOZbiQj nHHXMRSAKUMNnxtl9E8I1o6A6nNSuo5MQNqRsJfjYivxZUD8Jgpkj5BpF/qR+1+7cdFn CUog0+wn02E3xhFVUOA6g1gaEOPCx3uxG27eD5T9qDa+OFSv8agj2CTGA//mqXPOxqkb 1OYA== X-Gm-Message-State: AOAM533Da25v0PfmOSoSCYwgXqQBKDithxIhxHnRZ6jS+9Yeza0u7kng O7nCpTmKMjmidQ+T3mBLKSAIWWE7dV8oDS/9g41F1A== X-Google-Smtp-Source: ABdhPJxcUgTX9weTma+EcqILt6azsWiU1HUwixweQrSzgfkLRcep3rKYd2jd+Pgbck1Got2A6JrWo3L4iOugLpjBccI= X-Received: by 2002:a05:6214:1633:: with SMTP id e19mr8927244qvw.3.1617651051543; Mon, 05 Apr 2021 12:30:51 -0700 (PDT) MIME-Version: 1.0 References: <20210401145025.GA1202@naleco.com> <20210404052939.xivuinlcugqb5zde@localhost.localdomain> <19643.1617646039@hop.toad.com> In-Reply-To: <19643.1617646039@hop.toad.com> From: Clem Cole Date: Mon, 5 Apr 2021 15:30:25 -0400 Message-ID: To: John Gilmore Content-Type: multipart/alternative; boundary="0000000000004c4ee205bf3ebc28" Subject: Re: [TUHS] How to Kill a Technical Conference X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: TUHS main list Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" --0000000000004c4ee205bf3ebc28 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Apr 5, 2021 at 2:08 PM John Gilmore wrote: > The paper was rejected by the program committee, on the objection that > "ports aren't research". So > the pro-academic, anti-engineering mindset was already in place back then= . > John - to be honest, I think the attempt to make the standard for paper acceptance had started before 1988. I was on PCs in the early 1983s and pressure was already on the PCs (and authors) to use 'academic standards'. I think Ted described the issue well. The fact is a paper like the one you describe, I do think would not have been as interesting to some (maybe even many) in the USENIX audience, although I clearly agree with you that it would have been for others. The problem was that paper like that was not going to help people that were working on a tenure file and the PCs wanted to fil the sessions with them. To USENIX's credit, by the mid to late the 1980s, a USENIX was considered by many academic committees. The issue for the USENIX BOD had always been getting butts in the seats to pay the bills. Academics had a path, so following what IEEE and ACM did was well-trod and understood. Get the more pure hackers like yourself, even the engineers inside of places like Sun or Masscomp was often difficult and we know was not well understood. USENIX was hardly the only firm/org that made some bets in those days that in the long run might not have been the best. As Ted referred, at the time a compromise was created. First, LISA became the primary sys admin conferences and was and still is successful. It has always had a good mix of both practice and academic papers. As Ted, pointed out things like FREENIX, USELINUX, ALS, and the like were created with a different set of requirements. In the end, conferences like these three fell out of favor. As someone that lived it at the time and argued to try to keep/invest in them, I personally think there was more a crash of personality as much as anything else. They were a lot more work for the USENIX staff to produce and that did not help the argument. And in 1988, USENIX itself had the gold as UNIX and the UNIX marketplace was at its height. I suspect some bad behavior did come through that favored one view over another. I personally think the org did attempt to do better in serving this population, but ultimately did not do as well as many people would have liked. As more and, more $s in the market moved into the FOSS community and away from what was then called the OpenSystems community, it allowed the folks in FOSS like yourself to be served by others than USENIX. IMHO, USENIX walked away from a group that they should have been trying to cultivate. I'll give Mad Dog and Ted creds for at least trying to educate that BOD in those days that what was being done/not done was not going to work for that community. The problem is that what was proposed (what was needed) did not fit the model that the BOD and the then ED had in mind. Given some of the personalities, folks (on both sides) stopped trying. A big problem (IMO) was that USELINUX and FREENIX needed a conference organization model more like the Hackers Conference or AMW, ... but ... the personalities running USENIX at the time understood the traditional (more academic) scheme. It was a failure to communicate at a minimum, and certainly had large portions of a control problem. So where we are today is that the freshwater is long since over the dam, and by now well mixed into the salted ocean. Replaying the acts and complaining of what should have happened is not going to help here. Unfortunately, it is true that the actions of some people in those days bruised some egos, and feelings were hurt. I wish that were not true, but I know it happened. The key for all of us, in this list and else where in the reset of the UNIX industry is to try to avoid rewriting history, but to understand what went down and accept it, and move on. =E1=90=A7 --0000000000004c4ee205bf3ebc28 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Mon, Apr 5, 2021 at 2:08 = PM John Gilmore <gnu@toad.com> wr= ote:
The paper w= as rejected by the program committee, on the objection that &quo= t;ports aren't research".=C2=A0 So
the pro-academic, anti-engineering mindset was already in place back then.
John - to be honest, I think the attemp= t to make the standard for paper acceptance had started before 1988.=C2=A0 = I was on PCs in the early 1983s and pressure was already on the=C2=A0PCs (a= nd authors) to use 'academic standards'.=C2=A0 I think Ted describe= d the issue well.=C2=A0 =C2=A0 The fact is a paper like the one you describ= e, I do think=C2=A0would not have been as interesting to some (maybe even m= any) in the USENIX audience, although I clearly agree with you that it woul= d have been for others.=C2=A0 The problem was that paper like that was not = going to help people that were working on a tenure file and the PCs wanted = to fil the sessions with them.=C2=A0 To USENIX's credit, by the mid to = late the 1980s, a USENIX was considered by many academic=C2=A0committees.

The issue for the USENIX BOD = had always been getting butts in the seats to pay the bills.=C2=A0 =C2=A0Ac= ademics had a path, so following what IEEE and ACM did was well-trod and un= derstood.=C2=A0 =C2=A0 Get the more pure hackers like yourself, even the en= gineers inside of places like Sun or Masscomp was often difficult and we kn= ow was not well understood.=C2=A0 USENIX was hardly the only firm/org that = made=C2=A0some bets in those days that in the long=C2=A0run might not have = been the best.

As Ted referr= ed, at the time a compromise was created.=C2=A0 =C2=A0First, LISA became th= e primary sys admin=C2=A0conferences and was and still is successful.=C2=A0= It has always had a good mix of both practice and academic papers.=C2=A0 A= s Ted, pointed out things like FREENIX, USELINUX, ALS, and the like were cr= eated with a different set of requirements.=C2=A0=C2=A0In the end, conferences like these three=C2=A0fell out of favor. = As someone that lived it at the time and argued to try to keep/i= nvest in them, I personally think there was more a crash of personal= ity as much as anything else.=C2=A0 They=C2= =A0were a lot more work for the USENIX staff to produce and that did not he= lp the argument.=C2=A0 =C2=A0And in 19= 88, USENIX itself had=C2=A0the gold as UNIX and the UNIX marketplace was at i= ts height.=C2=A0 I suspect some bad behavior did come through that f= avored=C2=A0one view over another.=C2= =A0 =C2=A0I personally think the org d= id attempt to do better in serving this popul= ation, but ultimately did not do as well as many people w= ould have liked.=C2=A0 As more and, more $s i= n the market moved into the FOSS community and away from what was then call= ed the OpenSystems community, it allowed the folks in FOSS like yourself to= be served by others than USENIX.=C2=A0 IMHO, USENIX walked away from a gro= up that they should have been trying to cultivate.
=
I&#= 39;ll give Mad Dog and Ted creds for at least trying to educate that BOD in= those days that what was being done/not done was not going to work for tha= t community.=C2=A0 The problem is that what was proposed (what was needed) = did not fit the model that the BOD and the then ED had in mind.=C2=A0 Given= some of the personalities, folks (on both sides) stopped trying.=C2=A0 A b= ig problem (IMO) was that USELINUX and FREENIX=C2=A0needed a conference org= anization model more like the Hackers Conference or AMW, ... but ... the pe= rsonalities running USENIX at the time understood the traditional (more aca= demic) scheme.=C2=A0 =C2=A0It was a failure to communicate at a minimum, an= d certainly had large portions of a control problem.

<= span class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-seri= f">So where we are today is that=C2=A0the freshwater is long since over the= dam, and by now well mixed into the salted ocean.=C2=A0 Replaying the acts= and complaining of what should have happened is not going to help here.=C2= =A0 Unfortunately, it is true that the actions of some people in those days= bruised some egos, and feelings were hurt.=C2=A0 I wish that were not true= , but I know it happened.=C2=A0 The key for=C2=A0all of us, in this list an= d else where in the reset of the UNIX industry is to try to avoid rewriting= history, but to understand what went down and accept it, and move on.
3D""=E1=90=A7
--0000000000004c4ee205bf3ebc28--