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

Re:proposed constitution and NEW: proposed voting procedure




On Thu, 26 Mar 1998, Will Lowe wrote:

> > While I agree that the tally should not be revealed (to whom?) during the
> > period of voting, I don't understand how it matters when, in that period,
> Why bother tallying until all votes are cast or the voting period is over?

That was my point.

> 
> > issue, as I am always willing to state my opinion in public ;-), but I can
> > see why some, with more private views, might feel the need for a secret
> > ballot.
> We could include a field in the ballot for "Release this information" and
> after votes are counted those who'd like their votes released could have
> them posted.
> 
> > As for "validating" the voting results, and keeping the interrumn count
> > secret, we should be able to deal with this in software. We would need a
> > proceedure that would collect the votes in an area we all agree is "safe"
> > and let the software "secure" the votes until the voting period ends; at
> How's about a developer-vote@lists.debian.org ... require each
> maintainer to mail a pgp-encrypted voting ballot (ballot rather like the
> Usenet voting ballot).  Whatever script is the recipient of the
> mailinglist can (once a day or whatever) compare incoming mails to the
> developer keyring,  put all the acceptable ballots (those matching an
> entry in the Debian keyring) in an "accepted ballots" bin (discarding or
> bouncing those that don't match any developer's keys), and at the end
> of the voting period it simply counts the ballots.  This way:
> 1) Developers could change their votes, assuming the voting period has not
> ended,  by simply sending a new ballot,  and the script could discard
> any previous ballots from that pgpkey.
> 2) There's no tallying done until the voting period ends,  and hence no
> intermediate results to worry about posting.
> 3) No person has to ever "touch" the ballots ... the Project Secretary
> could simply run a "close-voting-period" script and have the relevant
> information output to text/html/sgml/whatever.
> 
Several refinements, but basicly what I was proposing. This looks better
as far as the details go.

Thanks,

Dwarf


--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org


Reply to: