RFD: comp.object.moderated moderated

RFD: comp.object.moderated moderated

[Tim Ottinger]

                     REQUEST FOR DISCUSSION (RFD)
                moderated group comp.object.moderated

comp.object.moderated    A moderated forum for Object-oriented issues.

This is a formal Request For Discussion (RFD) for the creation of a
world-wide moderated Usenet newsgroup comp.object.moderated.  This is
not a Call for Votes (CFV); you cannot vote at this time.  Procedural
details are below.

RATIONALE: comp.object.moderated

Object-oriented programming has long ago graduated from a niche study to
an industry force, so the discussion of things object-oriented has
likewise increased in general interest and audience. This surge has
increased the participation in comp.object so that it is difficult for
participants to keep up with the volume.

In addition, the comp.object newsgroup now receives a substantial
number of inappropriate posts, much of which are of little value or
interest to the community at large. The inappropriate postings have
caused many to cease participation due to the decreased signal-to-noise
ratio, and in some cases fear of reprisal.

There is therefore a need to provide a forum for which people with
interest in object-oriented theory and practice can freely and openly
discuss their problems and solutions, keep abreast of developments in
Object-oriented practice, and interact with their peers around the world
in a non-threatening manner without being harrassed by SPAM or articles
of otherwise inappropriate content.

In order to keep discussions centered on the issues of Object-oriented
theory and practice, encourage participation, and thereby better serve
the Object-oriented community in its entirety, a moderated discussion
group is required.

At the same time, there is also a demand for a continuing low-delay
unmoderated forum. Hence, this proposal is for the creation of a new
moderated group coupled with the existing unmoderated group comp.object.


This RFD favors this option because it interferes less with existing
practices and thus will more likely lead to manageable moderation
duties, and it parallels what was done with in the comp.lang.c and
comp.lang.C++, and thus is quite intuitive.


CHARTER: comp.object.moderated

Comp.object.moderated is a moderated news group for discussion of
issues directly related to Object-oriented theory and Object-oriented
practice, and of general interest to the Object-oriented community. Any
such articles are welcome, and are recommendations of alternative
approaches in response to questions directly related to Object-oriented
theory or practice.

Moderation Policy:

I PRINCIPLES

Moderation is desired to attract and maintain participation by old
posters, new posters, and especially expert posters. To do so,
comp.object.moderated provides a non-threatening forum for discussing
Object-oriented practice and theory. To attract and maintain a large
professional readership this policy ensures that the forum is as concise
and useful as it can possibly be.

Here is what this moderation policy is intended to achieve with
respect to each article:

1) ON TOPIC
2) NO FLAMES
3) NO SPAM
4) NO NONSENSE

These goals are characterized as follows:

1) ON TOPIC

(Discussions of) the following subjects are regarded as being on topic
in comp.object.moderated:

a) the syntax and semantics of various Object-oriented languages,
b) Object-oriented tricks and techniques,
c) case studies,
d) issues of software engineering related to Object-oriented,
e) issues of software management related to Object-oriented,
f) issue of design philosophy related to Object-oriented,
g) design patterns related to Object-oriented, etc.
h) Object-oriented analysis techniques.
i) Object-oriented process.
j) Object-oriented tools.
k) Object-oriented Modeling.
l) any and all other discussions relating or pertaining to Object-
oriented techniques.
m) management and policy of the newsgroup.

Articles may be rejected as being off-topic if there are
other, more specific newsgroups to which they belong.

If an article references products like tools, libraries or
platforms, it is still acceptable if the article just mentions
these products as illustrations or examples and abstains from
support questions.


WHEN IN DOUBT

An article shall be accepted, especially for short off-topic
digressions in a thread. In order to keep the noise level low, if such
an article has already been accepted in recent days, the moderator body
may decide to reject the newer one and refer the author to the earlier
one.

2) NO FLAMES

a) No threats or attempts at intimidation are tolerated.  Those drive
away audience. New posters are intimidated by it, and experts don't have
the time or energy to waste on it. Such things are personal, and not of
interest to the general Object-oriented audience.

b) No disrespect towards others is tolerated. When people are unkind,
new people will choose not to participate.  Personal feelings against
one or another are not of interest to the general Object-oriented
audience. People should read all ideas, and choose the ones that work
for them, and a poor idea should be shown to be poor by technical or
practical reasons.

c) No disdainful or belittling articles are tolerated, no matter
whether the contents of the article are otherwise correct or not.

d) Questioning of other people's motives and honesty is explicitly
considered both off-topic and extremely rude, no matter whether the
contents of the article are otherwise correct or not.

d) Any but the most light-hearted attempts at one-upmanship will be
disallowed. Participation in a comp.object.moderated thread is not a
contest with prizes for the winners.

In essence, all attempts to hijack comp.object.moderated to wage a
personal attack would not only be counter-productive, but also
off-topic. When people speak against each other, they've lost focus on
the issues at hand.

WHEN IN DOUBT

An article is rejected. Not a flame shall pass through.

3) NO NONSENSE

a) FAQs aren't nonsense, but the repeated posting and answering of
them is. Nobody wants to read the exact same questions and answers
over and over. It's a burden on the reader that gates his productive use
of the forum.

b) Verbatim or slightly rephrased reposts are nonsense.
c) Trolls are nonsense.
d) Binaries are considered inappropriate in this newsgroup.

In short, comp.object.moderated should be a forum you can read with the
same confidence you have reading a manual or technical journal. It is an
interactive professional forum, not a hobbyist board or a war board. It
belongs to the community of people whose work is the practice and theory
of Object-Orientation, and anything that turns the newsgroup away from
that community, or turns the community away from the newsgroup, is not
welcome.

WHEN IN DOUBT

An article is accepted, general noise level permitting.

4) NO SPAM

The war on SPAM is the war to maintain control of the professional
nature and the signal-to-noise ratio of a newsgroup.

The Jargon File (http://sagan.earthspace.net/jargon) describes
spam in the following terms:
"...To cause a newsgroup to be flooded with irrelevant or
inappropriate messages. [...] To send many identical
or nearly-identical messages separately to a large number
of Usenet newsgroups..."

Whatever a moderator has to do to stop SPAM without rejecting
legitimate posts is good. If stopping spam means blacklisting
spam-posters, then so be it. If it involves building complex filtering
rules, fine. If it is easily handled by rejecting posts, fine again.

WHEN IN DOUBT

An article is rejected.

II MEANS

These goals are to be achieved as follows:

1) Automated format checking

If the posted article is not properly formatted (i.e. the news headers
aren't right -- your news software should take care of this) or if the
article is larger than 50KB, then it will be automatically rejected. The
poster may or may not be notified of this kind of rejection, depending
upon just how bad the headers were. Articles without Date: or Subject:
headers are not properly formatted.

2) Moderator Notes

Moderators may add a note to an article only for the reasons and
according to the policies stated above or to correct incomplete or
incorrect references.

The form of those notes will always be the same. They will composed of
text in square brackets. The last four characters of the text in square
brackets will be -mod. Thus:

[text of the note. -mod].

Moderators will be extremely conservative with their use of notes.
Most articles should not have any notes. Those that do should have
only one, or at the most two. So be judicious.

3) Acceptance and Rejection Procedures

Accepted articles are to be posted immediately.  When an article is
rejected by a moderator, it will be emailed back to the poster. The
subject of the email message will be: "Rejected, violates: [reason
list]." where reason list is a comma separated list of the codes
specified in the acceptance criteria above. e.g.  "Rejected, violates:
[ON TOPIC, NO FLAMES c)]."

The moderator should include moderator notes in the body of the
article that explain why the article was rejected. The format of those
notes should be as specified above, but they can be as brief or wordy as
needed to get the point across. There also may be as many as needed.

4) Moderator Anonymity

Moderators act as a single body. Any rejection should be viewed as a
rejection by the moderators and not by any particular moderator.  As
such, the identity of the rejecting moderator will not be exposed to the
poster whose article was rejected (i.e. the moderator's signature will
be stripped). Any questions that the poster may have can be referred to
the moderator's hotline email address.

5) Appeal Policy

Any poster of a rejected message may appeal that rejection to the
moderators by emailing the article to the moderators' hotline. The
moderators will review the rejection and either post or reject the
article based upon their conclusion.

6) Moderator Posting Policy

Moderators are not allowed to moderate their own articles. No article
written by a moderator will be posted unless one of the other moderators
accepts it.

7) Moderator Body

The number of moderators shall not become less than five, so as to
preserve the integrity of the appeal process.

When there is a shortage of moderators, the remaining moderators
select willing volunteers who are participants in the newsgroup and
whose posting history shows understanding of and respect for the
moderation policy.

H) FAQ

There will be a collection of answers to comp.object.moderated FAQs
which is made publicly and freely available. The moderator body
maintains, extends and publishes this FAQ document and points the
comp.object.moderated readers to it as appropriate. The moderator body
may decide to delegate this work.

END CHARTER.

MODERATOR INFO: comp.object.moderated

Moderator: Patrick Logan <plogan@teleport.com>
Moderator: Patrick Doyle <doylep@ecf.utoronto.ca>
Moderator: Martijn Meijering <mmeijeri@wi.leidenuniv.nl>
Moderator: John Goodsen <jgoodsen@saguarosoft.com>
Moderator: Rolf Katzenberger <rfkat@ibm.net>
Moderator: Yonat Sharon <yonat@usa.net>

END MODERATOR INFO.

PROCEDURE:

This is a request for discussion, not a call for votes.  In this phase
of the process, any potential problems with the proposed newsgroups
should be raised and resolved.  The discussion period will continue for
a minimum of 21 days (starting from when the first RFD for this proposal
is posted to news.announce.newgroups), after which a Call For Votes
(CFV) may be posted by a neutral vote taker if the discussion warrants
it.  Please do not attempt to vote until this happens.

All discussion of this proposal should be posted to news.groups.

This RFD attempts to comply fully with the Usenet newsgroup creation
guidelines outlined in "How to Create a New Usenet Newsgroup" and "How
to Format and Submit a New Group Proposal".  Please refer to these
documents (available in news.announce.newgroups) if you have any
questions about the process.

DISTRIBUTION:

This RFD will be cross-posted to :
   news.announce.newgroups, news.groups,
   comp.lang.ada, comp.lang.c++, comp.lang.c++.moderated,
   comp.std.c++, comp.lang.clos, comp.lang.eiffel,
   comp.lang.java.programmer, comp.lang.python, comp.lang.smalltalk
   comp.object.corba, comp.object.logic, comp.object
   comp.software-eng, comp.lang.objective-c

Re: RFD: comp.object.moderated moderated

[Ell]

In comp.object Rolf F. Katzenberger <rfkat@ibm.net> wrote:

: <ell@access5.digex.net> wrote:
:>
:> In comp.object Tim Ottinger <ottinger@oma.com> wrote:
:> 
:> >                      REQUEST FOR DISCUSSION (RFD)
:> >                 moderated group comp.object.moderated
:> 
:> > comp.object.moderated    A moderated forum for Object-oriented issues.
:> 
:> > This is a formal Request For Discussion (RFD) for the creation of a
:> > world-wide moderated Usenet newsgroup comp.object.moderated.  This is
:> > not a Call for Votes (CFV); you cannot vote at this time.  Procedural
:> > details are below.
:> 
:> > RATIONALE: comp.object.moderated
:> 
:> >Object-oriented programming has long ago graduated from a niche study to
:> >an industry force, so the discussion of things object-oriented has
:> >likewise increased in general interest and audience. This surge has
:> >increased the participation in comp.object so that it is difficult for
:> >participants to keep up with the volume.
:> >
:> >In addition, the comp.object newsgroup now receives a substantial
:> >number of inappropriate posts, much of which are of little value or
:> >interest to the community at large. The inappropriate postings have
:> >caused many to cease participation due to the decreased signal-to-noise
:> >ratio, and in some cases fear of reprisal.

:> [Overall] The signal-to-noise ratio on comp.object seems very good.

Also Otttinger says above:
:> >and in some cases fear of reprisal.

The implication of physical threats is not absent from this.  And I think
its purpose is to bogusly establish some nebulous possible physical
threat in people's minds.  I have seen nothing of the sort.

: Personally, I find there are too much name calling, aggressive off
: topic postings and trolls here. The percentage varies over time, but
: I'd definitely prefer an additional group for the joy of exclusively
: debating OO topics. The RfD does not propose to replace comp.object
: but to create an additional comp.object.moderated.

My problem is that Usenet and other common resources are being used to
blunt criticism of an ideological position.  Kill files work wonders for
eliminating real noise, but nothing can recover the suppression of the
expression of significant, on-topic comments.

Ottinger in the RFD wrote:
:> >There is therefore a need to provide a forum for which people with
:> >interest in object-oriented theory and practice can freely and openly
:> >discuss their problems and solutions, keep abreast of developments in
:> >Object-oriented practice, and interact with their peers around the world
:> >in a non-threatening manner without being harrassed by SPAM or articles
:> >of otherwise inappropriate content.

: ... Any kind of harassments is annoying, and I'd highly welcome an
: additional newsgroup where I would not have to face them.

But to me the moderators and others opposition to the use of labels not
pertaining to federal civil rights categories is improper suppression of
freedom expression.  While I sympathize with your desire, the baby is
being thrown out with the bath water.

I have concretely and very specifically demonstrated how the labels they
oppose - craftitism craftite, pragmatism, pragmatists, empircicism,
empiricist - are thoroughly related to objects and the other issues of
software engineering.  These get to issues like epistemology - theories of
knowledge (how we gain knowledge) which Meyer mentions in OOSC, Booch
mentions in OOA&D, and RCM recently raised directly in reference to
Meyer's OOSC.  Epistemology is critically related to every aspect of OO
and software engineering.  Even very basic and fundamental questions of
like what is an object, and how should developers relate to users and
analysis are essential and key issues that epistemology and labels used
within it have a vital bearing upon.

