* The candidate release was made available on January 19, 2004
* A request for a vote of confidence was made by archon on January 22, 2004
* The election will continue until completed, but in no case will it end
before January 25, 2004.
* The release will occur 2 days after the election ends, but in no case will
it occur before January 27, 2004.
*******************************************************************************
************************** OFFICIAL BALLOT ************************************
*******************************************************************************
Please read *all* of the instructions before submitting this ballot!
BALLOTS CAST AFTER THE ELECTION IS OVER WILL BE DISCARDED.
RATIONALE:
----------
It is a long standing practice of mine to avoid the appearance of despotism.
Although I could ultimately claim authority to decide just when to make
a production EPIC release, I do not choose to do so. Instead, I defer this
decision to you, the user community.
It is my distinct honor and privelege to be a steward of the EPIC software,
and I am humbled by the number of people who choose to use EPIC. It is
only through the use, testing, bug reporting, and feedback of you users
that creates the EPIC community, the community that fosters and grows the
EPIC software through its wishes and designs. I could not, and would not,
do all this work without you all.
>From time to time, the EPIC software reaches a point where it appears to
be substantially bug free, and it has all of the major features that people
want, and a breaking point can be reached. After all of the I's have been
dotted and T's have been crossed, I submit a candidate release and say to
you, "I think this is worthy of production use. Do you agree with me?"
I am generally unwilling to release a production version of EPIC without a
clear and unambiguous mandate from the EPIC user community. This mandate
is gauged through a Vote of Confidence. You now have the opportunity to
tell me, and the world, that you feel that this candidate release is worthy
of being called a production EPIC client, or that it is not worthy. It is
not up to me, but up to you, to make that determination. If 15 of you
agree with me that it is worthy, and if none of you disagree, then I am
willing to stake the good reputation of the EPIC project on this.
Because of the rarity of production releases of EPIC (this is the sixth one,
the others being EPIC, EPIC2, EPIC3, EPIC3.004, and EPIC4-1.0), it is very
important that our production releases really be of the highest quality and
enduring usefulness. There is no better way for us to destroy the good name
of EPIC than by shipping a shoddy production release.
THEREFORE:
----------
Let it be known, that a candidate release of EPIC has been submitted by
EPIC Software Labs for consideration by The EPIC Project for acceptance
as the second production version of the ircII-EPIC4 software.
Whereas the candidate release, being known as:
EPIC4-1.2.7
and being made available at:
ftp://ftp.epicsol.org/pub/epic/EPIC4/EPIC4-BETA/epic4-1.2.7.tar.gz
shall be tested for satisfaction of the goals of The EPIC Project, as defined
by the desires of its members.
THEREFORE:
---------
You are requested to test the above version of EPIC and to submit a vote of
confidence, voting either "yes" or "no" as to whether or not you accept the
above candidate release, possibly with modifications, as a production release
of the ircII-EPIC software.
VOTING PROCEDURES:
------------------
Please fill out the following ballot, removing everything else in this
email, and email the vote of confidence or official objection to:
[EMAIL PROTECTED]
* Please remember to include all of the required information so that your
ballot will not be disqualified.
* Disqualified ballots will be sent back to the originator for correction.
* You are welcome to re-submit disqualified ballots once you fix them.
* Fifteen votes of confidence are required to pass this election.
* Zero official objections are required to pass this election.
* You may change your vote by submitting a new ballot. Your last ballot
will be considered your official ballot.
* Official objections must be filed using this mechanism. Telling me
about a bug you found on #epic on efnet is not sufficient. I need
specific written documentation.
* The purpose of this election is to gague user confidence in the software
that I am preparing to release on behalf of the project (ie, you all).
I am the final judge in all voting matters, with the stated prejudice that
if there is any question of any problems, I err on the side of not
releasing the software until all concerns have been addressed.
* Nicknames are ok for the "Name" field, if you're absolutely set against
giving your real name.
BALLOT:
-------
All information is required.
Ballots with missing information cannot be honored, sorry.
--------------------------->8 snip here 8<----------------------------------
Name: [ ]
Email address: [ ]
Date: [ ] Candidate [ EPIC4-1.2.7 ]
(Please choose one)
I, the above named person, affirm that I have tested the above named
candidate software and do publicly affirm support that it shall be
released as a production version of the EPIC software. [ ] <- Mark here
I, the above named person, having tested the above named candidate software
have found a substantially limiting defect in the software and object to
the release of the software as a production version of the EPIC software.
[ ] <- Mark here
Description of defect: (ABSOLUTELY REQUIRED)
[
[
[
[
IF THIS CANDIDATE IS ACCEPTED YOUR NAME AND EMAIL ADDRESS WILL BE INCLUDED
IN THE SOFTWARE DISTRIBUTION! DO NOT SEND IN A BALLOT IF YOU ARE UNWILLING
TO BE PUBLICLY LISTED AS A VOTER.
Email all ballots to [EMAIL PROTECTED]
--------------------------->8 snip here 8<----------------------------------
_______________________________________________
List mailing list
[EMAIL PROTECTED]
http://epicsol.org/mailman/listinfo/list
