The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] UNIX magazines
Date: Fri, 13 Jun 2014 09:43:18 -0400	[thread overview]
Message-ID: <CAC20D2NUFCJwoRU=pozb=mR8z2TGCs87aTn0NPn=FXCpkWQuUA@mail.gmail.com> (raw)
In-Reply-To: <20140613040322.793E81DE37F@lignose.oclsc.org>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2076 bytes --]

On Fri, Jun 13, 2014 at 12:03 AM, Norman Wilson <norman at oclsc.org> wrote:

> USENIX now makes all their conference papers available online,
> free to anyone, except that only those registered for a
> conference can read them before the conference actually happens.
> That's not a bad substitute for a journal, I suppose.
>

​Thank you Norman.​

​As President of USENIX during that choice, that is a legacy I am
particularly proud.  It was a bit of a scary thing to do and so far ACM and
IEEE have been loath to follow suite as completely (I suspect because the
digital library is (was) a significant source of revenue for all three
organizations).  [To be fair, there are some exceptions, I believe ACM
Queue is downloadable - although I note that it is interesting a lot of
people working on Queue are also USENIX folks some of whom may be lurking
on this mailing list].

For what ever its worth, just a month or so ago, I was very pleased to see
my now Sr in college CS major daughter  -- who went to her first USENIX
conference in 1993 in stroller -- just joined USENIX (maybe its a little
like joining "the party").  But if USENIX is to continue their tradition of
being open and freely accessible, I offer an unabashed advertisement (i.e
no pay walls): like her and her college peers, please consider a USENIX
membership and/or going to a conference or two.


To Doug's question -- I agree that the answers about "Computing Systems"
that have been given are pretty much to the mark.   It was not an
insignificant undertaking to publish such a journal; and keeping
it/dropping was a trade off.

To all on the list, I can say that the Board has toyed with bring it back a
couple of times when I was on it.   If any of you have thoughts on the
matter, send them to the current Board of Directors ( bod at usenix.org )
and/or the Executive Director:  Casey Henderson (execdir at usenix.org).


Clem
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20140613/72408362/attachment.html>


  parent reply	other threads:[~2014-06-13 13:43 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-13  4:03 Norman Wilson
2014-06-13  4:54 ` arnold
2014-06-13 13:43 ` Clem Cole [this message]
2014-06-13 16:04   ` scj
  -- strict thread matches above, loose matches on Subject: below --
2014-06-14  0:42 Nelson H. F. Beebe
2014-06-14  0:53 ` A. P. Garcia
2014-06-13 12:03 Norman Wilson
2014-06-13 13:10 ` arnold
2014-06-13  5:07 Brian Walden
2014-06-13  2:18 Doug McIlroy
2014-06-13  2:45 ` arnold
2014-06-13  0:45 Norman Wilson
2014-06-12  3:10 Sergey Lapin
2014-06-12  3:38 ` Deborah Scherrer
2014-06-12  8:00   ` Jaap Akkerhuis
2014-06-12 16:07     ` Deborah Scherrer
2014-06-12  3:46 ` Nick Downing
2014-06-12  3:59 ` Dan Cross
2014-06-12 12:56   ` Jeff Johnson

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='CAC20D2NUFCJwoRU=pozb=mR8z2TGCs87aTn0NPn=FXCpkWQuUA@mail.gmail.com' \
    --to=clemc@ccc.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).