From: Jan Isley
Subject: CFV: comp.std.lisp moderated and comp.org.lisp-users
Date:
Message-ID: <2cb95jINNo0l@rodan.UU.NET>
FIRST CALL FOR VOTES (of 2)
This is the first of two Call For Votes (CFV) regarding the proposed
creation of two new newsgroups. Please read the proposals before voting.
Detailed instructions for voting are given below.
Unmoderated group: comp.org.lisp-users
Moderated group: comp.std.lisp (moderated)
Newsgroups lines:
comp.org.lisp-users Association of Lisp Users related discussions.
comp.std.lisp User group (ALU) supported standards. (Moderated)
moderator: Brad Miller <······@cs.rochester.edu>
submission address: ··············@cs.rochester.edu
Votes must be received by 23:59:59 GMT, 7 December 1993.
This vote is being conducted by a neutral third party. All questions
regarding voting and procedure or reports of problems should be mailed
to Jan Isley <···@bagend.atl.ga.us>.
Votes should be mailed to ············@mathcs.emory.edu.
All questions regarding the proposed new groups should be mailed to
the proposer, Brad Miller <······@cs.rochester.edu>.
All questions regarding the comp.org.lisp-users to ALU mailing list
gateway to Charles Fry <······@ptolemy.arc.nasa.gov>.
The CFV will be sent to the following mailing lists:
··········@ucbvax.berkeley.edu ·········@ai.sri.com
···········@ai.sri.com ····@ai.sri.com
CHARTERS
comp.org.lisp-users
-------------------
Discussion of general topics relevant to the Association of Lisp Users
(ALU) (including Lisp Vendors), in particular centered on membership
issues, future conferences, publications, and Lisp advocacy issues.
Overlap with comp.lang.lisp.*, and other groups this message is cross-
posted to should be minimal, as this is NOT intended to be a technical,
but an organizational group. The ALU mailing list will be bidirectionally
gatewayed into this newsgroup.
Participation will not be limited to current ALU members.
comp.std.lisp (moderated)
-------------------------
This moderated group is intended to foster focused discussion on
user-group supported standards that are beyond the scope of more
formal standards e.g. that are not addressed in the (almost final)
ANSI Common Lisp. It will be moderated for appropriateness to the
group and timeliness, and not for technical content; the moderator
will periodically post the status of all ALU standard proposals,
open and close discussions on new standards, and call for specific
technical experts to take charge of each standard (for surveying
existing practice, proposing, incorporating changes, and wording
the final version). The moderator will be reponsible for recording
all finalized standards for the ALU, assigning identifiers and sub-
mitting copies to all interested vendors. The initial intent is to
give feedback to the several LISP vendors for inter-vendor compatible
support of various features that have developed too late to be included
in the work of ANSI committee X3J13, such as (but not limited to)
DEFSYSTEM, Foreign Function Interface, and Multiprocessing.
Participation will not be limited to current ALU members.
Moderator: Brad Miller <······@cs.rochester.edu>
Submission address: ··············@cs.rochester.edu
RATIONALE
comp.org.lisp-users
-------------------
Although SLUG (Symbolics Lisp Users Group) evolved into the Association
of Lisp Users, the mailing list for SLUG is still used for discussions
related to issues regarding Symbolics products. As such, it is not the
appropriate vehicle for discussions relevant for the entire membership
of ALU. One of the primary purposes behind the ALU organization is to
promote the use of, and education about LISP-like languages. At the ALU
(open) board meeting at LUV '93, we discussed this and felt that a
newsgroup in the comp.org hierarchy could best help us achieve our goals
of disseminating information about promoting lisp to interested parties,
have a single place for discussing how the ALU can help parties
interested in lisp, and have a useful place for discussion on future
conferences and a possible periodical take place. Furthermore the ALU
does NOT restrict itself to only common-lisp, but all dialects of lisp
like languages.
comp.std.lisp
-------------
At LUV-93 it was clear from the common lisp vendors that they would not
be investing substantial amounts of effort in attempting to make their
products compatible with each-other without some firm guidance and
commitment from their users. We felt that the ALU, by providing a forum
to define such "de facto" standards, could help the user community
better coordinate on cohesive needs, and thus provide a "single voice"
to the vendors for important (compatibility related) standards issues.
By opening up the discussion to the public via this newsgroup, we hope
to better represent real-world users, not just the "academic" few who
usually participate in standards adventures. At that time, I volunteered
to coordinate such "de facto" (better called "de dicto") standards
creation for the ALU, though commentary would be open to all interested
parties. comp.std.lisp would be the place to hold specific focused
discussion on these evolving standards, which would ultimately evolve
into some sort of request to the vendor community to support specific
features (in addition to, or in place of overlapping features they
already support).
While the initial discussion on comp.std.lisp will concentrate on
common-lisp, it is not, in principle, so limited; it is intended to be a
good place for users of any lisp dialect to communicate and attempt to
agree on non-formal standards that can be used as feedback from users to
vendors and other implementation groups. However, where better forums for
a particular dialect or branch of lisp exists, the user will be strongly
encouraged by the moderator to use that forum instead of comp.std.lisp
(since presumably that will be where the audience for the idea is).
VOTING INSTRUCTIONS
Mail votes to: ············@mathcs.emory.edu
(R)eplying to this message should address your vote correctly if
you are replying to this message in its originally posted form in
a newsgroup or mailing list, and your news reader or mail user
agent honors the Reply-To: header. Posted votes or votes mailed to
any other address do not count.
Valid votes are YES, NO, ABSTAIN or CANCEL. Case is not important.
If you don't want to vote on a particular group, just leave the space
blank. Anything else may be rejected by the automatic vote counting
program. ABSTAIN votes do not affect the vote outcome. If your mail
software does not include your name, include it in the ballot on the
line provided.
If you change your mind, revote. Only the last vote will count.
You should receive a personal acknowledgment of your vote by email
within a few days. Invalid votes and bounced acknowledgments will
be identified in the second (the last) call for votes. Addresses
and votes of all voters will be published in the vote results. If
you wish to remove your vote and all indication that you have voted
from the final list, send a vote with CANCEL in each voting position.
Standard Guidelines for voting apply - one vote per person, etc...
100 more YES votes than NO votes and 2/3 of all votes being YES are
the requirements for group creation. Read news.announce.newusers
and news.groups for more information on the group creation process.
QUICK AND EASY INSTRUCTIONS!
* Use the ballot.
* Include your name on the line provided.
* Indicate either YES, NO, ABSTAIN or CANCEL for each group.
* Check the address again <············@mathcs.emory.edu>
* Mail only the ballot and delete all other text.
-=-=- Do Not Delete Anything Between These Lines -=-=-
lisp groups Ballot [lisp-01]
Give your real name here:
[Your Vote] Group
------------------
[ ] comp.org.lisp-users
[ ] comp.std.lisp
-=-=- Do Not Delete Anything Between These Lines -=-=-
--
Jan Isley, the Knight who says ACK, can be reached at
···@bagend.atl.ga.us or mathcs.emory.edu!bagend!jan
From: Jan Isley
Subject: 2nd CFV: comp.std.lisp moderated and comp.org.lisp-users
Date:
Message-ID: <lisp-groups-CFV2@uunet.uu.net>
LAST CALL FOR VOTES (of 2)
This is the last of two Call For Votes (CFV) regarding the proposed
creation of two new newsgroups. Please read the proposals before voting.
Detailed instructions for voting are given below.
Unmoderated group: comp.org.lisp-users
Moderated group: comp.std.lisp (moderated)
Newsgroups lines:
comp.org.lisp-users Association of Lisp Users related discussions.
comp.std.lisp User group (ALU) supported standards. (Moderated)
moderator: Brad Miller <······@cs.rochester.edu>
submission address: ··············@cs.rochester.edu
Votes must be received by 23:59:59 GMT, 7 December 1993.
This vote is being conducted by a neutral third party. All questions
regarding voting and procedure or reports of problems should be mailed
to Jan Isley <···@bagend.atl.ga.us>.
Votes should be mailed to ············@mathcs.emory.edu.
All questions regarding the proposed new groups should be mailed to
the proposer, Brad Miller <······@cs.rochester.edu>.
All questions regarding the comp.org.lisp-users to ALU mailing list
gateway to Charles Fry <······@ptolemy.arc.nasa.gov>.
The CFV will be sent to the following mailing lists:
··········@ucbvax.berkeley.edu ·········@ai.sri.com
···········@ai.sri.com ····@ai.sri.com
CHARTERS
comp.org.lisp-users
-------------------
Discussion of general topics relevant to the Association of Lisp Users
(ALU) (including Lisp Vendors), in particular centered on membership
issues, future conferences, publications, and Lisp advocacy issues.
Overlap with comp.lang.lisp.*, and other groups this message is cross-
posted to should be minimal, as this is NOT intended to be a technical,
but an organizational group. The ALU mailing list will be bidirectionally
gatewayed into this newsgroup.
Participation will not be limited to current ALU members.
comp.std.lisp (moderated)
-------------------------
This moderated group is intended to foster focused discussion on
user-group supported standards that are beyond the scope of more
formal standards e.g. that are not addressed in the (almost final)
ANSI Common Lisp. It will be moderated for appropriateness to the
group and timeliness, and not for technical content; the moderator
will periodically post the status of all ALU standard proposals,
open and close discussions on new standards, and call for specific
technical experts to take charge of each standard (for surveying
existing practice, proposing, incorporating changes, and wording
the final version). The moderator will be reponsible for recording
all finalized standards for the ALU, assigning identifiers and sub-
mitting copies to all interested vendors. The initial intent is to
give feedback to the several LISP vendors for inter-vendor compatible
support of various features that have developed too late to be included
in the work of ANSI committee X3J13, such as (but not limited to)
DEFSYSTEM, Foreign Function Interface, and Multiprocessing.
Participation will not be limited to current ALU members.
Moderator: Brad Miller <······@cs.rochester.edu>
Submission address: ··············@cs.rochester.edu
RATIONALE
comp.org.lisp-users
-------------------
Although SLUG (Symbolics Lisp Users Group) evolved into the Association
of Lisp Users, the mailing list for SLUG is still used for discussions
related to issues regarding Symbolics products. As such, it is not the
appropriate vehicle for discussions relevant for the entire membership
of ALU. One of the primary purposes behind the ALU organization is to
promote the use of, and education about LISP-like languages. At the ALU
(open) board meeting at LUV '93, we discussed this and felt that a
newsgroup in the comp.org hierarchy could best help us achieve our goals
of disseminating information about promoting lisp to interested parties,
have a single place for discussing how the ALU can help parties
interested in lisp, and have a useful place for discussion on future
conferences and a possible periodical take place. Furthermore the ALU
does NOT restrict itself to only common-lisp, but all dialects of lisp
like languages.
comp.std.lisp
-------------
At LUV-93 it was clear from the common lisp vendors that they would not
be investing substantial amounts of effort in attempting to make their
products compatible with each-other without some firm guidance and
commitment from their users. We felt that the ALU, by providing a forum
to define such "de facto" standards, could help the user community
better coordinate on cohesive needs, and thus provide a "single voice"
to the vendors for important (compatibility related) standards issues.
By opening up the discussion to the public via this newsgroup, we hope
to better represent real-world users, not just the "academic" few who
usually participate in standards adventures. At that time, I volunteered
to coordinate such "de facto" (better called "de dicto") standards
creation for the ALU, though commentary would be open to all interested
parties. comp.std.lisp would be the place to hold specific focused
discussion on these evolving standards, which would ultimately evolve
into some sort of request to the vendor community to support specific
features (in addition to, or in place of overlapping features they
already support).
While the initial discussion on comp.std.lisp will concentrate on
common-lisp, it is not, in principle, so limited; it is intended to be a
good place for users of any lisp dialect to communicate and attempt to
agree on non-formal standards that can be used as feedback from users to
vendors and other implementation groups. However, where better forums for
a particular dialect or branch of lisp exists, the user will be strongly
encouraged by the moderator to use that forum instead of comp.std.lisp
(since presumably that will be where the audience for the idea is).
VOTING INSTRUCTIONS
Mail votes to: ············@mathcs.emory.edu
(R)eplying to this message should address your vote correctly if
you are replying to this message in its originally posted form in
a newsgroup or mailing list, and your news reader or mail user
agent honors the Reply-To: header. Posted votes or votes mailed to
any other address do not count.
Valid votes are YES, NO, ABSTAIN or CANCEL. Case is not important.
If you don't want to vote on a particular group, just leave the space
blank. Anything else may be rejected by the automatic vote counting
program. ABSTAIN votes do not affect the vote outcome. If your mail
software does not include your name, include it in the ballot on the
line provided.
If you change your mind, revote. Only the last vote will count.
You should receive a personal acknowledgment of your vote by email
within a few days. Invalid votes and bounced acknowledgments will
be identified in the second (the last) call for votes. Addresses
and votes of all voters will be published in the vote results. If
you wish to remove your vote and all indication that you have voted
from the final list, send a vote with CANCEL in each voting position.
Standard Guidelines for voting apply - one vote per person, etc...
100 more YES votes than NO votes and 2/3 of all votes being YES are
the requirements for group creation. Read news.announce.newusers
and news.groups for more information on the group creation process.
QUICK AND EASY INSTRUCTIONS!
* Use the ballot.
* Include your name on the line provided.
* Indicate either YES, NO, ABSTAIN or CANCEL for each group.
* Check the address again <············@mathcs.emory.edu>
* Mail only the ballot and delete all other text.
-=-=- Do Not Delete Anything Between These Lines -=-=-
lisp groups Ballot [lisp-02]
Give your real name here:
[Your Vote] Group
------------------
[ ] comp.org.lisp-users
[ ] comp.std.lisp
-=-=- Do Not Delete Anything Between These Lines -=-=-
If you voted, you should have received a vote ack. There are no
bounced acks at this time.
--
Jan Isley, the Knight who says ACK, can be reached at
···@bagend.atl.ga.us or mathcs.emory.edu!bagend!jan
Lisp groups results - 165 valid votes
Yes No : 2/3? >100? : Pass? : Group
---- ---- : ---- ----- : ----- : -------------------------------------------
142 14 : Yes Yes : Yes : comp.std.lisp (moderated)
148 13 : Yes Yes : Yes : comp.org.lisp-users
3 invalid votes
Newsgroups lines:
comp.org.lisp-users Association of Lisp Users related discussions.
comp.std.lisp User group (ALU) supported standards. (Moderated)
moderator: Brad Miller <······@cs.rochester.edu>
submission address: ··············@cs.rochester.edu
This vote was being conducted by a neutral third party. All questions
regarding voting and procedure or reports of problems should be mailed
to Jan Isley <···@bagend.atl.ga.us>.
Jan has had some problems on his end with getting the results out. He
sent me the raw results files and I've created this results posting.
All questions regarding the proposed new groups should be mailed to
the proposer, Brad Miller <······@cs.rochester.edu>.
All questions regarding the comp.org.lisp-users to ALU mailing list
gateway to Charles Fry <······@ptolemy.arc.nasa.gov>.
CHARTERS
comp.org.lisp-users
-------------------
Discussion of general topics relevant to the Association of Lisp Users
(ALU) (including Lisp Vendors), in particular centered on membership
issues, future conferences, publications, and Lisp advocacy issues.
Overlap with comp.lang.lisp.*, and other groups this message is cross-
posted to should be minimal, as this is NOT intended to be a technical,
but an organizational group. The ALU mailing list will be bidirectionally
gatewayed into this newsgroup.
Participation will not be limited to current ALU members.
comp.std.lisp (moderated)
-------------------------
This moderated group is intended to foster focused discussion on
user-group supported standards that are beyond the scope of more
formal standards e.g. that are not addressed in the (almost final)
ANSI Common Lisp. It will be moderated for appropriateness to the
group and timeliness, and not for technical content; the moderator
will periodically post the status of all ALU standard proposals,
open and close discussions on new standards, and call for specific
technical experts to take charge of each standard (for surveying
existing practice, proposing, incorporating changes, and wording
the final version). The moderator will be reponsible for recording
all finalized standards for the ALU, assigning identifiers and sub-
mitting copies to all interested vendors. The initial intent is to
give feedback to the several LISP vendors for inter-vendor compatible
support of various features that have developed too late to be included
in the work of ANSI committee X3J13, such as (but not limited to)
DEFSYSTEM, Foreign Function Interface, and Multiprocessing.
Participation will not be limited to current ALU members.
Moderator: Brad Miller <······@cs.rochester.edu>
Submission address: ··············@cs.rochester.edu
comp.*.lisp groups Final Vote Ack
comp.org.lisp-users ----+
comp.std.lisp ---+|
||
··········@mcimail.com Mahmoud Habboub YY
········@verdi.sra.com Myriam Abramson YY
···@ipvaim.unipv.it Alberto Riva YY
········@titanic.cs.umass.edu Scott D. Anderson YY
·······@harlequin.co.uk Andrew Armstrong YY
·····@harlequin.com Andy Latto YY
·····@harlequin.com Andy Sizer YY
········@crd.GE.COM Jim Aragones YY
······@nanterre.maraut.it Philippe Augras YY
····@cs.albany.edu James Ault YY
·····@marlin.arc.nasa.gov Carolyn Banda YY
······@Think.COM Barry Margolin YY
········@aur.alcatel.com Robert Floyd Benningfield Jr. NN
··@anarres.CS.Berkeley.EDU Brian Harvey YN
····@fcca.csi.com Bill McDonald YY
····@proton.uucp William R. McDonald YY
·······@flamingo.Stanford.EDU Tom Binford YY
··@herbison.com B.J. Herbison YY
···@remlap.UUCP Bob Palmer YY
·······@CS.Berkeley.EDU John Tang Boyland -Y
·······@verdi.sra.com Bill Brooks NY
····@cc.gatech.edu Richard Billington YY
·····@BBN.COM Daniel Cerys YY
··@lks.csi.com Christopher Hoover YY
·······@underdog.jpl.nasa.gov Len Charest YY
····@uhics.ics.Hawaii.Edu David N. Chin YY
······@freud.arc.nasa.gov Chuck Fry YY
·····@usceast.cs.scarolina.edu Ernest Cline N-
·······@cs.Usask.ca Randy Coulman YY
········@wavehh.hanse.de Martin Cracauer YY
········@inference.com Fred Dashiell YY
·····@advtech.uswest.com David Wroblewski -Y
······@pinus.slu.se David Axmark YY
·····@DRI.cornell.edu James R. Davis YY
········@BBN.COM Jonathan Delatizky YY
·······@tc.pw.com Jeff DeLisio YY
·····@hobbs.intel.com David Emme YY
···@netcom.com Dennis Allard YY
·······@ESOC.BITNET David Harper NN
··············@imag.fr Didier Guillon YY
·······@cwa.com Dan Murphy YY
·····@owlnet.rice.edu Dorai Sitaram YY
··@harlequin.com Jeff Del Papa YY
······@minerva.cis.yale.edu Rebecca Drayer NN
····@mitre.org David A. Duff YY
········@TITAN.KSC.NASA.GOV Jim Dumoulin YY
···@king.att.com David W. Dykstra YY
····@starbase.mitre.org Eric Lee Peterson YY
···········@avtc.sel.sony.com Eric Weaver Y-
········@irst.it Enrico Franconi YY
········@cs.umass.edu M. Timur Friedman YY
···@cdr.oz.au Frank R Smith YY
·····@aurora.alaska.edu Sean P. Ryan NN
·······@cs.utexas.edu David Gadbois YY
·········@cs.umass.edu Kevin Gallagher YY
·····@marie.physik.tu-berlin.de Georg Schwarz NN
···············@imag.fr Gilles Serasset YY
···@mitec2.mitech.com George Carrette YY
···@Think.COM Guy Steele YY
···@AVON.sltd.dialnet.symbolics.com Guy Footring YY
·······@gnu.ai.mit.edu Basalat Ali Raja YY
······@ma2s2.mathematik.uni-karlsruhe.de Bruno Haible NN
····@aplcenmp.apl.jhu.edu Marty Hall YY
···@NMSU.Edu Heather D. Pfeiffer YY
·····@ux1.cso.uiuc.edu Matt Hucke YY
·····@redrock.com Bob Hutchison YY
···@ai.mit.edu Masayuki Ida YY
·····@engin.umich.edu Iris D. Tommelein YY
·····@unidata.com James Powell YY
·······@gemstone.amd.com Joshua Bleier YY
·········@mmm.com John Collins YY
····@aiai.edinburgh.ac.uk Jeff Dalton YY
···@edsr John E. Mendenhall -Y
············@ucop.edu Jerry Wilcox YY
··@gensym.com John Hodgkinson YY
·······@mv.us.adobe.com Jim Meehan YY
····@mitre.org John Burger YY
···@wstar.mil.wi.us John P. Flanagan YY
····@maths.bath.ac.uk John Fitch -N
···@globalvillag.com John MacWilliamson NN
···@srs.gov John Krieger YY
···@cambridge.apple.com Kim Barrett -Y
·····@ptolemy.arc.nasa.gov Bob Kanefsky YY
······@montefiore.ulg.ac.be Vincent Keunen YY
·····@umunhum.stanford.edu Kevin W. Rudd YY
···@samson.cadr.amis.com Mark Alexander YY
·······@verdi.sra.com Paul Krause YY
·······@mcc.com Tomasz Ksiezyk YY
········@muir.arc.nasa.gov Kevin Thompson YY
·······@hpljl.hpl.hp.com Joachim H. Laubsch YY
···@iexist.att.com Lawrence G. Mayka YY
·············@po.gis.prc.com Bruce Loatman YY
·····@ils.nwu.edu Richard Lynch YY
······@aaii.oz.au Magnus Ljungberg YY
·····@cacs.usl.edu Tony Maida YY
·······@mosaic.nyu.edu Marco Antoniotti YY
·····@harlequin.com Mark Friedman YY
··················@imag.fr Mathieu Lafourcade YY
········@di.epfl.ch Fernando D. Mato Mira YY
······@silibio.ncsa.uiuc.edu Michael Bobak YY
·······@stc.lockheed.com Albert P. Mendall Jr. YY
······@cam.nist.gov Bruce Miller YY
······@cs.rochester.edu Brad Miller YY
······@stsci.edu Glenn Miller YY
·····@tc.pw.com Stephen E. Miner YY
···@jekyll.al.alcoa.com Michael L. Harper YY
···@adoc.xerox.com Richard Mlynarik YY
···@RedBrick.COM Maxime Taksar --
·····@rap.ucar.EDU Corinne Morse YY
······@BBN.COM Michael Thome YY
········@ann-arbor.applicon.slb.com Peter Mullarkey YY
··@dfki.uni-sb.de Stephan Oepen YY
·····@athena.gsfc.nasa.gov Bruce O'Neel YY
···@ai.mit.edu Patrick A. O'Donnell YY
·····@idsia.ch Paolo Cattaneo YY
·····@harlequin.co.uk Pekka P. Pirinen -Y
·····@hal.cs.uiuc.edu Eduardo Perez YY
·····@ggt.gsi.com Peter Denno YY
·······@isrc.sandia.gov Patrick G. Xavier YY
···@sunbim.be Pierre-Joseph GAILLY YY
·····@ai.sri.com Peter Karp YY
······@psilink.com Harold Ancell YY
····@potomac.ads.com Tom Pole YY
·······@ppn3.physics.nottingham.ac.uk Andy Cross NN
·····@usc.edu Keith Price YY
·····@phoenix.princeton.edu Michael Quinn YY
······@cs.rochester.edu Cesar Quiroz YY
·····@dax.cc.uakron.edu Mark Allgood YY
······@ki6.informatik.uni-hamburg.de Rainer Joswig YY
·······@linc.cis.upenn.edu Lance A. Ramshaw YY
···@csl.sri.com R. A. Riemenschneider YY
···@netcom.com Robert D. Pfeiffer YY
····@cambridge.apple.com Kalman Reti YY
····@midway.uchicago.edu Sendhil Revuluri YN
·······@bnr.ca Dick Peacocke --
····@bcm.tmc.edu Richard Miller NY
······@cfr32.cfr.nist.gov Richard L. Smith YY
···········@open.ac.uk Richard Barber YY
····@kurz-ai.com Sam Pilato YY
··········@mindlink.bc.ca Scott Busse YY
········@aero.org David Schulenburg YY
······@hplmsm.hpl.hp.com Shahid Mujtaba YY
·····@spr.com Shane Hartman NY
······@willow.sdd.trw.com Lynda L. True YY
·······@NADC.NADC.NAVY.MIL Mark Silbert NY
·····@lia.di.epfl.ch Simon Leinen YY
······@io.org Smarasderagd NN
··············@boeing.com Stephen L Nicoud YY
···@cs.hut.fi Seppo Torma YY
···@valinor.mythical.com Stu Labovitz YN
···@STONY-BROOK.SCRC.Symbolics.COM Scott McKay YY
···@ISI.EDU Thomas Russ -Y
······@ptolemy.arc.nasa.gov Will Taylor YY
···············@cup.portal.com Thomas E. Morgan YY
···@dpe.fi Tapio Karras YY
········@faui80.informatik.uni-erlangen.de Tim Geisler YY
····@cs.cmu.edu Todd Kaufmann YY
········@Ipchost.irmkant.rm.cnr.it Vittorio Giannini YY
········@lug.cs.brandeis.edu T.S. Waterman YY
·······@ipl.rpi.edu Frederick Wheeler YY
·····@cs.vu.nl Jude Arnout "Biep" Durieux YY
········@galcon.ersys.edmonton.ab.ca Dave Yadallee YY
····@harlequin.co.uk Judy Anderson YY
·······@meg.saic.com Tom Yonkman YY
····@parc.xerox.com William M. York YY
Votes in error
------------------------------------------------------------------------------
··········@BAM.GARNET.CS.CMU.EDU
! No name given
·······@elec.enst.fr JC Dufourd
! No votes
····@Exploder Clint Hyde -- Master of the ad hoc odd hack.
! No ballot