| From: | "Robert A. Hayden" <hayden@*******.MANKATO.MSUS.EDU> |
|---|---|
| Subject: | VOTING REGULATIONS (READ THIS!!!!!!!!!!) |
| Date: | Wed, 13 Oct 1993 15:40:06 -0500 |
----------------------------------------------------------
Do not delete this file as this contains instructions on how voting will
be carried out. You are responsible for following the guidelines and
formats described in this file, failure could result in your vote not
being counted.
As of Today (10/13), we have 50 submissions. There will probably be a
few more before closing on Sunday. When voting starts next week, I will
be posting about five or so per day.
-------------------
HOW VOTING WILL WORK
Each submission will be reposted to TOME by me
Each person on TOME is expected to then vote on that submission
There will be three ways to vote
Yes -- The submission is fine as is
Fix -- The submission needs to be changed
in some manner. You are then expected to
outline your concerns.
No -- The submission is evil, munchkinish, and
should be sent to the bit-bucket.
If >40% of the people vote yes, the submission will be accepted
as is.
If the vote fails, but >40% vote 'fix', the resons for fixing will
be posted and the author is expected to fix it and resubmit.
Fix votes take precedence over yes votes. (ie, if both are >40%)
If over 60% vote no, the submission will be scrapped.
If a submission needs to be fixed and resubmitted, it will go to
the bottom of the queue and be posted after all of the first-run
postings. Each submission will be limited to two resubmissions (ie,
on the third vote, the choices will be either yes or no).
Voting on each item will run for about one week.
-------------------
HOW TO VOTE
Each reposting will have an ID#. For example, if I was posting the
'buzz' spell, the subject line might look like this:
X-003-x: Spell, Buzz
Where:
X = a group identifier letter (tech, magic, races, etc)
### = the number of the submission in that group
x = a letter representing the number of times posted
Now, to submit a vote, use the following guidelines:
Send it to hayden@*******.mankato.msus.edu
The subject line should be the code number of the item, nothing else
The first line of text should be your vote, either 'YES' 'NO' or 'FIX'.
Case is NOT a factor.
Anything after the vote should be comments if you have voted FIX. No
comments should be made unless you vote FIX.
Yes, this means that each vote is a seperate emailing.
--------------------------------------------------------------
CORRECT EXAMPLES:
-----------------
TO: hayden@*******.mankato.msus.edu
SUBJ: B-005-a
FIX
This spell is too powerful and should be changed. Make it a deadly drain
instead and it would work
>or<
TO: Hayden@*******.mankato.msus.edu
SUBJ: C-010-b
YES
------------------------------
INCORRECT EXAMPLES:
TO: aq650@****.ins.cwru.edu
SUBJ: RE: B-005-a: Spell, Buzz
YES
I really like this spell.
>or<
TO: hayden@*******.mankato.msus.edu
SUBJ: Spell, Buzz: b-005-a
NO
THIS SPELL SUCKS!
*************
Comments are only needed on FIX votes
Make sure your subject lines are correct. ID#'s _are_ case sensitive.
Replying to the posting WILL NOT WORK!
Make sure to send to the right address.
-----------------------------------------------------------------------------
Please read over the above procedures and make sure you understand them.
If you have any questions, feel free to ask so I can avoind any confusion
when voting time comes around.
Thanks
{[> Robert A. Hayden ____ <[} Question Authority
{[> \ /__ <]} -=-=-
{[> aq650@****.INS.CWRU.Edu \/ / <]} Finger for PGP 2.3a Public Key
{[> hayden@*******.mankato.msus.edu \/ <]} Finger for Geek Code Info
-=-=-=-=-=-
(GEEK CODE 1.0.1) GSS d- -p+(---) c++(++++) l++ u++ e+/* m++(*)@ s-/++
n-(---) h+(*) f+ g+ w++ t++ r++ y+(*)