I see the suppression of those labels as a clear attempt to blunt
criticism of one viewpoint within OO and software engineering.  They are
are attempting to stomp on freedom of expression *within* a the OO
and related software engineering areas.

:> Next, in no way should labelling people and positions be considered
:> threatening, or spam.  That is a legitimate and appropriate aspect of
:> discussion and debate. 

: The RfD list the contents that are regarded as flames, spam and
: nonsense. It does not mention labelling at all, so all kinds of
: labelling that are not flames, spam or nonsense will be ok.

Given that nearly all proposed moderators opposed such labels in
discussion, I see no basis for thinking that they won't act ideas.

:> >Moderator: Patrick Logan <plogan@teleport.com>
:> >Moderator: Patrick Doyle <doylep@ecf.utoronto.ca>
:> >Moderator: Martijn Meijering <mmeijeri@wi.leidenuniv.nl>
:> >Moderator: John Goodsen <jgoodsen@saguarosoft.com>
:> >Moderator: Rolf Katzenberger <rfkat@ibm.net>
:> >Moderator: Yonat Sharon <yonat@usa.net>
 
:> At least 5 of these 6 hold the same overall software engineering,
:> object-oriented, and philosophical ideas. They will be biased toward
:> supporting and protecting a specific conservative, pragmatic, empiricist
:> software engineering viewpoint and opposing its opposite. 

: It does not matter what OO theories these people, including me,
: support in their postings. It is common for most Usenet moderated
: newsgroups that moderators as moderators do not comment on articles.
: In fact, the 6 people listed above have argued against arbitrary
: notes, as you did.

But their real power is to post or not post.  I have no reason not to
think that they will not post articles because they use the above labels.
Also it must be considered that the terms will probably occur in
posts in discussions where their own positions are being challenged.  In
such an environment, given their stance against the labels, I really think
that the mere presence of labels will cause them to reject it.  *Even as
a group in majority*.

: The current RfD acknowledges your earlier critique with respect to
: moderator notes and restricts the only allowed OO content
: of such notes to the completion of fragmentary or incorrect book/article
: references.

I really don't understand why they shouldn't just post a supposed
corrections like everyone else must.  There is often much more to
purported correction issues than simple correction. 

: Besides that, the only allowed content of such notes are
: references to the moderation policy itself. Period.

Fine.  And of course they hold the power to post or not post.
Nevertheless...

:> I urge that the creation of comp.object.moderated be opposed, as it's
:> formation is more motivated by the above viewpoint avoiding intellectual
:> criticism more than for any other reason. 
:>
:> Especially when one considers that the present comp.object group has low
:> off-topic, and spam messages, while at the same time it has a high degree
:> of informative, robust, vigorous, and useful debate, discussion, and
:> content. 

Elliott
-- 
   :=***=:  Objective  *  Pre-code Modelling  *  Holistic  :=***=:
                 Hallmarks of the best SW Engineering
         "The domain object model is the foundation of OOD."
 Check out SW Modeller vs SW Craftite Central : www.access.digex.net/~ell
   Copyright 1998 Elliott. exclusive of others' writing. may be copied
     without permission only in the comp.* usenet and bitnet groups.

Re: RFD: comp.object.moderated moderated

[Rolf F. Katzenberger]

On Sun, 06 Sep 1998 19:29:56 GMT, in article
<UoBI1.1872$vl.771620959@newsreader.digex.net> Ell
<ell@access2.digex.net> wrote:

> 
> In comp.object Rolf F. Katzenberger <rfkat@ibm.net> wrote:
> 
> : <ell@access5.digex.net> wrote:
> :>
> :> In comp.object Tim Ottinger <ottinger@oma.com> wrote:
> :> 
> :> >                      REQUEST FOR DISCUSSION (RFD)
> :> >                 moderated group comp.object.moderated
> :> 
> :> > comp.object.moderated    A moderated forum for Object-oriented issues.
> :> 
> :> > This is a formal Request For Discussion (RFD) for the creation of a
> :> > world-wide moderated Usenet newsgroup comp.object.moderated.  This is
> :> > not a Call for Votes (CFV); you cannot vote at this time.  Procedural
> :> > details are below.
> :> 
> :> > RATIONALE: comp.object.moderated
> :> 
> :> >Object-oriented programming has long ago graduated from a niche study to
> :> >an industry force, so the discussion of things object-oriented has
> :> >likewise increased in general interest and audience. This surge has
> :> >increased the participation in comp.object so that it is difficult for
> :> >participants to keep up with the volume.
> :> >
> :> >In addition, the comp.object newsgroup now receives a substantial
> :> >number of inappropriate posts, much of which are of little value or
> :> >interest to the community at large. The inappropriate postings have
> :> >caused many to cease participation due to the decreased signal-to-noise
> :> >ratio, and in some cases fear of reprisal.
> 
> :> [Overall] The signal-to-noise ratio on comp.object seems very good.
> 
> Also Otttinger says above:
> :> >and in some cases fear of reprisal.
> 
> The implication of physical threats is not absent from this.  And I think
> its purpose is to bogusly establish some nebulous possible physical
> threat in people's minds.  I have seen nothing of the sort.

I haven't seen anything of the sort, too. However, I did not interpret
"reprisal" as pertaining to physical action at all; after all, that
would be quite strange because newsgroups have participants from a
variety of continents, and e.g. I definitely don't expect anybody to
come to Germany and beat me up just like that ;-)

If I can trust my dictionaries, reprisal means "sanction with a
harmful intent". Of course, this could be a physical threat, too, but
with respect to newsgroup traffic, I exclusively associate it with all
kinds of insults that I found posted in response to even the most
defensive articles, so as to keep even a defensive poster from posting
anything on a topic again. IMHO reprisal is the perfect term for that,
but maybe you know of a better term?

> : Personally, I find there are too much name calling, aggressive off
> : topic postings and trolls here. The percentage varies over time, but
> : I'd definitely prefer an additional group for the joy of exclusively
> : debating OO topics. The RfD does not propose to replace comp.object
> : but to create an additional comp.object.moderated.
> 
> My problem is that Usenet and other common resources are being used to
> blunt criticism of an ideological position.

It seems there is considerable disagreement with respect to what is
"criticism of an ideological position", as well as to what a newsgroup
community may or may not ban.

Since this thread is in response to a concrete RfD, I presume that you
regard some behaviors listed in the NO FLAMES, NO SPAM and NO NONSENSE
sections of the RfD as such criticism that should be allowed. Please
correct me should that assumption be incorrect.

IMHO the RfD list corresponds exactly to all relevant netiquette
documents I have ever read. Furthermore, there are definitely
thousands of moderated Usenet groups. From that I conclude that there
is a wide-spread consensus that

a) flames, spam, and nonsense are unwanted content for most newsgroups
(notwithstanding things like alt.flame* and alt.job* etc., of course).

b) moderation is regarded as a legitimate means to exclude flames,
spam and nonsense from a newsgroup. (from all moderation policies I
know I draw the conclusion that most of them are concerned with
filtering out flames, spam and nonsense; in fact, most of them list
exactly the same things as unwanted that the current RfD lists).

I'm not sure whether you really oppose the netiquette documents or
moderated newsgroups *in principle*. If you don't, I need your help to
understand where the RfD deviates from standard netiquette principles
or why especially comp.object.moderated should *not* be allowed to ban
flames, spam and nonsense, as other moderated groups do.

> Kill files work wonders for
> eliminating real noise, but nothing can recover the suppression of the
> expression of significant, on-topic comments.

IMHO killfiles are clearly inferior to moderation. I only use them for
eliminating spam, but I have never used it to filter out articles by
certain authors (to be correct, I'm using them in the satirical group
de.talk.bizarre, but that is just part the fun going on there).

There is hardly anybody who exclusively posts flames, so in
interesting threads, when I come across articles posted by people who
have flamed others in the past, I nevertheless read those articles.
Like most regulars of moderated newsgroups, I'm glad some moderators
devote some of their time to filter out flames, spam and nonsense for
me.

> Ottinger in the RFD wrote:
> :> >There is therefore a need to provide a forum for which people with
> :> >interest in object-oriented theory and practice can freely and openly
> :> >discuss their problems and solutions, keep abreast of developments in
> :> >Object-oriented practice, and interact with their peers around the world
> :> >in a non-threatening manner without being harrassed by SPAM or articles
> :> >of otherwise inappropriate content.
> 
> : ... Any kind of harassments is annoying, and I'd highly welcome an
> : additional newsgroup where I would not have to face them.
> 
> But to me the moderators and others opposition to the use of labels not
> pertaining to federal civil rights categories is improper suppression of
> freedom expression.  While I sympathize with your desire, the baby is
> being thrown out with the bath water.
> 
> I have concretely and very specifically demonstrated how the labels they
> oppose - craftitism craftite, pragmatism, pragmatists, empircicism,
> empiricist - are thoroughly related to objects and the other issues of
> software engineering.

It is not correct to claim that the moderators in general opposed the
use of labels. E.g. I don't do that. Let me quote from a response
(<35aa7358.0@news1.ibm.net> on 1998-07-13) to one of your articles:

  IMHO "craftism", "empiricism" and "pragmatism" ("craftite",
  "empricist", "pragmatist") should pass moderation, since according
  to popular dictionaries in general none of them carries a negative
  connotation and they are not commonly used as pejorative terms.

  This might not hold true for the words used in your definitions of
  the above terms.

Same day, same thread (<35aa856d.0@news1.ibm.net> on 1998-07-13):

  to me it seems there is positively no need for labeling;
  but as long as a label isn't used as an ad hominem/ad personam
  attack, the moderators IMHO should let it pass (moderators don't
  have to like what they read...).

So should you e.g. ever call Grady Booch a "craftite", I'd let that
pass. Should you state that "Booch is slimy, craftite himself"  (I'm
afraid you did that), I'd reject that because of "slimy", but
certainly not because of "craftite".

I stand by that.

> These get to issues like epistemology - theories of
> knowledge (how we gain knowledge) which Meyer mentions in OOSC, Booch
> mentions in OOA&D, and RCM recently raised directly in reference to
> Meyer's OOSC.  Epistemology is critically related to every aspect of OO
> and software engineering.  Even very basic and fundamental questions of
> like what is an object, and how should developers relate to users and
> analysis are essential and key issues that epistemology and labels used
> within it have a vital bearing upon.

I'd really love to see your epistemological comments on the details of
articles in comp.object.moderated. I'd be a fool to reject them.

> I see the suppression of those labels as a clear attempt to blunt
> criticism of one viewpoint within OO and software engineering.  They are
> are attempting to stomp on freedom of expression *within* a the OO
> and related software engineering areas.

That would be the case, should there be more rejected than just the
flames. In the example cited above, I fail to see how pejorative
adjectives like "slimy" could ever contribute to the discussion of OO
matters.

> :> Next, in no way should labelling people and positions be considered
> :> threatening, or spam.  That is a legitimate and appropriate aspect of
> :> discussion and debate. 
> 
> : The RfD list the contents that are regarded as flames, spam and
> : nonsense. It does not mention labelling at all, so all kinds of
> : labelling that are not flames, spam or nonsense will be ok.
> 
> Given that nearly all proposed moderators opposed such labels in
> discussion, I see no basis for thinking that they won't act ideas.
>
> :> >Moderator: Patrick Logan <plogan@teleport.com>
> :> >Moderator: Patrick Doyle <doylep@ecf.utoronto.ca>
> :> >Moderator: Martijn Meijering <mmeijeri@wi.leidenuniv.nl>
> :> >Moderator: John Goodsen <jgoodsen@saguarosoft.com>
> :> >Moderator: Rolf Katzenberger <rfkat@ibm.net>
> :> >Moderator: Yonat Sharon <yonat@usa.net>
>  
> :> At least 5 of these 6 hold the same overall software engineering,
> :> object-oriented, and philosophical ideas. They will be biased toward
> :> supporting and protecting a specific conservative, pragmatic, empiricist
> :> software engineering viewpoint and opposing its opposite. 
> 
> : It does not matter what OO theories these people, including me,
> : support in their postings. It is common for most Usenet moderated
> : newsgroups that moderators as moderators do not comment on articles.
> : In fact, the 6 people listed above have argued against arbitrary
> : notes, as you did.
> 
> But their real power is to post or not post.  I have no reason not to
> think that they will not post articles because they use the above labels.
> Also it must be considered that the terms will probably occur in
> posts in discussions where their own positions are being challenged.  In
> such an environment, given their stance against the labels, I really think
> that the mere presence of labels will cause them to reject it.  *Even as
> a group in majority*.
> 
> : The current RfD acknowledges your earlier critique with respect to
> : moderator notes and restricts the only allowed OO content
> : of such notes to the completion of fragmentary or incorrect book/article
> : references.
> 
> I really don't understand why they shouldn't just post a supposed
> corrections like everyone else must.  There is often much more to
> purported correction issues than simple correction. 

Frankly, I don't see how e.g. changing "p. 456" to "p. 457" affects
the referenced thing. Correction does not mean things like

  [the original poster's link was inappropriate; you should
  visit www.mycompany.com/myhomepage.html instead -mod]

In fact, I think I'd add the correction after the corrected reference,
to make that clear.

> : Besides that, the only allowed content of such notes are
> : references to the moderation policy itself. Period.
> 
> Fine.  And of course they hold the power to post or not post.
> Nevertheless...

That is what moderators are for.

Maybe this discussion ends up with you stating that you simply will
never trust the/these moderators. I can't think of any way to convince
you, then. If, on the other hand, there is a possibility to make you
confident they will enforce the moderation policy as it is stated,
then please give me a hint how to do that.

Regards,
  Rolf


-- 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

