[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

2nd CFV: comp.std.lisp moderated and comp.org.lisp-users

                      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 <miller@cs.rochester.edu>
submission address:	lisp-standards@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 <jan@bagend.atl.ga.us>.

Votes should be mailed to usenet-votes@mathcs.emory.edu.

All questions regarding the proposed new groups should be mailed to
the proposer, Brad Miller <miller@cs.rochester.edu>.

All questions regarding the comp.org.lisp-users to ALU mailing list
gateway to Charles Fry <chucko@ptolemy.arc.nasa.gov>.

The CFV will be sent to the following mailing lists:

allegro-cl@ucbvax.berkeley.edu     alu-board@ai.sri.com
common-lisp@ai.sri.com             slug@ai.sri.com


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 <miller@cs.rochester.edu>
Submission address:  lisp-standards@cs.rochester.edu


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.

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).


Mail votes to: usenet-votes@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.

* Use the ballot.
* Include your name on the line provided.
* Indicate either YES, NO, ABSTAIN or CANCEL for each group.
* Check the address again <usenet-votes@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
jan@bagend.atl.ga.us  or  mathcs.emory.edu!bagend!jan