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=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HTML_MESSAGE,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 26001 invoked from network); 4 Apr 2021 18:24:00 -0000 Received: from minnie.tuhs.org (45.79.103.53) by inbox.vuxu.org with ESMTPUTF8; 4 Apr 2021 18:24:00 -0000 Received: by minnie.tuhs.org (Postfix, from userid 112) id 6C2EB9CA6C; Mon, 5 Apr 2021 04:23:59 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id B9BF19CA5C; Mon, 5 Apr 2021 04:22:53 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=pass (1024-bit key; unprotected) header.d=ccc.com header.i=@ccc.com header.b="FQgBAIT5"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id E6C759CA5C; Mon, 5 Apr 2021 04:22:50 +1000 (AEST) Received: from mail-qv1-f42.google.com (mail-qv1-f42.google.com [209.85.219.42]) by minnie.tuhs.org (Postfix) with ESMTPS id 4D8459CA5B for ; Mon, 5 Apr 2021 04:22:50 +1000 (AEST) Received: by mail-qv1-f42.google.com with SMTP id iu14so4643340qvb.4 for ; Sun, 04 Apr 2021 11:22:50 -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=c1sQKJw2yVq7xAK79Q4vfjU+HJ6czyCfDGPXLzIcAbg=; b=FQgBAIT59OLySt6OYhZt8JrgvVDPA3CYGGZG6MqQ1p6uRXGsVCF0nwo16SRXPEnFCT 2fDnidWkz7v2u5ERotu6DxEI0kGKgBi5N3OcVEzc3OrA9CKqgbBXK9A40n0GRzE1x/1/ f9dYiEeJlek16HtLPac2hxlj1/uc9HIVWvZGc= 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=c1sQKJw2yVq7xAK79Q4vfjU+HJ6czyCfDGPXLzIcAbg=; b=EJj4IU8sMTq1G+yQoUEMhcD8g+9ZwzbP5Lq2ziGW4rK77DIRjuRDXWsYELKNiDLne/ PCfYC/3PaMTnu9B0md1pmEg55+UE0g9CvSm0EWqS+LurwfqvbRERgi6gQyP9/E3ZOMZm oYjWPEWl9qEmbmW8+RSbVsPIyxC0KPAc8wpe24SwxkBDSSW8zZVcPJ5peS1dtQhtSs22 FLALpBLKFXxYQBwSdA7vKSMLEGKVlhsI7wXXglEAmxzN514sYLIT3AHgTSXD4xWjtAqb 6znCFkXdamW6wcawwpI+3bmZK+JVdYgCS7ZGMWy4B0P/ji4IhZlUvqNiZUk/CxeZbeeg IBAA== X-Gm-Message-State: AOAM530b3CvNPKK9fJ/I7sTNnDQfTXvLwqaQVog4fYg5eYIO5WQ0LWaE RJ9LS7SoW9rcnXdAfdWj5Erjh9ukU0mdHI+WtzOvNA== X-Google-Smtp-Source: ABdhPJwNIoKNqwm/2aJDIvfjCWQYxxt/lfktzSA8CwCxczDTucr3PI69jeZAgMEEhGw9QKERfetgGpsRKXgvO+DBQOc= X-Received: by 2002:a0c:b303:: with SMTP id s3mr20868250qve.22.1617560569055; Sun, 04 Apr 2021 11:22:49 -0700 (PDT) MIME-Version: 1.0 References: <20210401145025.GA1202@naleco.com> <20210404052939.xivuinlcugqb5zde@localhost.localdomain> In-Reply-To: <20210404052939.xivuinlcugqb5zde@localhost.localdomain> From: Clem Cole Date: Sun, 4 Apr 2021 14:22:22 -0400 Message-ID: To: "G. Branden Robinson" Content-Type: multipart/alternative; boundary="0000000000001f22ee05bf29ab57" Subject: Re: [TUHS] How to Kill a Technical Conference (was: Zombified SCO comes back from the dead, brings trial back to life against IBM) 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" --0000000000001f22ee05bf29ab57 Content-Type: text/plain; charset="UTF-8" Note: These are my opinions/experiences not necessarily those of the association or my employer. And, yes, I am a former BOD member as well as ex-President of same, as are a number of folks on this list. On Sun, Apr 4, 2021 at 1:30 AM G. Branden Robinson < g.branden.robinson@gmail.com> wrote: > > I'm too young to know--did USENIX follow the trajectory of reorienting > its focus from engineering and research to sales? Actually, quite the opposite, USENIX was getting more and more academic and research-oriented and less 'trade show.' The key is that USENIX and ALS should have been an excellent match, unfortunately, some of the personalities involved were at odds with each other. IMO: it was more of a crash of personalities/control issues - the details do not need to be repeated or aired again. Note: I was on the BOD at that time and in fact on the PC for that specific conference. Ted may have been on the BOD at the same time. > Why does it no longer occupy the premier place it once did? > As they say on Quora, "*never ask a question based on a false premise*." Sadly, this is a false statement. USENIX is extremely well respected in the systems research and security community in particular. And even during these Covid times has continued to have some of the premier conferences on the same; al biet virtual (more in a minute). An issue during the time you are discussing, USENIX had evolved into "two foci" between the practitioners (which included both FOSS community and LISA types) and the more academic-oriented folks looking for respected places to publish papers/develop their tenure files. USENIX had moved from its earlier (anything goes) - pure practitioner origins - which were also researchers, so at a meeting in a classroom at NYU, you told people you had something to say and came and did it, to a more structured (research) approach with program committees, submitted papers, and vetting and a hotel. Along the way, because it had both types of people and these were the folks that influenced the buying patterns, vendors started to show up to show off what they had. At the time of the ALS conference you mentioned, the things happening in the FOSS community - was much more like the origins of USENIX. What had for years separated USENIX from IEEE/ACM was it was where the two foci were really a single one, and thus had been together and actually considered what was potential as well as practical. In fact, USENIX was noted as the place where some of the most influential papers of the time had shown (numerous storage papers including Rusty's NFS and my EFS paper in the same session, just about any important security papers, numerous other system papers -- I could go a few pages here). Part of the issue was ACM's SOSP was every 2 years and there was too much good stuff going on in the system world (BTW - USENIX eventually created OSDI on alternate years because ACM was just going to do it). But USENIX also published less formal papers. In fact, one of my all-time favorite practitioner papers is from another member of this list -- Tom Lyon's "*All the Chips that Fit*" from the 1985 Summer USENIX [which if you have never read, send me an email, offline and I'll send you a scanned PDF -- note to Tom if you still have the original bits I bet USENIX would like them]. I suspect that such a paper would never have been acceptable in any of the IEEE or ACM conferences. Also unlike ACM/IEEE (and frankly the thing that happen at USENIX when I was President that I am most proud of) is that they do not have a paywall. Anything they published from the time when all proceedings were electronic is available and slowly some of the older papers are being scanned or reprinted from the source - as needed/possible. As much as possible, all of USENIX's papers are available to anyone [which was a huge thing to do - as it cut down a lot of revenue for them -- a paywall for papers is one of the things other associations use]. A number of good things happened at the time you mentioned, as well as some bad. Knowing the parties involved both today and at that time, if today's BOD and Executive Director was given the same choices that they had at the time of the action, I suspect we might have had a different outcome. IMO to the demise of FREENIX and ALS were two of the not-so-good choices that were made, but I understand why those conferences did go away at that point in history. If it makes you feel any better, as a former PC Chair for a couple of FREENIX (which was caught with the same bullet), and as I said a member of the PC of ALS, I was very sad to see that happen and I personally fought against it. But, I was on the losing side of that argument. Unfortunately, that ship sailed, and reviving them is unlikely to be possible although I believe it has been discussed a number of times since I left the BOD. Back to your point, USENIX may have stopped being as important to many practitioners, particularly ones in the FOSS community. Which I do find sad, but I understand the issues on both sides and why that might be so. For instance, Keith Packard of X11 fame, Steinhart, and I were all talking about "whence USENIX" at a Hackers conferences a few years back. So, if you come from that side of the world, you may not value membership or the results (BTW: my own now hacker daughter, who is a Googler, dropped her membership last year as she felt it was of less value to her); but so far USENIX has continued to be important to a large part of the research community and a set of some practitioners. That said, I also believe in 2021, that the USENIX BOD and their ED is struggling with a financial model that works for them when they do not have the conference revenue as they had before CV-19. I hope for their sake, the current treading water situation can find a way to bring them back to what they were pre-CV-19 because the conferences they traditionally have held, are excellent (premier in your words) and I would hate to see that really go away because they have had a lot of value and so far have continued to provide it. Respectfully -- my 2 cents. Clem --0000000000001f22ee05bf29ab57 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Note: These are my opinions/experience= s not necessarily=C2=A0those=C2=A0of the association or my employer.=C2=A0 = =C2=A0And, yes, I am a former BOD member as well as ex-President of same, a= s are a number of folks on this list.=C2=A0