______________________________________________________________________
Rolf F. Katzenberger | Software Developer | Trainer         1998-04-28
Home: http://www.geocities.com/SiliconValley/Park/9557
PGP : http://wwwkeys.pgp.net:11371/pks/lookup?op=get&search=0x3B39491F
      (Fingerprint F1C0 3116 F6D4 DA33 E61D  D2E4 2FB8 D6B6 3B39 491F)
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 5.5.3i for non-commercial use

iQA/AwUBNUX84C+41rY7OUkfEQLV8wCfb/IQACmn+qvT+EIftYMx36ivdRoAoNdF
ugze6Ry3oCiwMtGLSKXHOnqs
=+QML
-----END PGP SIGNATURE-----

Re: RFD: comp.object.moderated moderated

[Robert Martin]

Rolf F. Katzenberger wrote in message <35f3da26.0@news2.ibm.net>...
>On Sun, 06 Sep 1998 19:29:56 GMT, in article
><UoBI1.1872$vl.771620959@newsreader.digex.net> Ell
><ell@access2.digex.net> wrote:

>> Also Otttinger says above:
>> :> >and in some cases fear of reprisal.
>>
>> The implication of physical threats is not absent from this.  And I think
>> its purpose is to bogusly establish some nebulous possible physical
>> threat in people's minds.  I have seen nothing of the sort.
>
>I haven't seen anything of the sort, too.

I have.  How about this one:

---------------------------------------------------------------

Author:   Ell
Email: ell@access.digex.net
Date: 1998/06/17
Forums: comp.object
Message-ID:   <358b04ea.1529278@news.erols.com>
Organization:   Universe
References:   <6m2abn$kef$1@news.interlog.com> <6m35i5$ca4$1@hirame.wwa.com>
<35870B95.925FFB22@palladion.com> <3588e518.14231523@news.erols.com>
<6m8f28$am9$1@hirame.wwa.com>
Reply-To:   ell@access.digex.net
X-Complaints-To:   abuse@erols.com
X-Trace:   winter.news.erols.com 898124862 10511 207.172.87.200 (17 Jun 1998
23:07:43 GMT)

"Robert Martin" <rmartin@oma.com> wrote:

>As for the rest of Elliott's article, well (Reaganesque chuckle),
>who really cares?  Readers are welcome to peruse the articles
>on my website to see if they draw the same conclusions that
>Elliott does.

The ones who care Ronny are the ones who will make you pay for your
backward, reactionary crimes against human progress.

Elliott
----------------------------------------------------------------------------

I saw enough of a personal threat in this particular post to make sure that
my lawyer had a copy.


Robert C. Martin    | Design Consulting   | Training courses offered:
Object Mentor       | rmartin@oma.com     |   Object Oriented Design
14619 N Somerset Cr | Tel: (800) 338-6716 |   C++
Green Oaks IL 60048 | Fax: (847) 918-1023 | http://www.oma.com

"One of the great commandments of science is:
    'Mistrust arguments from authority.'" -- Carl Sagan

Re: RFD: comp.object.moderated moderated

[Charles Hixson]

I haven't been following this proposal, but isn't a moderated group
normally formed in parallel with an unmoderated group?  Are articles
from the moderated group cross-posted to the un-moderated group?  This
is how I have more-or-less assumed that things were done (without, I
must admit, actually checking [where?]).

Re: RFD: comp.object.moderated moderated

[Rolf F. Katzenberger]

On Mon, 7 Sep 1998 09:33:05 -0500, in article
<6t0rgi$ms4$1@hirame.wwa.com> "Robert Martin" <rmartin@oma.com> wrote:

> 
> Rolf F. Katzenberger wrote in message <35f3da26.0@news2.ibm.net>...
> >On Sun, 06 Sep 1998 19:29:56 GMT, in article
> ><UoBI1.1872$vl.771620959@newsreader.digex.net> Ell
> ><ell@access2.digex.net> wrote:
> 
> >> Also Otttinger says above:
> >> :> >and in some cases fear of reprisal.
> >>
> >> The implication of physical threats is not absent from this.  And I think
> >> its purpose is to bogusly establish some nebulous possible physical
> >> threat in people's minds.  I have seen nothing of the sort.
> >
> >I haven't seen anything of the sort, too.
> 
> I have.  How about this one:
> 
> ---------------------------------------------------------------
> 
> Author:   Ell
> Email: ell@access.digex.net
> Date: 1998/06/17
> Forums: comp.object
> Message-ID:   <358b04ea.1529278@news.erols.com>
> Organization:   Universe
> References:   <6m2abn$kef$1@news.interlog.com> <6m35i5$ca4$1@hirame.wwa.com>
> <35870B95.925FFB22@palladion.com> <3588e518.14231523@news.erols.com>
> <6m8f28$am9$1@hirame.wwa.com>
> Reply-To:   ell@access.digex.net
> X-Complaints-To:   abuse@erols.com
> X-Trace:   winter.news.erols.com 898124862 10511 207.172.87.200 (17 Jun 1998
> 23:07:43 GMT)
> 
> "Robert Martin" <rmartin@oma.com> wrote:
> 
> >As for the rest of Elliott's article, well (Reaganesque chuckle),
> >who really cares?  Readers are welcome to peruse the articles
> >on my website to see if they draw the same conclusions that
> >Elliott does.
> 
> The ones who care Ronny are the ones who will make you pay for your
> backward, reactionary crimes against human progress.
> 
> Elliott
> ----------------------------------------------------------------------------
> 
> I saw enough of a personal threat in this particular post to make sure that
> my lawyer had a copy.

My personal opinion, not as a candidate moderator but simply as a c.o.
reader: I considered the above posting extremely rude and at the same
time extremely infantile when I came across it. In my impression it
was void of any reasonable thinking, but if its author would have
taken action, I would rather have expected a smear campaign than a
physical assault. In any case, the intention of the phrase is
intimidation.

I did not trace the message back, so I don't know where exactly the
flaming started in that thread and where exactly the moderators would
have taken action in a supposed c.o.m., so that probably the article
quoted above would never have been written.

However, neither the article above nor the one it quotes would have
passed moderation seen *in isolation*.

"As for the rest of Elliott's article, well (Reaganesque chuckle), who
really cares?" would have been rejected because it violates NO FLAMES
c) (No disdainful or belittling articles are tolerated).

"The ones who care Ronny are the ones who will make you pay for your
backward, reactionary crimes against human progress." would have been
rejected because "will make you pay" violates NO FLAMES a) (No threats
or attempts at intimidation are tolerated) and "your backward,
reactionary crimes against human progress" violates NO FLAMES d)
(Questioning of other people's motives and honesty).

Just to make one point clear: any regular on Usenet will lose his or
her innocence with respect to netiquette at some point in time. E.g.
the most recent (just the most recent, not the only one!) example by
me would be my classification of Jacobson's view on reality as
"old-fashioned"; my fellow moderators would surely have rejected that
as a violation of NO FLAMES c), or d) or both.

So the moderation policy must never be concerned with people, but with
postings.

Regards,
  Rolf

-- 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

______________________________________________________________________
Rolf F. Katzenberger | Software Developer | Trainer         1998-04-28
Home: http://www.geocities.com/SiliconValley/Park/9557
PGP : http://wwwkeys.pgp.net:11371/pks/lookup?op=get&search=0x3B39491F
      (Fingerprint F1C0 3116 F6D4 DA33 E61D  D2E4 2FB8 D6B6 3B39 491F)
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 5.5.3i for non-commercial use

iQA/AwUBNUX84C+41rY7OUkfEQLV8wCfb/IQACmn+qvT+EIftYMx36ivdRoAoNdF
ugze6Ry3oCiwMtGLSKXHOnqs
=+QML
-----END PGP SIGNATURE-----

Re: RFD: comp.object.moderated moderated

[Tim Ottinger]

Charles Hixson wrote:
> 
> I haven't been following this proposal, but isn't a moderated group
> normally formed in parallel with an unmoderated group?  Are articles
> from the moderated group cross-posted to the un-moderated group?  This
> is how I have more-or-less assumed that things were done (without, I
> must admit, actually checking [where?]).

That is the intent this time. Messages may be cross-posted to this
group. Messages that are inappropriate will not be allowed in 
c.o.m, but will still appear here from time to time. So nobody
is prevented from writing a senseless and tasteless post, but
you won't see any of them if you read c.o.m exclusively.

tim

Re: RFD: comp.object.moderated moderated

[Tim Ottinger]

Charles Hixson wrote:
> 
> I haven't been following this proposal, but isn't a moderated group
> normally formed in parallel with an unmoderated group?  Are articles
> from the moderated group cross-posted to the un-moderated group?  This
> is how I have more-or-less assumed that things were done (without, I
> must admit, actually checking [where?]).

This one is just so.

CFV: comp.object.moderated moderated

[David Bostwick]

                     FIRST CALL FOR VOTES (of 2)
                moderated group comp.object.moderated

Instructions for voting are just before the ballot itself.  Please read
them before voting.  If you have questions about the voting process,
ask the votetaker.

This CFV is to be distributed only by the votetaker.  It is not to be
posted to newsgroups, or mailed to mailing lists or individuals, except by
the votetaker, and it is not to be placed on the World Wide Web.  Ballots
or CFVs provided by anyone except the votetaker will be invalid.

Newsgroups line:
comp.object.moderated	A moderated forum for Object-oriented issues. (Moderated)

Votes must be received by 23:59:59 UTC, 18 Nov 1998.

This vote is being conducted by a neutral third party.  Questions
about the proposed group should be directed to the proponent.

Proponent: Tim Ottinger <ottinger@oma.com>

Votetaker: David Bostwick <bostwick@cas.chemistry.gatech.edu>

RATIONALE: comp.object.moderated

Object-oriented programming has long ago graduated from a niche study
to an industry force, so the discussion of things object-oriented has
likewise increased in general interest and audience. This surge has
increased the participation in comp.object so that it is difficult for
participants to keep up with the volume.

In addition, the comp.object newsgroup now receives a substantial
number of inappropriate posts, much of which are of little value or
interest to the community at large, and a large number of which are
easily characterized as "flames" or "trolls".

For those who would like to have a greater signal-to-noise ratio
than is afforded in comp.object, we wish to create a second,
separate newsgroup which is moderated to reduce the occurrance
of spam, flames, trolls, and off-topic posts. In this way, the
newsgroup will cater to professionals with less time for scanning the
news, and those who wish to avoid flames.

The moderators of comp.object.moderated were elected by a
public, majority vote on comp.object and have produced a
policy which they feel will encourage OO discussions and
attract new readers and expert participants.

Comp.object will not be moderated, though. It will remain as an
alternative. On comp.object, one may have discussions on more
tangential topics. Comp.object.moderated merely provides the
readership with a well-focused, flame-free, spam-free choice.

CHARTER: comp.object.moderated

Comp.object.moderated is a moderated news group for discussion of
issues directly related to Object-oriented theory and Object-oriented
practice, and of general interest to the Object-oriented community.
Any such articles are welcome, and are recommendations of alternative
approaches in response to questions directly related to
Object-oriented theory or practice.

Moderation Policy:

I PRINCIPLES

Moderation is desired to attract and maintain participation by old
posters, new posters, and especially expert posters. To do so,
comp.object.moderated provides a non-threatening forum for discussing
Object-oriented practice and theory. To attract and maintain a large
professional readership this policy ensures that the forum is as
concise and useful as it can possibly be.

Here is what this moderation policy is intended to achieve with
respect to each article:

1) ON TOPIC
2) NO FLAMES
3) NO SPAM
4) NO NONSENSE

These goals are characterized as follows:

1) ON TOPIC

(Discussions of) the following subjects are regarded as being on topic
in comp.object.moderated:

a) the syntax and semantics of various Object-oriented languages, b)
Object-oriented tricks and techniques, c) case studies, d) issues of
software engineering related to Object-oriented, e) issues of software
management related to Object-oriented, f) issue of design philosophy
related to Object-oriented, g) design patterns related to
Object-oriented, etc. h) Object-oriented analysis techniques. i)
Object-oriented process. j) Object-oriented tools. k) Object-oriented
Modeling. l) any and all other discussions relating or pertaining to
Object- oriented techniques. m) management and policy of the
newsgroup.

Articles may be rejected as being off-topic if there are
other, more specific newsgroups to which they belong.

If an article references products like tools, libraries or
platforms, it is still acceptable if the article just mentions
these products as illustrations or examples and abstains from
support questions.

When in doubt:

An article shall be accepted, especially for short off-topic
digressions in a thread. In order to keep the noise level low, if such
an article has already been accepted in recent days, the moderator
body may decide to reject the newer one and refer the author to the
earlier one.

2) NO FLAMES

a) No threats or attempts at intimidation are tolerated.  Those drive
away audience. New posters are intimidated by it, and experts don't
have the time or energy to waste on it. Such things are personal, and
not of interest to the general Object-oriented audience.

b) No disrespect towards others is tolerated. When people are unkind,
new people will choose not to participate.  Personal feelings against
one or another are not of interest to the general Object-oriented
audience. People should read all ideas, and choose the ones that work
for them, and a poor idea should be shown to be poor by technical or
practical reasons.

c) No disdainful or belittling articles are tolerated, no matter
whether the contents of the article are otherwise correct or not.

d) Questioning of other people's motives and honesty is explicitly
considered both off-topic and extremely rude, no matter whether the
contents of the article are otherwise correct or not.

d) Any but the most light-hearted attempts at one-upmanship will be
disallowed. Participation in a comp.object.moderated thread is not a
contest with prizes for the winners.

In essence, all attempts to hijack comp.object.moderated to wage a
personal attack would not only be counter-productive, but also
off-topic. When people speak against each other, they've lost focus on
the issues at hand.

When in doubt:

An article is rejected. Not a flame shall pass through.

3) NO NONSENSE

