[ADMIN] Welcome to comp.std.lisp!
Brad Miller
You've seen it before, but here is a copy of the charter:
This moderated (sub)group is intended to foster focused
discussion on user-group supported standards 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 submitting copies to all interested vendors. The 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.
To submit articles, send them to lisp-st...@cs.rochester.edu
This newsgroup is Moderated and Undigested.
While the above are examples, I am not going to insist they are
addressed here initially (but see following messages).
What *is* addressed here is up to you. To keep the topics "relevant",
I'd like to propose that new topics should have some minimal consensus
of opinion for being addressed (i.e. that some user-group standard is
needed, and there is no real overlap with some other standards
organization, e.g. the current work of ANSI X3J13). So to open a new
topic, I'd like to propose that at least 5 individuals concur that the
topic should be opened, and 50% more people think the topic is needed
than do not.
I also propose the same for closing a topic (which is different from
accepting a standard, but I'll address that later :-). A topic may be
closed independantly of having acheived a standard. Normally that would
only be done if a consensus decides that a topic is no longer relevant,
e.g. technology has marched on, or ANSI has decided to add it to their
standard.
These rules aren't graven in stone; they're just my idea for keeping
things relevant. Feel free to critique and/or add your own ideas.
Further discussion on these rules will be marked [ADMIN], with a keyword
of admin and rules, just like this message is.
***
As moderator, I am not going to modify messages, with minor exceptions.
Headers will probably not be preserved, modulo From: ; in particular I
reserve the right to modify the Subject: line, and/or Summary: and
Keywords: to allow for easy filtering of (un)wanted material.
I may abbreviate excessive quoting, or answer questions of fact. These
sorts of alterations will appear within square brackets (i.e. [...]
indicates quoting deleted from the original). Mainly this is to cut down
on bandwidth on the mirror mailing list that is currently being set up.
Other than that, I'll keep my own comments to separate messages.
Inappropriate material, if rejected, will be returned to the sender.
I understand I need to post a "anonymous poster" policy. Basically, I
feel that the only thing keeping discussion civil (since I'm *not*
editing messages :-), is **your name** on it. Therefore, I will insist
all submissions come from real accounts, with real names attached to
them (either in the From: header or in your signature). If you have a
real reason for posting something anonymously (i.e. you wish to render
an opinion disjoint from your employer's, which you feel may lead to
some difficulties :-), then I'll make a decision on a case by case
basis. At any rate, I'll know who you are :-).
I'll keep up a list of keywords I'm using, and post them periodically,
i.e. messages like this one will have a keyword of "admin", and messages
about new topics (or asking for the close of an old one) will have a
keyword of "topic". The most important keyword, (or the proposed
standard id) will also appear in square brackets in the subject line,
since I understand some newsreaders (both programs and humans :-) don't
understand the keywords header.
---- Brad Miller mil...@cs.rochester.edu
Submissions to: lisp-st...@cs.rochester.edu
Metamail (not for publication) to: lisp-standa...@cs.rochester.edu
An archive is maintained on ftp.cs.rochester.edu:/pub/lisp-standards/
Code submissions to: ftp.cs.rochester.edu:/incoming/
Please read the README files in those directories for directions.