Re: motions and proxy voting proposals
Chris Wright <chrisw@...>
* Thomas Nadeau (tnadeau@...) wrote:
MotionsCome to think of it, we don't actually have "the development" list.
We have "the discuss" list, or "the TSC" list. Capturing the spirit here,
it'd be discuss.
business days prior to a vote. This will give a chance to the wider---
as well as accommodate the possibility that members might not attend---
Perhaps we could strike that bit, since we allow for proxy voting.
MotionsProbably redundant w/ "[motions] must be raised publically"
TSC members can vote via email positively, negatively, or abstain as isSimilarly here, another option is that we vote in the meeting and
require one of:
- member or proxy voting +1, -1, 0
- no show == no vote
The advantage is the simplicity of getting together and voting right
then and there.
ThisWhy would we count not voting as a "no" vote?
Decisions need more positive votes than negative votes (ties mean theNeed to reflect OpenDaylight structure here (TC->TSC, PTL->Project Lead,
and, well, +5...bleh ditch it all and just say "in a board w/ 13member
that means a minimum of 5 approvers). And while I like the spirit,
I think we'll need to change the TSC charter which currently states:
- Simple majority voting should be used for decisions within the TSC,
unless otherwise specified in Development Process.
Proxy DelegatesI think a proxy designation should go to public list. And I'm leaning
towards voting in the meeting, which would suggest this gets rewritten to:
Any Technical Steering Committee (TSC) member may designate a proxy
to attend a meeting in their place. This change must be sent to both
the TSC mailing list as well as the TSC chair at least 1 hour prior to
meeting during which designate will act as a proxy. This proxy may
represent the opinion of and vote on behalf of the TSC member.