a) FAQs aren't nonsense, but the repeated posting and answering of
them is. Nobody wants to read the exact same questions and answers
over and over. It's a burden on the reader that gates his productive
use of the forum.

b) Verbatim or slightly rephrased reposts are nonsense.
c) Trolls are nonsense.
d) Binaries are considered inappropriate in this newsgroup.

In short, comp.object.moderated should be a forum you can read with
the same confidence you have reading a manual or technical journal. It
is an interactive professional forum, not a hobbyist board or a war
board. It belongs to the community of people whose work is the
practice and theory of Object-Orientation, and anything that turns the
newsgroup away from that community, or turns the community away from
the newsgroup, is not welcome.

When in doubt:

An article is accepted, general noise level permitting.

4) NO SPAM

The war on SPAM is the war to maintain control of the professional
nature and the signal-to-noise ratio of a newsgroup.

The Jargon File (http://sagan.earthspace.net/jargon) describes
spam in the following terms:
"...To cause a newsgroup to be flooded with irrelevant or
inappropriate messages. [...] To send many identical
or nearly-identical messages separately to a large number
of Usenet newsgroups..."

Whatever a moderator has to do to stop SPAM without rejecting
legitimate posts is good. If stopping spam means blacklisting
spam-posters, then so be it. If it involves building complex filtering
rules, fine. If it is easily handled by rejecting posts, fine again.

When in doubt:

An article is rejected.

II MEANS

These goals are to be achieved as follows:

1) Automated format checking

If the posted article is not properly formatted (i.e. the news headers
aren't right -- your news software should take care of this) or if the
article is larger than 50KB, then it will be automatically rejected.
The poster may or may not be notified of this kind of rejection,
depending upon just how bad the headers were. Articles without Date:
or Subject: headers are not properly formatted.

2) Moderator Notes

Moderators may add a note to an article only for the reasons and
according to the policies stated above, to correct incomplete or
incorrect references, or to recommend changing thread titles when
topics drift from their original focus.

The form of those notes will always be the same. They will composed of
text in square brackets. The last four characters of the text in
square brackets will be -mod. Thus:

[text of the note. -mod].

Moderators will be extremely conservative with their use of notes.
Most articles should not have any notes. Those that do should have
only one, or at the most two. So be judicious.

3) Acceptance and Rejection Procedures

Accepted articles are to be posted immediately.  When an article is
rejected by a moderator, it will be emailed back to the poster. The
subject of the email message will be: "Rejected, violates: [reason
list]." where reason list is a comma separated list of the codes
specified in the acceptance criteria above. e.g.  "Rejected, violates:
[ON TOPIC, NO FLAMES c)]."

The moderator should include moderator notes in the body of the
article that explain why the article was rejected. The format of those
notes should be as specified above, but they can be as brief or wordy
as needed to get the point across. There also may be as many as
needed.

4) Moderator Anonymity

Moderators act as a single body. Any rejection should be viewed as a
rejection by the moderators and not by any particular moderator.  As
such, the identity of the rejecting moderator will not be exposed to
the poster whose article was rejected (i.e. the moderator's signature
will be stripped). Any questions that the poster may have can be
referred to the moderator's hotline email address.

5) Appeal Policy

Any poster of a rejected message may appeal that rejection to the
moderators by emailing the article to the moderators' hotline. The
moderators will review the rejection and either post or reject the
article based upon their conclusion.

6) Moderator Posting Policy

Moderators are not allowed to moderate their own articles. No article
written by a moderator will be posted unless one of the other
moderators accepts it.

7) Moderator Body

The number of moderators shall not become less than five, so as to
preserve the integrity of the appeal process.

When there is a shortage of moderators, the remaining moderators
select willing volunteers who are participants in the newsgroup and
whose posting history shows understanding of and respect for the
moderation policy.

H) FAQ

There will be a collection of answers to comp.object.moderated FAQs
which is made publicly and freely available. The moderator body
maintains, extends and publishes this FAQ document and points the
comp.object.moderated readers to it as appropriate. The moderator body
may decide to delegate this work.

END CHARTER.

MODERATOR INFO: comp.object.moderated

Moderator: Patrick Logan <plogan@teleport.com>
Moderator: Patrick Doyle <doylep@ecf.utoronto.ca>
Moderator: Martijn Meijering <mmeijeri@wi.leidenuniv.nl>
Moderator: John Goodsen <jgoodsen@saguarosoft.com>
Moderator: Rolf Katzenberger <rfkat@ibm.net>
Moderator: Yonat Sharon <yonat@usa.net>
Administrative contact address: comp.object.maintainer@oma.com
Article submission address: com.submit@oma.com

END MODERATOR INFO.

DISTRIBUTION:

Pointers directing readers to this CFV will be posted in these groups:

comp.object.logic
comp.lang.c++
comp.lang.clos
comp.lang.forth
comp.lang.java
comp.lang.objective-c
comp.lang.python
comp.std.c++

IMPORTANT VOTING PROCEDURE NOTES: READ THIS BEFORE VOTING

Only one vote is allowed per person or per account.  Duplicate votes
will be resolved in favor of the most recent valid vote.  Addresses and
votes of all voters will be listed in the final voting results post.

Votes must be mailed directly from the voter to the votetaker.  Anonymous,
forwarded, or proxy votes are not valid.  Votes mailed by WWW/HTML/CGI
forms are considered to be anonymous votes.

The use of spam blockers or other munged addresses will prevent you from
receiving an acknowledgement of your vote.  If the address cannot be
verified, the ballot will be disallowed.

Vote counting is automated, and failure to follow these directions may
mean that your vote does not get counted.  If you do not receive an
acknowledgment of your vote within three days contact the votetaker
about the problem.  It is your responsibility to make sure your vote
is registered correctly.

The purpose of a Usenet vote is to determine the genuine interest of
persons who would read a proposed newsgroup.  Soliciting votes from
uninterested parties defeats this purpose.  Please do not distribute
this CFV.  Instead, direct people to the official CFV as posted to
news.announce.newgroups.  Distributing pre-marked or otherwise
edited copies of this CFV is generally considered to be vote fraud.
When in doubt, ask the votetaker.

HOW TO VOTE:

Extract the ballot from the CFV by deleting everything before the
"BEGINNING OF BALLOT" and after the "END OF BALLOT" lines.  Don't worry
about the spacing of the columns or any quote characters (">") that your
reply inserts.  Please do not send the entire CFV back to me.

Fill in the ballot as shown below.  Please provide a valid name and
indicate your desired vote in the appropriate locations inside the ballot.

When finished, MAIL the ballot to: <bostwick@cas.chemistry.gatech.edu>.
Just "replying" to this message should work, but check the "To:" line.

Examples of how to properly indicate your vote (do not vote here):

  [ YES     ]  example.yes.vote
  [ NO      ]  example.no.vote
  [ ABSTAIN ]  example.abstention
  [ CANCEL  ]  example.cancellation

DO NOT modify, alter or delete any information in this ballot!
If you do, the voting software will probably reject your ballot.

If these instructions are unclear, please ask the votetaker.

======== BEGINNING OF BALLOT: Delete everything before this line =======
.-----------------------------------------------------------------------
| Do not edit anything in this ballot, except to add your name and vote.
|
| 1ST CALL FOR VOTES: comp.object.moderated
| Official Usenet Voting Ballot <COM-0001> (Do not remove this line!)
|-----------------------------------------------------------------------
| Please provide a valid name, or your vote may be rejected.  Place
| ONLY your name (i.e., do not include your e-mail address or any other
| information) after the colon on the line below.

Voter name:

| Insert YES, NO, ABSTAIN, or CANCEL inside the brackets for each
| newsgroup listed below (do not delete the newsgroup name):

 Your Vote   Newsgroup
 ---------   -----------------------------------------------------------
[         ]  comp.object.moderated

======== END OF BALLOT: Delete everything after this line ==============

This CFV was created with uvpq 1.0 (Aug 27 1997).
PQ datestamp: 980322

-- 
Voting address    : bostwick@cas.chemistry.gatech.edu

2nd CFV: comp.object.moderated moderated

[David Bostwick]

                      LAST CALL FOR VOTES (of 2)
                moderated group comp.object.moderated

Instructions for voting are just before the ballot itself.  Please read
them before voting.  If you have questions about the voting process,
ask the votetaker.

This CFV is to be distributed only by the votetaker.  It is not to be
posted to newsgroups, or mailed to mailing lists or individuals, except by
the votetaker, and it is not to be placed on the World Wide Web.  Ballots
or CFVs provided by anyone except the votetaker will be invalid.

Newsgroups line:
comp.object.moderated	A moderated forum for Object-oriented issues. (Moderated)

Votes must be received by 23:59:59 UTC, 18 Nov 1998.

This vote is being conducted by a neutral third party.  Questions
about the proposed group should be directed to the proponent.

Proponent: Tim Ottinger <ottinger@oma.com>

Votetaker: David Bostwick <bostwick@cas.chemistry.gatech.edu>

RATIONALE: comp.object.moderated

Object-oriented programming has long ago graduated from a niche study
to an industry force, so the discussion of things object-oriented has
likewise increased in general interest and audience. This surge has
increased the participation in comp.object so that it is difficult for
participants to keep up with the volume.

In addition, the comp.object newsgroup now receives a substantial
number of inappropriate posts, much of which are of little value or
interest to the community at large, and a large number of which are
easily characterized as "flames" or "trolls".

For those who would like to have a greater signal-to-noise ratio
than is afforded in comp.object, we wish to create a second,
separate newsgroup which is moderated to reduce the occurrance
of spam, flames, trolls, and off-topic posts. In this way, the
newsgroup will cater to professionals with less time for scanning the
news, and those who wish to avoid flames.

The moderators of comp.object.moderated were elected by a
public, majority vote on comp.object and have produced a
policy which they feel will encourage OO discussions and
attract new readers and expert participants.

Comp.object will not be moderated, though. It will remain as an
alternative. On comp.object, one may have discussions on more
tangential topics. Comp.object.moderated merely provides the
readership with a well-focused, flame-free, spam-free choice.

CHARTER: comp.object.moderated

Comp.object.moderated is a moderated news group for discussion of
issues directly related to Object-oriented theory and Object-oriented
practice, and of general interest to the Object-oriented community.
Any such articles are welcome, and are recommendations of alternative
approaches in response to questions directly related to
Object-oriented theory or practice.

Moderation Policy:

I PRINCIPLES

Moderation is desired to attract and maintain participation by old
posters, new posters, and especially expert posters. To do so,
comp.object.moderated provides a non-threatening forum for discussing
Object-oriented practice and theory. To attract and maintain a large
professional readership this policy ensures that the forum is as
concise and useful as it can possibly be.

Here is what this moderation policy is intended to achieve with
respect to each article:

1) ON TOPIC
2) NO FLAMES
3) NO SPAM
4) NO NONSENSE

These goals are characterized as follows:

1) ON TOPIC

(Discussions of) the following subjects are regarded as being on topic
in comp.object.moderated:

a) the syntax and semantics of various Object-oriented languages, b)
Object-oriented tricks and techniques, c) case studies, d) issues of
software engineering related to Object-oriented, e) issues of software
management related to Object-oriented, f) issue of design philosophy
related to Object-oriented, g) design patterns related to
Object-oriented, etc. h) Object-oriented analysis techniques. i)
Object-oriented process. j) Object-oriented tools. k) Object-oriented
Modeling. l) any and all other discussions relating or pertaining to
Object- oriented techniques. m) management and policy of the
newsgroup.

Articles may be rejected as being off-topic if there are
other, more specific newsgroups to which they belong.

If an article references products like tools, libraries or
platforms, it is still acceptable if the article just mentions
these products as illustrations or examples and abstains from
support questions.

When in doubt:

An article shall be accepted, especially for short off-topic
digressions in a thread. In order to keep the noise level low, if such
an article has already been accepted in recent days, the moderator
body may decide to reject the newer one and refer the author to the
earlier one.

2) NO FLAMES

a) No threats or attempts at intimidation are tolerated.  Those drive
away audience. New posters are intimidated by it, and experts don't
have the time or energy to waste on it. Such things are personal, and
not of interest to the general Object-oriented audience.

b) No disrespect towards others is tolerated. When people are unkind,
new people will choose not to participate.  Personal feelings against
one or another are not of interest to the general Object-oriented
audience. People should read all ideas, and choose the ones that work
for them, and a poor idea should be shown to be poor by technical or
practical reasons.

c) No disdainful or belittling articles are tolerated, no matter
whether the contents of the article are otherwise correct or not.

d) Questioning of other people's motives and honesty is explicitly
considered both off-topic and extremely rude, no matter whether the
contents of the article are otherwise correct or not.

d) Any but the most light-hearted attempts at one-upmanship will be
disallowed. Participation in a comp.object.moderated thread is not a
contest with prizes for the winners.

In essence, all attempts to hijack comp.object.moderated to wage a
personal attack would not only be counter-productive, but also
off-topic. When people speak against each other, they've lost focus on
the issues at hand.

When in doubt:

An article is rejected. Not a flame shall pass through.

3) NO NONSENSE

a) FAQs aren't nonsense, but the repeated posting and answering of
them is. Nobody wants to read the exact same questions and answers
over and over. It's a burden on the reader that gates his productive
use of the forum.

b) Verbatim or slightly rephrased reposts are nonsense.
c) Trolls are nonsense.
d) Binaries are considered inappropriate in this newsgroup.

In short, comp.object.moderated should be a forum you can read with
the same confidence you have reading a manual or technical journal. It
is an interactive professional forum, not a hobbyist board or a war
board. It belongs to the community of people whose work is the
practice and theory of Object-Orientation, and anything that turns the
newsgroup away from that community, or turns the community away from
the newsgroup, is not welcome.

When in doubt:

An article is accepted, general noise level permitting.

4) NO SPAM

