From riander@well.com Thu Jun 27 23:47:19 1996
Received: from mh1.well.com (mh1.well.com [206.15.64.22]) by mail.cis.ohio-state.edu (8.6.7/8.6.4) with ESMTP id XAA29706 for <perlman@cis.ohio-state.edu>; Thu, 27 Jun 1996 23:47:14 -0400
Received: from [206.15.68.121] (sf-tty28-ppp.well.com [206.15.68.127]) by mh1.well.com (8.7.5/8.7.5) with SMTP id UAA06008; Thu, 27 Jun 1996 20:47:09 -0700 (PDT)
X-Sender: riander@mail.well.com
Message-Id: <v01510103adf912da312d@[206.15.68.121]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Thu, 27 Jun 1996 20:49:42 -0800
To: Gary Perlman <perlman@cis.ohio-state.edu>
From: riander@well.com (Richard I. Anderson)
Subject: Re: videos for local SIGs?
Status: RO

Gary,

>I propose that SIGCHI fund the distribution of SIGCHI videos
>to all local SIGs (like the Central Ohio BuckCHI chapter :-).
>The local SIGs could set up a loan program for members,
>much as many have done for the CHI Conference tutorial notes.
>This could start with 1996, but it might also include 1995 and before.
>
>There are not many SIGs, so the cost would not be too high.
>I think that it might help increase the benefits of membership
>and make the videos more accessible to students.
>
>Comments?

I like the idea.  Consider soliciting feedback to the idea, though, not
from the EEC (many of whom haven't a clue about what happens in local
chapters), but from the local chapters.  (Use the local.sigs@xerox.com
mailing list.)

Richard

   __________________________________________________________________
     Richard I. Anderson, Usability/Design Adventures, 510-524-2421
           rianderson.chi@xerox.com         riander@well.com
                717 Coventry Road, Kensington CA 94707
                  http://www.well.com/user/riander/


