Call for Papers - Summer 1990 USENIX, Anaheim, CA

[John Mashey]

(sorry if duplicate, postnews problems)

     USENIX continues to seek papers describing new and interesting work.
However, the Summer 1990 Technical Conference also seeks to include papers
that emphasize retrospectives, analyses of tradeoffs, and critical thinking
about where we are, how we got here, and why we're here.  Thus, the theme is:

           Beyond Mere Data:  Perspective, Insight, Understanding.

     Some sessions will follow the normal 3-paper format, with questions fol-
lowing each talk.  In other sessions, the speakers will form a panel, follow-
ing the talks, first to compare approaches, and then to take questions from
the audience.  In some cases, other experts may be added to the panel to
broaden the discussion.  Especially desirable are sessions where several im-
portant different viewpoints are represented, and proposals for such sessions
are welcome.

     Appropriate topics include, but are not limited to:

        Software release systems
        User interfaces, windowing, graphics
        Compilers, debuggers, tools, run-time issues
        File systems
        Distributed systems
        UNIX kernel approaches
        Fault-tolerancy, reliability, or security
        Computer architectures that stretch UNIX

     We will accept full papers, but require at least an abstract and outline,
in a form that gives the committee confidence in the final paper.  A submis-
sion should be 2-3 typewritten pages and include the following:

  1. Author names, addresses, telephone numbers and E-mail addresses.

  2. Abstract:  100-300 words (half a page) to be included in the final paper.

  3. Outline:  1.5-2.5 pages, giving the major headings of the paper, plus a
few sentences per section that give the major points that will be covered in
that section in the final paper.

     The following is a sample outline, which is not necessarily appropriate
for all papers, but which illustrates the important topics.  The purpose of an
outline should be to convince the committee that something interesting and im-
portant will be said in the final paper.

1. Introduction
      o Background.
        Introduce the problem to be solved;
        why is it important?
        Reference previous work; make sure the committee knows the wheel is
        not being reinvented.
2. How We Solved the Problem
      o More details on the problem and its issues.
      o Design decisions and tradeoffs, and why they were made.
      o Implementation issues.
3. Evaluation
      o Data, on performance, effort required.
      o How well does it work?
      o What would we do differently?
      o If it failed, why? and what can we learn from it?
4. Conclusion
      o Summarize the paper, emphasizing why it is important, and what was
        learned.
5. References
      o List at least a few key references, preferably to other people's work.

     The final paper should retain the 100-300 word abstract,  include  illus-
trations  (where  needed),  and citations to relevant literature.  Only previ-
ously unpublished submissions will be considered,  although  ``retrospective''
papers  may  describe work done years ago.  Thinly-disguised product announce-
ments are rarely accepted.  Final papers should contain 8-12 pages  of  single
spaced  typeset  materials.   All  final papers must be submitted in a camera-
ready format or electronic format  (troff-ms  if  possible).   Typewritten  or
dot-matrix  output  is  not acceptable.  For authors without access to a laser
printer or typesetter, appropriate facilities will be provided by the  program
chair.

     Please submit abstracts with outline and proposals for sessions  as  soon
as  possible,  and mail one hard-copy and one electronic-copy to the addresses
below.  The final deadline for receipt of submissions  is  February  7,  1990.
Abstracts  received  after this deadline will not be considered.  Notification
of acceptance or rejection will be made by March 9, 1990.  Final  camera-ready
papers are due by April 17, 1990.

        John R. Mashey
        Anaheim USENIX Technical Program
        MIPS Computer Systems
        930 Arques Ave
        Sunnyvale, CA  94086

        Internet:  anaheim at mips.com
        UUCP:      uunet!mips.com!anaheim
        Phone:     (408) 991-0253
        FAX:       (408) 720-9809

     Please  include  your  physical  and  electronic  mail  address  in   all
correspondence.

Program Committee:
        John R. Mashey (Chair), MIPS Computer Systems
        Clem Cole, Cole Computer Consulting
        Doug Comer, Purdue University
        Tom Ferrin, Univ. of CA - San Francisco
        James Gettys, Digital Equipment Corp.
        Lori Grob, Chorus Systems
        Douglas P. Kingston III, Morgan Stanley & Co., Inc.
        Heinz Lycklama, Interactive Systems Corp.
        M. Douglas McIlroy, AT&T Bell Laboratories
        Joe Moran, Legato Systems, Inc.
        Pat Parseghian, Princeton University
        Lawrence Rosler, Hewlett Packard
        Bill Shannon, Sun Microsystems, Inc.
-- 
-john mashey	DISCLAIMER: <generic disclaimer, I speak for me only, etc>
UUCP: 	{ames,decwrl,prls,pyramid}!mips!mash  OR  mash at mips.com
DDD:  	408-991-0253 or 408-720-1700, x253
USPS: 	MIPS Computer Systems, 930 E. Arques, Sunnyvale, CA 94086