🚀 go-pugleaf

First, if I were at ACM and reading this, I'd think it would be nuts
to address these issues directly on this list.  There is something only
slightly less than "a linch-mob" attitude.  And the list represents a
very small percentage of the total membership.

On my library shelf, right here next to me, I have some 15 years worth
of CACM issues.  While the new format is a bit overzelous, compared to the
1976 format, it is great.

Good design is done in an iterative fashion.  You try something, you see
if it works, you learn if it doesn't.  We have to give ACM a lot of credit
for trying something.  Now we have to help them learn what worked and what
didn't.

I think the best way to get HQ's attention is to send a letter to the editor.
The letter shouldn't be "THE NEW FORMAT STINKS!".  Instead, it should be
something constructive that they can work with.

If everyone on this list were to write a letter to the editor stating
three things that the CACM should stop doing, three things it should start
doing and three things that it should continue doing, I bet you would see
ACM being very responsive.  This would give HQ some hard and fast information
to learn from.

The April issue has a small paragraph in the "Editorial Pointers" column:

  "Thanks to those of you have have taken the time to offer us feedback
   on these efforts.  As a result of your letters, we have added some
   refinements to our editorial and design goals and will continue to do
   so.  We value the tradition of community involvement in this publication
   and encourage the continue partnership of readers, authors, advertisors,
   ACM members and volunteers.  Like the computing industry, _Communications_
   is moving with the times and benefitting from the process of change."

It was signed by James Maurer, Executive Editor.  He lists his email
address as "JIMM@ACMVM.BITNET" in the publisher's box.

ACM is our organization.  Let's all help make it be what we want it to be.

Jared M. Spool
Greater Boston SIGCHI Chair
also Principal Founder, User Interface Engineering