The war on SPAM is the war to maintain control of the professional
nature and the signal-to-noise ratio of a newsgroup.

The Jargon File (http://sagan.earthspace.net/jargon) describes
spam in the following terms:
"...To cause a newsgroup to be flooded with irrelevant or
inappropriate messages. [...] To send many identical
or nearly-identical messages separately to a large number
of Usenet newsgroups..."

Whatever a moderator has to do to stop SPAM without rejecting
legitimate posts is good. If stopping spam means blacklisting
spam-posters, then so be it. If it involves building complex filtering
rules, fine. If it is easily handled by rejecting posts, fine again.

When in doubt:

An article is rejected.

II MEANS

These goals are to be achieved as follows:

1) Automated format checking

If the posted article is not properly formatted (i.e. the news headers
aren't right -- your news software should take care of this) or if the
article is larger than 50KB, then it will be automatically rejected.
The poster may or may not be notified of this kind of rejection,
depending upon just how bad the headers were. Articles without Date:
or Subject: headers are not properly formatted.

2) Moderator Notes

Moderators may add a note to an article only for the reasons and
according to the policies stated above, to correct incomplete or
incorrect references, or to recommend changing thread titles when
topics drift from their original focus.

The form of those notes will always be the same. They will composed of
text in square brackets. The last four characters of the text in
square brackets will be -mod. Thus:

[text of the note. -mod].

Moderators will be extremely conservative with their use of notes.
Most articles should not have any notes. Those that do should have
only one, or at the most two. So be judicious.

3) Acceptance and Rejection Procedures

Accepted articles are to be posted immediately.  When an article is
rejected by a moderator, it will be emailed back to the poster. The
subject of the email message will be: "Rejected, violates: [reason
list]." where reason list is a comma separated list of the codes
specified in the acceptance criteria above. e.g.  "Rejected, violates:
[ON TOPIC, NO FLAMES c)]."

The moderator should include moderator notes in the body of the
article that explain why the article was rejected. The format of those
notes should be as specified above, but they can be as brief or wordy
as needed to get the point across. There also may be as many as
needed.

4) Moderator Anonymity

Moderators act as a single body. Any rejection should be viewed as a
rejection by the moderators and not by any particular moderator.  As
such, the identity of the rejecting moderator will not be exposed to
the poster whose article was rejected (i.e. the moderator's signature
will be stripped). Any questions that the poster may have can be
referred to the moderator's hotline email address.

5) Appeal Policy

Any poster of a rejected message may appeal that rejection to the
moderators by emailing the article to the moderators' hotline. The
moderators will review the rejection and either post or reject the
article based upon their conclusion.

6) Moderator Posting Policy

Moderators are not allowed to moderate their own articles. No article
written by a moderator will be posted unless one of the other
moderators accepts it.

7) Moderator Body

The number of moderators shall not become less than five, so as to
preserve the integrity of the appeal process.

When there is a shortage of moderators, the remaining moderators
select willing volunteers who are participants in the newsgroup and
whose posting history shows understanding of and respect for the
moderation policy.

H) FAQ

There will be a collection of answers to comp.object.moderated FAQs
which is made publicly and freely available. The moderator body
maintains, extends and publishes this FAQ document and points the
comp.object.moderated readers to it as appropriate. The moderator body
may decide to delegate this work.

END CHARTER.

MODERATOR INFO: comp.object.moderated

Moderator: Patrick Logan <plogan@teleport.com>
Moderator: Patrick Doyle <doylep@ecf.utoronto.ca>
Moderator: Martijn Meijering <mmeijeri@wi.leidenuniv.nl>
Moderator: John Goodsen <jgoodsen@saguarosoft.com>
Moderator: Rolf Katzenberger <rfkat@ibm.net>
Moderator: Yonat Sharon <yonat@usa.net>
Administrative contact address: comp.object.maintainer@oma.com
Article submission address: com.submit@oma.com

END MODERATOR INFO.

DISTRIBUTION:

Pointers directing readers to this CFV will be posted in these groups:

comp.object.logic
comp.lang.c++
comp.lang.clos
comp.lang.forth
comp.lang.java
comp.lang.objective-c
comp.lang.python
comp.std.c++

IMPORTANT VOTING PROCEDURE NOTES: READ THIS BEFORE VOTING

Only one vote is allowed per person or per account.  Duplicate votes
will be resolved in favor of the most recent valid vote.  Addresses and
votes of all voters will be listed in the final voting results post.

Votes must be mailed directly from the voter to the votetaker.  Anonymous,
forwarded, or proxy votes are not valid.  Votes mailed by WWW/HTML/CGI
forms are considered to be anonymous votes.

The use of spam blockers or other munged addresses will prevent you from
receiving an acknowledgement of your vote.  If the address cannot be
verified, the ballot will be disallowed.

Vote counting is automated, and failure to follow these directions may
mean that your vote does not get counted.  If you do not receive an
acknowledgment of your vote within three days contact the votetaker
about the problem.  It is your responsibility to make sure your vote
is registered correctly.

The purpose of a Usenet vote is to determine the genuine interest of
persons who would read a proposed newsgroup.  Soliciting votes from
uninterested parties defeats this purpose.  Please do not distribute
this CFV.  Instead, direct people to the official CFV as posted to
news.announce.newgroups.  Distributing pre-marked or otherwise
edited copies of this CFV is generally considered to be vote fraud.
When in doubt, ask the votetaker.

HOW TO VOTE:

Extract the ballot from the CFV by deleting everything before the
"BEGINNING OF BALLOT" and after the "END OF BALLOT" lines.  Don't worry
about the spacing of the columns or any quote characters (">") that your
reply inserts.  Please do not send the entire CFV back to me.

Fill in the ballot as shown below.  Please provide a valid name and
indicate your desired vote in the appropriate locations inside the ballot.

When finished, MAIL the ballot to: <bostwick@cas.chemistry.gatech.edu>.
Just "replying" to this message should work, but check the "To:" line.

Examples of how to properly indicate your vote (do not vote here):

  [ YES     ]  example.yes.vote
  [ NO      ]  example.no.vote
  [ ABSTAIN ]  example.abstention
  [ CANCEL  ]  example.cancellation

DO NOT modify, alter or delete any information in this ballot!
If you do, the voting software will probably reject your ballot.

If these instructions are unclear, please ask the votetaker.

======== BEGINNING OF BALLOT: Delete everything before this line =======
..-----------------------------------------------------------------------
| Do not edit anything in this ballot, except to add your name and vote.
|
| 2ND CALL FOR VOTES: comp.object.moderated
| Official Usenet Voting Ballot <COM-0002> (Do not remove this line!)
|-----------------------------------------------------------------------
| Please provide a valid name, or your vote may be rejected.  Place
| ONLY your name (i.e., do not include your e-mail address or any other
| information) after the colon on the line below.

Voter name:

| Insert YES, NO, ABSTAIN, or CANCEL inside the brackets for each
| newsgroup listed below (do not delete the newsgroup name):

 Your Vote   Newsgroup
 ---------   -----------------------------------------------------------
[         ]  comp.object.moderated

======== END OF BALLOT: Delete everything after this line ==============

This CFV was created with uvpq 1.0 (Aug 27 1997).
PQ datestamp: 980322

comp.object.moderated Bounce List - These ballots have been recorded
------------------------------------------------------------------------------
duncan@esatst.yc.estec.esa.nl                                    Duncan Gibson
gregm_spam_bites@cc.gatech.edu                                 Greg Montgomery
patrickl@servio.gemstone.com                                  Patrick D. Logan
trimble@trimble.co.nz                                                Nick Mein

Re: 2nd CFV: comp.object.moderated moderated

[Patrick Doyle]

Just in case the massive crossposting got this ejected from your
newsreader...


