@device(imprint10)
@display[

                                          November 27, 1984


 
To:    Athena Staff
From:  Linda B. Merims


Subject:  December Newsletter Review


]
Here is your review copy of the December Athena @i(Newsletter).
Newsletter circulation is now about 500 copies.
The newsletter is large this time because it announces the
January system release.  Please return it to Will Doherty by the end of the
day on Thursday, November 29.

What do I mean when I say I would like you to "review" this?

Different people get review copies for different reasons.
@itemize[
User Services people get it because they have to know what
   users are being told.  Is it correct?  Is it good?  Does
   it conflict with other plans?  Do we really have time to
   prepare for this?

Managers get it so they know how the organization is being
   represented to the world, and what other managers are saying
   they are doing.

People who have contributed articles get it so that they
   can be dead sure that what's represented as their words
   are acceptable.

People who are strongly associated with any event or piece
   of software that's being described get it so that they
   can make sure "the story" matches what they thought was
   happening.  (This is why all developers are getting a
   copy this time--since all had some hand in the new release
   that may be inaccurately portrayed or omitted altogether.
   The Operations systems staff are all getting copies, too.)
]
With all this, you can see that the least important way to
review the newsletter is to check the punctuation and spelling,
although that is helpful.  It is valuable to scan the entire
newsletter for factual inaccuracies, misrepresentations, or
omissions, but @i(not necessary if the material really has nothing
to do with you).   I don't expect review copies back from even
the majority of people who get them.

It is @b(absolutely imperative) that you find the parts of the
newsletter that describe things you are responsible for or
have some active hand in or that are promising that you are going
to do something.  Check them to be sure they are correct and
complete.  Raise a ruckus if they aren't.

Make review comments on the paper copy and return the paper copy
to Will Doherty.  Please do not send mail commentary.  It is
much harder to handle when we finally merge review comments.  Thanks!