On= Sun, Apr 4, 2021 at 1:30 AM G. Branden Robinson <g.branden.robinson@gmail.com> wrote:

I'm too young to know--did USENIX follow the trajectory of reorienting<= br> its focus from engineering and research to sales?=C2=A0
Actually, quite=C2=A0the opposite, USENIX was getting more and mor= e academic and research-oriented and less 'trade show.'=C2=A0 The k= ey is that USENIX and ALS should have been an excellent match, unfortunatel= y, some of the personalities involved were at odds with each other.=C2=A0 I= MO: it was more of=C2=A0a crash of personalities/control issues - the detai= ls do not need to be repeated or aired again. Note: I was on the BOD at tha= t time and in fact on the PC for that specific conference.=C2=A0 Ted may ha= ve been on the BOD at the same time.


=C2=A0
<= font color=3D"#ff0000">Why does it no longer occupy the premier = place it once did?
As they say on=C2=A0Quor= a, "never ask a question=C2=A0based on a false premise." S= adly, this is=C2=A0=C2=A0a false statement.

USENIX is extremely well respected in the systems resear= ch and security community in particular.=C2=A0 And even during these Covid = times has continued to have some of the premier conferences on the same; al= biet virtual (more in a minute).=C2=A0 =C2=A0 An issue during the time you= are discussing, USENIX had evolved into "two foci" between the p= ractitioners (which included both FOSS community and LISA types) and the mo= re academic-oriented folks looking for respected places to publish papers/d= evelop their tenure files.

