The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Larry McVoy <lm@mcvoy.com>
To: Clem Cole <clemc@ccc.com>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: ACM opens up much of its archives
Date: Wed, 25 May 2022 18:54:36 -0700	[thread overview]
Message-ID: <20220526015436.GP30142@mcvoy.com> (raw)
In-Reply-To: <CAC20D2NdPTh7X9g=247C=uC-oRp6t=TaKPPB1r+j1icw0juyJQ@mail.gmail.com>

I'll admit to being butt hurt about all of these journal places being behind
a paywall.  90% or 99.9% of that work was funded by our tax dollars, right?
Then the journal organization says you have to pay more.

It pisses me off.  If you are doing research you want to share that to help
the world.  Then you publish and they hide your work behind a paywall.

On Wed, May 25, 2022 at 11:53:15AM -0400, Clem Cole wrote:
> Indeed -- a small step in the right direction by ACM, but don't be too
> excited.   If you go to the ACM DL website, sadly, most of the library is
> still behind the paywall (or not scanned).  I do still have access
> from Intel, but when I retire, I think I will lose that access - even
> though I'm a long-time ACM (and IEEE) member.  In fact, the thing about ACM
> and IEEE that frosts my cookies the most is that I already paid for these
> journals.   [My wife would love it if I got rid of them from the basement,
> but if I do, I lose that investment].
> 
> FWIW: the single item that I am the proudest of when I was USENIX President
> was opening access to its entire library to everyone - members or
> otherwise.   This meant taking a leap of faith by the org that people would
> stay members - as it does cost the USENIX money to be there for us all (so
> I highly encourage people on this list to consider it to support the work
> they continue to do -- https://www.usenix.org/membership).
> 
> Clem
> ???
> 
> On Tue, May 24, 2022 at 7:29 PM <arnold@skeeve.com> wrote:
> 
> >
> > https://associationsnow.com/2022/05/the-way-things-were-why-open-access-to-the-a
> > cm-digital-library-matters/
> > <https://associationsnow.com/2022/05/the-way-things-were-why-open-access-to-the-acm-digital-library-matters/>
> >
> >

-- 
---
Larry McVoy            	     lm at mcvoy.com             http://www.mcvoy.com/lm 

  parent reply	other threads:[~2022-05-26  1:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-24 23:29 [TUHS] " arnold
2022-05-25 15:53 ` [TUHS] " Clem Cole
2022-05-25 16:00   ` Richard Salz
2022-05-25 16:01     ` Clem Cole
2022-05-26  1:54   ` Larry McVoy [this message]
2022-05-26 17:09   ` Henry Mensch
2022-05-26 17:13     ` Dan Cross
2022-05-26 19:49       ` Stephen Kitt
2022-05-26 20:39 [TUHS] " Douglas McIlroy
2022-05-26 20:43 ` [TUHS] " Dan Cross
2022-05-26 20:53 ` Clem Cole
2022-05-26 21:13   ` Charles H Sauer (he/him)

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=20220526015436.GP30142@mcvoy.com \
    --to=lm@mcvoy.com \
    --cc=clemc@ccc.com \
    --cc=tuhs@tuhs.org \
    /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).