Skip to Content.
Sympa Menu

sm-discuss - Re: [SM-Discuss] Vote changes proposal

sm-discuss AT lists.ibiblio.org

Subject: Public SourceMage Discussion List

List archive

Chronological Thread  
  • From: Seth Alan Woolley <seth AT positivism.org>
  • To: Eric Sandall <eric AT sandall.us>
  • Cc: sm-discuss AT lists.ibiblio.org
  • Subject: Re: [SM-Discuss] Vote changes proposal
  • Date: Fri, 15 Apr 2005 11:48:47 -0700

On Fri, Apr 15, 2005 at 09:55:30AM -0700, Eric Sandall wrote:
> Okay, so it sounds like this is what we're wanting for the addendum:
>
> (Add a comment that the Project Lead is a member of the Team Leads)
> (All numbers will be changed to <word> <(#)>, e.g. "forty-two (42)")
>
> * No vote shall be sent to the public mailing list (a note saying you voted
> is
> allowed, but do not include your vote in the e-mail).
>
> * Voting shall last for one (1) week (seven (7) days from the time the vote
> is
> started).
>
> * If there is no winner by our standards then a new voting process is
> started
> (skipping nominations), but with only the top fifty percent (50%) of the
> candidates automatically nominated and seconded (minimum of two (2)
> candidates).

Why not use ranking? Then you can do an instant runoff and not require a
revote, and it's more accurate than a simple runoff.

>
> * Team Leads can be voted out of office in the following way
> # A request is sent for the removal of a current Team Lead along with a
> nomination for a replacement (no Team Lead can be removed without a
> replacement).
> # A vote to remove a Lead can only occur once (1) a term for each
> individual
> Lead.

I'd like to remove this provision and replace it with assent of half the
respective team members under the lead or two of the team leaders without
the respective team lead.

# A vote to remove a Lead can only occur with an assent of half of the
team members under the Lead or an assent of two other Leads.

I think that would prevent a recall from happening too often but would
enable emergency recalls even if they survived one previous recall.

Surviving a recall gains them immunity under the proposed system, so
they could purposefully engineer their own recall and survive it and
then procede to destroy the project and have no recourse for recalling
them.

> # Both the request and the nomination must be seconded by distinct
> individuals
> (e.g. the person proposing cannot second either the nomination or the vote,
> nor
> can another individual second both the nomination and the vote).

This would then be moot under the above proposed change.

>
> * Team Lead positions have a term of one (1) year starting from when they
> take
> office.
> # Before the end of one (1) year a request for nominations as for a normal
> Team Lead vote will occur.
> # If no nominations are forthcoming and/or the only nominee is the current
> Team Lead and the Team Lead accepts the nomination (or default in the prior
> case) then he/she remains the Team Lead with no vote needed.
> # Voting must be finished one (1) month before the current Lead's term is
> up.
>
> * A vote of all the Team Leads may veto any nomination/vote
>
> * At the end of the vote the Project Lead will post the results along with
> an
> alphabetical listing of all valid voters to sm-discuss.
>
> * In the event that a Team Lead steps down and he/she has an Assistant Lead,
> that Assistant Lead will become the Team Lead while nominations and voting
> are
> conducted for the recently vacated position. The Assistant Team Lead may be
> nominated for the position.
>
> * Team Leads are responsible for fulfilling their duties listed here:
> http://wiki.sourcemage.org/index.php?page=Team+Lead+Duties
>
> * The Team Leads are responisble for interpreting organizational documents.
>
> Do we want to have a "voting season" so that voting happens at the same time
> (though technically it will anyways once we get the terms in, since every
> year
> that Lead will be up for a vote again around the same time). We also don't
> want
> all the Leads replaced at the same time (or have the potential to be
> replaced),
> so staggering the votes would probably be a good idea.

I think a voting season is desirable and would increase participation.

>
> Any nays? Comments?
>
> -sandalle
>
> --
> Eric Sandall | Source Mage GNU/Linux Developer
> eric AT sandall.us PGP: 0xA8EFDD61 | http://www.sourcemage.org/
> http://eric.sandall.us/ | SysAdmin @ Inst. Shock Physics @ WSU
> http://counter.li.org/ #196285 | http://www.shock.wsu.edu/
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
> _______________________________________________
> SM-Discuss mailing list
> SM-Discuss AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/sm-discuss
>

--
Seth Alan Woolley [seth at positivism.org], SPAM/UCE is unauthorized
Key id 00BA3AF3 = 8BE0 A72E A47E A92A 0737 F2FF 7A3F 6D3C 00BA 3AF3
Security Team Member Source Mage GNU/Linux http://www.sourcemage.org
Elected Coordinating Committee Member, Pacific Green Party of Oregon

Attachment: pgpmIXo_4cvdI.pgp
Description: PGP signature




Archive powered by MHonArc 2.6.24.

Top of Page