U= SENIX had moved from its earlier (anything goes) - pure practitioner origin= s - which were also researchers, so at a meeting in a classroom at NYU, you= told people you had something to say and came and did it, to a more struct= ured (research) approach with program committees, submitted papers, and vet= ting and a hotel.=C2=A0 Along the way, because it had both types of people = and these were the folks that influenced the buying patterns,=C2=A0vendors = started to show up to=C2=A0show off what they had.=C2=A0 =C2=A0At the time = of the ALS=C2=A0conference you mentioned, the things happening in the FOSS = community - was much more like the origins of USENIX.=C2=A0 =C2=A0What had = for years separated USENIX from IEEE/ACM was it was where the two foci were= really a single one, and thus had been together and actually considered wh= at was potential as well as practical.=C2=A0 In fact, USENIX was noted=C2= =A0as the place where some of the most influential papers of the time had s= hown (numerous storage papers including Rusty's NFS and my EFS paper in= the same session, just about any important security papers, numerous other= system papers -- I could go a few pages here).

Part of the issue was ACM= 9;s SOSP was every 2 years and there was too much good stuff going on i= n the system world (BTW -=C2=A0USENIX eventually created OSDI on alternate years because ACM was just going to do it<= /span>).=C2=A0 =C2=A0 =C2=A0But USENIX also published less formal paper= s.=C2=A0 In fact, one of my all-time favorite practitioner papers is from another member of this list --=C2=A0Tom Lyon's "<= i>All the Chips that Fit" from the 1985 Summer USEN= IX [which if you have never read, send me an email, offline and I'll se= nd you a scanned PDF -- note to Tom if you still have the original bits I b= et USENIX would like them]. I suspect that such a paper would never = have been acceptable in any of the IEEE or ACM conferences.=C2=A0 =C2= =A0Also unlike ACM/IEEE (and frankly the thing that happen at USENIX when I= was President that I am most proud of) is that they do not have a paywall.= =C2=A0 Anything they published from the time when all proceedings=C2=A0were= electronic is available and slowly some of the older papers are being scan= ned or reprinted from the source - as needed/possible.=C2=A0 As much as pos= sible, all of U= SENIX's papers are available to anyone [which was a huge thing to d= o - as it cut down a lot of revenue for them -- a paywall for papers is one= of the things other associations use].

A number o= f good things happened at the time you mentioned, as well as some bad.=C2= =A0 Knowing the parties involved both today and at that time, if today'= s BOD and Executive Director was given the same choices that they had at th= e time of the action, I suspect we might have had a different outcome. IMO = to the demise of FREENIX and ALS were two of the not-so-good choices that= =C2=A0were made, but I understand why those conferences did go away at that= point in history.=C2=A0 =C2=A0If it makes you feel any better, as a former= PC Chair for a couple of FREENIX (which was caught with the same bullet), = and as I said a member of the PC of ALS, I was very sad to see that happen = and I personally fought against it.=C2=A0 But, I was on the losing side of = that argument. Unfortunately, that ship sailed, and reviving them is unlike= ly to be possible although I believe it has been discussed a number of time= s since I left the BOD.

Back to your point, USENIX may= have stopped being as important to many practitioners, particularly ones i= n the FOSS community. Which I do find sad, but I understand the issues on b= oth sides and why that might be so.=C2=A0 For=C2=A0instance, Keith Packard = of X11 fame, Steinhart,=C2=A0 =C2=A0and I were all talking about "when= ce USENIX" at a=C2=A0Hackers conferences a few years back.=C2=A0 =C2= =A0So, if you come from that side of the world, you may not value membershi= p or the results (BTW: my own now hacker daughter,=C2=A0 who is a Googler, = dropped her membership last year as she felt it was of less value to her); = but so far USENIX has continued to be important to a large part of the rese= arch community and a set of some practitioners.=C2=A0 =C2=A0<= /div>

That said, I also believe in 2021, that the USENIX BOD and their ED = is struggling with a financial model that works for them when they do not h= ave the conference revenue as they had before CV-19.=C2=A0 I hope for their= sake, the current treading water situation can find a way to bring them ba= ck to what they were pre-CV-19 because the conferences they traditionally h= ave held, are excellent (premier in=C2=A0your words) and I would hate to se= e that really go away because they have had a lot of value and so far have = continued to provide it.

Respectfully -- my 2 cents.=

Clem

--0000000000001f22ee05bf29ab57--