In article <910744959.17155@isc.org>,
David Bostwick  <bostwick@cas.chemistry.gatech.edu> wrote:
>                      LAST CALL FOR VOTES (of 2)
>                moderated group comp.object.moderated
>
>Instructions for voting are just before the ballot itself.  Please read
>them before voting.  If you have questions about the voting process,
>ask the votetaker.
>
>This CFV is to be distributed only by the votetaker.  It is not to be
>posted to newsgroups, or mailed to mailing lists or individuals, except by
>the votetaker, and it is not to be placed on the World Wide Web.  Ballots
>or CFVs provided by anyone except the votetaker will be invalid.
>
>Newsgroups line:
>comp.object.moderated	A moderated forum for Object-oriented issues. (Moderated)
>
>Votes must be received by 23:59:59 UTC, 18 Nov 1998.
>
>This vote is being conducted by a neutral third party.  Questions
>about the proposed group should be directed to the proponent.
>
>Proponent: Tim Ottinger <ottinger@oma.com>
>
>Votetaker: David Bostwick <bostwick@cas.chemistry.gatech.edu>
>
>RATIONALE: comp.object.moderated
>
>Object-oriented programming has long ago graduated from a niche study
>to an industry force, so the discussion of things object-oriented has
>likewise increased in general interest and audience. This surge has
>increased the participation in comp.object so that it is difficult for
>participants to keep up with the volume.
>
>In addition, the comp.object newsgroup now receives a substantial
>number of inappropriate posts, much of which are of little value or
>interest to the community at large, and a large number of which are
>easily characterized as "flames" or "trolls".
>
>For those who would like to have a greater signal-to-noise ratio
>than is afforded in comp.object, we wish to create a second,
>separate newsgroup which is moderated to reduce the occurrance
>of spam, flames, trolls, and off-topic posts. In this way, the
>newsgroup will cater to professionals with less time for scanning the
>news, and those who wish to avoid flames.
>
>The moderators of comp.object.moderated were elected by a
>public, majority vote on comp.object and have produced a
>policy which they feel will encourage OO discussions and
>attract new readers and expert participants.
>
>Comp.object will not be moderated, though. It will remain as an
>alternative. On comp.object, one may have discussions on more
>tangential topics. Comp.object.moderated merely provides the
>readership with a well-focused, flame-free, spam-free choice.
>
>CHARTER: comp.object.moderated
>
>Comp.object.moderated is a moderated news group for discussion of
>issues directly related to Object-oriented theory and Object-oriented
>practice, and of general interest to the Object-oriented community.
>Any such articles are welcome, and are recommendations of alternative
>approaches in response to questions directly related to
>Object-oriented theory or practice.
>
>Moderation Policy:
>
>I PRINCIPLES
>
>Moderation is desired to attract and maintain participation by old
>posters, new posters, and especially expert posters. To do so,
>comp.object.moderated provides a non-threatening forum for discussing
>Object-oriented practice and theory. To attract and maintain a large
>professional readership this policy ensures that the forum is as
>concise and useful as it can possibly be.
>
>Here is what this moderation policy is intended to achieve with
>respect to each article:
>
>1) ON TOPIC
>2) NO FLAMES
>3) NO SPAM
>4) NO NONSENSE
>
>These goals are characterized as follows:
>
>1) ON TOPIC
>
>(Discussions of) the following subjects are regarded as being on topic
>in comp.object.moderated:
>
>a) the syntax and semantics of various Object-oriented languages, b)
>Object-oriented tricks and techniques, c) case studies, d) issues of
>software engineering related to Object-oriented, e) issues of software
>management related to Object-oriented, f) issue of design philosophy
>related to Object-oriented, g) design patterns related to
>Object-oriented, etc. h) Object-oriented analysis techniques. i)
>Object-oriented process. j) Object-oriented tools. k) Object-oriented
>Modeling. l) any and all other discussions relating or pertaining to
>Object- oriented techniques. m) management and policy of the
>newsgroup.
>
>Articles may be rejected as being off-topic if there are
>other, more specific newsgroups to which they belong.
>
>If an article references products like tools, libraries or
>platforms, it is still acceptable if the article just mentions
>these products as illustrations or examples and abstains from
>support questions.
>
>When in doubt:
>
>An article shall be accepted, especially for short off-topic
>digressions in a thread. In order to keep the noise level low, if such
>an article has already been accepted in recent days, the moderator
>body may decide to reject the newer one and refer the author to the
>earlier one.
>
>2) NO FLAMES
>
>a) No threats or attempts at intimidation are tolerated.  Those drive
>away audience. New posters are intimidated by it, and experts don't
>have the time or energy to waste on it. Such things are personal, and
>not of interest to the general Object-oriented audience.
>
>b) No disrespect towards others is tolerated. When people are unkind,
>new people will choose not to participate.  Personal feelings against
>one or another are not of interest to the general Object-oriented
>audience. People should read all ideas, and choose the ones that work
>for them, and a poor idea should be shown to be poor by technical or
>practical reasons.
>
>c) No disdainful or belittling articles are tolerated, no matter
>whether the contents of the article are otherwise correct or not.
>
>d) Questioning of other people's motives and honesty is explicitly
>considered both off-topic and extremely rude, no matter whether the
>contents of the article are otherwise correct or not.
>
>d) Any but the most light-hearted attempts at one-upmanship will be
>disallowed. Participation in a comp.object.moderated thread is not a
>contest with prizes for the winners.
>
>In essence, all attempts to hijack comp.object.moderated to wage a
>personal attack would not only be counter-productive, but also
>off-topic. When people speak against each other, they've lost focus on
>the issues at hand.
>
>When in doubt:
>
>An article is rejected. Not a flame shall pass through.
>
>3) NO NONSENSE
>
>a) FAQs aren't nonsense, but the repeated posting and answering of
>them is. Nobody wants to read the exact same questions and answers
>over and over. It's a burden on the reader that gates his productive
>use of the forum.
>
>b) Verbatim or slightly rephrased reposts are nonsense.
>c) Trolls are nonsense.
>d) Binaries are considered inappropriate in this newsgroup.
>
>In short, comp.object.moderated should be a forum you can read with
>the same confidence you have reading a manual or technical journal. It
>is an interactive professional forum, not a hobbyist board or a war
>board. It belongs to the community of people whose work is the
>practice and theory of Object-Orientation, and anything that turns the
>newsgroup away from that community, or turns the community away from
>the newsgroup, is not welcome.
>
>When in doubt:
>
>An article is accepted, general noise level permitting.
>
>4) NO SPAM
>
>The war on SPAM is the war to maintain control of the professional
>nature and the signal-to-noise ratio of a newsgroup.
>
>The Jargon File (http://sagan.earthspace.net/jargon) describes
>spam in the following terms:
>"...To cause a newsgroup to be flooded with irrelevant or
>inappropriate messages. [...] To send many identical
>or nearly-identical messages separately to a large number
>of Usenet newsgroups..."
>
>Whatever a moderator has to do to stop SPAM without rejecting
>legitimate posts is good. If stopping spam means blacklisting
>spam-posters, then so be it. If it involves building complex filtering
>rules, fine. If it is easily handled by rejecting posts, fine again.
>
>When in doubt:
>
>An article is rejected.
>
>II MEANS
>
>These goals are to be achieved as follows:
>
>1) Automated format checking
>
>If the posted article is not properly formatted (i.e. the news headers
>aren't right -- your news software should take care of this) or if the
>article is larger than 50KB, then it will be automatically rejected.
>The poster may or may not be notified of this kind of rejection,
>depending upon just how bad the headers were. Articles without Date:
>or Subject: headers are not properly formatted.
>
>2) Moderator Notes
>
>Moderators may add a note to an article only for the reasons and
>according to the policies stated above, to correct incomplete or
>incorrect references, or to recommend changing thread titles when
>topics drift from their original focus.
>
>The form of those notes will always be the same. They will composed of
>text in square brackets. The last four characters of the text in
>square brackets will be -mod. Thus:
>
>[text of the note. -mod].
>
>Moderators will be extremely conservative with their use of notes.
>Most articles should not have any notes. Those that do should have
>only one, or at the most two. So be judicious.
>
>3) Acceptance and Rejection Procedures
>
>Accepted articles are to be posted immediately.  When an article is
>rejected by a moderator, it will be emailed back to the poster. The
>subject of the email message will be: "Rejected, violates: [reason
>list]." where reason list is a comma separated list of the codes
>specified in the acceptance criteria above. e.g.  "Rejected, violates:
>[ON TOPIC, NO FLAMES c)]."
>
>The moderator should include moderator notes in the body of the
>article that explain why the article was rejected. The format of those
>notes should be as specified above, but they can be as brief or wordy
>as needed to get the point across. There also may be as many as
>needed.
>
>4) Moderator Anonymity
>
>Moderators act as a single body. Any rejection should be viewed as a
>rejection by the moderators and not by any particular moderator.  As
>such, the identity of the rejecting moderator will not be exposed to
>the poster whose article was rejected (i.e. the moderator's signature
>will be stripped). Any questions that the poster may have can be
>referred to the moderator's hotline email address.
>
>5) Appeal Policy
>
>Any poster of a rejected message may appeal that rejection to the
>moderators by emailing the article to the moderators' hotline. The
>moderators will review the rejection and either post or reject the
>article based upon their conclusion.
>
>6) Moderator Posting Policy
>
>Moderators are not allowed to moderate their own articles. No article
>written by a moderator will be posted unless one of the other
>moderators accepts it.
>
>7) Moderator Body
>
>The number of moderators shall not become less than five, so as to
>preserve the integrity of the appeal process.
>
>When there is a shortage of moderators, the remaining moderators
>select willing volunteers who are participants in the newsgroup and
>whose posting history shows understanding of and respect for the
>moderation policy.
>
>H) FAQ
>
>There will be a collection of answers to comp.object.moderated FAQs
>which is made publicly and freely available. The moderator body
>maintains, extends and publishes this FAQ document and points the
>comp.object.moderated readers to it as appropriate. The moderator body
>may decide to delegate this work.
>
>END CHARTER.
>
>MODERATOR INFO: comp.object.moderated
>
>Moderator: Patrick Logan <plogan@teleport.com>
>Moderator: Patrick Doyle <doylep@ecf.utoronto.ca>
>Moderator: Martijn Meijering <mmeijeri@wi.leidenuniv.nl>
>Moderator: John Goodsen <jgoodsen@saguarosoft.com>
>Moderator: Rolf Katzenberger <rfkat@ibm.net>
>Moderator: Yonat Sharon <yonat@usa.net>
>Administrative contact address: comp.object.maintainer@oma.com
>Article submission address: com.submit@oma.com
>
>END MODERATOR INFO.
>
>DISTRIBUTION:
>
>Pointers directing readers to this CFV will be posted in these groups:
>
>comp.object.logic
>comp.lang.c++
>comp.lang.clos
>comp.lang.forth
>comp.lang.java
>comp.lang.objective-c
>comp.lang.python
>comp.std.c++
>
>IMPORTANT VOTING PROCEDURE NOTES: READ THIS BEFORE VOTING
>
>Only one vote is allowed per person or per account.  Duplicate votes
>will be resolved in favor of the most recent valid vote.  Addresses and
>votes of all voters will be listed in the final voting results post.
>
>Votes must be mailed directly from the voter to the votetaker.  Anonymous,
>forwarded, or proxy votes are not valid.  Votes mailed by WWW/HTML/CGI
>forms are considered to be anonymous votes.
>
>The use of spam blockers or other munged addresses will prevent you from
>receiving an acknowledgement of your vote.  If the address cannot be
>verified, the ballot will be disallowed.
>
>Vote counting is automated, and failure to follow these directions may
>mean that your vote does not get counted.  If you do not receive an
>acknowledgment of your vote within three days contact the votetaker
>about the problem.  It is your responsibility to make sure your vote
>is registered correctly.
>
>The purpose of a Usenet vote is to determine the genuine interest of
>persons who would read a proposed newsgroup.  Soliciting votes from
>uninterested parties defeats this purpose.  Please do not distribute
>this CFV.  Instead, direct people to the official CFV as posted to
>news.announce.newgroups.  Distributing pre-marked or otherwise
>edited copies of this CFV is generally considered to be vote fraud.
>When in doubt, ask the votetaker.
>
>HOW TO VOTE:
>
>Extract the ballot from the CFV by deleting everything before the
>"BEGINNING OF BALLOT" and after the "END OF BALLOT" lines.  Don't worry
>about the spacing of the columns or any quote characters (">") that your
>reply inserts.  Please do not send the entire CFV back to me.
>
>Fill in the ballot as shown below.  Please provide a valid name and
>indicate your desired vote in the appropriate locations inside the ballot.
>
>When finished, MAIL the ballot to: <bostwick@cas.chemistry.gatech.edu>.
>Just "replying" to this message should work, but check the "To:" line.
>
>Examples of how to properly indicate your vote (do not vote here):
>
>  [ YES     ]  example.yes.vote
>  [ NO      ]  example.no.vote
>  [ ABSTAIN ]  example.abstention
>  [ CANCEL  ]  example.cancellation
>
>DO NOT modify, alter or delete any information in this ballot!
>If you do, the voting software will probably reject your ballot.
>
>If these instructions are unclear, please ask the votetaker.
>
>======== BEGINNING OF BALLOT: Delete everything before this line =======
>..-----------------------------------------------------------------------
>| Do not edit anything in this ballot, except to add your name and vote.
>|
>| 2ND CALL FOR VOTES: comp.object.moderated
>| Official Usenet Voting Ballot <COM-0002> (Do not remove this line!)
>|-----------------------------------------------------------------------
>| Please provide a valid name, or your vote may be rejected.  Place
>| ONLY your name (i.e., do not include your e-mail address or any other
>| information) after the colon on the line below.
>
>Voter name:
>
>| Insert YES, NO, ABSTAIN, or CANCEL inside the brackets for each
>| newsgroup listed below (do not delete the newsgroup name):
>
> Your Vote   Newsgroup
> ---------   -----------------------------------------------------------
>[         ]  comp.object.moderated
>
>======== END OF BALLOT: Delete everything after this line ==============
>
>This CFV was created with uvpq 1.0 (Aug 27 1997).
>PQ datestamp: 980322
>
>comp.object.moderated Bounce List - These ballots have been recorded
>------------------------------------------------------------------------------
>duncan@esatst.yc.estec.esa.nl                                    Duncan Gibson
>gregm_spam_bites@cc.gatech.edu                                 Greg Montgomery
>patrickl@servio.gemstone.com                                  Patrick D. Logan
>trimble@trimble.co.nz                                                Nick Mein


-- 
--
Patrick Doyle
doylep@ecf.toronto.edu

RESULT: comp.object.moderated moderated passes 324:24

[David Bostwick]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 39774 bytes --]

                                RESULT
         moderated group comp.object.moderated passes 324:24

There were 324 YES votes and 24 NO votes, for a total of 348 valid votes.
There were 5 abstains.

For group passage, YES votes must be at least 2/3 of all valid (YES and NO)
votes.   There also must be at least 100 more YES votes than NO votes.

There is a five day discussion period after these results are posted.  If no
serious allegations of voting irregularities are raised, the moderator of
news.announce.newgroups will create the group shortly thereafter.

Newsgroups line:
comp.object.moderated	A moderated forum for Object-oriented issues. (Moderated)

The voting period ended at 23:59:59 UTC, 18 Nov 1998.

This vote was conducted by a neutral third party.  Questions
about the proposed group should be directed to the proponent.

Proponent: Tim Ottinger <ottinger@oma.com>

Votetaker: David Bostwick <bostwick@cas.chemistry.gatech.edu>

RATIONALE: comp.object.moderated

Object-oriented programming has long ago graduated from a niche study
to an industry force, so the discussion of things object-oriented has
likewise increased in general interest and audience. This surge has
increased the participation in comp.object so that it is difficult for
participants to keep up with the volume.

In addition, the comp.object newsgroup now receives a substantial
number of inappropriate posts, much of which are of little value or
interest to the community at large, and a large number of which are
easily characterized as "flames" or "trolls".

For those who would like to have a greater signal-to-noise ratio
than is afforded in comp.object, we wish to create a second,
separate newsgroup which is moderated to reduce the occurrance
of spam, flames, trolls, and off-topic posts. In this way, the
newsgroup will cater to professionals with less time for scanning the
news, and those who wish to avoid flames.

The moderators of comp.object.moderated were elected by a
public, majority vote on comp.object and have produced a
policy which they feel will encourage OO discussions and
attract new readers and expert participants.

Comp.object will not be moderated, though. It will remain as an
alternative. On comp.object, one may have discussions on more
tangential topics. Comp.object.moderated merely provides the
readership with a well-focused, flame-free, spam-free choice.

CHARTER: comp.object.moderated

Comp.object.moderated is a moderated news group for discussion of
issues directly related to Object-oriented theory and Object-oriented
practice, and of general interest to the Object-oriented community.
Any such articles are welcome, and are recommendations of alternative
approaches in response to questions directly related to
Object-oriented theory or practice.

Moderation Policy:

I PRINCIPLES

Moderation is desired to attract and maintain participation by old
posters, new posters, and especially expert posters. To do so,
comp.object.moderated provides a non-threatening forum for discussing
Object-oriented practice and theory. To attract and maintain a large
professional readership this policy ensures that the forum is as
concise and useful as it can possibly be.

Here is what this moderation policy is intended to achieve with
respect to each article:

1) ON TOPIC
2) NO FLAMES
3) NO SPAM
4) NO NONSENSE

These goals are characterized as follows:

1) ON TOPIC

(Discussions of) the following subjects are regarded as being on topic
in comp.object.moderated:

a) the syntax and semantics of various Object-oriented languages, b)
Object-oriented tricks and techniques, c) case studies, d) issues of
software engineering related to Object-oriented, e) issues of software
management related to Object-oriented, f) issue of design philosophy
related to Object-oriented, g) design patterns related to
Object-oriented, etc. h) Object-oriented analysis techniques. i)
Object-oriented process. j) Object-oriented tools. k) Object-oriented
Modeling. l) any and all other discussions relating or pertaining to
Object- oriented techniques. m) management and policy of the
newsgroup.

Articles may be rejected as being off-topic if there are
other, more specific newsgroups to which they belong.

If an article references products like tools, libraries or
platforms, it is still acceptable if the article just mentions
these products as illustrations or examples and abstains from
support questions.

When in doubt:

An article shall be accepted, especially for short off-topic
digressions in a thread. In order to keep the noise level low, if such
an article has already been accepted in recent days, the moderator
body may decide to reject the newer one and refer the author to the
earlier one.

2) NO FLAMES

a) No threats or attempts at intimidation are tolerated.  Those drive
away audience. New posters are intimidated by it, and experts don't
have the time or energy to waste on it. Such things are personal, and
not of interest to the general Object-oriented audience.

b) No disrespect towards others is tolerated. When people are unkind,
new people will choose not to participate.  Personal feelings against
one or another are not of interest to the general Object-oriented
audience. People should read all ideas, and choose the ones that work
for them, and a poor idea should be shown to be poor by technical or
practical reasons.

c) No disdainful or belittling articles are tolerated, no matter
whether the contents of the article are otherwise correct or not.

d) Questioning of other people's motives and honesty is explicitly
considered both off-topic and extremely rude, no matter whether the
contents of the article are otherwise correct or not.

d) Any but the most light-hearted attempts at one-upmanship will be
disallowed. Participation in a comp.object.moderated thread is not a
contest with prizes for the winners.

In essence, all attempts to hijack comp.object.moderated to wage a
personal attack would not only be counter-productive, but also
off-topic. When people speak against each other, they've lost focus on
the issues at hand.

When in doubt:

An article is rejected. Not a flame shall pass through.

3) NO NONSENSE

a) FAQs aren't nonsense, but the repeated posting and answering of
them is. Nobody wants to read the exact same questions and answers
over and over. It's a burden on the reader that gates his productive
use of the forum.