From riander@well.com Tue Jul  2 14:14:15 1996
Received: from ACM.ORG (ACM.ORG [192.135.174.1]) by mail.cis.ohio-state.edu (8.6.7/8.6.4) with ESMTP id OAA20782 for <perlman@cis.ohio-state.edu>; Tue, 2 Jul 1996 14:14:10 -0400
Received: from alpha.xerox.com ("port 2169"@alpha.Xerox.COM)
 by ACM.ORG (PMDF V5.0-6 #10219) id <01I6LK6H04OU001H5V@ACM.ORG> for
 perlman@ACM.ORG; Tue, 02 Jul 1996 13:13:31 -0500 (CDT)
Received: from pigeon.Parc.Xerox.xns by alpha.xerox.com via XNS id <15562(7)
 >; Tue, 02 Jul 1996 11:12:18 -0700 (PDT)
Received: from mh1.well.com ([206.15.64.22]) by alpha.xerox.com with SMTP id
 <15523(6)>; Tue, 02 Jul 1996 11:09:29 -0700 (PDT)
Received: from [206.15.68.105] (sf-tty40-ppp.well.com [206.15.68.139])
 by mh1.well.com (8.7.5/8.7.5) with SMTP id LAA19104 for <eec.chi@xerox.com>;
 Tue, 02 Jul 1996 11:09:21 -0700 (PDT)
Date: Tue, 02 Jul 1996 12:12:02 -0700 (PDT)
From: riander@well.com (Richard I. Anderson)
Subject: Re: videos for local SIGs?
X-Sender: riander@mail.well.com
To: eec.chi@xerox.com
Message-id: <v01510104adff23ad9da1@[206.15.68.105]>
MIME-version: 1.0
Content-type: text/plain; charset="us-ascii"
Content-transfer-encoding: 7BIT
X-NS-Transport-ID: 0800207424C500DBFE3C
Status: RO

Jim Miller wrote:
>A couple of years ago, a comparable question came up about sending tutorial
>notes to the local SIGs.  It is indeed a good thing to do, but the trick is
>to figure out what the SIGs will do with them to insure that the members
>have access to them -- where do they physically reside, how do members get
>them, how do they get returned, etc.  Videos are small enough that the
>answer might be to bring them to the SIGs meetings, and maybe the "rental"
>period is from one meeting to the next.  The real point, of course, is to
>think through questions like that, and answer them in the context of
>putting a plan together.

I've encouraged Gary to obtain feedback from the local chapters directly.
Some local chapters have already addressed these kinds of issues, and tis
very possible that different local chapters will and should handle these
things very differently.

Richard
(the local SIGs chair)

   __________________________________________________________________
     Richard I. Anderson, Usability/Design Adventures, 510-524-2421
           rianderson.chi@xerox.com         riander@well.com
                717 Coventry Road, Kensington CA 94707
                  http://www.well.com/user/riander/


From perlman@mailer Tue Aug 20 10:00:55 1996
Received: from mailer.oclc.org (mailer.dev.oclc.org) by fssun09.dev.oclc.org (4.1/SMI-4.1)
	id AA20566; Tue, 20 Aug 96 10:00:55 EDT
Received: from turing.acm.org by mailer.oclc.org (5.0/SMI-4.1)
	id AA27118; Tue, 20 Aug 1996 10:00:53 +0500
Received: by turing.acm.org; id AA32276; Tue, 20 Aug 1996 08:49:10 -0500
Return-Path: perlman@oclc.org
Received: from alpha.xerox.com ("port 3021"@alpha.Xerox.COM)
 by ACM.ORG (PMDF V5.0-6 #10219) id <01I8HR8T5GWO000UVK@ACM.ORG> for
 perlman@ACM.ORG; Tue, 20 Aug 1996 08:50:06 -0500 (CDT)
Received: from Homer.PARC.Xerox.xns by alpha.xerox.com via XNS id <14760(7)
 >; Tue, 20 Aug 1996 06:49:22 -0700 (PDT)
Received: from fssun09.dev.oclc.org ([132.174.19.10])
 by alpha.xerox.com with SMTP id <14930(9)>; Tue,
 20 Aug 1996 06:47:49 -0700 (PDT)
Received: from dev1.NISDEV (dev1.dev.oclc.org)
 by fssun09.dev.oclc.org (4.1/SMI-4.1) id AA19413; Tue,
 20 Aug 1996 09:47:44 -0400 (EDT)
Received: by dev1.NISDEV (SMI-8.6/SMI-SVR4) id JAA09732; Tue,
 20 Aug 1996 09:47:43 -0400
Date: Tue, 20 Aug 1996 06:47:43 -0700 (PDT)
From: perlman@fssun09.dev.oclc.org (Gary PERLMAN)
Subject: SIGCHI VIdeos for Local SIGs
To: rianderson.chi@xerox.com
Cc: ec.chi@xerox.com, perlman@ACM.ORG
Message-Id: <199608201347.JAA09732@dev1.NISDEV>
Content-Transfer-Encoding: 7BIT
X-Ns-Transport-Id: 0800207424C500EEF45D
Content-Length: 2335
Status: O

Richard,

At the July SIGCHI EC meeting, we discussed
providing local SIGs with SIGCHI videos,
much as SIGCHI has provided them with CHI Tutorial notes.

The SIGCHI EC suggested that I work with
the local SIGs to see if this sort of
distribution would be of value to the local SIGs.
So, as the Adjunct Chair for Local SIGs,
could you please contact the Local Chapter chairs
to get some feedback about whether they could make
use of the CHI Conference videos?

Some questions that come to my mind are:

Would the local SIGCHI Chapters like to receive
CHI Conference videos for use in their chapters
(e.g., for lending, or for viewing before meetings)?

Do the Local SIGCHI Chapters have a circulation
mechanism in place for members to borrow videos
(e.g., a librarian)?

How far back would the Local SIGCHI Chapters want
to receive CHI Conference videos?  In 1997, all
conference attendees will receive the conference
video, but that still leaves out many SIGCHI and
Local SIGCHI Chapter members.  Distribution of
CHI'96 videos was much larger than previous years,
but still a small percentage of SIGCHI members,
and distribution of previous years' videos have
been small.  Distribution of older CHI videos
might be a way to rekindle interest in them
(and at a time when SIGCHI is taking over
the CHI videos in the SIGGRAPH Video Review).

And a related question is:

What have Local SIGCHI Chapters been doing with
the CHI Tutorial notes?  Are there any measures
of how much use and what type of use there has been?
Are there successful uses and mechanisms
that you might share with all the local SIGs?

Kate Ehrlich used to ask which Local SIGCHI Chapters would
like to receive tutorial notes, so a positive response
was at least some indication that someone found the notes useful.
A similar model might be used for the CHI Conference videos.

If you could, please send some, all, or more of the above
questions to the current Local SIGCHI Chapters for their opinions.
Once you get some feedback from the Local SIGCHI chapters,
I'd like to pass a summary of that feedback on to the
SIGCHI EC to consider the possibility of SIGCHI sending
the CHI Conference videos to the Local SIGCHI Chapters.

Of course, if you (or others) have concerns about this,
we can discuss it.

Cheers,

Gary Perlman, ACM SIGCHI Vice-Chair for Publications

From riander@well.COM Mon Sep  9 18:30:56 1996
Return-Path: <riander@well.COM>
Received: from mailer.oclc.org (mailer.dev.oclc.org) by oclc.org (4.1/SMI-4.1)
	id AA20075; Mon, 9 Sep 96 18:30:56 EDT
Received: from turing.acm.org ([199.222.69.20]) by mailer.oclc.org (5.0/SMI-4.1)
	id AA01989; Mon, 9 Sep 1996 18:30:55 +0500
Received: by turing.acm.org; id AA27755; Mon, 9 Sep 1996 11:11:08 -0500
Received: from mh1.well.com ("port 48807"@mh1.well.com)
 by ACM.ORG (PMDF V5.0-6 #10219) id <01I99RSHOI1U005PVB@ACM.ORG> for
 perlman@ACM.ORG; Mon, 09 Sep 1996 10:08:09 -0500 (CDT)
Received: from [206.15.69.93] (sf1-ppp93.well.com [206.15.69.93])
 by mh1.well.com (8.7.5/8.7.5) with SMTP id IAA18516; Mon,
 09 Sep 1996 08:07:56 -0700 (PDT)
Date: Mon, 09 Sep 1996 08:12:33 -0800
From: riander@well.COM (Richard I. Anderson)
Subject: CHI conference videos for local SIGCHI chapters
X-Sender: riander@mail.well.com
To: local-sigs.chi@XEROX.COM
Cc: perlman@ACM.ORG
Message-Id: <v01510100ae59e5abd1bf@[206.15.69.33]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7BIT
Content-Length: 2692
Status: RO

Hi,

Gary Perlman has proposed that SIGCHI provide interested local chapters
with CHI conference videos, much as it has been providing interested local
chapters with copies of the CHI conference tutorial notes.  (Note that "CHI
conference videos" are NOT videos of CHI conference sessions; rather, they
are videos that were accepted by the CHI conference committee to be a part
of the CHI conference video program.  See
http://www.acm.org:82/~perlman/sigchi/608962.html for a list of the
contents of the CHI'96 video program; see
http://www.acm.org:82/~perlman/sigchi/608953.html for a list of the
contents of the CHI'95 video program.)

Gary would like to learn more about the extent to which such videos would
be of value to the local chapters (e.g., how/if they would be used).
Hence, please send Gary and I your answers to the following questions:

    Would your local SIGCHI Chapter like to receive
    CHI Conference videos for use in their chapters
    (e.g., for lending, or for viewing before meetings)?

    Does your Local SIGCHI Chapter have a circulation
    mechanism in place for members to borrow videos
    (e.g., a librarian)?

    How far back would your Local SIGCHI Chapter want
    to receive CHI Conference videos?  [In 1997, all
    conference attendees will receive the conference
    video, but that still leaves out many SIGCHI and
    Local SIGCHI Chapter members.  Distribution of
    CHI'96 videos was much larger than previous years,
    but still a small percentage of SIGCHI members,
    and distribution of previous years' videos have
    been small.  Distribution of older CHI videos
    might be a way to rekindle interest in them
    (and at a time when SIGCHI is taking over
    the CHI videos in the SIGGRAPH Video Review).]

    What has your Local SIGCHI Chapter been doing with
    the CHI Tutorial notes?  Have you any measures
    of how much use and what type of use there has been?
    Are there successful uses and mechanisms
    that you might recommend to all the local SIGs?

Richard Anderson, SIGCHI Local SIGs Chair
(with and for Gary Perlman, SIGCHI Vice-Chair for Publications)


P.S. Please let me (i.e., Richard) know how many copies you receive of this
email from me, whether you believe you should have received this email from
me, and the email addresses of others whom you believe should have received
this email from me.

   __________________________________________________________________
     Richard I. Anderson, Usability/Design Adventures, 510-524-2421
           rianderson.chi@xerox.com         riander@well.com
                717 Coventry Road, Kensington CA 94707
                  http://www.well.com/user/riander/



From riander@well.com Fri Sep 13 09:28:11 1996
Return-Path: <riander@well.com>
Received: from mailer.oclc.org (mailer.dev.oclc.org) by oclc.org (4.1/SMI-4.1)
	id AA28008; Fri, 13 Sep 96 09:28:11 EDT
Received: from mh1.well.com by mailer.oclc.org (5.0/SMI-4.1)
	id AA09044; Fri, 13 Sep 1996 09:28:09 +0500
Received: from [206.15.69.64] (sf1-ppp64.well.com [206.15.69.64]) by mh1.well.com (8.7.5/8.7.5) with SMTP id GAA02520; Fri, 13 Sep 1996 06:28:01 -0700 (PDT)
X-Sender: riander@mail.well.com
Message-Id: <v01510100ae5f1b1f922a@[206.15.69.70]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Fri, 13 Sep 1996 06:32:45 -0800
To: perlman@mailer.oclc.org (Gary PERLMAN)
From: jabbott@world.std.com (Jamison H Abbott) (by way of riander@well.com (Richard
 I. Anderson))
Subject: Re: CHI conference videos for local SIGCHI chapters
Content-Length: 4086
Status: RO

Gary,

Only one response thus far, representing GBSIGCHI.  It is appended to this
message.

I'll add that BayCHI only recently initiated a lending library, so it has
little to offer in terms of experience, though it seems to be doing very
well in its early stages.  We decided to add the available videos (CHI'96
and CHI'95) to the library, but ACM botched my order (and aren't being
responsive to my report of the botch), so we've not yet ANY experience with
lending the videos.

Richard

==============
> Hi,
>
> Gary Perlman has proposed that SIGCHI provide interested local chapters
> with CHI conference videos, much as it has been providing interested local
> chapters with copies of the CHI conference tutorial notes.  (Note that "CHI
> conference videos" are NOT videos of CHI conference sessions; rather, they
> are videos that were accepted by the CHI conference committee to be a part
> of the CHI conference video program.  See
> http://www.acm.org:82/~perlman/sigchi/608962.html for a list of the
> contents of the CHI'96 video program; see
> http://www.acm.org:82/~perlman/sigchi/608953.html for a list of the
> contents of the CHI'95 video program.)
>
> Gary would like to learn more about the extent to which such videos would
> be of value to the local chapters (e.g., how/if they would be used).
> Hence, please send Gary and I your answers to the following questions:
>
>     Would your local SIGCHI Chapter like to receive
>     CHI Conference videos for use in their chapters
>     (e.g., for lending, or for viewing before meetings)?

Yes, very much so!  We have a lending library.  The pre-meeting
viewing sounds like a great idea also.

>
>     Does your Local SIGCHI Chapter have a circulation
>     mechanism in place for members to borrow videos
>     (e.g., a librarian)?

Yes, we have a chapter librarian (myself) and chapter members can
borrow items from our library.

>
>     How far back would your Local SIGCHI Chapter want
>     to receive CHI Conference videos?  [In 1997, all
>     conference attendees will receive the conference
>     video, but that still leaves out many SIGCHI and
>     Local SIGCHI Chapter members.  Distribution of
>     CHI'96 videos was much larger than previous years,
>     but still a small percentage of SIGCHI members,
>     and distribution of previous years' videos have
>     been small.  Distribution of older CHI videos
>     might be a way to rekindle interest in them
>     (and at a time when SIGCHI is taking over
>     the CHI videos in the SIGGRAPH Video Review).]

Some of our members were involved in the founding of CHI and others
are actively involved in research, so I think there would be definite
interest in having videos back to the beginning.

>     What has your Local SIGCHI Chapter been doing with
>     the CHI Tutorial notes?  Have you any measures
>     of how much use and what type of use there has been?
>     Are there successful uses and mechanisms
>     that you might recommend to all the local SIGs?

We have made our chapter library materials including the CHI tutorial
notes available to our chapter members via our librarian.  We've found
that the success of our library program is tied quite closely to the
amount of effort the Librarian puts into making our members aware of
what we've got and how they can access it.


Jim Abbott
Acting Librarian
Greater Boston SIGCHI


> Richard Anderson, SIGCHI Local SIGs Chair
> (with and for Gary Perlman, SIGCHI Vice-Chair for Publications)
>
>
> P.S. Please let me (i.e., Richard) know how many copies you receive of this
> email from me, whether you believe you should have received this email from
> me, and the email addresses of others whom you believe should have received
> this email from me.
>
>    __________________________________________________________________
>      Richard I. Anderson, Usability/Design Adventures, 510-524-2421
>            rianderson.chi@xerox.com         riander@well.com
>                 717 Coventry Road, Kensington CA 94707
>                   http://www.well.com/user/riander/
>
==============



From perlman@mailer Fri Sep 13 11:18:44 1996
Return-Path: <perlman@mailer>
Received: from mailer.oclc.org (mailer.dev.oclc.org) by oclc.org (4.1/SMI-4.1)
	id AA07035; Fri, 13 Sep 96 11:18:44 EDT
Received: from turing.acm.org ([199.222.69.20]) by mailer.oclc.org (5.0/SMI-4.1)
	id AA14654; Fri, 13 Sep 1996 11:18:43 +0500
Received: by turing.acm.org; id AA13440; Fri, 13 Sep 1996 11:21:23 -0500
Received: from oclc.org ("port 4158"@fssun09.dev.oclc.org)
 by ACM.ORG (PMDF V5.0-6 #10219) id <01I9FDBS13ZA008KFV@ACM.ORG> for
 perlman@ACM.ORG; Fri, 13 Sep 1996 10:18:33 -0500 (CDT)
Received: from dev1.NISDEV (dev1.dev.oclc.org) by oclc.org (4.1/SMI-4.1)
 id AA07017; Fri, 13 Sep 1996 11:18:31 -0400 (EDT)
Received: by dev1.NISDEV (SMI-8.6/SMI-SVR4) id LAA17591; Fri,
 13 Sep 1996 11:18:30 -0400
Date: Fri, 13 Sep 1996 11:18:30 -0400 (EDT)
From: perlman@oclc.org (Gary PERLMAN)
Subject: Re: CHI conference videos for local SIGCHI chapters
In-Reply-To: <v01510100ae5f1b1f922a@[206.15.69.70]> from
 <"jabbott@world.std.com"@Sep>
To: jabbott@world.std.com
Cc: rianderson.chi@xerox.com, perlman@ACM.ORG
Message-Id: <199609131518.LAA17591@dev1.NISDEV>
Mime-Version: 1.0
X-Mailer: ELM [version 2.4 PL23beta3]
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 2226
Status: O

Thanks Jim for answering Richard's questions.
That there was only one response was disappointing,
but your comment suggests an opportunity (see below),
perhaps for the Local SIGs chair.

Richard,
  I am not sure what to do with the issue of videos and local SIGs.
If the response is so low, then maybe distribution is premature,
or even not desired.  I propose that we let the issue sit
for a while, and perhaps take it up again when there is more interest.
To increase the interest in videos and in local sig libraries,
perhaps the local sigs should be helped out by a guiding force.

Jim Abbott wrote:
> We have made our chapter library materials including the CHI tutorial
> notes available to our chapter members via our librarian.  We've found
> that the success of our library program is tied quite closely to the
> amount of effort the Librarian puts into making our members aware of
> what we've got and how they can access it.
> 
> Jim Abbott
> Acting Librarian
> Greater Boston SIGCHI

Perhaps if there was a description of a "model" library program,
other SIGS could set up their own like it.
In fact, since many of the materials available
are those provided by SIGCHI (tutorial notes, and hopefully videos),
there could be a standard set of instructions (text and web page).
These standard pages could be set up at www.acm.org in:
	http://www.acm.org/sigchi/local-sigs/
for people to refer to, such as:
	http://www.acm.org/sigchi/chi95/proceedings/tutors/
	http://www.acm.org/sigchi/chi95/proceedings/videos/
BayCHI has a tutorial notes page:
	http://www.baychi.org/general/tutorial_notes.html
for which they mainly used the chi96 advance program.

I think some coordination would be a big help, especially after looking at
the "library" entry for BuckCHI (Central Ohio Local SIGCHI):
	http://gecko.web.compuserve.com:2000/BuckCHI/Other.html#Library
which says (alas):
  Library Catalog
    Here go descriptions of what we have in our library and how to get stuff.

Gary Perlman, ACM SIGCHI Vice Chair for Publications

Gary PERLMAN, OCLC Online Computer Library Center
6565 Frantz Road, Dublin, Ohio 43017 USA
Voice: +1-614-761-5058  Fax: +1-614-793-0915  email: perlman@oclc.org
WWW: http://www.acm.org/~perlman

From riander@well.com Sat Sep 14 15:50:26 1996
Return-Path: <riander@well.com>
Received: from mailer.oclc.org (mailer.dev.oclc.org) by oclc.org (4.1/SMI-4.1)
	id AA10768; Sat, 14 Sep 96 15:50:25 EDT
Received: from mh1.well.com by mailer.oclc.org (5.0/SMI-4.1)
	id AA21012; Sat, 14 Sep 1996 15:50:25 +0500
Received: from [206.15.69.95] (sf1-ppp101.well.com [206.15.69.101]) by mh1.well.com (8.7.5/8.7.5) with SMTP id MAA06603; Sat, 14 Sep 1996 12:50:15 -0700 (PDT)
X-Sender: riander@mail.well.com
Message-Id: <v01510100ae60cb186a6d@[206.15.69.95]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Sat, 14 Sep 1996 12:55:01 -0800
To: perlman@mailer.oclc.org (Gary PERLMAN)
From: riander@well.com (Richard I. Anderson)
Subject: Re: CHI conference videos for local SIGCHI chapters
Cc: jabbott@world.std.com
Content-Length: 510
Status: RO

Gary,

>That there was only one response was disappointing,

Relax, Gary!!!  More responses are coming in; I just forwarded to you the
first I had received.

(Thanks, Jim, for your response.)

Richard

   __________________________________________________________________
     Richard I. Anderson, Usability/Design Adventures, 510-524-2421
           rianderson.chi@xerox.com         riander@well.com
                717 Coventry Road, Kensington CA 94707
                  http://www.well.com/user/riander/



From riander@well.com Sun Sep 15 03:35:52 1996
Return-Path: <riander@well.com>
Received: from mailer.oclc.org (mailer.dev.oclc.org) by oclc.org (4.1/SMI-4.1)
	id AA27029; Sun, 15 Sep 96 03:35:52 EDT
Received: from mh1.well.com by mailer.oclc.org (5.0/SMI-4.1)
	id AA14694; Sun, 15 Sep 1996 03:35:50 +0500
Received: from [206.15.69.88] (sf1-ppp92.well.com [206.15.69.92]) by mh1.well.com (8.7.5/8.7.5) with SMTP id AAA22951 for <perlman@oclc.org>; Sun, 15 Sep 1996 00:35:45 -0700 (PDT)
X-Sender: riander@mail.well.com
Message-Id: <v01510101ae617098cf05@[206.15.69.88]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Sun, 15 Sep 1996 00:40:31 -0800
To: perlman@mailer.oclc.org (Gary PERLMAN)
From: riander@well.com (Richard I. Anderson)
Subject: Re: CHI conference videos for local SIGCHI chapters
Content-Length: 2305
Status: RO

Gary,

Another response:

>To: riander@well.com (Richard I. Anderson)
>Subject: Re: CHI conference videos for local SIGCHI chapters
>Date: Fri, 13 Sep 1996 17:28:49 +0200
>From: Michel Beaudouin-Lafon <Michel.Beaudouin-Lafon@lri.fr>
>
>
>Hi Richard,
>
>> P.S. Please let me (i.e., Richard) know how many copies you receive of this
>> email from me, whether you believe you should have received this email from
>> me, and the email addresses of others whom you believe should have received
>> this email from me.
>
>I got 2 copies of your message, one to mbl@lri.fr, the other to
>local-sigs.chi@xerox.com. Representing the forming "French" local chapter
>of SIGCHI, I beleive I should have received this message.
>
>As for getting CHI videos, this is a very good idea!
>
>>    Would your local SIGCHI Chapter like to receive
>>    CHI Conference videos for use in their chapters
>>    (e.g., for lending, or for viewing before meetings)?
>
>yes yes yes!
>
>>    Does your Local SIGCHI Chapter have a circulation
>>    mechanism in place for members to borrow videos
>>    (e.g., a librarian)?
>
>as you know, the chapter does not exist yet, but we would
>certainly put something like this in place.
>
>>    How far back would your Local SIGCHI Chapter want
>>    to receive CHI Conference videos?  [In 1997, all
>
>I have no idea. The more the better. I remember the videos
>I saw at CHI back in 88, and I'm sure they would still be
>useful as a resource, e.g. for reference or for teaching.
>
>>    What has your Local SIGCHI Chapter been doing with
>>    the CHI Tutorial notes?  Have you any measures
>
>as a yet non-existent chapter, we haven't received tutorial notes.
>
>
>hope this helps,
>michel
>
>
>   ___    0  Michel Beaudouin-Lafon        e-mail: mbl@lri.fr
>  /   \  /   LRI - Bat 490                 www   : http://www-ihm.lri.fr/~mbl
> /  __/ /    Universite de Paris-Sud       voice : +33 (1) 69 41 69 10
>/__   \/     91 405 ORSAY Cedex - FRANCE   fax   : +33 (1) 69 41 65 86
>

   __________________________________________________________________
     Richard I. Anderson, Usability/Design Adventures, 510-524-2421
           rianderson.chi@xerox.com         riander@well.com
                717 Coventry Road, Kensington CA 94707
                  http://www.well.com/user/riander/



From riander@well.com Sun Sep 15 03:35:58 1996
Return-Path: <riander@well.com>
Received: from mailer.oclc.org (mailer.dev.oclc.org) by oclc.org (4.1/SMI-4.1)
	id AA27033; Sun, 15 Sep 96 03:35:58 EDT
Received: from mh1.well.com by mailer.oclc.org (5.0/SMI-4.1)
	id AA14698; Sun, 15 Sep 1996 03:35:56 +0500
Received: from [206.15.69.88] (sf1-ppp92.well.com [206.15.69.92]) by mh1.well.com (8.7.5/8.7.5) with SMTP id AAA22967 for <perlman@oclc.org>; Sun, 15 Sep 1996 00:35:51 -0700 (PDT)
X-Sender: riander@mail.well.com
Message-Id: <v01510102ae61710cea4c@[206.15.69.88]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Sun, 15 Sep 1996 00:40:37 -0800
To: perlman@mailer.oclc.org (Gary PERLMAN)
From: riander@well.com (Richard I. Anderson)
Subject: RE: CHI conference videos for local SIGCHI chapters
Content-Length: 2769
Status: RO

Another:

>From: Peter Szmyt <SZMYT@simware.com>
>To: riander <riander@well.com>
>Subject: RE: CHI conference videos for local SIGCHI chapters
>Date: Fri, 13 Sep 96 15:36:00 EDT
>
>
>hi richard.
>
>    Would your local SIGCHI Chapter like to receive
>    CHI Conference videos for use in their chapters
>    (e.g., for lending, or for viewing before meetings)?
>
>yes. i bought a copy of the chi '96 videos for just this purpose.
>
>    Does your Local SIGCHI Chapter have a circulation
>    mechanism in place for members to borrow videos
>    (e.g., a librarian)?
>
>not an official mechanism. but it has worked in the past with the
>tutorial notes.
>
>    How far back would your Local SIGCHI Chapter want
>    to receive CHI Conference videos?  [In 1997, all
>    conference attendees will receive the conference
>    video, but that still leaves out many SIGCHI and
>    Local SIGCHI Chapter members.  Distribution of
>    CHI'96 videos was much larger than previous years,
>    but still a small percentage of SIGCHI members,
>    and distribution of previous years' videos have
>    been small.  Distribution of older CHI videos
>    might be a way to rekindle interest in them
>    (and at a time when SIGCHI is taking over
>    the CHI videos in the SIGGRAPH Video Review).]
>
>i'd have to put this out and see what kind of feedback i'd get. if you
>want me to guess, i'd say we wouldn't need any past videos.
>
>    What has your Local SIGCHI Chapter been doing with
>    the CHI Tutorial notes?  Have you any measures
>    of how much use and what type of use there has been?
>    Are there successful uses and mechanisms
>    that you might recommend to all the local SIGs?
>
>use has been light of the tutorial notes. i'd say 4 or 5 borrowed. i
>don't keep really good track of this.
>
>P.S. Please let me (i.e., Richard) know how many copies you receive of
>this
>email from me, whether you believe you should have received this email
>from
>me, and the email addresses of others whom you believe should have
>received
>this email from me.
>
>i've received two copies of this email. one to me and one through
>local-sigs.chi@xerox.com
>
>
>hope this helps,
>peter
>
>__________________________________________________________________________
>
>Peter Szmyt, Chair, Ottawa ACM SIGCHI
>http://ksl1000.ai.iit.nrc.ca/capchi/
>Email: szmyt@simware.com  Phone: 613.228.5100 x4029  Fax: 613.727.9409
>2 Gurdwara Road, Ottawa, Ontario, Canada, K2E 1A2
>

   __________________________________________________________________
     Richard I. Anderson, Usability/Design Adventures, 510-524-2421
           rianderson.chi@xerox.com         riander@well.com
                717 Coventry Road, Kensington CA 94707
                  http://www.well.com/user/riander/



From riander@well.com Mon Sep 16 23:58:19 1996
Return-Path: <riander@well.com>
Received: from mailer.oclc.org (mailer.dev.oclc.org) by oclc.org (4.1/SMI-4.1)
	id AA15802; Mon, 16 Sep 96 23:58:19 EDT
Received: from mh1.well.com by mailer.oclc.org (5.0/SMI-4.1)
	id AA29809; Mon, 16 Sep 1996 23:58:15 +0500
Received: from [206.15.69.44] (sf1-ppp44.well.com [206.15.69.44]) by mh1.well.com (8.7.5/8.7.5) with SMTP id UAA25867 for <perlman@oclc.org>; Mon, 16 Sep 1996 20:58:08 -0700 (PDT)
X-Sender: riander@mail.well.com
Message-Id: <v01510101ae63e0b2fd9a@[206.15.69.28]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Mon, 16 Sep 1996 21:02:59 -0800
To: perlman@mailer.oclc.org (Gary PERLMAN)
From: riander@well.com (Richard I. Anderson)
Subject: Re: CHI conference videos for local SIGCHI chapters
Content-Length: 1161
Status: RO

>Date:   Mon, 16 Sep 1996 20:56:08 -0400
>From: William Hunt <hunt@dgp.toronto.edu>
>To: riander@well.com
>Subject: Re: CHI conference videos for local SIGCHI chapters
>
>Richard,
>
>Hi.  Yes, you send the conference video email to the right place.  We
>received two copies of it.  I do think that ToRCHI would benefit for
>getting the videos.  We have many members who do not go to the SIGCHI
>annual meeting or are not SIGCHI members.  They would learn from the
>videos.  Viewing before meetings and lending are definite possibilities.
>We would have to poll the membership about interest in older videos.
>
>We loan out the tutorial notes, but have had little response this year.
>More use is made by those with quick access, e.g., browsing or keeping
>for a few hours or days.
>
>...
>
>William Hunt, acting chair, and information director, ToRCHI

   __________________________________________________________________
     Richard I. Anderson, Usability/Design Adventures, 510-524-2421
           rianderson.chi@xerox.com         riander@well.com
                717 Coventry Road, Kensington CA 94707
                  http://www.well.com/user/riander/



From perlman@cis.ohio-state.edu Thu Jun 27 13:13:23 1996
Received: from ACM.ORG (ACM.ORG [192.135.174.1]) by mail.cis.ohio-state.edu (8.6.7/8.6.4) with ESMTP id NAA14725 for <perlman@cis.ohio-state.edu>; Thu, 27 Jun 1996 13:13:17 -0400
Received: from alpha.xerox.com ("port 3257"@alpha.Xerox.COM)
 by ACM.ORG (PMDF V5.0-6 #10219) id <01I6EIM0TW0C00BAZ9@ACM.ORG> for
 perlman@ACM.ORG; Thu, 27 Jun 1996 12:13:15 -0500 (CDT)
Received: from Storm.Parc.Xerox.xns by alpha.xerox.com via XNS id <14733(2)
 >; Thu, 27 Jun 1996 10:10:47 -0700 (PDT)
Received: from mail.cis.ohio-state.edu ([164.107.8.55])
 by alpha.xerox.com with SMTP id <14423(5)>; Thu,
 27 Jun 1996 10:03:02 -0700 (PDT)
Received: from indiana.cis.ohio-state.edu
 (indiana.cis.ohio-state.edu [164.107.137.4]) by mail.cis.ohio-state.edu
 (8.6.7/8.6.4) with ESMTP id NAA14380 for <eec.chi@xerox.com>; Thu,
 27 Jun 1996 13:02:49 -0400
Received: (perlman@localhost) by indiana.cis.ohio-state.edu (8.6.7/8.6.4)
 id NAA11121 for eec.chi@xerox.com; Thu, 27 Jun 1996 13:02:49 -0400
Date: Thu, 27 Jun 1996 10:02:49 -0700 (PDT)
From: Gary Perlman <perlman@cis.ohio-state.edu>
Subject: videos for local SIGs?
Sender: perlman@cis.ohio-state.edu
To: eec.chi@xerox.com
Message-id: <199606271702.NAA11121@indiana.cis.ohio-state.edu>
Content-transfer-encoding: 7BIT
X-NS-Transport-ID: 0800207424C500DBA5F8
Status: RO

I propose that SIGCHI fund the distribution of SIGCHI videos
to all local SIGs (like the Central Ohio BuckCHI chapter :-).
The local SIGs could set up a loan program for members,
much as many have done for the CHI Conference tutorial notes.
This could start with 1996, but it might also include 1995 and before.

There are not many SIGs, so the cost would not be too high.
I think that it might help increase the benefits of membership
and make the videos more accessible to students.

Comments?

Gary Perlman, ACM SIGCHI Vice-Chair for Publications

From perlman@oclc.org Tue Sep 24 16:09:37 1996
Return-Path: <perlman@oclc.org>
Received: from dev1.NISDEV (dev1.dev.oclc.org) by oclc.org (4.1/SMI-4.1)
	id AA22228; Tue, 24 Sep 96 16:09:37 EDT
Received: by dev1.NISDEV (SMI-8.6/SMI-SVR4)
	id QAA14519; Tue, 24 Sep 1996 16:09:36 -0400
From: perlman@oclc.org (Gary PERLMAN)
Message-Id: <199609242009.QAA14519@dev1.NISDEV>
Subject: Re: CHI conference videos for local SIGCHI chapters
To: riander@well.com (Richard I. Anderson)
Date: Tue, 24 Sep 1996 16:09:36 -0400 (EDT)
Cc: perlman@mailhost (Gary Perlman)
In-Reply-To: <v01510100ae60cb186a6d@[206.15.69.95]> from "Richard I. Anderson" at Sep 14, 96 12:55:01 pm
X-Mailer: ELM [version 2.4 PL23beta3]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Status: O

> Gary,
> 
> >That there was only one response was disappointing,
> 
> Relax, Gary!!!  More responses are coming in; I just forwarded to you the
> first I had received.
> 
> (Thanks, Jim, for your response.)
> 
> Richard

I received four responses.  Were there any more?
My general impression is that the reception
is only mildly positive from the few Chapters that responded.
The use of tutorial notes seems very light
(perhaps too light to warrant continuing their distribution),
and there seems to be little current infrastructure
for circulating media such as tutorial notes or videos.

Here is what I propose:

Someone (e.g., the Adjunct Chair for Local SIGs)
should create a model lending library
for all the local SIGs, with listings of all
the currently and potentially available materials.
This would not take long, given the existence of
web pages at acm.org describing tutorials and videos.
Along with that, I suggest creating a guide to
the successful use of media, or at least suggestions
of ideas to try, in the absence of real exerience.
Some ideas:
	- showing videos before local chapter meetings
		(this means having available equipment)
	- lending out materials, especially to schools
		(this means having ties with schools)
Them I propose that local chapters link in
the page to their own pages, so that their members
know what's out there.

The above might generate more interest in videos
and more interest in the tutorial notes.
If it does, then I think we should return to
the idea of sending videos to local SIGs.

From riander@well.com Tue Sep 24 22:52:52 1996
Return-Path: <riander@well.com>
Received: from mailer.oclc.org (mailer.dev.oclc.org) by oclc.org (4.1/SMI-4.1)
	id AA24524; Tue, 24 Sep 96 22:52:51 EDT
Received: from mh1.well.com by mailer.oclc.org (5.0/SMI-4.1)
	id AA01480; Tue, 24 Sep 1996 22:52:50 +0500
Received: from [206.15.69.19] (sf1-ppp68.well.com [206.15.69.68]) by mh1.well.com (8.7.6/8.7.5) with SMTP id TAA07489; Tue, 24 Sep 1996 19:52:41 -0700 (PDT)
X-Sender: riander@mail.well.com
Message-Id: <v01510109ae6e5abb8180@[206.15.69.19]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Tue, 24 Sep 1996 19:57:44 -0800
To: perlman@mailer.oclc.org (Gary PERLMAN)
From: riander@well.com (Richard I. Anderson)
Subject: Re: CHI conference videos for local SIGCHI chapters
Content-Length: 1239
Status: RO

Gary,

>I received four responses.  Were there any more?
>My general impression is that the reception
>is only mildly positive from the few Chapters that responded.
>The use of tutorial notes seems very light
>(perhaps too light to warrant continuing their distribution),
>and there seems to be little current infrastructure
>for circulating media such as tutorial notes or videos.

Please be a tad more patient.  My/your email queries were sent out only a
couple of weeks ago.  Lots of people are very busy; some may not be
attending to such things until their steering committee meetings; some
local chapter officers have more important things on their local chapter
plates; etc. etc.  I'll send a second mailing in a couple of weeks.

>Here is what I propose:

I appreciate your ideas.  They are good ones.

>the idea of sending videos to local SIGs.

BayCHI will start lending videos soon.  T'will provide good data.

Richard

   __________________________________________________________________
     Richard I. Anderson, Usability/Design Adventures, 510-524-2421
           rianderson.chi@xerox.com         riander@well.com
                717 Coventry Road, Kensington CA 94707
                  http://www.well.com/user/riander/



From perlman@mailer Wed Sep 25 14:06:20 1996
Return-Path: <perlman@mailer>
Received: from mailer.oclc.org (mailer.dev.oclc.org) by oclc.org (4.1/SMI-4.1)
	id AA14263; Wed, 25 Sep 96 14:06:20 EDT
Received: from mail.cis.ohio-state.edu by mailer.oclc.org (5.0/SMI-4.1)
	id AA11779; Wed, 25 Sep 1996 14:06:20 +0500
Received: from mail.acm.org (mail.hq.acm.org [199.222.69.4]) by mail.cis.ohio-state.edu (8.6.7/8.6.4) with ESMTP id JAA06253 for <perlman@cis.ohio-state.edu>; Wed, 25 Sep 1996 09:04:12 -0400
Received: from oclc.org (fssun10.dev.oclc.org [132.174.19.11]) by mail.acm.org (8.7.5/8.7.5) with SMTP id JAA16566 for <perlman@acm.org>; Wed, 25 Sep 1996 09:05:08 -0400
Received: from dev1.NISDEV (dev1.dev.oclc.org) by oclc.org (4.1/SMI-4.1)
	id AA27099; Wed, 25 Sep 96 09:03:41 EDT
Received: by dev1.NISDEV (SMI-8.6/SMI-SVR4)
	id JAA16441; Wed, 25 Sep 1996 09:03:40 -0400
From: perlman@oclc.org (Gary PERLMAN)
Message-Id: <199609251303.JAA16441@dev1.NISDEV>
Subject: Re: CHI conference videos for local SIGCHI chapters
To: riander@well.com (Richard I. Anderson)
Date: Wed, 25 Sep 1996 09:03:40 -0400 (EDT)
Cc: perlman@acm.org
In-Reply-To: <v01510109ae6e5abb8180@[206.15.69.19]> from "Richard I. Anderson" at Sep 24, 96 07:57:44 pm
X-Mailer: ELM [version 2.4 PL23beta3]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 1812
Status: RO

> >I received four responses.  Were there any more?
> >My general impression is that the reception
> >is only mildly positive from the few Chapters that responded.
> >The use of tutorial notes seems very light
> >(perhaps too light to warrant continuing their distribution),
> >and there seems to be little current infrastructure
> >for circulating media such as tutorial notes or videos.
> 
> Please be a tad more patient.  My/your email queries were sent out only a
> couple of weeks ago.  Lots of people are very busy; some may not be
> attending to such things until their steering committee meetings; some
> local chapter officers have more important things on their local chapter
> plates; etc. etc.  I'll send a second mailing in a couple of weeks.

I am not ruling out sending videos in the future,
or suggesting that we stop sending tutorial notes.
But after the small response and after checking
10 chapter sites, I did not find much evidence
that providing materials would have much impact.
The only web site I found with any materials listed was:
	http://www-ir.inf.ethz.ch/SWE/Library.html
(I could have missed others), and that did not
list the tutorial notes (although they might
not have received any).

So, I think there is no rush to provide the videos.

> >Here is what I propose:
> 
> I appreciate your ideas.  They are good ones.
> 
> >the idea of sending videos to local SIGs.
> 
> BayCHI will start lending videos soon.  T'will provide good data.
> 
> Richard
> 
>    __________________________________________________________________
>      Richard I. Anderson, Usability/Design Adventures, 510-524-2421
>            rianderson.chi@xerox.com         riander@well.com
>                 717 Coventry Road, Kensington CA 94707
>                   http://www.well.com/user/riander/
> 
> 
> 


From riander@well.com Tue Oct  8 11:56:29 1996
Return-Path: <riander@well.com>
Received: from mailer.oclc.org (mailer.dev.oclc.org) by oclc.org (4.1/SMI-4.1)
	id AA17504; Tue, 8 Oct 96 11:56:28 EDT
Received: from turing.acm.org by mailer.oclc.org (5.0/SMI-4.1)
	id AA09783; Tue, 8 Oct 1996 11:56:24 +0500
Received: by turing.acm.org; id AA23496; Tue, 8 Oct 1996 11:58:56 -0500
Received: from [206.15.69.18] (sf1-ppp43.well.com [206.15.69.43]) by mh1.well.com (8.7.6/8.7.5) with SMTP id IAA01044; Tue, 8 Oct 1996 08:56:08 -0700 (PDT)
X-Sender: riander@mail.well.com
Message-Id: <v01510103ae80371e0630@[206.15.69.18]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Tue, 8 Oct 1996 09:01:34 -0800
To: Gary PERLMAN <perlman@turing.acm.org>,
        perlman@mailer.oclc.org (Gary PERLMAN)
From: riander@well.com (Richard I. Anderson)
Subject: CHI conference videos for local SIGCHI chapters
Content-Length: 2802
Status: RO

Gary,

Here is another (from a "propsective chapter"):

>From: "Patrick Steiger" <pst@zurich.ibm.com>
>Date: Tue, 8 Oct 1996 09:54:23 +0200
>To: riander@well.com (Richard I. Anderson)
>Subject: CHI conference videos for local SIGCHI chapters
>
>Hi,
>
>I am the librarian of the Swiss SIGCHI Chapter
>(http://www-ir.inf.ethz.ch/SWE/SWE.html).
>
>Our library currently consists of about 10 Books/Proceedings and 20
>HCI-Videos (http://www-ir.inf.ethz.ch/SWE/Library.html).
>
>>    Would your local SIGCHI Chapter like to receive
>>    CHI Conference videos for use in their chapters
>>    (e.g., for lending, or for viewing before meetings)?
>
>        ==> We would appreciate such an offer. We started building up
>this library 10 month ago. It is one of the very valuable offerings to
>our members.
>>
>>    Does your Local SIGCHI Chapter have a circulation
>>    mechanism in place for members to borrow videos
>>    (e.g., a librarian)?
>
>        ==> yes, see http://www-ir.inf.ethz.ch/SWE/Library.html
>>
>>    How far back would your Local SIGCHI Chapter want
>>    to receive CHI Conference videos?  [In 1997, all
>>    conference attendees will receive the conference
>>    video, but that still leaves out many SIGCHI and
>>    Local SIGCHI Chapter members.  Distribution of
>>    CHI'96 videos was much larger than previous years,
>>    but still a small percentage of SIGCHI members,
>>    and distribution of previous years' videos have
>>    been small.  Distribution of older CHI videos
>>    might be a way to rekindle interest in them
>>    (and at a time when SIGCHI is taking over
>>    the CHI videos in the SIGGRAPH Video Review).]
>
>        ==> We still do not have CHI'94 and CHI'95 videos. CHI'96 we
>got since a member visited CHI'96.
>>
>>    What has your Local SIGCHI Chapter been doing with
>>    the CHI Tutorial notes?  Have you any measures
>>    of how much use and what type of use there has been?
>>    Are there successful uses and mechanisms
>>    that you might recommend to all the local SIGs?
>
>        ==> We didn't get yet any CHI Tutorials.
>
>--
>
>----------------------------------------------------------------------
>Patrick Steiger                 Phone:  ++41 1 724 89 42
>IBM Zurich Research Laboratory  Fax:    ++41 1 710 36 08
>Saeumerstrasse 4                E-Mail: pst@zurich.ibm.com
>8803 Rueschlikon/Switzerland    WWW:    http://www.zurich.ibm.com/~pst
>----------------------------------------------------------------------

Richard

   __________________________________________________________________
     Richard I. Anderson, Usability/Design Adventures, 510-524-2421
           rianderson.chi@xerox.com         riander@well.com
                717 Coventry Road, Kensington CA 94707
                  http://www.well.com/user/riander/



From perlman Fri Dec  6 13:31:38 1996
Received: by turing.acm.org; id AA06037; Fri, 6 Dec 1996 13:31:36 -0500
Date: Fri, 6 Dec 1996 13:31:36 -0500
From: Gary PERLMAN <perlman>
Message-Id: <9612061831.AA06037@turing.acm.org>
To: instone@cs.bgsu.edu, perlman@turing.acm.org, riander@well.com
Subject: Re:  space for local sig web page
Status: RO

> Gary & Keith,
> 
> Who should a local sig contact if they would like to obtain space from acm
> for a web page?
> 
> Richard
> (Local SIGs Chair)

Feel free to distribut this, or stick it onto
the local-sigs page (after some editing).

Gary Perlman, ACM SIGCHI Vice-Chair for Publications

ACM is not well organized on this, yet,
so I suggest sending a message to clore@acm.org
(he is the network admin and has all permissions).
Otherwise, requests should go to support@acm.org.

Keep in mind that, for ACM, there is no such thing
as a Local SIG, to ACM, they are called Local Chapters
and are governed by the Local Activities Board.
It explains the use by ACM of the name "chapters"
instead of "Local SIGs".

I suggest that the account application contain:

1. The name and email of the Local Chapter's Information Director.
	Ask for a login on turing.acm.org with in that person's name,
	and any other names of people who will be in that group.
	CC the request to the Chapter Chair, who is the official
	who is allowed to make such requests on a chapter's behalf.
	ACM will respond with the account name and passwords
	when the work is done, not likely when the request is received (:-().
2. The name of the chapter home directory and group alias,
	which I recommend be the same lower case name for simplicity.
	The home dir of the chapter will be created owned by
	the information director in the chapter's group.
	For example, buckchi is in:
		/acminfo/1/chapters/buckchi
	and their infodir owns the directory.
	The URL for this directory is:
		http://www.acm.org/chapters/buckchi/
3. I recommend that as part of the request,
	the chapter ask for a http server link from
		http://www.acm.org/buckchi/ -> http://www.acm.org/chapters/buckchi/
	so they can advertise a shorter URL

I highly recommend putting extra effort into submitting
a numbered list of requests.  A paragraph of requests
may only have one item addressed (for example, buckchi's
request 3 was buried and has still not been done).

Chapter infodirs should be familiar with UNIX, ftp, and HTML.
They might take a look at the SIGCHI InfoDir page,
which has links to what SIGCHI and ACM has done.
	http://www.acm.org/sigchi/infodir/

In addition to web pages, I recommend using the ACM listserv
for a variety of lists:
	BuckCHI-Chair
	BuckCHI-Officers
	BuckCHI-Steering
	BuckCHI-Members
	BuckCHI-Events
Bu this request can be done independently.
Like SIGCHI, which uses CHI- for their list prefix,
I recommend a standard prefix, so that a request of:
	LISTS
to listserv@acm.org will come back with all the chapter
lists in the same place.  I hope to soon have instructions
for Local Chapters to help them set up mailing lists.
I recommend using the same prefix for the lists as the
group name for the web page.

From <@explorer.dgp.toronto.edu:hunt@dgp.toronto.edu> Thu Dec 19 12:59:36 1996
Received: from mercury.dgp.dgp.toronto.edu ([128.100.4.4]) by explorer.dgp.toronto.edu with SMTP id <144011>; Thu, 19 Dec 1996 13:01:59 -0500
Received: by mercury.dgp.dgp.toronto.edu (SMI-8.6/SMI-SVR4)
	id NAA18557; Thu, 19 Dec 1996 13:01:40 -0500
Date: 	Thu, 19 Dec 1996 13:01:40 -0500
Message-Id: <199612191801.NAA18557@mercury.dgp.dgp.toronto.edu>
From: William Hunt <hunt@dgp.toronto.edu>
To: riander@well.com
Subject: info regarding ToRCHI local chapter alias
Cc: Gary PERLMAN <perlman@turing.acm.org>
Status: R


> 1. Is the information alias name tentatively chosen okay?

Yes,  the alias  CHI-ToRCHI  for Toronto, Ontario SIGCHI is fine.


> 2. a. Who at each local SIG will serve as this alias owner?

The current Information Director is:  William Hunt  and he will
currently serve as the alias owner.


>    b. What is the email address FROM which they send mail?
>       (that address is used by the listserv to identify owners)

Most of William's mailing comes from:  hunt@dgp.utoronto.ca  or
                                       hunt@dgp.toronto.edu

The ToRCHI mail comes from:            torchi@itrc.on.ca


William Hunt
-- 
email: hunt@dgp.toronto.edu
phone: 416 978-1531
  fax: 416 978-5184
  URL: www.dgp.utoronto.ca/~hunt


From riander@well.com Sat Dec 21 10:10:01 1996
Received: from [206.15.68.47] (pm1-ppp47.well.com [206.15.68.47]) by mh1.well.com (8.7.6/8.7.5) with SMTP id HAA21267 for <perlman@turing.acm.org>; Sat, 21 Dec 1996 07:12:28 -0800 (PST)
X-Sender: riander@mail.well.com
Message-Id: <v01510102aee1ae225b76@[206.15.68.51]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Sat, 21 Dec 1996 07:14:43 -0800
To: Gary PERLMAN <perlman@turing.acm.org>
From: riander@well.com (Richard I. Anderson)
Subject: Re: we need some info regarding YOUR new local chapter alias
Status: RO

Gary,

>I am gathering the info as you send it,
>but it would help me if you could send the whole message header
>so that I can better determine the actual mail address.
>For example, I am not sure if I must use:
>woodl@acd1.byu.edu (Larry Wood) or woodl@byu.edu (Larry Wood)
>for the following.

Of course, you are assuming that the person responding is using the actual
address he or she wants used for the owner.  That may not be true, yes?

Here are the full responses with headers (this includes a new one not yet
sent to you):

====================
Date: Fri, 20 Dec 1996 09:22:15 -0800 (PST)
From: balazs schreil <hcpsy007@email.csun.edu>
X-Sender: hcpsy007@csun2.csun.edu
To: "Richard I. Anderson" <riander@well.com>
Subject: Re: we need some info regarding YOUR new local chapter alias
Mime-Version: 1.0

Hi Richard;


For each local SIG, we need to know:
 1. Is the information alias name tentatively chosen (see below) okay?
 2. a. Who at each local SIG will serve as this alias owner?
    b. What is the email address FROM which they send mail?
       (that address is used by the listserv to identify owners)

The alias chosen is fine, I will serve as the alias owner, and the email
address is bluejay@csun.edu

Thnax,

Balazs
====================
Date: Thu, 19 Dec 1996 14:39:51 -0600
From: Larry Wood <woodl@byu.edu>
Subject: Re: we need some info regarding YOUR new local chapter alias
X-Sender: woodl@acd1.byu.edu
To: riander@well.com (Richard I. Anderson)
MIME-version: 1.0

Richard,
>
>For each local SIG, we need to know:
> 1. Is the information alias name tentatively chosen (see below) okay?

Yes, CHI-NUCHI is fine.

> 2. a. Who at each local SIG will serve as this alias owner?

Larry Wood

>    b. What is the email address FROM which they send mail?
>       (that address is used by the listserv to identify owners)

WoodL@byu.edu

- Larry Wood
====================
From: wixon@orion.ENET.dec.com
Date: Thu, 19 Dec 96 16:23:12 EST
To: riander@well.com
Cc: wixon@orion.ENET.dec.com
Apparently-To: riander@well.com
Subject: RE: we need some info regarding YOUR new local chapter alias

Hi Richard,

GBSIGCHI is a fine alias for us.

I will own alias.

Dennis
====================



Richard

   __________________________________________________________________
     Richard I. Anderson, Usability/Design Adventures, 510-524-2421
    riander@well.com  rianderson.chi@xerox.com rianderson@baychi.org
                 717 Coventry Road, Kensington CA 94707
                   http://www.well.com/user/riander/



From riander@well.com Sun Dec 22 08:17:19 1996
Received: from [206.15.68.62] (pm1-ppp62.well.com [206.15.68.62]) by mh1.well.com (8.7.6/8.7.5) with SMTP id RAA28569 for <perlman@turing.acm.org>; Sat, 21 Dec 1996 17:54:40 -0800 (PST)
X-Sender: riander@mail.well.com
Message-Id: <v01510101aee245cb61a1@[206.15.68.62]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Sat, 21 Dec 1996 17:56:55 -0800
To: Gary PERLMAN <perlman@turing.acm.org>
From: riander@well.com (Richard I. Anderson)
Subject: Re: we need some info regarding YOUR new local chapter alias
Status: R

>Please send back the following with the name of the chapter.
>
>Gary
>
>> Date: Fri, 20 Dec 1996 09:22:15 -0800 (PST)
>> From: balazs schreil <hcpsy007@email.csun.edu>
>> X-Sender: hcpsy007@csun2.csun.edu
>> To: "Richard I. Anderson" <riander@well.com>
>> Subject: Re: we need some info regarding YOUR new local chapter alias
>> Mime-Version: 1.0
>>
>> Hi Richard;
>>
>>
>> For each local SIG, we need to know:
>>  1. Is the information alias name tentatively chosen (see below) okay?
>>  2. a. Who at each local SIG will serve as this alias owner?
>>     b. What is the email address FROM which they send mail?
>>        (that address is used by the listserv to identify owners)
>>
>> The alias chosen is fine, I will serve as the alias owner, and the email
>> address is bluejay@csun.edu
>>
>> Thnax,
>>
>> Balazs

Los Angeles

Richard

   __________________________________________________________________
     Richard I. Anderson, Usability/Design Adventures, 510-524-2421
    riander@well.com  rianderson.chi@xerox.com rianderson@baychi.org
                 717 Coventry Road, Kensington CA 94707
                   http://www.well.com/user/riander/



From KDELAERE@CSI.compuserve.com Thu Dec 26 22:45:43 1996
Received: from mail.cis.ohio-state.edu (mail.cis.ohio-state.edu [164.107.8.55]) by mail.acm.org (8.7.5/8.7.5) with SMTP id WAA21464 for <perlman@acm.org>; Thu, 26 Dec 1996 22:45:41 -0500
Received: from hil-img-4.compuserve.com (hil-img-4.compuserve.com [149.174.177.134]) by mail.cis.ohio-state.edu (8.6.7/8.6.4) with ESMTP id WAA28213 for <perlman@archive.cis.ohio-state.edu>; Thu, 26 Dec 1996 22:48:25 -0500
Received: by hil-img-4.compuserve.com (8.6.10/5.950515)
	id WAA11677; Thu, 26 Dec 1996 22:48:15 -0500
Date: 26 Dec 96 22:46:37 EST
From: Kevin De Laere <KDELAERE@CSI.compuserve.com>
To: "'Richard I. Anderson'" <riander@well.com>,
        "'Gary Perlman'" <perlman@cis.ohio-state.edu>
Subject: RE: we need some info regarding YOUR new local chapter alias
Message-Id: <CSI_6297-76838@CompuServe.COM>
Status: R

Richard, 

in reply to your letter about Chapter aliases:

1.  The proposed chapter alias 'CHI-BuckCHI' is fine.

2. I, as Info Director, will be the list owner, and the address of the owner is
'kdelaere@csi.compuserve.com' but I guess you already know this.
___________________
Kevin H. De Laere
Human Factors Specialist
CompuServe, Inc.
http://kdelaere.inhouse.compuserve.com:2000/
1.614.798.3199

"Man should continually strive for what is just outside his grasp"


From riander@well.com Thu Dec 19 10:46:42 1996
Received: from [206.15.68.68] (pm1-ppp68.well.com [206.15.68.68]) by mh1.well.com (8.7.6/8.7.5) with SMTP id HAA10438; Thu, 19 Dec 1996 07:48:59 -0800 (PST)
X-Sender: riander@mail.well.com
Message-Id: <v01510100aedf09292214@[206.15.68.66]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Thu, 19 Dec 1996 07:51:12 -0800
To: local-sigs.chi@xerox.com
From: riander@well.com (Richard I. Anderson)
Subject: we need some info regarding YOUR new local chapter alias
Cc: Gary PERLMAN <perlman@turing.acm.org>
Status: RO

Hi,

The SIGCHI electronic mailing lists will be moving from Xerox to the new
ACM listserv sometime soon, and all existing list and alias names will
change in the process.  This affects your local chapter, since your local
chapter may now have a .chi@xerox.com alias (which will be going away) and
will have a new alias.  This alias is (to be) used by people trying to
contact someone or more "in charge" at a local chapter or someone or more
others who have been designated as an information contact point.

With the new listserv, YOU will be able to control who gets mail sent to
YOUR information alias, via a few commands in email messages to
listserv@acm.org.  Note that all local SIG information aliases will be
maintained by SIGCHI and displayed/used on the SIGCHI Local-SIGs page
(http://www.acm.org/sigchi/local-sigs/) as well as be published in the
SIGCHI Bulletin.  (All chartered ACM Local SIGCHI Chapters will also be
provided with the ability to create ADDITIONAL mailing lists and mail
aliases, such as for members, for the steering committee, ...; more on
these in the future.)

For each local SIG, we need to know:
 1. Is the information alias name tentatively chosen (see below) okay?
 2. a. Who at each local SIG will serve as this alias owner?
    b. What is the email address FROM which they send mail?
       (that address is used by the listserv to identify owners)

Each information alias can point to one or more email addresses.  Hence,
the alias owner is actually a mailing list owner.  However, we suspect that
most of these aliases will point to just one address.


1. Your local SIG's information alias name.

Proposed names for local SIG aliases are listed in:

        http://www.acm.org/sigchi/listserv/email.htm#LOCALSIG

However, here is that list of proposed aliases (chartered and prospective
chapters mixed together, with each alias to be followed by "@acm.org" to
complete the email address):

    Alias Name:      Corresponding Local Chapter:
        CHI-BayCHI       San Francisco Bay Area SIGCHI
        CHI-BuckCHI      Central Ohio SIGCHI
        CHI-CapCHI       Ottawa, Ontario SIGCHI
        CHI-CHIFOO       Portland, Oregon SIGCHI
        CHI-GBSIGCHI     Greater Boston Area SIGCHI
        CHI-Iowa         Central Iowa SIGCHI
        CHI-Italy        Italy SIGCHI
        CHI-KC-CHI       Kansas City, Missouri SIGCHI
        CHI-Knoxville    Knoxville, Tennessee SIGCHI
        CHI-LACHI        Los Angeles, California SIGCHI
        CHI-LoneStar     Dallas/Ft. Worth SIGCHI
        CHI-MosCHI       Moscow SIGCHI
        CHI-Netherlands  Netherlands SIGCHI
        CHI-NUCHI        Northern Utah SIGCHI
        CHI-NYCHI        New York City SIGCHI
        CHI-Paris        Paris SIGCHI
        CHI-PSCHI        Puget Sound (Seattle, Washington) SIGCHI
        CHI-Puebla       Puebla SIGCHI
        CHI-St-Louis     St. Louis SIGCHI
        CHI-Switzerland  Switzerland SIGCHI
        CHI-ToRCHI       Toronto, Ontario SIGCHI
        CHI-Toulouse     Toulouse SIGCHI
        CHI-TriCHI       NC Triangle SIGCHI

Is the alias name chosen for your local SIG (see above list) okay with your
chapter?  It is relatively hard to change the alias name after it's
created, but any other attributes (where mail is sent, alias owners, etc.)
can be changed easily.

(As stated earlier, these aliases will be listed by SIGCHI as points of
contact for Local SIGCHI Chapters, and mail to these addresses would be
forwarded to whomever the Local SIGs chose.)


2. Your local SIG's alias owner.

Who at your Local SIG will serve as the alias owner?  That person will need
to learn a few commands and make sure that the alias points to the right
address(es).  What is the email address from which he or she will work (see
example below for some words about this email address)?

Here is an example.

BuckCHI has an Information Director, and his name is Kevin De Laere.
Suppose Kevin's email address was kdelaere@compuserve.com, but that when he
sent mail, it was apparently from kdelaere@csi.compuserve.com.  We need
Kevin's "apparent" address so that the listserv will recognize the sender
as someone with special authority.

The alias owner will be allowed to add or delete users pointed to by the
alias.   For example, Kevin might make make himself the contact point on
the SIGCHI Local-SIGs page:

     add    chi-BuckCHI kdelaere@csi.compuserve.com Kevin De Laere

and later decide to change it to the Membership Chair:

     delete chi-BuckCHI kdelaere@csi.compuserve.com
     add    chi-BuckCHI rbran@aol.com Russ Branaghan

Further info about these commands will be provided to each information
alias owner.


Please provide answers to these questions ASAP but no later than January
15, 1997.

Gary Perlman, ACM SIGCHI Vice-Chair for Publications
Richard Anderson, ACM SIGCHI Adjunct Chair for Local SIGs



From riander@well.com Fri Jan  3 14:45:40 1997
Received: from [206.15.68.52] (pm2-ppp78.well.com [206.15.68.78]) by mh1.well.com (8.7.6/8.7.5) with SMTP id LAA00422 for <perlman@turing.acm.org>; Fri, 3 Jan 1997 11:48:35 -0800 (PST)
X-Sender: riander@mail.well.com
Message-Id: <v0151010baef311599345@[206.15.68.52]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Fri, 3 Jan 1997 11:51:14 -0800
To: Gary PERLMAN <perlman@turing.acm.org>
From: riander@well.com (Richard I. Anderson)
Subject: Re: we need some info regarding YOUR new local chapter alias
Status: RO

Date: Fri, 3 Jan 1997 11:12:01 PST
To: riander@well.com
Subject: Re: we need some info regarding YOUR new local chapter alias
Cc: la-chi-council@hesp.es.xerox.com
From: Bruce Hamilton <bhami@hesp.es.xerox.com>
Reply-To: bhami@hesp.es.xerox.com
X-Sun-Charset: US-ASCII

> 1. Is the information alias name tentatively chosen (CHI-LACHI) okay?
> 2. a. Who at each local SIG will serve as this alias owner?
>    b. What is the email address FROM which they send mail?
>       (that address is used by the listserv to identify owners)
>

Balazs Schreil <hcpsy007@email.csun.edu> is the chapter President.  Unless
you hear differently from him:

1. Yes

2.a. Bruce Hamilton
  b. bhami@hesp.es.xerox.com


--Bruce  <bhami@hesp.es.xerox.com>  310-333-3538
fax: 310-333-6898

   __________________________________________________________________
     Richard I. Anderson, Usability/Design Adventures, 510-524-2421
    riander@well.com  rianderson.chi@xerox.com rianderson@baychi.org
                 717 Coventry Road, Kensington CA 94707
                   http://www.well.com/user/riander/



From riander@well.com Fri Jan  3 17:43:49 1997
Received: from [206.15.68.52] (pm1-ppp54.well.com [206.15.68.54]) by mh1.well.com (8.7.6/8.7.5) with SMTP id OAA02749 for <perlman@TURING.ACM.ORG>; Fri, 3 Jan 1997 14:46:47 -0800 (PST)
X-Sender: riander@mail.well.com
Message-Id: <v0151010faef33c93bb17@[206.15.68.52]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Fri, 3 Jan 1997 14:49:23 -0800
To: Gary PERLMAN <perlman@TURING.ACM.ORG>
From: riander@well.com (Richard I. Anderson)
Subject: RE: we need some info regarding YOUR new local chapter alias
Status: RO

From: "Dieken, Lisa J." <DIEKENLJ@phibred.com>
To: "'riander@well.com'" <riander@well.com>
Subject: RE: we need some info regarding YOUR new local chapter alias
Date: Fri, 3 Jan 1997 15:54:36 -0600
MIME-Version: 1.0

>
> 1. Is the information alias name tentatively chosen (see below) okay?
>        CHI-Iowa     is fine.

> 2. a. Who at each local SIG will serve as this alias owner?
           Lisa Dieken
>    b. What is the email address FROM which they send mail?
>       (that address is used by the listserv to identify owners)
        diekenlj@phibred.com

>

   __________________________________________________________________
     Richard I. Anderson, Usability/Design Adventures, 510-524-2421
    riander@well.com  rianderson.chi@xerox.com rianderson@baychi.org
                 717 Coventry Road, Kensington CA 94707
                   http://www.well.com/user/riander/



From perlman Sun Jan  5 10:47:24 1997
Received: by turing.acm.org; id AA02254; Sun, 5 Jan 1997 10:47:24 -0500
Date: Sun, 5 Jan 1997 10:47:24 -0500
From: Gary PERLMAN <perlman>
Message-Id: <9701051547.AA02254@turing.acm.org>
To: riander@well.com
Subject: Re: chi-eec information
Cc: perlman
Status: R

Hi Richard,

I have info for the following six local chapters:

	Toronto, Ontario SIGCHI, Canada chi-ToRCHI@acm.org
	hunt@dgp.utoronto.ca (William Hunt)
	--
	Central Ohio SIGCHI, USA chi-BuckCHI@acm.org
	kdelaere@csi.compuserve.com (Kevin De Laere)
	--
	Central Iowa, USA chi-Iowa@acm.org
	diekenlj@phibred.com (Lisa Dieken)
	--
	Greater Boston Area SIGCHI, USA chi-GBSIGCHI@acm.org
	wixon@orion.ENET.dec.com (Dennis Wixon)
	--
	Los Angeles, California  SIGCHI, USA chi-LACHI@acm.org
	bhami@hesp.es.xerox.com (Bruce Hamilton)
	hcpsy007@email.csun.edu (Balazs Schreil)
	bluejay@csun.edu (Balazs Schreil)
	--
	Northern Utah SIGCHI, USA chi-NUCHI@acm.org
	woodl@acd1.byu.edu (Larry Wood)
	woodl@byu.edu (Larry Wood)
	--

For some, I decided to use more than one address so that they would be
sure to have list owner permissions -- no big deal, I think.
The real problem is that most of the others have not responded.
Given that it is pretty easy to handle the one or two subscriptions
for each of the local sig aliases, I suggest that you be the owner of
all the aliases and change the alias when appropriate, along with
other contact info as it changes.  I think you would have to manage
some of the aliases anyway, and after the initial setup, which I
could do for you, you would only need to do commands like:
	delete chi-buckchi *
	add chi-buckchi delaere@csi.compuserve.com (Kevin De Laere)
to clear out a list and add the new alias(es).  This would not
preclude adding chapter reps as owners, but I think I'd rather
not have to worry about training many list owners.

Since you already have contact email addresses for the chapters,
creating an initial list of aliases should be easy.
The main bottleneck that I see is the name issue;
we have been asking the chapters to approve the names
(so far with no complaints).  I propose sending mail to
the remaining chapters and just ask for their okay on the name,
and tell them that you will be the owner but they could add
their own secondary owners, if they like.  Okaying the name
should not take long, right?

Gary Perlman, ACM SIGCHI Vice-Chair for Publications

From fcosta@ercole.iesi.ba.cnr.it Tue Jan 14 11:36:13 1997
Received: from ercole.iesi.ba.cnr.it by area.ba.cnr.it (5.65/1.1.10.5/02Sep96-0553PM)
	id AA01892; Tue, 14 Jan 1997 17:34:28 +0100
Received: from costa.uniba.it by ercole.iesi.ba.cnr.it; (5.65/1.1.8.2/28Mar96-1016PM)
	id AA16987; Tue, 14 Jan 1997 17:34:05 +0100
Date: Tue, 14 Jan 1997 17:34:05 +0100
Message-Id: <9701141634.AA16987@ercole.iesi.ba.cnr.it>
From: "Maria Francesca Costabile"  <fcosta@ercole.iesi.ba.cnr.it>
Reply-To: "Maria Francesca Costabile"  <fcosta@ercole.iesi.ba.cnr.it>
To: riander@well.com
Cc: perlman@turing.acm.org
Subject: info on local chapter alias
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Mailer: POPmail 2.3b6
Status: RO

Dear Richard, 
here are the answers to your questions:


> For each local SIG, we need to know:
>  1. Is the information alias name tentatively chosen (see below) okay?
>  2. a. Who at each local SIG will serve as this alias owner?
>     b. What is the email address FROM which they send mail?
       (that address is used by the listserv to identify owners)

>    Alias Name:      Corresponding Local Chapter:
>        CHI-BayCHI       San Francisco Bay Area SIGCHI
>        CHI-BuckCHI      Central Ohio SIGCHI
>        CHI-CapCHI       Ottawa, Ontario SIGCHI
>        CHI-CHIFOO       Portland, Oregon SIGCHI
>        CHI-GBSIGCHI     Greater Boston Area SIGCHI
>        CHI-Iowa         Central Iowa SIGCHI
>        CHI-Italy        Italy SIGCHI

CHi-Italy is OK for the Italian Chapter


> 2. Your local SIG's alias owner.

I will personally work and send mail from my address 

fcosta@ercole.iesi.ba.cnr.it


If you need further information, please, do not hesitate to contact me.

Regards.

Maria Francesca Costabile






Maria Francesca COSTABILE
Dipartimento di Informatica
Universita' di Bari
Via Orabona 4
70125 Bari, Italy

Tel. +39 80 5443300  Fax +39 80 5443300 or +39 80 5443196
e-mail fcosta@iesi.ba.cnr.it


From perlman Wed Jan 15 14:09:01 1997
Received: by turing.acm.org; id AA24190; Wed, 15 Jan 1997 14:08:52 -0500
From: Gary PERLMAN <perlman>
Message-Id: <9701151908.AA24190@turing.acm.org>
Subject: Re: we need some info regarding YOUR new local chapter alias
To: Michel.Beaudouin-Lafon@lri.fr (Michel Beaudouin-Lafon)
Date: Wed, 15 Jan 1997 14:08:52 -0500 (EST)
Cc: riander@well.com, perlman
In-Reply-To: <199701151556.QAA06549@sun2.lri.fr> from "Michel Beaudouin-Lafon" at Jan 15, 97 04:56:05 pm
X-Mailer: ELM [version 2.4 PL25]
Content-Type: text
Content-Length: 1469      
Status: O

Will there be a separate chapter for chi-Paris?
That is, do we need both chi-France and chi-Paris?
If you want people to be able to contact Paris only,
then I think you need (or at least coouyld use) both.

Please get back to us so that the local-sigs page can be updated.
Then, I'll set up the lists.

Will Toulouse agree to this?
They have not responded yet to the previous request,
but I don't see why they would complain.

Option 3: have only chi-France with mail
	redirected to designees of both Paris and Toulouse
	(and ....).

> Hi,
> 
> Sorry for not answering your e-mail earlier.
> 
> As you know, we are in the process of establishing a French chapter
> instead of the Paris chapter, of which the Toulouse chapter would be 
> a "branch".
> 
> Therefore it seems more appropriate to have CHI-France
> rather than CHI-Paris as alias.
> 
> CHI-France would point to
> 	- me (mbl@lri.fr or Michel.Beaudouin-Lafon@lri.fr)
> 	- CHI-Toulouse
> and other French local SIGs that may be created in the future.
> 
> The alias owner for CHI-France should be me:
> 	Michel.Beaudouin-Lafon@lri.fr
> 
> Let me know if you see any problem with this,
> 
> cheers,
> michel
> 
> 
>    ___    0  Michel Beaudouin-Lafon        e-mail: mbl@lri.fr
>   /   \  /   LRI - Bat 490                 www   : http://www-ihm.lri.fr/~mbl
>  /  __/ /    Universite de Paris-Sud       voice : +33 (0)1 69 15 69 10
> /__   \/     91 405 ORSAY Cedex - FRANCE   fax   : +33 (0)1 69 15 65 86
> 


From perlman Thu Jan 16 23:16:49 1997
Received: by turing.acm.org; id AA31157; Thu, 16 Jan 1997 23:16:48 -0500
Date: Thu, 16 Jan 1997 23:16:48 -0500
From: Gary PERLMAN <perlman>
Message-Id: <9701170416.AA31157@turing.acm.org>
To: chi-local-sigs@acm.org
Subject: Welcome to CHI-Local-SIGs@acm.org - Respond by January 28!
Cc: perlman
Status: RO

I am pleased to announce the creation of:
	chi-local-sigs@acm.org
This mailing list should reach all contacts at all
chartered and forming local SIGCHI chapters.
Your list owner is Richard Anderson, the SIGCHI
Adjunct Chair for Local SIGs (riander@well.com),
but I will be sticking around for a while
during the transition from the xerox.com list to ACM.

The first order of business is to finish the creation
of the SIGCHI service aliases to reach the contracts
at individual chapters.  We have tried to do this,
with limited success, so I will try again.

SIGCHI wants to maintain an alias for each local chapter
to put on its local-sigs page so that prospective members
can contact someone at the chapter (often the chair,
but maybe the membership chair, or someone else).
For example, SIGCHI will be creating chi-BuckCHI@acm.org,
which will reach a person of BuckCHI's choosing.
BuckCHI, as a chartered local chapter, can make its
own lists and aliases on the ACM listserv,
and SIGCHI can help with that process if necessary.

The most difficult thing to change is the name of the alias
(e.g., chi-BuckCHI) because it involves ACM staff
hand-tweaking the LISTSERV setup.  Listowners, recipients,
chapter title, and options are easy for us to change.

So, all we need right now is for you to okay the NAME
of the alias SIGCHI will maintain to contact you.
In the following list, a "." in column 1 means
you have already approved the name.
All others should reply to me by Tuesday, January 28.
I will send in the requests for the aliases on January 29.

  ALIAS NAME          CHAPTER TITLE
  chi-BayCHI          San Francisco Bay Area
. chi-BuckCHI         Central Ohio
  chi-CapCHI          Ottawa, Ontario
  chi-CHIFOO          Portland, Oregon
. chi-France          France
. chi-GBSIGCHI        Greater Boston Area
. chi-Iowa            Central Iowa
. chi-Italy           Italian (Bari)
  chi-KC-CHI          Kansas City, Missouri
  chi-Knoxville       Knoxville, Tennessee
. chi-LACHI           Los Angeles, California 
  chi-LoneStar        Dallas/Ft. Worth
  chi-MosCHI          Moscow
  chi-Netherlands     Netherlands
. chi-NUCHI           Northern Utah
  chi-NYCHI           New York City
  chi-PSCHI           Puget Sound (Seattle, Washington)
  chi-Puebla          Puebla
  chi-St-Louis        St. Louis, Missouri       (no, it can't be St.Louis)
  chi-Switzerland     (Zurich) Switzerland
  chi-ToRCHI          Toronto, Ontario
  chi-Toulouse        Toulouse
  chi-TriCHI          NC Triangle

Gary Perlman, ACM SIGCHI Vice-Chair for Publications

From riander@well.com Mon Jan 20 17:08:42 1997
Received: from [206.15.68.69] (pm1-ppp57.well.com [206.15.68.57]) by mh1.well.com (8.7.6/8.7.5) with SMTP id OAA12603 for <perlman@turing.acm.org>; Mon, 20 Jan 1997 14:08:43 -0800 (PST)
X-Sender: riander@mail.well.com
Message-Id: <v01510105af098e20d07b@[206.15.68.69]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Mon, 20 Jan 1997 14:07:41 -0800
To: Gary PERLMAN <perlman@turing.acm.org>
From: riander@well.com (Richard I. Anderson)
Subject: listserv
Status: RO

Gary,

I'm trying to get caught up on this listserv stuff, and I find myself very
quickly lost and trying to motivate myself to decipher contents of long
files of stuff written for people who think very differently than I.  (That
is a diplomatic way of saying that my experience of use of this stuff is
pretty equal to that reported by CHIFOO's Jenny Greenleaf; if you don't
remember, that is a NEGATIVE experience of use.)

I'm left not clear on what I need to do.

A specific question: are the present contents of chi-local-sigs NOT just a
collection of all of the mailing aliases (i.e., lists) for the individual
local sigs?  Since the list is already pretty exhaustive, I gather that
chi-local-sigs is NOT a collection of all of the mailing aliases, because I
was under the impression that you hadn't created any for those local sigs
that hadn't yet responded to the alias queries.  If this is true, then my
question becomes: shouldn't chi-local-sigs BE just the collection of the
individual local aliases/lists?

I'm sorry I get confused by all of this, but...

Note that Pat Sachs ("heading" the local sig effort in NYC) has no email
address.  So, ...

Richard

P.S. Here is a response to the alias query that you might not have
received.  It is followed by a related message that you may have received
(??????).

======================
From: Peter Szmyt <SZMYT@simware.com>
To: riander <riander@well.com>
Subject: RE: we need some info regarding YOUR new local chapter alias
Date: Mon, 06 Jan 97 15:22:00 EST
Encoding: 32 TEXT


>>It appears that the local-sigs.chi@xerox.com mailing list isn't
up-to-date,
so here is a resend using my own mailing list.  My apologies if you
receive
two copies of this email.<<

i got both copies.

>> 1. Is the information alias name tentatively chosen (see below)
okay?<<

CHI-CapCHI is fine for our chapter.


>> 2. a. Who at each local SIG will serve as this alias owner?<<
peter@acm.org

>>  b. What is the email address FROM which they send mail?<<
peter@acm.org

peter
__________________________________________________________________________

Peter Szmyt, Chair, Ottawa ACM SIGCHI
http://ksl1000.ai.iit.nrc.ca/capchi/
Email: peter@acm.org  Phone: 613.228.5100 x4029  Fax: 613.727.9409
Simware, 2 Gurdwara Road, Ottawa, Ontario, Canada, K2E 1A2

====================================

Date:         Mon, 20 Jan 1997 12:35:57 -0500
From: "L-Soft list server at ACM (1.8b)" <LISTSERV@ACM.ORG>
Subject:      CHI-LOCAL-SIGS: error report from SIMWARE.COM
To: "Richard I. Anderson (Local-SIGs)" <RIANDER@well.com>
X-LSV-ListID: None

The enclosed mail  file has been identified as a  delivery error for list
CHI-LOCAL-SIGS because it was sent to the reserved 'owner-chi-local-sigs'
mailbox.

------------------------------ Message in error -------------------------------
Received: from SIMWARE.COM (vm.simware.com [198.53.208.20]) by mail.acm.org
          (8.7.5/8.7.5) with SMTP id MAA33076 for
          <owner-chi-local-sigs@ACM.ORG>; Mon, 20 Jan 1997 12:35:55 -0500
Received: from msmail.simware.com by SIMWARE.COM (IBM VM SMTP V2R3) with TCP;
   Mon, 20 Jan 97 12:35:40 EST
Received: by msmail.simware.com with Microsoft Mail
        id <32E3ACFB@msmail.simware.com>; Mon, 20 Jan 97 12:35:55 EST
From: Peter Szmyt <SZMYT@simware.com>
To: owner-chi-local-sigs <owner-chi-local-sigs>
Subject: RE: Welcome to CHI-Local-SIGs@acm.org - Respond by January 28!
Date: Mon, 20 Jan 97 12:35:00 EST
Message-ID: <32E3ACFB@msmail.simware.com>
Encoding: 14 TEXT
X-Mailer: Microsoft Mail V3.0



  ALIAS NAME          CHAPTER TITLE
  chi-CapCHI          Ottawa, Ontario

this is my acceptance of the above alias for our chapter.

thanks,
peter
__________________________________________________________________________

Peter Szmyt, Chair, Ottawa ACM SIGCHI
http://ksl1000.ai.iit.nrc.ca/capchi/
Email: peter@acm.org  Phone: 613.228.5100 x4029  Fax: 613.727.9409
Simware, 2 Gurdwara Road, Ottawa, Ontario, Canada, K2E 1A2
====================================


   __________________________________________________________________
     Richard I. Anderson, Usability/Design Adventures, 510-524-2421
    riander@well.com  rianderson.chi@xerox.com rianderson@baychi.org
                 717 Coventry Road, Kensington CA 94707
                   http://www.well.com/user/riander/



From riander@well.com Mon Jan 20 17:23:21 1997
Received: from [206.15.68.69] (pm1-ppp59.well.com [206.15.68.59]) by mh1.well.com (8.7.6/8.7.5) with SMTP id OAA15862 for <perlman@turing.acm.org>; Mon, 20 Jan 1997 14:23:24 -0800 (PST)
X-Sender: riander@mail.well.com
Message-Id: <v01510109af09a00f0742@[206.15.68.69]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Mon, 20 Jan 1997 14:22:21 -0800
To: Gary PERLMAN <perlman@turing.acm.org>
From: riander@well.com (Richard I. Anderson)
Subject: Re: we need some info regarding YOUR new local chapter alias
Status: RO

Date: Fri, 17 Jan 1997 11:33:12 PST
To: riander@well.com (Richard I. Anderson)
Subject: Re: we need some info regarding YOUR new local chapter alias
From: bobw@lore.kla.com (Bob Weissman)

On Dec 19, 12:10pm -0800, riander@well.com (Richard I. Anderson) wrote:
> For each local SIG, we need to know:
>  1. Is the information alias name tentatively chosen (see below) okay?

Yes, CHI-BayCHI@acm.org is fine.  It should initially point to
our own alias, info@baychi.org.

>  2. a. Who at each local SIG will serve as this alias owner?

I will.

>     b. What is the email address FROM which they send mail?
>        (that address is used by the listserv to identify owners)

I have many addresses.  I most commonly use bobw@lore.kla.com and
weissman@netcom.com.  Do I have to pick one?

== Bob

   __________________________________________________________________
     Richard I. Anderson, Usability/Design Adventures, 510-524-2421
    riander@well.com  rianderson.chi@xerox.com rianderson@baychi.org
                 717 Coventry Road, Kensington CA 94707
                   http://www.well.com/user/riander/



From riander@well.com Mon Jan 20 17:29:16 1997
Received: from [206.15.68.69] (pm1-ppp53.well.com [206.15.68.53]) by mh1.well.com (8.7.6/8.7.5) with SMTP id OAA17241 for <perlman@turing.acm.org>; Mon, 20 Jan 1997 14:29:17 -0800 (PST)
X-Sender: riander@mail.well.com
Message-Id: <v0151010baf09a1074183@[206.15.68.69]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Mon, 20 Jan 1997 14:28:17 -0800
To: Gary PERLMAN <perlman@turing.acm.org>
From: riander@well.com (Richard I. Anderson)
Subject: Re: we need some info regarding YOUR new local chapter alias
Status: RO

Gary,

Please include Jenny Greenleaf as well.  Her email address (from the email
she sent discussing the ui): jennyg@teleport.com

========================
From: Kristine Maneely <krism@bv.ngc.com>
Date: Mon, 6 Jan 1997 17:37:03 -0800
To: riander@well.com
Subject: Re: we need some info regarding YOUR new local chapter alias
Mime-Version: 1.0


> For each local SIG, we need to know:
>  1. Is the information alias name tentatively chosen (see below) okay?

         CHI-CHIFOO       Portland, Oregon SIGCHI
         Yes, this is just fine

>  2. a. Who at each local SIG will serve as this alias owner?

        Kris Maneely

>     b. What is the email address FROM which they send mail?
>        (that address is used by the listserv to identify owners)

        krism@bv.ngc.com (This is what email from me says)
        krism@pobox.com  (This is the forwarding email address I prefer to use)

========================

Richard

   __________________________________________________________________
     Richard I. Anderson, Usability/Design Adventures, 510-524-2421
    riander@well.com  rianderson.chi@xerox.com rianderson@baychi.org
                 717 Coventry Road, Kensington CA 94707
                   http://www.well.com/user/riander/



From riander@well.com Mon Jan 20 18:30:11 1997
Received: from [206.15.68.69] (pm1-ppp50.well.com [206.15.68.50]) by mh1.well.com (8.7.6/8.7.5) with SMTP id PAA00054 for <perlman@turing.acm.org>; Mon, 20 Jan 1997 15:30:11 -0800 (PST)
X-Sender: riander@mail.well.com
Message-Id: <v01510112af09aed17ed4@[206.15.68.69]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Mon, 20 Jan 1997 15:29:10 -0800
To: Gary PERLMAN <perlman@turing.acm.org>
From: riander@well.com (Richard I. Anderson)
Subject: Re: we need some info regarding YOUR new local chapter alias
Status: RO

X-Sender: dianews@pop.mindspring.com
Mime-Version: 1.0
Date: Wed, 15 Jan 1997 08:02:43 -0500
To: riander@well.com
From: Diane Wilson <dewilson@pobox.com>

For the new local SIG mailing list,

1.  The alias for TriCHI (CHI-TriCHI) is fine.
2.  a.  I will be the alias owner for TriCHI.
    b.  Email should appear from dewilson@pobox.com.  It is actually
        sent from dianews@mindspring.com, so the "from" line has the
        dewilson@pobox.com address, while the "X-sender" line has
        dianews@pop.mindspring.com.  See the headers on this message
        if that seems confusing.

If you have questions, please let me know.

Also, (perhaps this is just FYI) we are establishing a web page for
TriCHI; it's at http://www.vrx.net/trichi/ .

Take care,
Diane
--
Diane Wilson, gender renegade         |  What we need is an optimistic
dewilson@pobox.com                    |  Shostakovich.
http://www.lava.net/~dewilson         |             --Shostakovich, quoting
http://www.lava.net/~dewilson/asd/    |               official sources
http://www.lava.net/~dewilson/menace/ |

   __________________________________________________________________
     Richard I. Anderson, Usability/Design Adventures, 510-524-2421
    riander@well.com  rianderson.chi@xerox.com rianderson@baychi.org
                 717 Coventry Road, Kensington CA 94707
                   http://www.well.com/user/riander/



From riander@well.com Tue Jan 28 18:07:57 1997
Received: from [206.15.84.103] (sf3-ppp83.well.com [206.15.84.83])
	by mail.well.com (8.8.5/8.8.5) with SMTP id PAA02421;
	Tue, 28 Jan 1997 15:08:12 -0800 (PST)
X-Sender: riander@mail.well.com
Message-Id: <v01510101af142fb2b215@[206.15.84.103]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Tue, 28 Jan 1997 15:07:30 -0800
To: Gary PERLMAN <perlman@turing.acm.org>
From: riander@well.com (Richard I. Anderson)
Subject: Re: Welcome to CHI-Local-SIGs@acm.org - Respond by January 28!
Status: RO

Gary,

>See:
>        http://www.acm.org/sigchi/listserv/email.htm#LOCALSIG
>and look for a blank done? field. "+" means the list is
>created, and a "." means the list name has been confirmed.
>Sorry for the cryptic format.

If you do not hear anything to the contrary prior to the end of today, please:

 - create chi-KC-CHI (Kansas City, Missouri) with atiritoglu@mjharden.com
   (Alp Tiritoglu) as the owner
 - do NOT create chi-Knoxville (Knoxville, Tennessee)
 - create chi-LoneStar (Dallas/Ft. Worth) with mshurtleff@dfwmm.net (Mark
   Shurtleff) as the owner
 - create chi-MosCHI (Moscow) with enir@icsti.su (Juri Gornostaev) as the
   owner
 - do NOT create chi-NYCHI (New York City)
 - create chi-PSCHI (Puget Sound, Washington) with
   jking@stout.hitl.washington.edu (W. Joseph King) and
   rcburns@atc.boeing.com (Robert C. Burns as the owners
 - create chi-St-Louis (St. Louis, Missouri) with jgrant@cpicorp.com
   (Joe Grant) as the owner
 - create chi-Toulouse (Toulouse, France) with barthet@cict.fr
   (Marie-France Barthet), barthet@mail.univ-tlse1.fr (Marie-France Barthet),
   boy@eurydice.onecert.fr (Guy Boy), and Guy.Boy@onecert.fr (Guy Boy) as
   the owners

Richard

   __________________________________________________________________
     Richard I. Anderson, Usability/Design Adventures, 510-524-2421
       riander@well.com  rianderson@acm.org rianderson@baychi.org
                 717 Coventry Road, Kensington CA 94707
                   http://www.well.com/user/riander/



From riander@well.com Tue Jan 28 18:07:57 1997
Received: from [206.15.84.103] (sf3-ppp83.well.com [206.15.84.83])
	by mail.well.com (8.8.5/8.8.5) with SMTP id PAA02421;
	Tue, 28 Jan 1997 15:08:12 -0800 (PST)
X-Sender: riander@mail.well.com
Message-Id: <v01510101af142fb2b215@[206.15.84.103]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Tue, 28 Jan 1997 15:07:30 -0800
To: Gary PERLMAN <perlman@turing.acm.org>
From: riander@well.com (Richard I. Anderson)
Subject: Re: Welcome to CHI-Local-SIGs@acm.org - Respond by January 28!
Status: RO

Gary,

>See:
>        http://www.acm.org/sigchi/listserv/email.htm#LOCALSIG
>and look for a blank done? field. "+" means the list is
>created, and a "." means the list name has been confirmed.
>Sorry for the cryptic format.

If you do not hear anything to the contrary prior to the end of today, please:

 - create chi-KC-CHI (Kansas City, Missouri) with atiritoglu@mjharden.com
   (Alp Tiritoglu) as the owner
 - do NOT create chi-Knoxville (Knoxville, Tennessee)
 - create chi-LoneStar (Dallas/Ft. Worth) with mshurtleff@dfwmm.net (Mark
   Shurtleff) as the owner
 - create chi-MosCHI (Moscow) with enir@icsti.su (Juri Gornostaev) as the
   owner
 - do NOT create chi-NYCHI (New York City)
 - create chi-PSCHI (Puget Sound, Washington) with
   jking@stout.hitl.washington.edu (W. Joseph King) and
   rcburns@atc.boeing.com (Robert C. Burns as the owners
 - create chi-St-Louis (St. Louis, Missouri) with jgrant@cpicorp.com
   (Joe Grant) as the owner
 - create chi-Toulouse (Toulouse, France) with barthet@cict.fr
   (Marie-France Barthet), barthet@mail.univ-tlse1.fr (Marie-France Barthet),
   boy@eurydice.onecert.fr (Guy Boy), and Guy.Boy@onecert.fr (Guy Boy) as
   the owners

Richard

   __________________________________________________________________
     Richard I. Anderson, Usability/Design Adventures, 510-524-2421
       riander@well.com  rianderson@acm.org rianderson@baychi.org
                 717 Coventry Road, Kensington CA 94707
                   http://www.well.com/user/riander/



From riander@well.com Mon Feb  3 12:44:52 1997
Received: from [206.15.84.82] (sf3-ppp78.well.com [206.15.84.78])
	by mail.well.com (8.8.5/8.8.5) with SMTP id JAA14544
	for <perlman@turing.acm.org>; Mon, 3 Feb 1997 09:45:28 -0800 (PST)
X-Sender: riander@mail.well.com
Message-Id: <v01510103af1bd3640391@[206.15.84.82]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Mon, 3 Feb 1997 09:44:48 -0800
To: Gary PERLMAN <perlman@turing.acm.org>
From: riander@well.com (Richard I. Anderson)
Subject: can CHI-PSCHI be CHI-PSSIGCHI?
Status: RO

Gary,

>From interaction with folks at the Puget Sound chapter:

>>> Lastly, neither I nor Gary Perlman heard from anyone in your chapter
>>> of the acceptability of the new alias for your chapter and about who
>>> the owner of that alias would be. We will just go with the proposed
>>> alias, and I've asked that you and Joey be listed as the owners.
>>
>>I must of missed this also, probably because the email went to Joey
>>alone, as well. What is the proposed alias? We have always used
>>
>>                        PSSIGCHI
>>
>>which is short for Puget Sound SIGCHI. It is okay for Joey and I to
>>be the owners (although I need to know what that means so I can
>>ensure that we live up to the responsibility).
>
>The alias Gary Perlman proposed was CHI-PSCHI@acm.org.  I'll ask that it
>be changed to CHI-PSSIGCHI@acm.org.  (I'm not sure when the new aliases
>will be created, though twas scheduled to have happened by now; I'll
>append our first email about this to this message.)

Richard

   __________________________________________________________________
     Richard I. Anderson, Usability/Design Adventures, 510-524-2421
       riander@well.com  rianderson@acm.org rianderson@baychi.org
                 717 Coventry Road, Kensington CA 94707
                   http://www.well.com/user/riander/



From perlman Mon Feb 10 13:30:38 1997
Received: by turing.acm.org; id AA05044; Mon, 10 Feb 1997 13:30:35 -0500
Date: Mon, 10 Feb 1997 13:30:35 -0500
From: Gary PERLMAN <perlman>
Message-Id: <9702101830.AA05044@turing.acm.org>
Subject: SIGCHI list: chi-ToRCHI creation request
Apparently-To: hunt@dgp.utoronto.ca
Apparently-To: riander@well.com
Apparently-To: perlman@turing.acm.org
Apparently-To: instone@cs.bgsu.edu
Apparently-To: support@acm.org
Status: RO

Please create a new SIGCHI LISTSERV list:
	chi-ToRCHI@acm.org

Please make the password for the list: kate

In addition to the list chi-ToRCHI@acm.org,
please make sure that the forwarding aliases are set up:
	chi-ToRCHI-request@acm.org -> chi-ToRCHI-request@listserv.acm.org
	owner-chi-ToRCHI@acm.org   -> owner-chi-ToRCHI@listserv.acm.org
We realize that the creation of these aliases may generate
some automatic messages-to-members to the list owners.

Note that SIGCHI lists use a dash "-" as delimiter.

Please use the following list header to initialize the options:

* ACM SIGCHI Toronto, Ontario, Canada Local Chapter Information
*
* Owner= riander@well.com (Richard I. Anderson, SIGCHI Local SIGs Chair)
* Owner= Quiet:
* Owner= hunt@dgp.utoronto.ca (William Hunt)
* Owner= perlman@turing.acm.org (Gary Perlman, SIGCHI Email Manager)
* Owner= instone@cs.bgsu.edu (Keith Instone, SIGCHI Information Director)
* Owner= clore@acm.org (Michael Clore, ACM Network Information Manager)
* Errors-To= Owner            Reply-to= Sender,Respect
* Subscription= Closed        Validate= No                Notify= No
* Send= Public                Mail-Via= Distribute        Ack= Yes
* Notebook= No                Digest= No                  Files= No
* Review= Public              Confidential= No
* Default-Options= NoFiles,Repro,Ack

From perlman Mon Feb 10 13:30:39 1997
Received: by turing.acm.org; id AA01227; Mon, 10 Feb 1997 13:30:34 -0500
Date: Mon, 10 Feb 1997 13:30:34 -0500
From: Gary PERLMAN <perlman>
Message-Id: <9702101830.AA01227@turing.acm.org>
Subject: SIGCHI list: chi-CapCHI creation request
Apparently-To: peter@acm.org
Apparently-To: szmyt@simware.com
Apparently-To: riander@well.com
Apparently-To: perlman@turing.acm.org
Apparently-To: instone@cs.bgsu.edu
Apparently-To: support@acm.org
Status: RO

Please create a new SIGCHI LISTSERV list:
	chi-CapCHI@acm.org

Please make the password for the list: kate

In addition to the list chi-CapCHI@acm.org,
please make sure that the forwarding aliases are set up:
	chi-CapCHI-request@acm.org -> chi-CapCHI-request@listserv.acm.org
	owner-chi-CapCHI@acm.org   -> owner-chi-CapCHI@listserv.acm.org
We realize that the creation of these aliases may generate
some automatic messages-to-members to the list owners.

Note that SIGCHI lists use a dash "-" as delimiter.

Please use the following list header to initialize the options:

* ACM SIGCHI Ottawa, Ontario, Canada Local Chapter Information
*
* Owner= riander@well.com (Richard I. Anderson, SIGCHI Local SIGs Chair)
* Owner= Quiet:
* Owner= szmyt@simware.com (Peter Szmyt)
* Owner= peter@acm.org (Peter Szmyt)
* Owner= perlman@turing.acm.org (Gary Perlman, SIGCHI Email Manager)
* Owner= instone@cs.bgsu.edu (Keith Instone, SIGCHI Information Director)
* Owner= clore@acm.org (Michael Clore, ACM Network Information Manager)
* Errors-To= Owner            Reply-to= Sender,Respect
* Subscription= Closed        Validate= No                Notify= No
* Send= Public                Mail-Via= Distribute        Ack= Yes
* Notebook= No                Digest= No                  Files= No
* Review= Public              Confidential= No
* Default-Options= NoFiles,Repro,Ack

From perlman Mon Feb 10 13:30:40 1997
Received: by turing.acm.org; id AA17816; Mon, 10 Feb 1997 13:30:36 -0500
Date: Mon, 10 Feb 1997 13:30:36 -0500
From: Gary PERLMAN <perlman>
Message-Id: <9702101830.AA17816@turing.acm.org>
Subject: SIGCHI list: chi-Toulouse creation request
Apparently-To: Guy.Boy@onecert.fr
Apparently-To: boy@eurydice.onecert.fr
Apparently-To: barthet@mail.univ-tlse1.fr
Apparently-To: barthet@cict.fr
Apparently-To: riander@well.com
Apparently-To: perlman@turing.acm.org
Apparently-To: instone@cs.bgsu.edu
Apparently-To: support@acm.org
Status: RO

Please create a new SIGCHI LISTSERV list:
	chi-Toulouse@acm.org

Please make the password for the list: kate

In addition to the list chi-Toulouse@acm.org,
please make sure that the forwarding aliases are set up:
	chi-Toulouse-request@acm.org -> chi-Toulouse-request@listserv.acm.org
	owner-chi-Toulouse@acm.org   -> owner-chi-Toulouse@listserv.acm.org
We realize that the creation of these aliases may generate
some automatic messages-to-members to the list owners.

Note that SIGCHI lists use a dash "-" as delimiter.

Please use the following list header to initialize the options:

* ACM SIGCHI Toulouse, France Local Chapter Information
*
* Owner= riander@well.com (Richard I. Anderson, SIGCHI Local SIGs Chair)
* Owner= Quiet:
* Owner= barthet@cict.fr (Marie-France Barthet)
* Owner= barthet@mail.univ-tlse1.fr (Marie-France Barthet)
* Owner= boy@eurydice.onecert.fr (Guy Boy)
* Owner= Guy.Boy@onecert.fr (Guy Boy)
* Owner= perlman@turing.acm.org (Gary Perlman, SIGCHI Email Manager)
* Owner= instone@cs.bgsu.edu (Keith Instone, SIGCHI Information Director)
* Owner= clore@acm.org (Michael Clore, ACM Network Information Manager)
* Errors-To= Owner            Reply-to= Sender,Respect
* Subscription= Closed        Validate= No                Notify= No
* Send= Public                Mail-Via= Distribute        Ack= Yes
* Notebook= No                Digest= No                  Files= No
* Review= Public              Confidential= No
* Default-Options= NoFiles,Repro,Ack

From perlman Mon Feb 10 13:30:41 1997
Received: by turing.acm.org; id AA13458; Mon, 10 Feb 1997 13:30:37 -0500
Date: Mon, 10 Feb 1997 13:30:37 -0500
From: Gary PERLMAN <perlman>
Message-Id: <9702101830.AA13458@turing.acm.org>
Subject: SIGCHI list: chi-France creation request
Apparently-To: barthet@cict.fr
Apparently-To: Michel.Beaudouin-Lafon@lri.fr
Apparently-To: mbl@lri.fr
Apparently-To: riander@well.com
Apparently-To: perlman@turing.acm.org
Apparently-To: instone@cs.bgsu.edu
Apparently-To: support@acm.org
Status: RO

Please create a new SIGCHI LISTSERV list:
	chi-France@acm.org

Please make the password for the list: kate

In addition to the list chi-France@acm.org,
please make sure that the forwarding aliases are set up:
	chi-France-request@acm.org -> chi-France-request@listserv.acm.org
	owner-chi-France@acm.org   -> owner-chi-France@listserv.acm.org
We realize that the creation of these aliases may generate
some automatic messages-to-members to the list owners.

Note that SIGCHI lists use a dash "-" as delimiter.

Please use the following list header to initialize the options:

* ACM SIGCHI France Local Chapter Information
*
* Owner= riander@well.com (Richard I. Anderson, SIGCHI Local SIGs Chair)
* Owner= Quiet:
* Owner= mbl@lri.fr (Michel Beaudouin-Lafon)
* Owner= Michel.Beaudouin-Lafon@lri.fr (Michel Beaudouin-Lafon)
* Owner= barthet@cict.fr (Marie-France Barthet)
* Owner= perlman@turing.acm.org (Gary Perlman, SIGCHI Email Manager)
* Owner= instone@cs.bgsu.edu (Keith Instone, SIGCHI Information Director)
* Owner= clore@acm.org (Michael Clore, ACM Network Information Manager)
* Errors-To= Owner            Reply-to= Sender,Respect
* Subscription= Closed        Validate= No                Notify= No
* Send= Public                Mail-Via= Distribute        Ack= Yes
* Notebook= No                Digest= No                  Files= No
* Review= Public              Confidential= No
* Default-Options= NoFiles,Repro,Ack

From perlman Mon Feb 10 13:30:41 1997
Received: by turing.acm.org; id AA00043; Mon, 10 Feb 1997 13:30:37 -0500
Date: Mon, 10 Feb 1997 13:30:37 -0500
From: Gary PERLMAN <perlman>
Message-Id: <9702101830.AA00043@turing.acm.org>
Subject: SIGCHI list: chi-Mexico creation request
Apparently-To: Cleo@udlapvms.pue.udlap.mx
Apparently-To: riander@well.com
Apparently-To: perlman@turing.acm.org
Apparently-To: instone@cs.bgsu.edu
Apparently-To: support@acm.org
Status: RO

Please create a new SIGCHI LISTSERV list:
	chi-Mexico@acm.org

Please make the password for the list: kate

In addition to the list chi-Mexico@acm.org,
please make sure that the forwarding aliases are set up:
	chi-Mexico-request@acm.org -> chi-Mexico-request@listserv.acm.org
	owner-chi-Mexico@acm.org   -> owner-chi-Mexico@listserv.acm.org
We realize that the creation of these aliases may generate
some automatic messages-to-members to the list owners.

Note that SIGCHI lists use a dash "-" as delimiter.

Please use the following list header to initialize the options:

* ACM SIGCHI Mexico (Puebla) Local Chapter Information
*
* Owner= riander@well.com (Richard I. Anderson, SIGCHI Local SIGs Chair)
* Owner= Quiet:
* Owner= Cleo@udlapvms.pue.udlap.mx (Cleotilde Gonzalez)
* Owner= perlman@turing.acm.org (Gary Perlman, SIGCHI Email Manager)
* Owner= instone@cs.bgsu.edu (Keith Instone, SIGCHI Information Director)
* Owner= clore@acm.org (Michael Clore, ACM Network Information Manager)
* Errors-To= Owner            Reply-to= Sender,Respect
* Subscription= Closed        Validate= No                Notify= No
* Send= Public                Mail-Via= Distribute        Ack= Yes
* Notebook= No                Digest= No                  Files= No
* Review= Public              Confidential= No
* Default-Options= NoFiles,Repro,Ack

From perlman Mon Feb 10 13:30:41 1997
Received: by turing.acm.org; id AA19605; Mon, 10 Feb 1997 13:30:38 -0500
Date: Mon, 10 Feb 1997 13:30:38 -0500
From: Gary PERLMAN <perlman>
Message-Id: <9702101830.AA19605@turing.acm.org>
Subject: SIGCHI list: chi-Italy creation request
Apparently-To: fcosta@ercole.iesi.ba.cnr.it
Apparently-To: riander@well.com
Apparently-To: perlman@turing.acm.org
Apparently-To: instone@cs.bgsu.edu
Apparently-To: support@acm.org
Status: RO

Please create a new SIGCHI LISTSERV list:
	chi-Italy@acm.org

Please make the password for the list: kate

In addition to the list chi-Italy@acm.org,
please make sure that the forwarding aliases are set up:
	chi-Italy-request@acm.org -> chi-Italy-request@listserv.acm.org
	owner-chi-Italy@acm.org   -> owner-chi-Italy@listserv.acm.org
We realize that the creation of these aliases may generate
some automatic messages-to-members to the list owners.

Note that SIGCHI lists use a dash "-" as delimiter.

Please use the following list header to initialize the options:

* ACM SIGCHI Italian (Bari) Local Chapter Information
*
* Owner= riander@well.com (Richard I. Anderson, SIGCHI Local SIGs Chair)
* Owner= Quiet:
* Owner= fcosta@ercole.iesi.ba.cnr.it (Maria Francesca Costabile)
* Owner= perlman@turing.acm.org (Gary Perlman, SIGCHI Email Manager)
* Owner= instone@cs.bgsu.edu (Keith Instone, SIGCHI Information Director)
* Owner= clore@acm.org (Michael Clore, ACM Network Information Manager)
* Errors-To= Owner            Reply-to= Sender,Respect
* Subscription= Closed        Validate= No                Notify= No
* Send= Public                Mail-Via= Distribute        Ack= Yes
* Notebook= No                Digest= No                  Files= No
* Review= Public              Confidential= No
* Default-Options= NoFiles,Repro,Ack

From perlman Mon Feb 10 13:30:42 1997
Received: by turing.acm.org; id AA13465; Mon, 10 Feb 1997 13:30:39 -0500
Date: Mon, 10 Feb 1997 13:30:39 -0500
From: Gary PERLMAN <perlman>
Message-Id: <9702101830.AA13465@turing.acm.org>
Subject: SIGCHI list: chi-Netherlands creation request
Apparently-To: steven.pemberton@cwi.nl
Apparently-To: riander@well.com
Apparently-To: perlman@turing.acm.org
Apparently-To: instone@cs.bgsu.edu
Apparently-To: support@acm.org
Status: RO

Please create a new SIGCHI LISTSERV list:
	chi-Netherlands@acm.org

Please make the password for the list: kate

In addition to the list chi-Netherlands@acm.org,
please make sure that the forwarding aliases are set up:
	chi-Netherlands-request@acm.org -> chi-Netherlands-request@listserv.acm.org
	owner-chi-Netherlands@acm.org   -> owner-chi-Netherlands@listserv.acm.org
We realize that the creation of these aliases may generate
some automatic messages-to-members to the list owners.

Note that SIGCHI lists use a dash "-" as delimiter.

Please use the following list header to initialize the options:

* ACM SIGCHI Netherlands Local Chapter Information
*
* Owner= riander@well.com (Richard I. Anderson, SIGCHI Local SIGs Chair)
* Owner= Quiet:
* Owner= steven.pemberton@cwi.nl (Steven Pemberton)
* Owner= perlman@turing.acm.org (Gary Perlman, SIGCHI Email Manager)
* Owner= instone@cs.bgsu.edu (Keith Instone, SIGCHI Information Director)
* Owner= clore@acm.org (Michael Clore, ACM Network Information Manager)
* Errors-To= Owner            Reply-to= Sender,Respect
* Subscription= Closed        Validate= No                Notify= No
* Send= Public                Mail-Via= Distribute        Ack= Yes
* Notebook= No                Digest= No                  Files= No
* Review= Public              Confidential= No
* Default-Options= NoFiles,Repro,Ack

From perlman Mon Feb 10 13:30:43 1997
Received: by turing.acm.org; id AA08559; Mon, 10 Feb 1997 13:30:40 -0500
Date: Mon, 10 Feb 1997 13:30:40 -0500
From: Gary PERLMAN <perlman>
Message-Id: <9702101830.AA08559@turing.acm.org>
Subject: SIGCHI list: chi-Switzerland creation request
Apparently-To: felix@iha.bepr.ethz.ch
Apparently-To: riander@well.com
Apparently-To: perlman@turing.acm.org
Apparently-To: instone@cs.bgsu.edu
Apparently-To: support@acm.org
Status: RO

Please create a new SIGCHI LISTSERV list:
	chi-Switzerland@acm.org

Please make the password for the list: kate

In addition to the list chi-Switzerland@acm.org,
please make sure that the forwarding aliases are set up:
	chi-Switzerland-request@acm.org -> chi-Switzerland-request@listserv.acm.org
	owner-chi-Switzerland@acm.org   -> owner-chi-Switzerland@listserv.acm.org
We realize that the creation of these aliases may generate
some automatic messages-to-members to the list owners.

Note that SIGCHI lists use a dash "-" as delimiter.

Please use the following list header to initialize the options:

* ACM SIGCHI Switzerland (Zurich) Local Chapter Information
*
* Owner= riander@well.com (Richard I. Anderson, SIGCHI Local SIGs Chair)
* Owner= Quiet:
* Owner= felix@iha.bepr.ethz.ch (Daniel Felix)
* Owner= perlman@turing.acm.org (Gary Perlman, SIGCHI Email Manager)
* Owner= instone@cs.bgsu.edu (Keith Instone, SIGCHI Information Director)
* Owner= clore@acm.org (Michael Clore, ACM Network Information Manager)
* Errors-To= Owner            Reply-to= Sender,Respect
* Subscription= Closed        Validate= No                Notify= No
* Send= Public                Mail-Via= Distribute        Ack= Yes
* Notebook= No                Digest= No                  Files= No
* Review= Public              Confidential= No
* Default-Options= NoFiles,Repro,Ack

From perlman Mon Feb 10 13:30:44 1997
Received: by turing.acm.org; id AA14114; Mon, 10 Feb 1997 13:30:41 -0500
Date: Mon, 10 Feb 1997 13:30:41 -0500
From: Gary PERLMAN <perlman>
Message-Id: <9702101830.AA14114@turing.acm.org>
Subject: SIGCHI list: chi-BayCHI creation request
Apparently-To: weissman@netcom.com
Apparently-To: bobw@lore.kla.com
Apparently-To: info@baychi.org
Apparently-To: riander@well.com
Apparently-To: perlman@turing.acm.org
Apparently-To: instone@cs.bgsu.edu
Apparently-To: support@acm.org
Status: RO

Please create a new SIGCHI LISTSERV list:
	chi-BayCHI@acm.org

Please make the password for the list: kate

In addition to the list chi-BayCHI@acm.org,
please make sure that the forwarding aliases are set up:
	chi-BayCHI-request@acm.org -> chi-BayCHI-request@listserv.acm.org
	owner-chi-BayCHI@acm.org   -> owner-chi-BayCHI@listserv.acm.org
We realize that the creation of these aliases may generate
some automatic messages-to-members to the list owners.

Note that SIGCHI lists use a dash "-" as delimiter.

Please use the following list header to initialize the options:

* ACM SIGCHI San Francisco Bay Area Local Chapter Information
*
* Owner= riander@well.com (Richard I. Anderson, SIGCHI Local SIGs Chair)
* Owner= Quiet:
* Owner= info@baychi.org
* Owner= bobw@lore.kla.com (Bob Weissman)
* Owner= weissman@netcom.com (Bob Weissman)
* Owner= perlman@turing.acm.org (Gary Perlman, SIGCHI Email Manager)
* Owner= instone@cs.bgsu.edu (Keith Instone, SIGCHI Information Director)
* Owner= clore@acm.org (Michael Clore, ACM Network Information Manager)
* Errors-To= Owner            Reply-to= Sender,Respect
* Subscription= Closed        Validate= No                Notify= No
* Send= Public                Mail-Via= Distribute        Ack= Yes
* Notebook= No                Digest= No                  Files= No
* Review= Public              Confidential= No
* Default-Options= NoFiles,Repro,Ack

From perlman Mon Feb 10 13:30:45 1997
Received: by turing.acm.org; id AA23267; Mon, 10 Feb 1997 13:30:39 -0500
Date: Mon, 10 Feb 1997 13:30:39 -0500
From: Gary PERLMAN <perlman>
Message-Id: <9702101830.AA23267@turing.acm.org>
Subject: SIGCHI list: chi-MosCHI creation request
Apparently-To: enir@icsti.su
Apparently-To: riander@well.com
Apparently-To: perlman@turing.acm.org
Apparently-To: instone@cs.bgsu.edu
Apparently-To: support@acm.org
Status: RO

Please create a new SIGCHI LISTSERV list:
	chi-MosCHI@acm.org

Please make the password for the list: kate

In addition to the list chi-MosCHI@acm.org,
please make sure that the forwarding aliases are set up:
	chi-MosCHI-request@acm.org -> chi-MosCHI-request@listserv.acm.org
	owner-chi-MosCHI@acm.org   -> owner-chi-MosCHI@listserv.acm.org
We realize that the creation of these aliases may generate
some automatic messages-to-members to the list owners.

Note that SIGCHI lists use a dash "-" as delimiter.

Please use the following list header to initialize the options:

* ACM SIGCHI Moscow, Russia Local Chapter Information
*
* Owner= riander@well.com (Richard I. Anderson, SIGCHI Local SIGs Chair)
* Owner= Quiet:
* Owner= enir@icsti.su (Juri Gornostaev)
* Owner= perlman@turing.acm.org (Gary Perlman, SIGCHI Email Manager)
* Owner= instone@cs.bgsu.edu (Keith Instone, SIGCHI Information Director)
* Owner= clore@acm.org (Michael Clore, ACM Network Information Manager)
* Errors-To= Owner            Reply-to= Sender,Respect
* Subscription= Closed        Validate= No                Notify= No
* Send= Public                Mail-Via= Distribute        Ack= Yes
* Notebook= No                Digest= No                  Files= No
* Review= Public              Confidential= No
* Default-Options= NoFiles,Repro,Ack

From perlman Mon Feb 10 13:30:45 1997
Received: by turing.acm.org; id AA12144; Mon, 10 Feb 1997 13:30:42 -0500
Date: Mon, 10 Feb 1997 13:30:42 -0500
From: Gary PERLMAN <perlman>
Message-Id: <9702101830.AA12144@turing.acm.org>
Subject: SIGCHI list: chi-CHIFOO creation request
Apparently-To: jennyg@teleport.com
Apparently-To: krism@bv.ngc.com
Apparently-To: krism@pobox.com
Apparently-To: riander@well.com
Apparently-To: perlman@turing.acm.org
Apparently-To: instone@cs.bgsu.edu
Apparently-To: support@acm.org
Status: RO

Please create a new SIGCHI LISTSERV list:
	chi-CHIFOO@acm.org

Please make the password for the list: kate

In addition to the list chi-CHIFOO@acm.org,
please make sure that the forwarding aliases are set up:
	chi-CHIFOO-request@acm.org -> chi-CHIFOO-request@listserv.acm.org
	owner-chi-CHIFOO@acm.org   -> owner-chi-CHIFOO@listserv.acm.org
We realize that the creation of these aliases may generate
some automatic messages-to-members to the list owners.

Note that SIGCHI lists use a dash "-" as delimiter.

Please use the following list header to initialize the options:

* ACM SIGCHI Portland, Oregon Local Chapter Information
*
* Owner= riander@well.com (Richard I. Anderson, SIGCHI Local SIGs Chair)
* Owner= Quiet:
* Owner= krism@pobox.com (Kris Maneely)
* Owner= krism@bv.ngc.com (Kris Maneely)
* Owner= jennyg@teleport.com (Jenny Greenleaf)
* Owner= perlman@turing.acm.org (Gary Perlman, SIGCHI Email Manager)
* Owner= instone@cs.bgsu.edu (Keith Instone, SIGCHI Information Director)
* Owner= clore@acm.org (Michael Clore, ACM Network Information Manager)
* Errors-To= Owner            Reply-to= Sender,Respect
* Subscription= Closed        Validate= No                Notify= No
* Send= Public                Mail-Via= Distribute        Ack= Yes
* Notebook= No                Digest= No                  Files= No
* Review= Public              Confidential= No
* Default-Options= NoFiles,Repro,Ack

From perlman Mon Feb 10 13:30:46 1997
Received: by turing.acm.org; id AA18831; Mon, 10 Feb 1997 13:30:43 -0500
Date: Mon, 10 Feb 1997 13:30:43 -0500
From: Gary PERLMAN <perlman>
Message-Id: <9702101830.AA18831@turing.acm.org>
Subject: SIGCHI list: chi-BuckCHI creation request
Apparently-To: kdelaere@csi.compuserve.com
Apparently-To: riander@well.com
Apparently-To: perlman@turing.acm.org
Apparently-To: instone@cs.bgsu.edu
Apparently-To: support@acm.org
Status: RO

Please create a new SIGCHI LISTSERV list:
	chi-BuckCHI@acm.org

Please make the password for the list: kate

In addition to the list chi-BuckCHI@acm.org,
please make sure that the forwarding aliases are set up:
	chi-BuckCHI-request@acm.org -> chi-BuckCHI-request@listserv.acm.org
	owner-chi-BuckCHI@acm.org   -> owner-chi-BuckCHI@listserv.acm.org
We realize that the creation of these aliases may generate
some automatic messages-to-members to the list owners.

Note that SIGCHI lists use a dash "-" as delimiter.

Please use the following list header to initialize the options:

* ACM SIGCHI Central Ohio (Columbus) Local Chapter Information
*
* Owner= riander@well.com (Richard I. Anderson, SIGCHI Local SIGs Chair)
* Owner= Quiet:
* Owner= kdelaere@csi.compuserve.com (Kevin De Laere)
* Owner= perlman@turing.acm.org (Gary Perlman, SIGCHI Email Manager)
* Owner= instone@cs.bgsu.edu (Keith Instone, SIGCHI Information Director)
* Owner= clore@acm.org (Michael Clore, ACM Network Information Manager)
* Errors-To= Owner            Reply-to= Sender,Respect
* Subscription= Closed        Validate= No                Notify= No
* Send= Public                Mail-Via= Distribute        Ack= Yes
* Notebook= No                Digest= No                  Files= No
* Review= Public              Confidential= No
* Default-Options= NoFiles,Repro,Ack

From perlman Mon Feb 10 13:30:46 1997
Received: by turing.acm.org; id AA23618; Mon, 10 Feb 1997 13:30:43 -0500
Date: Mon, 10 Feb 1997 13:30:43 -0500
From: Gary PERLMAN <perlman>
Message-Id: <9702101830.AA23618@turing.acm.org>
Subject: SIGCHI list: chi-LoneStar creation request
Apparently-To: mshurtleff@dfwmm.net
Apparently-To: riander@well.com
Apparently-To: perlman@turing.acm.org
Apparently-To: instone@cs.bgsu.edu
Apparently-To: support@acm.org
Status: RO

Please create a new SIGCHI LISTSERV list:
	chi-LoneStar@acm.org

Please make the password for the list: kate

In addition to the list chi-LoneStar@acm.org,
please make sure that the forwarding aliases are set up:
	chi-LoneStar-request@acm.org -> chi-LoneStar-request@listserv.acm.org
	owner-chi-LoneStar@acm.org   -> owner-chi-LoneStar@listserv.acm.org
We realize that the creation of these aliases may generate
some automatic messages-to-members to the list owners.

Note that SIGCHI lists use a dash "-" as delimiter.

Please use the following list header to initialize the options:

* ACM SIGCHI Dallas/Ft. Worth, Texas Local Chapter Information
*
* Owner= riander@well.com (Richard I. Anderson, SIGCHI Local SIGs Chair)
* Owner= Quiet:
* Owner= mshurtleff@dfwmm.net (Mark Shurtleff)
* Owner= perlman@turing.acm.org (Gary Perlman, SIGCHI Email Manager)
* Owner= instone@cs.bgsu.edu (Keith Instone, SIGCHI Information Director)
* Owner= clore@acm.org (Michael Clore, ACM Network Information Manager)
* Errors-To= Owner            Reply-to= Sender,Respect
* Subscription= Closed        Validate= No                Notify= No
* Send= Public                Mail-Via= Distribute        Ack= Yes
* Notebook= No                Digest= No                  Files= No
* Review= Public              Confidential= No
* Default-Options= NoFiles,Repro,Ack

From perlman Mon Feb 10 13:30:47 1997
Received: by turing.acm.org; id AA01733; Mon, 10 Feb 1997 13:30:44 -0500
Date: Mon, 10 Feb 1997 13:30:44 -0500
From: Gary PERLMAN <perlman>
Message-Id: <9702101830.AA01733@turing.acm.org>
Subject: SIGCHI list: chi-Iowa creation request
Apparently-To: diekenlj@phibred.com
Apparently-To: riander@well.com
Apparently-To: perlman@turing.acm.org
Apparently-To: instone@cs.bgsu.edu
Apparently-To: support@acm.org
Status: RO

Please create a new SIGCHI LISTSERV list:
	chi-Iowa@acm.org

Please make the password for the list: kate

In addition to the list chi-Iowa@acm.org,
please make sure that the forwarding aliases are set up:
	chi-Iowa-request@acm.org -> chi-Iowa-request@listserv.acm.org
	owner-chi-Iowa@acm.org   -> owner-chi-Iowa@listserv.acm.org
We realize that the creation of these aliases may generate
some automatic messages-to-members to the list owners.

Note that SIGCHI lists use a dash "-" as delimiter.

Please use the following list header to initialize the options:

* ACM SIGCHI Central Iowa Local Chapter Information
*
* Owner= riander@well.com (Richard I. Anderson, SIGCHI Local SIGs Chair)
* Owner= Quiet:
* Owner= diekenlj@phibred.com (Lisa Dieken)
* Owner= perlman@turing.acm.org (Gary Perlman, SIGCHI Email Manager)
* Owner= instone@cs.bgsu.edu (Keith Instone, SIGCHI Information Director)
* Owner= clore@acm.org (Michael Clore, ACM Network Information Manager)
* Errors-To= Owner            Reply-to= Sender,Respect
* Subscription= Closed        Validate= No                Notify= No
* Send= Public                Mail-Via= Distribute        Ack= Yes
* Notebook= No                Digest= No                  Files= No
* Review= Public              Confidential= No
* Default-Options= NoFiles,Repro,Ack

From perlman Mon Feb 10 13:30:48 1997
Received: by turing.acm.org; id AA11376; Mon, 10 Feb 1997 13:30:45 -0500
Date: Mon, 10 Feb 1997 13:30:45 -0500
From: Gary PERLMAN <perlman>
Message-Id: <9702101830.AA11376@turing.acm.org>
Subject: SIGCHI list: chi-GBSIGCHI creation request
Apparently-To: wixon@orion.ENET.dec.com
Apparently-To: riander@well.com
Apparently-To: perlman@turing.acm.org
Apparently-To: instone@cs.bgsu.edu
Apparently-To: support@acm.org
Status: RO

Please create a new SIGCHI LISTSERV list:
	chi-GBSIGCHI@acm.org

Please make the password for the list: kate

In addition to the list chi-GBSIGCHI@acm.org,
please make sure that the forwarding aliases are set up:
	chi-GBSIGCHI-request@acm.org -> chi-GBSIGCHI-request@listserv.acm.org
	owner-chi-GBSIGCHI@acm.org   -> owner-chi-GBSIGCHI@listserv.acm.org
We realize that the creation of these aliases may generate
some automatic messages-to-members to the list owners.

Note that SIGCHI lists use a dash "-" as delimiter.

Please use the following list header to initialize the options:

* ACM SIGCHI Greater Boston Area Local Chapter Information
*
* Owner= riander@well.com (Richard I. Anderson, SIGCHI Local SIGs Chair)
* Owner= Quiet:
* Owner= wixon@orion.ENET.dec.com (Dennis Wixon)
* Owner= perlman@turing.acm.org (Gary Perlman, SIGCHI Email Manager)
* Owner= instone@cs.bgsu.edu (Keith Instone, SIGCHI Information Director)
* Owner= clore@acm.org (Michael Clore, ACM Network Information Manager)
* Errors-To= Owner            Reply-to= Sender,Respect
* Subscription= Closed        Validate= No                Notify= No
* Send= Public                Mail-Via= Distribute        Ack= Yes
* Notebook= No                Digest= No                  Files= No
* Review= Public              Confidential= No
* Default-Options= NoFiles,Repro,Ack

From perlman Mon Feb 10 13:30:49 1997
Received: by turing.acm.org; id AA09911; Mon, 10 Feb 1997 13:30:45 -0500
Date: Mon, 10 Feb 1997 13:30:45 -0500
From: Gary PERLMAN <perlman>
Message-Id: <9702101830.AA09911@turing.acm.org>
Subject: SIGCHI list: chi-KC-CHI creation request
Apparently-To: alp@mjharden.com
Apparently-To: riander@well.com
Apparently-To: perlman@turing.acm.org
Apparently-To: instone@cs.bgsu.edu
Apparently-To: support@acm.org
Status: RO

Please create a new SIGCHI LISTSERV list:
	chi-KC-CHI@acm.org

Please make the password for the list: kate

In addition to the list chi-KC-CHI@acm.org,
please make sure that the forwarding aliases are set up:
	chi-KC-CHI-request@acm.org -> chi-KC-CHI-request@listserv.acm.org
	owner-chi-KC-CHI@acm.org   -> owner-chi-KC-CHI@listserv.acm.org
We realize that the creation of these aliases may generate
some automatic messages-to-members to the list owners.

Note that SIGCHI lists use a dash "-" as delimiter.

Please use the following list header to initialize the options:

* ACM SIGCHI Kansas City, Missouri Local Chapter Information
*
* Owner= riander@well.com (Richard I. Anderson, SIGCHI Local SIGs Chair)
* Owner= Quiet:
* Owner= alp@mjharden.com (Alp Tiritoglu)
* Owner= perlman@turing.acm.org (Gary Perlman, SIGCHI Email Manager)
* Owner= instone@cs.bgsu.edu (Keith Instone, SIGCHI Information Director)
* Owner= clore@acm.org (Michael Clore, ACM Network Information Manager)
* Errors-To= Owner            Reply-to= Sender,Respect
* Subscription= Closed        Validate= No                Notify= No
* Send= Public                Mail-Via= Distribute        Ack= Yes
* Notebook= No                Digest= No                  Files= No
* Review= Public              Confidential= No
* Default-Options= NoFiles,Repro,Ack

From perlman Mon Feb 10 13:30:59 1997
Received: by turing.acm.org; id AA14713; Mon, 10 Feb 1997 13:30:47 -0500
Date: Mon, 10 Feb 1997 13:30:47 -0500
From: Gary PERLMAN <perlman>
Message-Id: <9702101830.AA14713@turing.acm.org>
Subject: SIGCHI list: chi-LACHI creation request
Apparently-To: hcpsy007@email.csun.edu
Apparently-To: bhami@hesp.es.xerox.com
Apparently-To: bluejay@csun.edu
Apparently-To: riander@well.com
Apparently-To: perlman@turing.acm.org
Apparently-To: instone@cs.bgsu.edu
Apparently-To: support@acm.org
Status: RO

Please create a new SIGCHI LISTSERV list:
	chi-LACHI@acm.org

Please make the password for the list: kate

In addition to the list chi-LACHI@acm.org,
please make sure that the forwarding aliases are set up:
	chi-LACHI-request@acm.org -> chi-LACHI-request@listserv.acm.org
	owner-chi-LACHI@acm.org   -> owner-chi-LACHI@listserv.acm.org
We realize that the creation of these aliases may generate
some automatic messages-to-members to the list owners.

Note that SIGCHI lists use a dash "-" as delimiter.

Please use the following list header to initialize the options:

* ACM SIGCHI Los Angeles, California Local Chapter Information
*
* Owner= riander@well.com (Richard I. Anderson, SIGCHI Local SIGs Chair)
* Owner= Quiet:
* Owner= bluejay@csun.edu (Balazs Schreil)
* Owner= bhami@hesp.es.xerox.com (Bruce Hamilton)
* Owner= hcpsy007@email.csun.edu (Balazs Schreil)
* Owner= perlman@turing.acm.org (Gary Perlman, SIGCHI Email Manager)
* Owner= instone@cs.bgsu.edu (Keith Instone, SIGCHI Information Director)
* Owner= clore@acm.org (Michael Clore, ACM Network Information Manager)
* Errors-To= Owner            Reply-to= Sender,Respect
* Subscription= Closed        Validate= No                Notify= No
* Send= Public                Mail-Via= Distribute        Ack= Yes
* Notebook= No                Digest= No                  Files= No
* Review= Public              Confidential= No
* Default-Options= NoFiles,Repro,Ack

From perlman Mon Feb 10 13:31:04 1997
Received: by turing.acm.org; id AA14811; Mon, 10 Feb 1997 13:30:57 -0500
Date: Mon, 10 Feb 1997 13:30:57 -0500
From: Gary PERLMAN <perlman>
Message-Id: <9702101830.AA14811@turing.acm.org>
Subject: SIGCHI list: chi-NUCHI creation request
Apparently-To: woodl@acd1.byu.edu
Apparently-To: woodl@byu.edu
Apparently-To: riander@well.com
Apparently-To: perlman@turing.acm.org
Apparently-To: instone@cs.bgsu.edu
Apparently-To: support@acm.org
Status: RO

Please create a new SIGCHI LISTSERV list:
	chi-NUCHI@acm.org

Please make the password for the list: kate

In addition to the list chi-NUCHI@acm.org,
please make sure that the forwarding aliases are set up:
	chi-NUCHI-request@acm.org -> chi-NUCHI-request@listserv.acm.org
	owner-chi-NUCHI@acm.org   -> owner-chi-NUCHI@listserv.acm.org
We realize that the creation of these aliases may generate
some automatic messages-to-members to the list owners.

Note that SIGCHI lists use a dash "-" as delimiter.

Please use the following list header to initialize the options:

* ACM SIGCHI Northern Utah Local Chapter Information
*
* Owner= riander@well.com (Richard I. Anderson, SIGCHI Local SIGs Chair)
* Owner= Quiet:
* Owner= woodl@byu.edu (Larry Wood)
* Owner= woodl@acd1.byu.edu (Larry Wood)
* Owner= perlman@turing.acm.org (Gary Perlman, SIGCHI Email Manager)
* Owner= instone@cs.bgsu.edu (Keith Instone, SIGCHI Information Director)
* Owner= clore@acm.org (Michael Clore, ACM Network Information Manager)
* Errors-To= Owner            Reply-to= Sender,Respect
* Subscription= Closed        Validate= No                Notify= No
* Send= Public                Mail-Via= Distribute        Ack= Yes
* Notebook= No                Digest= No                  Files= No
* Review= Public              Confidential= No
* Default-Options= NoFiles,Repro,Ack

From perlman Mon Feb 10 13:31:06 1997
Received: by turing.acm.org; id AA11053; Mon, 10 Feb 1997 13:31:03 -0500
Date: Mon, 10 Feb 1997 13:31:03 -0500
From: Gary PERLMAN <perlman>
Message-Id: <9702101831.AA11053@turing.acm.org>
Subject: SIGCHI list: chi-TriCHI creation request
Apparently-To: trauch@raleigh.ibm.com
Apparently-To: dianews@pop.mindspring.com
Apparently-To: dianews@mindspring.com
Apparently-To: dewilson@pobox.com
Apparently-To: riander@well.com
Apparently-To: perlman@turing.acm.org
Apparently-To: instone@cs.bgsu.edu
Apparently-To: support@acm.org
Status: RO

Please create a new SIGCHI LISTSERV list:
	chi-TriCHI@acm.org

Please make the password for the list: kate

In addition to the list chi-TriCHI@acm.org,
please make sure that the forwarding aliases are set up:
	chi-TriCHI-request@acm.org -> chi-TriCHI-request@listserv.acm.org
	owner-chi-TriCHI@acm.org   -> owner-chi-TriCHI@listserv.acm.org
We realize that the creation of these aliases may generate
some automatic messages-to-members to the list owners.

Note that SIGCHI lists use a dash "-" as delimiter.

Please use the following list header to initialize the options:

* ACM SIGCHI NC Triangle Local Chapter Information
*
* Owner= riander@well.com (Richard I. Anderson, SIGCHI Local SIGs Chair)
* Owner= Quiet:
* Owner= dewilson@pobox.com (Diane Wilson)
* Owner= dianews@mindspring.com (Diane Wilson)
* Owner= dianews@pop.mindspring.com (Diane Wilson)
* Owner= trauch@raleigh.ibm.com (Thyra Rausch)
* Owner= perlman@turing.acm.org (Gary Perlman, SIGCHI Email Manager)
* Owner= instone@cs.bgsu.edu (Keith Instone, SIGCHI Information Director)
* Owner= clore@acm.org (Michael Clore, ACM Network Information Manager)
* Errors-To= Owner            Reply-to= Sender,Respect
* Subscription= Closed        Validate= No                Notify= No
* Send= Public                Mail-Via= Distribute        Ack= Yes
* Notebook= No                Digest= No                  Files= No
* Review= Public              Confidential= No
* Default-Options= NoFiles,Repro,Ack

From perlman Mon Feb 10 13:31:06 1997
Received: by turing.acm.org; id AA24979; Mon, 10 Feb 1997 13:31:03 -0500
Date: Mon, 10 Feb 1997 13:31:03 -0500
From: Gary PERLMAN <perlman>
Message-Id: <9702101831.AA24979@turing.acm.org>
Subject: SIGCHI list: chi-St-Louis creation request
Apparently-To: jgrant@CPICORP.COM
Apparently-To: riander@well.com
Apparently-To: perlman@turing.acm.org
Apparently-To: instone@cs.bgsu.edu
Apparently-To: support@acm.org
Status: RO

Please create a new SIGCHI LISTSERV list:
	chi-St-Louis@acm.org

Please make the password for the list: kate

In addition to the list chi-St-Louis@acm.org,
please make sure that the forwarding aliases are set up:
	chi-St-Louis-request@acm.org -> chi-St-Louis-request@listserv.acm.org
	owner-chi-St-Louis@acm.org   -> owner-chi-St-Louis@listserv.acm.org
We realize that the creation of these aliases may generate
some automatic messages-to-members to the list owners.

Note that SIGCHI lists use a dash "-" as delimiter.

Please use the following list header to initialize the options:

* ACM SIGCHI St. Louis, Missouri Local Chapter Information
*
* Owner= riander@well.com (Richard I. Anderson, SIGCHI Local SIGs Chair)
* Owner= Quiet:
* Owner= jgrant@CPICORP.COM (Joe Grant)
* Owner= perlman@turing.acm.org (Gary Perlman, SIGCHI Email Manager)
* Owner= instone@cs.bgsu.edu (Keith Instone, SIGCHI Information Director)
* Owner= clore@acm.org (Michael Clore, ACM Network Information Manager)
* Errors-To= Owner            Reply-to= Sender,Respect
* Subscription= Closed        Validate= No                Notify= No
* Send= Public                Mail-Via= Distribute        Ack= Yes
* Notebook= No                Digest= No                  Files= No
* Review= Public              Confidential= No
* Default-Options= NoFiles,Repro,Ack

From perlman Mon Feb 10 13:31:22 1997
Received: by turing.acm.org; id AA29852; Mon, 10 Feb 1997 13:31:02 -0500
Date: Mon, 10 Feb 1997 13:31:02 -0500
From: Gary PERLMAN <perlman>
Message-Id: <9702101831.AA29852@turing.acm.org>
Subject: SIGCHI list: chi-PSSIGCHI creation request
Apparently-To: rcburns@atc.boeing.com
Apparently-To: jking@stout.hitl.washington.edu
Apparently-To: pssigchi@hitl.washington.edu
Apparently-To: riander@well.com
Apparently-To: perlman@turing.acm.org
Apparently-To: instone@cs.bgsu.edu
Apparently-To: support@acm.org
Status: RO

Please create a new SIGCHI LISTSERV list:
	chi-PSSIGCHI@acm.org

Please make the password for the list: kate

In addition to the list chi-PSSIGCHI@acm.org,
please make sure that the forwarding aliases are set up:
	chi-PSSIGCHI-request@acm.org -> chi-PSSIGCHI-request@listserv.acm.org
	owner-chi-PSSIGCHI@acm.org   -> owner-chi-PSSIGCHI@listserv.acm.org
We realize that the creation of these aliases may generate
some automatic messages-to-members to the list owners.

Note that SIGCHI lists use a dash "-" as delimiter.

Please use the following list header to initialize the options:

* ACM SIGCHI Puget Sound (Seattle, Washington) Local Chapter Information
*
* Owner= riander@well.com (Richard I. Anderson, SIGCHI Local SIGs Chair)
* Owner= Quiet:
* Owner= pssigchi@hitl.washington.edu (W. Joseph King)
* Owner= jking@stout.hitl.washington.edu (W. Joseph King)
* Owner= rcburns@atc.boeing.com (Robert C. Burns)
* Owner= perlman@turing.acm.org (Gary Perlman, SIGCHI Email Manager)
* Owner= instone@cs.bgsu.edu (Keith Instone, SIGCHI Information Director)
* Owner= clore@acm.org (Michael Clore, ACM Network Information Manager)
* Errors-To= Owner            Reply-to= Sender,Respect
* Subscription= Closed        Validate= No                Notify= No
* Send= Public                Mail-Via= Distribute        Ack= Yes
* Notebook= No                Digest= No                  Files= No
* Review= Public              Confidential= No
* Default-Options= NoFiles,Repro,Ack

From perlman Mon Feb 10 14:04:09 1997
Received: by turing.acm.org; id AA19811; Mon, 10 Feb 1997 14:04:09 -0500
Date: Mon, 10 Feb 1997 14:04:09 -0500
From: Gary PERLMAN <perlman>
Message-Id: <9702101904.AA19811@turing.acm.org>
To: rianderson@acm.org
Subject: Local SIGs aliases requested
Cc: perlman
Status: RO

So, you probably figured out that I just requested the aliases.
You may get a barrage of confusing mail when ACM sets up some aliases:

>From the SIGCHI Listowner's manual:

	The problem is that the listserv is not at listserv@acm.org
	but is really at listserv@listserv.acm.org, which is where all
	our lists really reside. Along with the lists, we have to set up
	aliases for owner-listname and listname-request. When
	ACM sets these up, it uses a script that sends the recipient
	of the alias mail some "friendly member mail". So, a list
	owner will get a message to listname-request which looks
	like mail to an ACM member, and when mail is sent to
	owner-listname, listserv picks up that this is probably an
	error and sends a message to that effect to the list owner,
	possibly identifying the member message as SPAM. By
	then, the mail is TOTALLY incomprehensible. 

	But here is the good part. It only happens once. If ACM
	would set up the aliases without sending mail, then none of
	this would happen. 

The lists have not been initialized with recipients.
It turned out to be just too complex to get independent
ownership and recipient information (for LISTSERV,
they are completely independent).
Some "list owners" are clearly meant to be recipients
(info@baychi.org) but having them as Quiet: owners
is not a problem.

I made you the primary listowner, so that if mail
to an alias bounces, it bounces to you.
I did not want the primary list owner to
be the same as the recipient; where would
the bounce go?

Here are the current subscribers to chi-local-sigs:

committee@BAYCHI.ORG              Steering Committee (BayCHI)
woodl@BYU.EDU                     Larry Wood (NUCHI)
barthet@CICT.FR                   Marie-France Barthet (Toulouse)
jgrant@CPICORP.COM                Joe Grant (St-Louis)
kdelaere@CSI.COMPUSERVE.COM       Kevin De Laere (BuckCHI)
bluejay@CSUN.EDU                  Balazs Schreil (LACHI)
steven.pemberton@CWI.NL           Steven Pemberton (Netherlands)
mshurtleff@DFWMM.NET              Mark Shurtleff (LoneStar)
hunt@DGP.UTORONTO.CA              William Hunt (ToRCHI)
fcosta@ERCOLE.IESI.BA.CNR.IT      Maria Francesca Costabile (Italy)
enir@ICSTI.SU                     Juri Gornostaev (MosCHI)
felix@IHA.BEPR.ETHZ.CH            Daniel Felix (Switzerland)
mbl@LRI.FR                        Michel Beaudouin-Lafon (France)
alp@MJHARDEN.COM                  Alp Tiritoglu (KC-CHI)
wixon@ORION.ENET.DEC.COM          Dennis Wixon (GBSIGCHI)
diekenlj@PHIBRED.COM              Lisa Dieken (Iowa)
krism@POBOX.COM                   Kris Maneely (CHIFOO)
trauch@RALEIGH.IBM.COM            Thyra Rausch (TriCHI)
szmyt@SIMWARE.COM                 Peter Szmyt (CapCHI)
Cleo@UDLAPVMS.PUE.UDLAP.MX        Cleotilde Gonzalez (Puebla)
PSSIGCHI@USABILITY-ARCHITECTS.COM Steering Committee (PSCHI)
riander@WELL.COM                  Richard I. Anderson (Local-SIGs)

The BayCHI entry seems to be the right one for contacting
all local chapters, but for the information contact,
I think you could do this:

quiet add chi-BayCHI info@baychi.org *
The * is needed or LISTSERV will ask for a name.

Given that the recipients might be different
for chi-local-sigs and the union of the local-sig aliases,
I don't think the new LISTSERV Sub-List= feature
will be generally useful.  Anyway, Sub-Lists are not well done:
	http://www.acm.org/sigchi/listserv/listown/options.html#alias

Other lists are easier:

quiet add chi-BuckCHI kdelaere@CSI.COMPUSERVE.COM       Kevin De Laere

Gather up a file of all the subscriptions,
and (once the lists are created) send them to:
	listserv@acm.org
as one big request.

You might drop the QUIET option,
and the addresses getting added will receive notification.

Once the lists are set up, some lists might benefit from
getting an HTML description added to its header.
See:
	http://www.lsoft.com/SCRIPTS/WL.EXE?SL1=CHI-LOCAL-SIGS&H=ACM.ORG
for and example, and help on this is in the SIGCHI list owners guide:
	http://www.acm.org/sigchi/listserv/listown/names.html#html
You can point people to the guide for help:
	http://www.acm.org/sigchi/listserv/listown/

Tell me if you are not comfortable being on your own from here.

Good luck.

Gary

From perlman Mon Feb 17 10:07:12 1997
Received: by turing.acm.org; id AA04550; Mon, 17 Feb 1997 10:07:06 -0500
From: Gary PERLMAN <perlman>
Message-Id: <9702171507.AA04550@turing.acm.org>
Subject: local SIG information aliases up and running
To: chi-local-sigs@acm.org
Date: Mon, 17 Feb 1997 10:07:06 -0500 (EST)
Cc: cgibbs@sj-coop.net, kenny@numega.com, perlman
X-Mailer: ELM [version 2.4 PL25]
Content-Type: text
Content-Length: 1608      
Status: O

I have created the SIGCHI aliases for local SIGs
and added my best guess at the destination(s) for the alias.
All these aliases are implemented as LISTSERV lists,
so if you want to make changes to the list,
you can use your listowner privileges.

All list management commands are sent to:
	listserv@acm.org
To review the list header (options) and subscribers:
	review ListName
To add a person to ListName@acm.org:
	[quiet] add ListName NetAddress Firstname Lastname
To delete a person:
	[quiet] del ListName NetAddress
The [quiet] option (without the []s) stops notification from being sent.

I suggest that you use your SIGCHI information alias
as a permanent address for people to use to get information.
It will mean less updates to web sites and less outdating
of printed materials.  So, for example, people will be
able to get information about the Lone Star chapter from
	chi-LoneStar@acm.org
and not have to worry about it being out of date (if it it,
then the mail will go to the SIGCHI Local SIGs chair, who
will fix the addressing problem).

The SIGCHI local-sigs page should update its email links
immediately to use the new aliases.

There is a SIGCHI list owner's guide at:
	http://www.acm.org/sigchi/listserv/listown/
under the SIGCHI listserv page:
	http://www.acm.org/sigchi/listserv/

I will now have the Xerox lists point to the new lists
so that if people use the old Xerox aliases, the
mail will continue to get through.

If any local SIGs need help creating their own lists,
for member lists, announcements, etc. I am happy to help.

Gary Perlman, ACM SIGCHI Vice-Chair for Publications

From  Mon Feb 17 09:47:57 1997
Received: from mail (mail.acm.org [199.222.69.4]) by mail.acm.org (8.8.4/8.7.5) with ESMTP id JAA24514 for <perlman@TURING.ACM.ORG>; Mon, 17 Feb 1997 09:47:56 -0500
Message-Id: <199702171447.JAA24514@mail.acm.org>
Date:         Mon, 17 Feb 1997 09:47:56 -0500
From: "L-Soft list server at ACM (1.8c)" <LISTSERV@ACM.ORG>
Subject:      Output of your job "perlman"
To: Gary Perlman <perlman@TURING.ACM.ORG>
Status: RO

> quiet add chi-CapCHI peter@acm.org (Peter Szmyt)
Peter Szmyt <peter@ACM.ORG> has been added to the CHI-CAPCHI list. No
notification has been sent.

> quiet add chi-ToRCHI hunt@dgp.utoronto.ca (William Hunt)
William Hunt <hunt@DGP.UTORONTO.CA> has been added to the CHI-TORCHI list.
No notification has been sent.

> quiet add chi-Toulouse barthet@cict.fr (Marie-France Barthet)
Marie-France Barthet <barthet@CICT.FR> has been added to the CHI-TOULOUSE
list. No notification has been sent.

> quiet add chi-France Michel.Beaudouin-Lafon@lri.fr (Michel Beaudouin-Lafon)
Michel Beaudouin-Lafon <Michel.Beaudouin-Lafon@LRI.FR> has been added to the
CHI-FRANCE list. No notification has been sent.

> quiet add chi-France barthet@cict.fr (Marie-France Barthet)
Marie-France Barthet <barthet@CICT.FR> has been added to the CHI-FRANCE
list. No notification has been sent.

> quiet add chi-Mexico Cleo@udlapvms.pue.udlap.mx
"Cleotilde Gonzalez (Puebla)" <Cleo@UDLAPVMS.PUE.UDLAP.MX> has been added to
the CHI-MEXICO list. No notification has been sent.

> quiet add chi-Italy fcosta@ercole.iesi.ba.cnr.it (Maria Francesca Costabile)
Maria Francesca Costabile <fcosta@ERCOLE.IESI.BA.CNR.IT> has been added to
the CHI-ITALY list. No notification has been sent.

> quiet add chi-Netherlands steven.pemberton@cwi.nl (Steven Pemberton)
Steven Pemberton <steven.pemberton@CWI.NL> has been added to the
CHI-NETHERLANDS list. No notification has been sent.

> quiet add chi-MosCHI enir@icsti.su (Juri Gornostaev)
Juri Gornostaev <enir@ICSTI.SU> has been added to the CHI-MOSCHI list. No
notification has been sent.

> quiet add chi-Switzerland felix@iha.bepr.ethz.ch (Daniel Felix)
Daniel Felix <felix@IHA.BEPR.ETHZ.CH> has been added to the CHI-SWITZERLAND
list. No notification has been sent.

> quiet add chi-BayCHI info@baychi.org
info@BAYCHI.ORG is not yet in the signup file. Please specify the full name
of that person, as in "ADD MYLIST JOE@XYZ.EDU Joe H. Smith".

> quiet add chi-CHIFOO krism@pobox.com (Kris Maneely)
Kris Maneely <krism@POBOX.COM> has been added to the CHI-CHIFOO list. No
notification has been sent.

> quiet add chi-BuckCHI kdelaere@csi.compuserve.com (Kevin De Laere)
kdelaere@CSI.COMPUSERVE.COM is already subscribed to the CHI-BUCKCHI list
under the name "Kevin De Laere".

> quiet add chi-LoneStar mshurtleff@dfwmm.net (Mark Shurtleff)
Mark Shurtleff <mshurtleff@DFWMM.NET> has been added to the CHI-LONESTAR
list. No notification has been sent.

> quiet add chi-Iowa diekenlj@phibred.com (Lisa Dieken)
Lisa Dieken <diekenlj@PHIBRED.COM> has been added to the CHI-IOWA list. No
notification has been sent.

> quiet add chi-GBSIGCHI wixon@orion.ENET.dec.com (Dennis Wixon)
Dennis Wixon <wixon@ORION.ENET.DEC.COM> has been added to the CHI-GBSIGCHI
list. No notification has been sent.

> quiet add chi-KC-CHI alp@mjharden.com (Alp Tiritoglu)
Alp Tiritoglu <alp@MJHARDEN.COM> has been added to the CHI-KC-CHI list. No
notification has been sent.

> quiet add chi-LACHI bluejay@csun.edu (Balazs Schreil)
Balazs Schreil <bluejay@CSUN.EDU> has been added to the CHI-LACHI list. No
notification has been sent.

> quiet add chi-NUCHI woodl@byu.edu (Larry Wood)
Larry Wood <woodl@BYU.EDU> has been added to the CHI-NUCHI list. No
notification has been sent.

> quiet add chi-PSSIGCHI rcburns@atc.boeing.com (Robert C. Burns)
"Robert C. Burns" <rcburns@ATC.BOEING.COM> has been added to the
CHI-PSSIGCHI list. No notification has been sent.

> quiet add chi-PSSIGCHI pssigchi@hitl.washington.edu
"W. Joseph King (PSCHI)" <pssigchi@HITL.WASHINGTON.EDU> has been added to
the CHI-PSSIGCHI list. No notification has been sent.

> quiet add chi-TriCHI trauch@raleigh.ibm.com (Thyra Rausch)
Thyra Rausch <trauch@RALEIGH.IBM.COM> has been added to the CHI-TRICHI list.
No notification has been sent.

> quiet add chi-St-Louis jgrant@CPICORP.COM (Joe Grant)
Joe Grant <jgrant@CPICORP.COM> has been added to the CHI-ST-LOUIS list. No
notification has been sent.

Summary of resource utilization
-------------------------------
 CPU time:        0.150 sec                Device I/O:        0
 Overhead CPU:    0.190 sec                Paging I/O:       17
 CPU model:         000151404800

From instone@cs.bgsu.edu Wed Mar 19 10:27:05 1997
Received: from cs.bgsu.edu (maestro.cs.bgsu.edu [129.1.64.4]) by mail.acm.org (8.8.4/8.7.5) with ESMTP id KAA25960 for <perlman@acm.org>; Wed, 19 Mar 1997 10:26:57 -0500
Received: from [129.1.64.70] (dudley.cs.bgsu.edu [129.1.64.70]) 
	by cs.bgsu.edu (8.7.5/950727cs.bgsu.edu)  with ESMTP
	id KAA25389 sender instone@cs.bgsu.edu
	; Wed, 19 Mar 1997 10:29:13 -0500 (EST)
X-Sender: instone@mail.cs.bgsu.edu
Message-Id: <l03010d02af55b664a307@[129.1.64.70]>
In-Reply-To: <v01510102af547280d73d@[206.15.84.76]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Wed, 19 Mar 1997 10:29:14 -0500
To: riander@well.com (Richard I. Anderson)
From: Keith Instone <instone@cs.bgsu.edu>
Subject: Re: Local SIGs workshop
Cc: perlman@acm.org
Status: RO

>As you may know, I'm leading a full-day Local SIGs workshop on Monday in
>Atlanta.  (See
>http://www.well.com/user/riander/chi97-localsigs-wkshp.html.)  Almost all
>of the chartered and prospective Local SIGs will be represented.
>
>Might you be available sometime on Monday to come in to discuss what web
>and mailing list and ... services are available to the Local SIGs?  (I
>invited Gary, who has been so very helpful with this, but he is teaching
>all day Monday.)  I'm not sure YET exactly when on Monday we will address
>this topic, but I'd like to find out about your availability and interest.

I will be at a workshop all day Monday. )^: Perhaps Gary and I can
whip up a quick list on paper that you can hand out to people?



Keith


Keith Instone                   http://web.cs.bgsu.edu/instone/
Computer Science Department     instone@cs.bgsu.edu
Bowling Green State University
Bowling Green, OH 43403 USA



From perlman@turing.acm.org Wed Mar 19 11:26:25 1997
Received: from turing.acm.org (turing.acm.org [199.222.69.20]) by mail.acm.org (8.8.4/8.7.5) with SMTP id LAA47586 for <perlman@acm.org>; Wed, 19 Mar 1997 11:26:22 -0500
Received: by turing.acm.org; id AA01470; Wed, 19 Mar 1997 11:26:18 -0500
From: Gary PERLMAN <perlman@turing.acm.org>
Message-Id: <9703191626.AA01470@turing.acm.org>
Subject: Re: Local SIGs workshop
To: instone@cs.bgsu.edu (Keith Instone)
Date: Wed, 19 Mar 1997 11:26:18 -0500 (EST)
Cc: riander@well.com, perlman@acm.org
In-Reply-To: <l03010d02af55b664a307@[129.1.64.70]> from "Keith Instone" at Mar 19, 97 10:29:14 am
X-Mailer: ELM [version 2.4 PL25]
Content-Type: text
Status: O

> >As you may know, I'm leading a full-day Local SIGs workshop on Monday in
> >Atlanta.  (See
> >http://www.well.com/user/riander/chi97-localsigs-wkshp.html.)  Almost all
> >of the chartered and prospective Local SIGs will be represented.
> >
> >Might you be available sometime on Monday to come in to discuss what web
> >and mailing list and ... services are available to the Local SIGs?  (I
> >invited Gary, who has been so very helpful with this, but he is teaching
> >all day Monday.)  I'm not sure YET exactly when on Monday we will address
> >this topic, but I'd like to find out about your availability and interest.

BuckCHI created:
	BuckCHI-Info     for chapter info
	BuckCHI-InfoDir  for contact on web pages
	BuckCHI-Officers for officers (and maybe other key people)
	BuckCHI-Members  for announcements
I think a chapter might want a closed subscription list for
members only, but keep a separate list for announcements.
I can provide templates for requesting lists.

BuckCHI also has a web site at:
	www.acm.org/chapters/buckchi
and a login for their infodir.

I think SIGCHI could support some of the above lists
under its CHI- scheme for forming chapters.

I think that's all a chapter needs.

> I will be at a workshop all day Monday. )^: Perhaps Gary and I can
> whip up a quick list on paper that you can hand out to people?
> 
> 
> 
> Keith
> 
> 
> Keith Instone                   http://web.cs.bgsu.edu/instone/
> Computer Science Department     instone@cs.bgsu.edu
> Bowling Green State University
> Bowling Green, OH 43403 USA
> 
> 
> 


From perlman Sun Mar 30 22:16:58 1997
Received: by turing.acm.org; id AA29851; Sun, 30 Mar 1997 22:16:49 -0500
From: Gary PERLMAN <perlman>
Message-Id: <9703310316.AA29851@turing.acm.org>
Subject: Re: local chapter start-up package request
To: riander@well.com (Richard I. Anderson)
Date: Sun, 30 Mar 1997 22:16:48 -0500 (EST)
Cc: sears@cs.depaul.edu, perlman
In-Reply-To: <v01510102af64b6f2dffd@[206.15.68.48]> from "Richard I. Anderson" at Mar 30, 97 04:47:54 pm
X-Mailer: ELM [version 2.4 PL25]
Content-Type: text
Content-Length: 2516      
Status: O

CHICHI = CHI-Squared.  Cute.
It's also a statistical distribution, I'm sure you know.

Much less violent than CHI-ILL (KILL).

The main idea of the CHI- prefix is to group all the
CHI aliases together in the ACM list of lists/aliases.
I see no problem with chi-chi-squared, except for the
obvious questions about the Mexican restaurant chain.
Multiple hyphens are not a problem, but, believe it
or not, the hyphen is the SIGCHI EC designated delimiter.
But, I also see no problem with CHI-Squared@acm.org
as long as the list has a title that is consistent
with the other local sigs' and one that is descriptive.

In general, as long as there is a chi- prefix, I like to go with
what the list beneficiaries want.

Looking forward, as in the case of BuckCHI, which as a
chartered chapter, now has some lists of its own:
	BuckCHI-Info which has the same function as CHI-BuckCHI
	BuckCHI-Members
	BuckCHI-Officers
What would CHI-Squared have:
	CHI-Squared-Info
	CHI-Squared-Members
	CHI-Squared-Officers
Although there is a distinction between SIGCHI-maintained lists
and those mantained by a local SIG, I see no benefit to members
of making the names artificially different.  So I suggest going
with chi-squared@acm.org.  Many people will be confused and amazed
at what CHI-Squared is, but that's more fun than a problem,
as long as the list gets a consistent and descriptive title.

> Andrew,
> 
> >> 1. Your local SIG's information alias name.
> >>
> >> The proposed name for your local SIG alias is CHI-CHI-SQUARED@acm.org.
> >
> >Could it just be:
> >CHI-SQUARED@acm.org
> >
> >I think the proposed name for the chapter would be CHI-Squared, but
> >adding the extra CHI- in front of it gets kind of long.
> 
> Hmm.  There is a "chi-" prefix before each of the local chapter identities.
> Hence, BayCHI's info alias is chi-BayCHI, CHIFOO's is chi-CHIFOO, etc.  If
> you deviated from this, some might think you are just called Squared.  Hmm.
> How about with only one hyphen: chi-CHISquared@acm.org?  Only KC-CHI and
> St-Louis have the second hyphen, presently.
> 
> I'll "cc" this to Gary to see if he has any ideas.  (Gary: this is for a
> Chicago-based chapter.)
> 
> Richard
> 
>    __________________________________________________________________
>      Richard I. Anderson, Usability/Design Adventures, 510-524-2421
>        riander@well.com  rianderson@acm.org rianderson@baychi.org
>                  717 Coventry Road, Kensington CA 94707
>                    http://www.well.com/user/riander/
> 
> 
> 


From owner-chi-local-sigs@acm.org Sun Aug 31 19:15:22 1997
Received: from mail (mail.acm.org [199.222.69.4]) by mail.acm.org (8.8.5/8.7.5) with ESMTP id RAA32806; Sun, 31 Aug 1997 17:31:53 -0400
Received: from ACM.ORG by ACM.ORG (LISTSERV-TCP/IP release 1.8c) with spool id
          388543 for CHI-LOCAL-SIGS@ACM.ORG; Sun, 31 Aug 1997 17:31:52 -0400
Received: from smtp.well.com (smtp.well.com [206.80.6.147]) by mail.acm.org
          (8.8.5/8.7.5) with ESMTP id RAA15098 for <chi-local-sigs@ACM.ORG>;
          Sun, 31 Aug 1997 17:31:46 -0400
Received: from [206.15.85.31] (pm3-ppp31.well.com [206.15.85.31]) by
          smtp.well.com (8.8.6/8.8.4) with SMTP id NAA12171 for
          <chi-local-sigs@acm.org>; Sun, 31 Aug 1997 13:38:59 -0700 (PDT)
X-Sender: riander@mail.well.com (Unverified)
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Message-Id:  <v01510100b02f7553cb28@[206.169.228.86]>
Date:         Sun, 31 Aug 1997 13:44:17 -0700
Reply-To: "Richard I. Anderson" <riander@WELL.COM>
Sender: "ACM SIGCHI Contacts for All Local SIGs (Mailing List)"
              <CHI-LOCAL-SIGS@acm.org>
From: "Richard I. Anderson" <riander@WELL.COM>
Subject:      your information email alias
To: CHI-LOCAL-SIGS@acm.org
Status: RO

Hi,

SIGCHI has given many of you an "information email alias" for your
prospective or chartered local chapter.  This email address is
advertised in SIGCHI Bulletin and on the Local SIGs webpage as
an email address via which people can contact your local chapter
with their questions.

Please remember that you need to keep your information email alias
up to date.  That is, you need to make sure that the recipient(s) of
email sent to that information email alias is (or are) the right
person(s).

Only the "owner(s)" of the alias can update the list of recipients
of the email sent to the alias.  If you are unsure of whom in your
chapter has been designated as the owner of the alias, you can
find out by using the "review" listserv command.  (For example,
information about the chi-Bulgaria information email alias can
be obtained by sending the command "review chi-Bulgaria" to
listserv@acm.org.)  The "review" listserv command will reveal
not only who the owners are, but also who have been designated as
the recipients of email sent to that alias.

If you need assistance with this, let me know.  Remember that
there is a SIGCHI list owner's guide at
http://www.acm.org/sigchi/listserv/listown/.  Most of what the
owner needs to know is:

   All list management commands are sent to:
        listserv@acm.org
   To review list information:
        review ListName
   To add a person to ListName@acm.org:
        [quiet] add ListName NetAddress Firstname Lastname
   To delete a person:
        [quiet] del ListName NetAddress
   The [quiet] option (without the []s) stops notification from
   being sent to NetAddress.

Here is the list of existing information email aliases for local
chapters:

Europe
 chi-Bulgaria
 chi-Toulouse
 chi-France
 chi-Italy
 chi-Netherlands
 chi-MosCHI
 chi-Switzerland

Americas (outside USA)
 chi-Brazil
 chi-CapCHI
 chi-ToRCHI
 chi-Mexico

United States
 chi-BayCHI
 chi-LACHI
 chi-Atlanta
 chi-Squared
 chi-Iowa
 chi-MaineCHI
 chi-GBSIGCHI
 chi-KC-CHI
 chi-St-Louis
 chi-NYC
 chi-TriCHI
 chi-BuckCHI
 chi-CHIFOO
 chi-Austin
 chi-LoneStar
 chi-NUCHI
 chi-PSCHI

If SIGCHI has not yet created an information email alias for you and
you are ready for one, let me know.

Richard Anderson
Local SIGs Chair

   ___________________________________________________________________
                           Richard I. Anderson
          Usability/Design/Discovery Adventures, +1 510 524-2421
       riander@well.com  rianderson@acm.org  rianderson@baychi.org
               717 Coventry Road, Kensington CA 94707 USA
                   http://www.well.com/user/riander/

From owner-chi-local-sigs@ACM.ORG Sun Aug 31 21:58:30 1997
Received: from mail (mail.acm.org [199.222.69.4]) by mail.acm.org (8.8.5/8.7.5) with ESMTP id VAA50426; Sun, 31 Aug 1997 21:58:15 -0400
Received: from ACM.ORG by ACM.ORG (LISTSERV-TCP/IP release 1.8c) with spool id
          388741 for CHI-LOCAL-SIGS@ACM.ORG; Sun, 31 Aug 1997 21:58:14 -0400
Received: from k2.llnl.gov (dpatt@k2.llnl.gov [134.9.1.1]) by mail.acm.org
          (8.8.5/8.7.5) with ESMTP id VAA51272 for <CHI-LOCAL-SIGS@ACM.ORG>;
          Sun, 31 Aug 1997 21:48:13 -0400
Received: (from dpatt@localhost) by k2.llnl.gov (8.8.5/8.8.5/LLNL-Jun96) id
          SAA00892; Sun, 31 Aug 1997 18:42:30 -0700 (PDT)
X-Mailer: ELM [version 2.4 PL25]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Message-Id:  <199709010142.SAA00892@k2.llnl.gov>
Date:         Sun, 31 Aug 1997 18:42:30 -0700
Reply-To: Don Patterson <dpatt@K2.LLNL.GOV>
Sender: "ACM SIGCHI Contacts for All Local SIGs (Mailing List)"
              <CHI-LOCAL-SIGS@ACM.ORG>
From: Don Patterson <dpatt@K2.LLNL.GOV>
Subject:      Re: Starting a local chapter...
Comments: cc: Don Patterson <dpatt@ACM.ORG>
To: CHI-LOCAL-SIGS@ACM.ORG
Status: RO

Local CHI folk,

As I noted during the workshop at CHI'97 in Atlanta, I have access to
the attendee contact information for past CHI conferences. I provided
some of you with information about attendees at CHI'95 and CHI'96 from
your local areas. I now have access to the attendee information for
CHI'97. For those of you that I could find records of my search criteria
I have already sent the CHI'97 data to you. These include: Austin,
CT/MA/NH/RI, The Netherlands, St Louis, Switzerland, Toronto, and Utah.

If anyone else would like information about attendees in your area just
send me a request and I will forward a list of attendees from your area
to you.

Cheers, Don

From riander@well.com Mon Oct 20 23:12:17 1997
Received: from [206.169.227.218] (libya-218.ppp.hooked.net [206.169.227.218])
          by smtp.well.com (8.8.6/8.8.4) with SMTP
	  id UAA03361; Mon, 20 Oct 1997 20:08:13 -0700 (PDT)
X-Sender: riander@mail.well.com
Message-Id: <v01510108b071cd3087b6@[206.169.227.218]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Mon, 20 Oct 1997 20:11:52 -0700
To: support@acm.org
From: riander@well.com (Richard I. Anderson)
Subject: SIGCHI list: chi-TwinCHI creation request
Cc: Keith Instone <instone@usableweb.com>,
        Gary PERLMAN <perlman@turing.acm.org>
Status: RO

Please create a new SIGCHI LISTSERV list:
        chi-TwinCHI@acm.org

Please make the password for the list: kate

In addition to the list chi-TwinCHI@acm.org,
please make sure that the forwarding aliases are set up:
     chi-TwinCHI-request@acm.org ->
chi-TwinCHI-request@listserv.acm.org
     owner-chi-TwinCHI@acm.org   -> owner-chi-TwinCHI@listserv.acm.org
We realize that the creation of these aliases may generate
some automatic messages-to-members to the list owners.

Note that SIGCHI lists use a dash "-" as delimiter.

Please use the following list header to initialize the options:

* ACM SIGCHI TwinCHI Local Chapter Information
*
* Owner= riander@well.com (Richard I. Anderson, SIGCHI Local SIGs Chair)
* Owner= Quiet:
* Owner= scott@jensondesign.com (Scott Jenson)
* Owner= perlman@turing.acm.org (Gary Perlman, SIGCHI Email Manager)
* Owner= instone@cs.bgsu.edu (Keith Instone, SIGCHI Information Director)
* Owner= clore@acm.org (Michael Clore, ACM Network Information Manager)
* Errors-To= Owner            Reply-to= Sender,Respect
* Subscription= Closed        Validate= No                Notify= No
* Send= Public                Mail-Via= Distribute        Ack= Yes
* Notebook= No                Digest= No                  Files= No
* Review= Public              Confidential= No
* Default-Options= NoFiles,Repro,Ack

Richard Anderson
ACM SIGCHI Adjunct Chair for Local SIGs

   ___________________________________________________________________
                           Richard I. Anderson
          Usability/Design/Discovery Adventures, +1 510 524-2421
       riander@well.com  rianderson@acm.org  rianderson@baychi.org
               717 Coventry Road, Kensington CA 94707 USA
                   http://www.well.com/user/riander/



From riander@well.com Thu Nov 20 11:55:29 1997
Received: from [206.15.85.16] (pm3-ppp9.well.com [206.15.85.9])
          by smtp.well.com (8.8.6/8.8.4) with SMTP
	  id IAA22786; Thu, 20 Nov 1997 08:52:38 -0800 (PST)
X-Sender: riander@mail.well.com
Message-Id: <v01510104b09a0cee13e9@[206.15.85.16]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Thu, 20 Nov 1997 08:57:05 -0700
To: support@acm.org
From: riander@well.com (Richard I. Anderson)
Subject: SIGCHI list: chi-Poland creation request
Cc: Keith Instone <instone@usableweb.com>,
        Gary PERLMAN <perlman@turing.acm.org>
Status: RO

Please create a new SIGCHI LISTSERV list:
        chi-Poland@acm.org

Please make the password for the list: kate

In addition to the list chi-Poland@acm.org,
please make sure that the forwarding aliases are set up:
   chi-Poland-request@acm.org -> chi-Poland-request@listserv.acm.org
   owner-chi-Poland@acm.org   -> owner-chi-Poland@listserv.acm.org
We realize that the creation of these aliases may generate
some automatic messages-to-members to the list owners.

Note that SIGCHI lists use a dash "-" as delimiter.

Please use the following list header to initialize the options:

* ACM SIGCHI Poland Local Chapter Information
*
* Owner= riander@well.com (Richard I. Anderson, SIGCHI Local SIGs Chair)
* Owner= Quiet:
* Owner= msik@sunrise.pg.gda.pl (Marcin Sikorski)
* Owner= msik@pg.gda.pl (Marcin Sikorski)
* Owner= perlman@turing.acm.org (Gary Perlman, SIGCHI Email Manager)
* Owner= instone@acm.org (Keith Instone, SIGCHI Information Director)
* Owner= clore@acm.org (Michael Clore, ACM Network Information Manager)
* Errors-To= Owner            Reply-to= Sender,Respect
* Subscription= Closed        Validate= No                Notify= No
* Send= Public                Mail-Via= Distribute        Ack= Yes
* Notebook= No                Digest= No                  Files= No
* Review= Public              Confidential= No
* Default-Options= NoFiles,Repro,Ack

Richard Anderson
ACM SIGCHI Adjunct Chair for Local SIGs

   ___________________________________________________________________
                           Richard I. Anderson
          Usability/Design/Discovery Adventures, +1 510 524-2421
       riander@well.com  rianderson@acm.org  rianderson@baychi.org
               717 Coventry Road, Kensington CA 94707 USA
                   http://www.well.com/user/riander/



From riander@well.com Thu Dec 18 18:10:13 1997
Received: from [206.15.85.15] (pm3-ppp15.well.com [206.15.85.15])
          by smtp.well.com (8.8.6/8.8.4) with SMTP
	  id PAA24449; Thu, 18 Dec 1997 15:08:28 -0800 (PST)
X-Sender: riander@mail.well.com (Unverified)
Message-Id: <v01510102b0bf4eab88bc@[206.15.85.19]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Thu, 18 Dec 1997 15:13:40 -0700
To: "Patrick Steiger" <pst@zurich.ibm.com>
From: riander@well.com (Richard I. Anderson)
Subject: Re: Webserver
Cc: felix@iha.bepr.ethz.ch, Gary PERLMAN <perlman@TURING.ACM.ORG>
Status: RO

Patrick,

> We would
>like to spread our new name (SwissCHI) by using it also for our own
>domain on the World Wide Web/Internet.
>
>My question: is there an offer from SIGCHI or ACM to provide space for
>a website such as the one from SwissCHI. I remember that you told about
>such an offer at the CHI 97 workshop. But is it also valid if we want
>to have our own domain (www.SwissCHI.ch). Additionally, if the URL(s)
>http://www.acm.org/sigchi/SwissCHI and/or
>http://www.acm.org/chapters/SwissCHI would point to our domain we could
>be reached by several path.
>
>Anyhow, we will acquire the domain www.SwissCHI.ch and look for a
>provider to host that domain. So, could you tell me if this could be
>ACM or SIGCHI or point me to somebody who can answer that.

Gary Perlman recently answered similar questions posed by folks at CHIA
(the Atlanta prospective chapter).  Here is the Q&A of relevance (where
"they" is a reference to ACM):

>>    Can they handle virtual URL's? (e.g. www.chia.org)
>
>Yes, but they prefer to not do that, I think.
>You would be responsible for registering your domain.
>If they agree to it, your URL is likely to break often
>(that's my experience with www.hcibib.org).

I've "cc"ed Gary on this in the event that my extraction of the Q&A leaves
something out that he thinks is important.

Richard

P.S. In the event you need further instructions for obtaining webspace from
ACM, here they -- written mostly by Gary -- are:

=================
To request a web account on acm.org, send email to both clore@acm.org and
support@acm.org.

The account application should contain:

1. The name of your local chapter.

2. The name and email of the Local Chapter's Information Director.
        Ask for a login on turing.acm.org in that person's name,
        and any other names of people who will be in that group.
        CC the request to the Chapter Chair, who is the official
        who is allowed to make such requests on a chapter's behalf.
        ACM will respond with the account name and passwords
        when the work is done (not likely when the request is received).

3. The name of the chapter home directory and group alias,
        which I recommend be the same lower case name for simplicity.
        The home dir of the chapter will be owned by the
        information director in the chapter's group.
        For example, buckchi is in:
                /acminfo/1/chapters/buckchi
        and their infodir owns the directory.
        The URL for this directory is:
                http://www.acm.org/chapters/buckchi/

Gary highly recommends putting extra effort into submitting a numbered
list of requests.  A paragraph of requests may only have one item
addressed.  Numbered lists are good for progress tracking.  Keep all
requests so you can complain about lack of service.

Chapter infodirs should be familiar with UNIX, ftp, and HTML.  They
might take a look at the SIGCHI InfoDir page, which has links to what
SIGCHI and ACM has done.
        http://www.acm.org/sigchi/infodir/
One other option is for the page owners to develop and maintain
their pages on their machines and ftp the pages to turing.acm.org.
=================

   ___________________________________________________________________
                           Richard I. Anderson
          Usability/Design/Discovery Adventures, +1 510 524-2421
       riander@well.com  rianderson@acm.org  rianderson@baychi.org
               717 Coventry Road, Kensington CA 94707 USA
                   http://www.well.com/user/riander/



From jkramer@nyse.com Thu Jul  2 08:26:54 1998
Received: (from uucp@localhost) by nyse-bh.nyse.com (8.6.12/8.6.11) id IAA12870; Thu, 2 Jul 1998 08:33:34 -0400
From: jkramer@nyse.com
Received: from 159.125.144.33 by nyse-bh.nyse.com via smap (3.2)
	id xmaa12774; Thu, 2 Jul 98 08:33:12 -0400
Received: by nyse.com(Lotus SMTP MTA v1.1 (385.6 5-6-1997))  id 85256635.0044D744 ; Thu, 2 Jul 1998 08:31:55 -0400
X-Lotus-Fromdomain: NYSECORP@NYSE
To: sweiss@usableproducts.com, Phillips@hq.acm.org, riander@well.com,
        instone@usableweb.com, israel@acm.org, jkramer@nyse.com,
        perlman@turing.acm.org
Message-Id: <85256635.00433264.00@nyse.com>
Date: Thu, 2 Jul 1998 08:21:54 -0400
Subject: Apologies & Moving Forward
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Status: RO


I would like to publicly apologize to Richard for the tone of some of the
recent emails.  The majority of us are volunteering and trying to do what
we can to promote and encourage professional discussions of subject matter
related to our field.  It is unfortunate that sometimes things digress to a
personal level and this should not happen.
Hopefully on a more positive note, moving forward, it is definitely my
intention to try and schedule a meeting (by the latest end of the summer)
where we present to all the names on our mailing list the option, benefits
and proposed charter to become a legitimate authorized SIGCHI chapter.
Joseph



