• Do we want to Handle Secret Ballots in the same GR as Voting Changes

    From Sam Hartman@21:1/5 to All on Mon Nov 8 18:10:02 2021
    Russ made a final call for informal discussion.
    I'd like to ask the community whether we'd like to handle secret ballots
    now, or in a separate GR.

    The rationale for handling things now is that we can get it done with
    and if a controversial GR comes up, we'll have the option of secret
    ballots if that's how we decide things.

    The rationale for delaying is that it may make Russ's vote easier.
    we may also have a large number of ballot options if there end up being
    a significant number of amendments to Russ's proposal.

    Here's what a simple proposal for making all votes secret ballot might
    look like.
    If we choose to handle things this time around, someone (I'd be happy
    to) could propose this as an amendment when Russ makes his formal GR.
    I suspect Russ probably wouldn't accept the amendment just so we could
    have both options on the ballot.
    Given the discussions so far we'd probably have four ballot options
    (secret ballots times the two approaches to managing discussion
    periods).

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

    Resolved that the Debian Developers make the following changes to the
    Debian Constitution:

    4.1.3:
    old:
    3. Votes are taken by the Project Secretary. Votes, tallies, and
    results are not revealed during the voting period; after the vote
    the Project Secretary lists all the votes cast. The voting period
    is 2 weeks, but may be varied by up to 1 week by the Project
    Leader.

    new:
    3. Votes are taken by the Project Secretary. Votes, tallies, and
    results are not revealed during the voting period; after the vote
    the Project Secretary lists all the votes cast. The identity of a
    developer casting a particular vote is not public. The voting period
    is 2 weeks, but may be varied by up to 1 week by the Project
    Leader.

    rationale: I think we still want the ballots public because there's a
    lot of useful analysis you can do on that.
    Minimally state that the votes are not public without providing any
    mechanism for how that works; that's up to the secretary. There was
    some discussion of using a DEP to provide specific mechanisms for
    handling this; the secretary could of course take advantage of such
    a DEP if it emerged.


    4.1.6:
    old:
    6. Votes are cast by email in a manner suitable to the Secretary. The
    Secretary determines for each poll whether voters can change their
    votes.

    new:
    6. Votes are cast in a manner suitable to the Secretary. The
    Secretary determines for each poll whether voters can change their
    votes.

    rationale:
    Some of the systems being proposed for anonymous voting would work
    better if they didn't need to use email.
    Leave how that works up to the secretary.

    5.2.5:
    old:
    5. The next two weeks are the polling period during which Developers
    may cast their votes. Votes in leadership elections are kept
    secret, even after the election is finished.
    new:
    5. The next two weeks are the polling period during which Developers
    may cast their votes.

    rationale: no need for a special case for leadership elections any more.

    --=-=-Content-Type: application/pgp-signature; name="signature.asc"

    -----BEGIN PGP SIGNATURE-----

    iHUEARYIAB0WIQSj2jRwbAdKzGY/4uAsbEw8qDeGdAUCYYlX9wAKCRAsbEw8qDeG dHtvAQD0WDnAtT3zd/UWpX7WPmq8TGoIIuIdknRRIqtN92jDBQEA5cBEVsfQUZmP uji0qlhK930h6DOvL57I/PCsyBjEgQM=zNwd
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)