b) Verbatim or slightly rephrased reposts are nonsense.
c) Trolls are nonsense.
d) Binaries are considered inappropriate in this newsgroup.

In short, comp.object.moderated should be a forum you can read with
the same confidence you have reading a manual or technical journal. It
is an interactive professional forum, not a hobbyist board or a war
board. It belongs to the community of people whose work is the
practice and theory of Object-Orientation, and anything that turns the
newsgroup away from that community, or turns the community away from
the newsgroup, is not welcome.

When in doubt:

An article is accepted, general noise level permitting.

4) NO SPAM

The war on SPAM is the war to maintain control of the professional
nature and the signal-to-noise ratio of a newsgroup.

The Jargon File (http://sagan.earthspace.net/jargon) describes
spam in the following terms:
"...To cause a newsgroup to be flooded with irrelevant or
inappropriate messages. [...] To send many identical
or nearly-identical messages separately to a large number
of Usenet newsgroups..."

Whatever a moderator has to do to stop SPAM without rejecting
legitimate posts is good. If stopping spam means blacklisting
spam-posters, then so be it. If it involves building complex filtering
rules, fine. If it is easily handled by rejecting posts, fine again.

When in doubt:

An article is rejected.

II MEANS

These goals are to be achieved as follows:

1) Automated format checking

If the posted article is not properly formatted (i.e. the news headers
aren't right -- your news software should take care of this) or if the
article is larger than 50KB, then it will be automatically rejected.
The poster may or may not be notified of this kind of rejection,
depending upon just how bad the headers were. Articles without Date:
or Subject: headers are not properly formatted.

2) Moderator Notes

Moderators may add a note to an article only for the reasons and
according to the policies stated above, to correct incomplete or
incorrect references, or to recommend changing thread titles when
topics drift from their original focus.

The form of those notes will always be the same. They will composed of
text in square brackets. The last four characters of the text in
square brackets will be -mod. Thus:

[text of the note. -mod].

Moderators will be extremely conservative with their use of notes.
Most articles should not have any notes. Those that do should have
only one, or at the most two. So be judicious.

3) Acceptance and Rejection Procedures

Accepted articles are to be posted immediately.  When an article is
rejected by a moderator, it will be emailed back to the poster. The
subject of the email message will be: "Rejected, violates: [reason
list]." where reason list is a comma separated list of the codes
specified in the acceptance criteria above. e.g.  "Rejected, violates:
[ON TOPIC, NO FLAMES c)]."

The moderator should include moderator notes in the body of the
article that explain why the article was rejected. The format of those
notes should be as specified above, but they can be as brief or wordy
as needed to get the point across. There also may be as many as
needed.

4) Moderator Anonymity

Moderators act as a single body. Any rejection should be viewed as a
rejection by the moderators and not by any particular moderator.  As
such, the identity of the rejecting moderator will not be exposed to
the poster whose article was rejected (i.e. the moderator's signature
will be stripped). Any questions that the poster may have can be
referred to the moderator's hotline email address.

5) Appeal Policy

Any poster of a rejected message may appeal that rejection to the
moderators by emailing the article to the moderators' hotline. The
moderators will review the rejection and either post or reject the
article based upon their conclusion.

6) Moderator Posting Policy

Moderators are not allowed to moderate their own articles. No article
written by a moderator will be posted unless one of the other
moderators accepts it.

7) Moderator Body

The number of moderators shall not become less than five, so as to
preserve the integrity of the appeal process.

When there is a shortage of moderators, the remaining moderators
select willing volunteers who are participants in the newsgroup and
whose posting history shows understanding of and respect for the
moderation policy.

H) FAQ

There will be a collection of answers to comp.object.moderated FAQs
which is made publicly and freely available. The moderator body
maintains, extends and publishes this FAQ document and points the
comp.object.moderated readers to it as appropriate. The moderator body
may decide to delegate this work.

END CHARTER.

MODERATOR INFO: comp.object.moderated

Moderator: Patrick Logan <plogan@teleport.com>
Moderator: Patrick Doyle <doylep@ecf.utoronto.ca>
Moderator: Martijn Meijering <mmeijeri@wi.leidenuniv.nl>
Moderator: John Goodsen <jgoodsen@saguarosoft.com>
Moderator: Rolf Katzenberger <rfkat@ibm.net>
Moderator: Yonat Sharon <yonat@usa.net>
Administrative contact address: comp.object.maintainer@oma.com
Article submission address: com.submit@oma.com

END MODERATOR INFO.

comp.object.moderated Final Vote Ack

Voted Yes
------------------------------------------------------------------------------
1grotria [at] informatik.uni-hamburg.de                         Peter Grotrian
70672.1744 [at] compuserve.com                              John I. Moore, Jr.
aaw [at] ascham.demon.co.uk                                 Anthony Willoughby
adam [at] flash.irvine.com                                      Adam Beneschan
adrianh [at] victoriareal.co.uk                                  Adrian Howard
ady [at] thermoteknix.co.uk                                          Ady Coles
afrazer [at] ophelia.telstra.com.au                              Andrew Frazer
ahecht [at] mindspring.com                                          Alan Hecht
alfred.gebert [at] systor.com                                    Alfred Gebert
allender [at] erols.com                                          John Allender
andy [at] ffaltd.demon.co.uk                                         Andy Hunt
anilk [at] arbornet.org                                     Anil Krishnamurthy
anupriyo [at] delphi.com                                  Anupriyo Chakravarti
arielle [at] taronga.com                                    Stephanie da Silva
ark [at] research.att.com                                        Andrew Koenig
assfalg [at] dsi.unifi.it                                       Jurgen Assfalg
a_bond [at] rinet.ru                                          Anton Bondarenko
BAILEYK [at] SCHNEIDER.COM                                      Kendall Bailey
balser [at] uke.uni-hamburg.de                                   Markus Balser
barry.prescott [at] wanadoo.fr                                  Barry Prescott
bbutton [at] insight-tech.com                                     Brian Button
BCasiello [at] Banyan.com                                       Brian Casiello
behrends [at] cse.msu.edu                                      Reimer Behrends
bernhard.buergin [at] ubs.com                                   Bernard Burgin
bert [at] dgb.nl                                                     Bert Bril
bijuthom [at] ibm.net                                              Biju Thomas
bill [at] wadley.org                                               Bill Wadley
binkley [at] bigfoot.com                                     Brian Keith Oxley
bjv [at] herbison.com                                            B.J. Herbison
bmiller [at] cccglobal.com                                     Brian R. Miller
bodewig [at] bost.de                                            Stefan Bodewig
booda [at] datasync.com                                        Martin H. Booda
boud [at] rempt.xs4all.nl                                      Boudewijn Rempt
bparsia [at] email.unc.edu                                        Bijan Parsia
bpr [at] best.com                                                 Brian Rogoff
bradapp [at] enteract.com                                        Brad Appleton
brand [at] nina.pagesz.net                                    Jeff Brandenburg
Brane.Dernac [at] select-tech.si                                  Brane Dernac
brangdon [at] cix.co.uk                                            Dave Harris
britt [at] acm.org                                          F. BRITT SNODGRASS
BrookeF [at] gvsi.com                                              Brooke Fair
Brownsta [at] concentric.net                                        Stan Brown
bsey [at] pobox.com                                               Bill Seymour
burris [at] neosoft.com                                         Rick A. Burris
c [at] nautronix.com.au                                           carl johnson
c.stadler [at] delta-ii.de                                    Christof Stadler
Caedmontwo [at] aol.com                                   Troy Caedmon Parsons
cameron-mellor [at] deshaw.com                                  Cameron Mellor
cd [at] tps.de                                                    Charles Dapp
Charles.Burton [at] evolving.com                                  Chuck Burton
chrismck [at] earthlink.net                                  Christine McKenna
Christian.Angerer [at] sea.ericsson.se                       Christian Angerer
christopher.varlese [at] broadnet.ascom.ch                 Christopher Varlese
ckf [at] majure.com                                       Creighton K. Frommer
clayberg [at] smalltalksystems.com                               Eric Clayberg
coelho [at] dca.fee.unicamp.br                   Andre Luis Vasconcelos Coelho
craig [at] scot.demon.co.uk                                     Craig Cockburn
crawley [at] dstc.edu.au                                       Stephen Crawley
crocker [at] cig.mot.com                                           Ron Crocker
CVilla [at] tekscan.com                                       Charles W. Villa
czerwonka [at] corbatech.com                                 Andy L. Czerwonka
dacut [at] ece.cmu.edu                                       David A. Cuthbert
daniel.sundman [at] usa.net                                     Daniel Sundman
danielp [at] interlog.com                                        Daniel Parker
Danny.Lingman.lingman [at] nt.com                                  Dan Lingman
dany.steyaert [at] ping.be                                       Dany Steyaert
DasBuro.Com!mfx [at] DasBuro.com                              Markus Freericks
dave [at] goopot.demon.co.uk                                       David Potts
Dave.Murrells [at] ehv.ce.philips.com                           David Murrells
davep [at] iisc.co.uk                                             Dave Postill
daver [at] teleport.com                                             D Reynolds
david [at] elqui.qant.ucl.ac.be                                  David Massart
david [at] farrar.com                                             David Farrar
david [at] pottage.demon.co.uk    David Pottage <david [at] pottage.demon.co.u
david.price [at] research.nokia.com                                David Price
david.whipp [at] hl.siemens.de                                     David Whipp
David_Keller [at] sealand.com                                  David A. Keller
dbh [at] transarc.com                                              David Hodge
dboucher [at] locus.ca                                       Dominique Boucher
dc [at] panix.com                                            David W. Crawford
dermot [at] clubi.ie                                              Dermot Casey
DESiegel [at] aol.com                                             D. E. Siegel
dittmann [at] gfai.de                                         Stephan Dittmann
dittoC [at] ix.netcom.com                                       David Cattarin
dkarr [at] nmo.gtegsc.com                                        David M. Karr
dlmatt [at] canopus.bu.edu                               Dr. David L. Matthews
Dmckeon [at] swcp.com                                             Denis McKeon
Dominique.Colnet [at] loria.fr                                Dominique Colnet
doylep [at] ecf.utoronto.ca                                      Patrick Doyle
dpw [at] cs.arizona.edu                                           Don Waugaman
DRaizen [at] dataware.com                                           Dan Raizen
drybowski [at] email.com                                       Daniel Rybowski
dsr [at] mail.lns.cornell.edu                                        Dan Riley
duncan [at] esatst.yc.estec.esa.nl                               Duncan Gibson
e.blood [at] citr.com                                               Eric Blood
ehoffman [at] fzi.de                                         Ekkehard Hoffmann
ehsmalu [at] ehpt.com                                        Mattias Lundstrom
Ekkehard.Uthke [at] gmx.de                                      Ekkehard Uthke
ems [at] jrandom.com                                              Erik Seaberg
eric [at] aerie-pr.com                                       Eric G. Roesinger
eric.diamond [at] bankerstrust.com                                Eric Diamond
eridani [at] databasix.com                                             Belinda
esap [at] cs.tut.fi                                              Esa Pulkkinen
escowles [at] gort.ucsd.edu                                        Esme Cowles
ewan_benson [at] hotmail.com                                       Ewan Benson
e_j_m [at] yahoo.com                                               Eric Miller
FALE [at] skidata.com                                        Leopold Faschalek
falk.bruegmann [at] student.uni-augsburg.de                     Falk Bruegmann
fche [at] cygnus.com                                          Frank Ch. Eigler
fischerd [at] rd.hydro.on.ca                                    Daniel Fischer
fjh [at] cs.mu.OZ.AU                                          Fergus Henderson
Frank_Adrian [at] firstdatabank.com                            Frank A. Adrian
franz [at] mips.complang.tuwien.ac.at                           Franz Puntigam
Franz.Seiser [at] sea.ericsson.se                                 Franz Seiser
fredrik [at] pythonware.com                                      Fredrik Lundh
f_clerc [at] effix.fr                                            Fabrice Clerc
g.h.smith [at] marconicomms.com                                   Graham Smith
gavan [at] magna.com.au                                        Gavan Schneider
gboes [at] ashfordtech.com                                           Greg Boes
gdosreis [at] sophia.inria.fr                                 Gabriel Dos Reis
gelderen [at] mediaport.org                             Jeroen C. van Gelderen
geneo [at] Rational.Com                                              Gene Ouye
Geoff_Odhner [at] franklin.com                                 Geoffrey Odhner
gerald.zottl [at] sea.ericsson.se                                 Gerald Zottl
gerhard.menzl [at] sea.ericsson.se                               Gerhard Menzl
graham [at] parana.pentacom.co.uk                                  Graham Ward
gregfra [at] iname.com                                           Greg Franklin
gregm_spam_bites [at] cc.gatech.edu                            Greg Montgomery
grenning [at] oma.com                                        James W. Grenning
gsez020 [at] compo.bedford.waii.com                                Pete Forman
guymacon [at] deltanet.com              guymacon [at] deltanet.com (Guy Macon)
harry.protoolis [at] nautronix.com.au                          Harry Protoolis
harvey [at] iupui.edu                                             James Harvey
heiler [at] rumms.uni-mannheim.de                              Matthias Heiler
holger [at] wizards.de                                      Holger Hoffstaette
hslama [at] datacomm.ch                                         Heribert Slama
hubert [at] patrol.i-way.co.uk                                 Hubert Matthews
hymie [at] prolifics.com                                           Hyman Rosen
hyphen [at] xs4all.nl                                           Carlo Hogeveen
ica2ph [at] csv.ica.uni-stuttgart.de                             Peter Hermann
James.Bridson [at] ks.sel.alcatel.de                          James M. Bridson
James.Weirich [at] sdrc.com                                        Jim Weirich
jamesr [at] objectshare.com                                 James A. Robertson
james_wolffe [at] ny.essd.northgrum.com                           James Wolffe
jap [at] interaccess.com                                        Jeff Pleimling
jb [at] mail.com                                                   John Burton
jcoffin [at] taeus.com                                            Jerry Coffin
jdassen [at] wi.leidenuniv.nl                                    J.H.M. Dassen
jeff [at] mdli.com                                                Jeff Younker
jgoodsen [at] radsoft.com                                         John Goodsen
jharby [at] san.rr.com                                              John Harby
jhg [at] acm.org                                                James Garrison
jim.ancona [at] geac.com                                            Jim Ancona
jkr [at] phon1.ikp.uni-bonn.de                                 Juergen Kraemer
joachim.durchholz [at] munich.netsurf.de                     Joachim Durchholz
joet [at] cse.unsw.edu.au                                          Joe Thurbon
johanj [at] acm.org                                            Johan Johansson
jonboy [at] onlink.net                                          Trevor Tymchuk
JonesR [at] tetraworld.com                                          Rick Jones
josef.fromwald [at] sea.ericsson.se                             Josef Fromwald
jpotter [at] falcon.lhup.edu                                       John Potter
jsiegle [at] phoenix.lhup.edu                                  Jonathan Siegle
julesd [at] erols.com                                             Jules Dubois
junga [at] leo.org                                                  Achim Jung
juris [at] rfb.lv                                                 Juris Krikis
K.Hagan [at] thermoteknix.co.uk                                      Ken Hagan
kapson [at] mays.Central.Sun.COM                                   John Kapson
kderrick [at] my-dejanews.com                                    Keith Derrick
keegansj [at] perkin-elmer.com                                  Stephen Keegan
keesey [at] us.ibm.com                                            James Keesey
kelley [at] ruralnet.net                                          Kevin Kelley
Kevin [at] RightWall.com                                   Kevin H Blenkinsopp
kielmann [at] cs.vu.nl                                          Thilo Kielmann
klein [at] newmonics.com                                          Andrew Klein
KousenKA [at] utrc.utc.com                                   Kenneth A. Kousen
kpascoe [at] ford.com                                             Kathy Pascoe
kwong [at] cs.ubc.ca                                                  Ken Wong
larrybr [at] seanet.com                                        Larry Brasfield
lee.s.fields [at] usa.dupont.com                                 Lee S. Fields
lindstrom [at] oma.com                                        Lowell Lindstrom
Link [at] decrc.abb.de                                           Johannes Link
list-votes [at] dream.kn-bremen.de                            Martin Schr"oder
llgerholz [at] mmm.com                                          Laurie Gerholz
MacDonaldRJ [at] bv.com                                                Richard
macgyver [at] dcc.ufmg.br                                     Cassio Pennachin
maeder [at] glue.ch                                              Thomas Maeder
mahesh [at] paragon-software.com                                   B.G. Mahesh
mal [at] bewoner.dma.be                                        Lieven Marchand
malay [at] miel.mot.com                                         Malay Vaishanv
mamcdow [at] ia.net                                           Mark A. McDowell
manfred.schneider [at] rhein-neckar.de                       Manfred Schneider
marco_dallaGasperina [at] mentorg.com                    Marco Dalla Gasperina
mark [at] hsi.com                                               Mark Sicignano
mark.fussell [at] chimu.com                                       Mark Fussell
Mark.Wright [at] NBNZ.CO.NZ                                        Mark Wright
Matt.Terski [at] mchugh.com                                  Matthew A. Terski
Matthew.Helliwell [at] dresdnerkb.com                           Matt Helliwell
matts [at] shore.net                                             Matt Sullivan
mayp [at] tibco.com                                                Patrick May
mcbreenp [at] cadvision.com                                       Pete McBreen
mckewan [at] tmqaustin.com                                      Andrew McKewan
mdick [at] insect.sd.monash.edu.au                                 Martin Dick
mfl [at] sams.co.uk                                              Martin Flower
mgc [at] cs.rmit.edu.au                                    Michael Chamberlain
Michael.McMahon.mmcmahon [at] nt.com                           Michael McMahon
Michel.Clamagirand [at] alcatel.fr                          Michel Clamagirand
michi [at] dstc.edu.au                                           Michi Henning
Mike.Parmley [at] postoffice.co.uk                                Mike Parmley
millette [at] bigfoot.com                                    Robin Y. Millette
mkc [at] sky.net                                                  Mike Coleman
mlievaart [at] orion.nl                                       Martijn Lievaart
mmeijeri [at] wi.leidenuniv.nl                               Martijn Meijering
mmquinn1 [at] mmm.com                                         Michael M. Quinn
mooring [at] antares.Tymnet.COM                                     Ed Mooring
mshoemaker [at] insight-tech.com                             Michael Shoemaker
mslamm [at] mscc.huji.ac.il                                          Ehud Lamm
msundararajan [at] ibs-ltd.co.uk                         Mukundan Sundararajan
murphyjr [at] mags.net                                         James R. Murphy
nab [at] acm.org                                                 Neville Black
naddy [at] mips.rhein-neckar.de                           Christian Weisgerber
nate [at] mcnamara.net                                           Nate McNamara
newkirk [at] oma.com                                             James Newkirk
Nick.Mein [at] trimble.co.nz                                         Nick Mein
NickKetter [at] mindspring.com                               Nicholas J Ketter
nidoyle [at] nortel.ca                                          Nicholas Doyle
np [at] stardivision.de                                       Nikolai Pretzell
objetos [at] satlink.com                                      Miguel J. Pinkas
olczyk [at] interaccess.com                                 Thaddeus L. Olczyk
oliva [at] dcc.unicamp.br                                      Alexandre Oliva
oliverr [at] pop.erols.com                                    Robert G. Oliver
ottinger [at] oma.com                                             Tim Ottinger
P.Roberts [at] perth.wgc.com.au                                   Paul Roberts
pachling [at] kapsch.net                                     Walter Pachlinger
palecoin [at] my-dejanews.com                                  Pascal LECOINTE
patrickl [at] servio.gemstone.com                             Patrick D. Logan
pats [at] acm.org                                            Patricia Shanahan
paul.grealish [at] uk.geopak-tms.com                             Paul Grealish
Paul.Webster.paulweb [at] nt.com                                  Paul Webster
pch [at] verdi.iisd.sra.com                                 Peter C. Halverson
per.angstrom [at] mind.nu                                         Per �ngstr�m
peter [at] weblogic.com                                           Peter Seibel
peter.lindgren [at] emw.ericsson.se                             Peter Lindgren
pezzini [at] ibm.net                                              Igor Pezzini
pgoodwin [at] my-dejanews.com                                     Phil Goodwin
phil [at] panix.com                                             Phil Gustafson
phil [at] paule.demon.co.uk                             Philip William Britton
philip [at] preston20.freeserve.co.uk                           Philip Preston
plogston [at] yahoo.com                                           Paul Logston
polemic [at] iinet.net.au                                    Richard Puchmayer
poleur [at] crpcu.lu                                             Michel Poleur
porter.clark [at] msfc.nasa.gov                                J. Porter Clark
potargen [at] imec.be                                         Freddy Potargent
prudrakshala [at] statestreet.com                           Purush Rudrakshala
pschow [at] advtech.uswest.com                                     Peter Schow
psnorby [at] cacd.rockwell.com                                      P.S. Norby
qranian [at] lmera.ericsson.se                                    Niklas Storm
Ralf.Comtesse [at] microtool.de                                           Ralf
rapp [at] lmr.com                                              Larry Rappaport
rbinder [at] rbsc.com                                         Robert V. Binder
reissing [at] informatik.uni-stuttgart.de                        Ralf Reissing
rfkat [at] ibm.net                                        Rolf F. Katzenberger
rgarcia4 [at] darwin.helios.nd.edu                               Ronald Garcia
rich [at] dsp.sps.mot.com                                     Richard Bartlett
rick [at] bcm.tmc.edu                                           Richard Miller
ricksand [at] mediaone.net                                      Rick Sanderson
riddle [at] Iname.com                                             Steve Riddle
ritzmann [at] trshp.ntc.nokia.com                              Fabian Ritzmann
rkirti [at] ix.netcom.com                                        Rituraj Kirti
rmartin [at] oma.com                                          Robert C. Martin
Robert.Lukassen [at] ehv.ce.philips.com                     Robert J. Lukassen
roland [at] inherit.se                             Roland Hedayat</BLOCKQUOTE>
rracine [at] draper.com                                           Roger Racine
rstamerjohn [at] QGRAPH.COM                                   Ralph Stamerjohn
rufinus [at] mbe.ece.wisc.edu                                        J Rufinus
russ_freeman [at] hotmail.com                                     Russ Freeman
rvaitk [at] soften.ktu.lt                               Raimundas Vaitkevicius
s.sudik [at] larc.nasa.gov                                        Steven Sudik
safa [at] icrl.mew.co.jp                                          Laurent SAFA
salter [at] chrontech.com                                        Steven Salter
Sandy.Grosvenor [at] gsfc.nasa.gov                             Sandy Grosvenor
sbo [at] psy.med.uni-muenchen.de                                Boris Schaefer
schlegel [at] informatik.uni-rostock.de                 J=FCrgen Schlegelmilch
schmidt [at] cs.wustl.edu                                   Douglas C. Schmidt
schuerig [at] acm.org                                         Michael Schuerig
seriakov [at] aha.ru                                           George Seriakov
sferris [at] tiny.net                                          Scott M. Ferris
sgb [at] praxis-cs.co.uk                                          Stephen Bull
shrum [at] hpnut.fc.hp.com                                           Ken Shrum
simon [at] icpdd.neca.nec.com.au                                Simon A. Crase
simon.guest [at] roke.co.uk                                        Simon Guest
simonwillcocks [at] enterprise.net                             Simon Willcocks
sintzoff [at] art.alcatel.fr                                  Andr=E9 Sintzoff
source [at] netcom.com                                            David Harmon
squeegee [at] concentric.net                                Stephen C. Gilardi
srini_n1 [at] verifone.com                                       Srinivasan N.
srs [at] vuse.vanderbilt.edu                                 Stephen R. Schach
steve.banks [at] marketdatasys.com                                 Steve Banks
Susan.Allen [at] PSS.Boeing.com                                 Susan A. Allen
sven [at] sass.de                                                    Sven Sass
swelham [at] mlswa.uk.lucent.com                                 Stuart Welham
tannhauser [at] crf.canon.fr                                 Falk Tannh=E4user
tc [at] gauss.muc.de                                           Matthias Hoelzl
thomas.land [at] rhein-main.net                                    Thomas Land
tmoore [at] celwave.com                                           Thomas Moore
tony.payton [at] gecm.com                                          Tony Payton
trajon [at] fred.net                                               Jon Poletti
travis [at] SEDSystems.ca                                         Shane Travis
treid [at] primenet.com                                               Tom Reid
tseaver [at] palladion.com                                         Tres Seaver
va [at] org.chemie.uni-frankfurt.de                               Volker Apelt
vijay [at] CellNet.com                                      Vijay Ramachandran
vote-n-run [at] huug.demon.nl                                             huug
westphal [at] acm.org                                           Frank Westphal
wilba [at] bigfoot.com                                           Alan Williams
winkler [at] balancetechnology.com                            Peter K. Winkler
wkdugan [at] ix.netcom.com                                          Bill Dugan
wolf.siberski [at] rwg.de                                        Wolf Siberski
wolfgang.poechgraber [at] sea.ericsson.se                 Wolfgang Poechgraber
xanthian [at] well.com                                         Kent Paul Dolan
yardley [at] interlog.com                                    Graham N. Yardley
yCothouit [at] teaser.fr                              Domenikos Theotokopoulos
yonat [at] email.com                                                 Ron Yonat
yonat [at] usa.net                                                Yonat Sharon
zach [at] instantplanet.com                                         Zach Baker

Voted No
------------------------------------------------------------------------------
aj [at] arthur.rhein-neckar.de                                  Andreas Jaeger
AlanM [at] hpdi.demon.co.uk                                         Alan Macro
brownbear [at] earthdome.com                                         Ira Brown
capitaljo [at] fexnet.com                                        Jodie Ballast
Dale.A.Force [at] lerc.nasa.gov                                     Dale Force
dialysis [at] starplace.com                                       Guy Marciano
dringhof [at] linktrader.com                                      Doc Ringhoff
ell [at] access.digex.net                                       Elliott Coates
erigbadj [at] postmaster.co.uk                                     Eric Badger
fayet [at] nancy.inra.fr                                             Guy FAYET
ferret [at] enteract.com                                            Karl Meyer
Hein.Roehrig [at] cwi.nl                                          Hein Roehrig
hougen [at] cs.umn.edu                                             Dean Hougen
kimdv [at] best.com                                               Kim DeVaughn
knemeyer [at] ix.netcom.com                                   Manfred Knemeyer
laverno [at] pacbell.net                                      La Vern R. Ogden
madhusudhan.r.doddabele [at] lmco.com                                    madhu
olav [at] viking.mv.com                                        Olav Nieuwejaar
phil [at] pfsystems.com                                           Phil Stenson
RBaker6223 [at] aol.com                                              Ray Baker
sean.duffy [at] goldengate.net                                      Sean Duffy
stainles [at] bga.com                                             Dwight Brown
territickle [at] heartthrob.com                                 Terri DeSistoh
wakelyn [at] pinn.net                                            N. T. Wakelyn

Abstained
------------------------------------------------------------------------------
AshleyB [at] halcyon.com                                        Ashley Yakeley
chris [at] kzim.com                                Christopher Robin Zimmerman
gjohnson [at] dream.season.com                                    Gary Johnson
murray-paul [at] usa.net                                           Paul Murray
rich [at] vax2.concordia.ca                                      Rich Lafferty