I have tried to capture the details of our discussion last week. Please
comment on the proposal below so that we can amend the process as soon as
possible.

--Tom



Email-based or Proxy-based Voting

This proposal amends the existing TSC voting procedures that stipulate
that voting by TSC members must be done "in person" during scheduled
meetings.


Motions

Before being put to a vote, motions presented before the TSC must be
raised publicly on the development mailing-list for a minimum of 4
business days prior to a vote. This will give a chance to the wider
community to express their opinion as well as accommodate the
possibility
that members might not attend a meeting and vote in person. Motions
not posted to the list will not be considered official motions.

TSC members can vote via email positively, negatively, or abstain as is
the case
today, but must voice their votes in writing on the public mailing list.
This
will serve as the official written public record of their vote.
Members or their proxies and designates that do not vote or have their
votes received by the chair via the official mailing list will be counted
as no-vote.

Decisions need more positive votes than negative votes (ties mean the
motion is rejected), and a minimum of positive votes of at least one
third of the total number of TC members (rounded up: in a board with
8PTLs+5 that means a minimum of 5 approvers).


Proxy Delegates

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 (private) list as well as the TSC chair in writing at least 1
hour prior to the expiration period of a motion for a vote. This person
may place votes on behalf of the TSC member both in person at a meeting,
or via email in case they cannot attend the meeting for the period
of 1 meeting unless otherwise stipulated.

Thanks Tom. A few questions/comments in line. --dmm

* David Meyer (dmm@...) wrote:

On Fri, May 3, 2013 at 2:25 PM, Thomas Nadeau <tnadeau@...> wrote:

Decisions need more positive votes than negative votes (ties mean the
motion is rejected), and a minimum of positive votes of at least one
third of the total number of TC members (rounded up: in a board with
8PTLs+5 that means a minimum of 5 approvers).

dmm> I didn't understand the parenthetical comment (and what does PTL
stand for?)

That's boilerplate from the original. OpenStack has a TC (Technical
Committee), which is built of PTLs (Project Technical Leads) and 5
community voted representatives (the +5).

thanks,
-chris

* Thomas Nadeau (tnadeau@...) wrote:

Motions

Before being put to a vote, motions presented before the TSC must be
raised publicly on the development mailing-list for a minimum of 4

Come 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
community to express their opinion

---

as well as accommodate the possibility that members might not attend
a meeting and vote in person.

---
Perhaps we could strike that bit, since we allow for proxy voting.

Motions
not posted to the list will not be considered official motions.

Probably redundant w/ "[motions] must be raised publically"

TSC members can vote via email positively, negatively, or abstain as is
the case
today, but must voice their votes in writing on the public mailing list.

Similarly 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.

This
will serve as the official written public record of their vote.
Members or their proxies and designates that do not vote or have their
votes received by the chair via the official mailing list will be counted
as no-vote.

Why would we count not voting as a "no" vote?

Decisions need more positive votes than negative votes (ties mean the
motion is rejected), and a minimum of positive votes of at least one
third of the total number of TC members (rounded up: in a board with
8PTLs+5 that means a minimum of 5 approvers).

Need 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 Delegates

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 (private) list as well as the TSC chair in writing at least 1
hour prior to the expiration period of a motion for a vote. This person
may place votes on behalf of the TSC member both in person at a meeting,
or via email in case they cannot attend the meeting for the period
of 1 meeting unless otherwise stipulated.

I 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.

thanks,
-chris

First off, Dave, do you have the editing pen now for this?

* Thomas Nadeau (tnadeau@...) wrote:

Motions

Before being put to a vote, motions presented before the TSC must be
raised publicly on the development mailing-list for a minimum of 4

Come 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
community to express their opinion

---

as well as accommodate the possibility that members might not attend
a meeting and vote in person.

---
Perhaps we could strike that bit, since we allow for proxy voting.

Motions
not posted to the list will not be considered official motions.

Probably redundant w/ "[motions] must be raised publically"

TSC members can vote via email positively, negatively, or abstain as
is
the case
today, but must voice their votes in writing on the public mailing
list.

Similarly 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.

Right, no vote == abstain.

This
will serve as the official written public record of their vote.
Members or their proxies and designates that do not vote or have their
votes received by the chair via the official mailing list will be
counted
as no-vote.

Why would we count not voting as a "no" vote?

You need some default state. It seems the most obvious route is no vote
== abstain to me.

Decisions need more positive votes than negative votes (ties mean the
motion is rejected), and a minimum of positive votes of at least one
third of the total number of TC members (rounded up: in a board with
8PTLs+5 that means a minimum of 5 approvers).

Need 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 Delegates

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 (private) list as well as the TSC chair in writing at least 1
hour prior to the expiration period of a motion for a vote. This
person
may place votes on behalf of the TSC member both in person at a
meeting,
or via email in case they cannot attend the meeting for the period
of 1 meeting unless otherwise stipulated.

I 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.

Cool.

--Tom

thanks,
-chris

On Mon, May 6, 2013 at 7:21 AM, Thomas Nadeau <tnadeau@...> wrote:

First off, Dave, do you have the editing pen now for this?

No, not unless you need me to take it. --dmm

* Thomas Nadeau (tnadeau@...) wrote:

Motions

Before being put to a vote, motions presented before the TSC must be
raised publicly on the development mailing-list for a minimum of 4

Come 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
community to express their opinion

---

as well as accommodate the possibility that members might not attend
a meeting and vote in person.

---
Perhaps we could strike that bit, since we allow for proxy voting.

Motions
not posted to the list will not be considered official motions.

Probably redundant w/ "[motions] must be raised publically"

TSC members can vote via email positively, negatively, or abstain as
is
the case
today, but must voice their votes in writing on the public mailing
list.

Similarly 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.

Right, no vote == abstain.

This
will serve as the official written public record of their vote.
Members or their proxies and designates that do not vote or have their
votes received by the chair via the official mailing list will be
counted
as no-vote.

Why would we count not voting as a "no" vote?

You need some default state. It seems the most obvious route is no vote
== abstain to me.

Decisions need more positive votes than negative votes (ties mean the
motion is rejected), and a minimum of positive votes of at least one
third of the total number of TC members (rounded up: in a board with
8PTLs+5 that means a minimum of 5 approvers).

Need 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 Delegates

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 (private) list as well as the TSC chair in writing at least 1
hour prior to the expiration period of a motion for a vote. This
person
may place votes on behalf of the TSC member both in person at a
meeting,
or via email in case they cannot attend the meeting for the period
of 1 meeting unless otherwise stipulated.

I 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.

Cool.

--Tom

thanks,
-chris

_______________________________________________
TSC mailing list
TSC@...
https://lists.opendaylight.org/mailman/listinfo/tsc

* Thomas Nadeau (tnadeau@...) wrote:

* Thomas Nadeau (tnadeau@...) wrote:

Motions

Before being put to a vote, motions presented before the TSC must be
raised publicly on the development mailing-list for a minimum of 4

Come 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
community to express their opinion

---

as well as accommodate the possibility that members might not attend
a meeting and vote in person.

---
Perhaps we could strike that bit, since we allow for proxy voting.

Motions
not posted to the list will not be considered official motions.

Probably redundant w/ "[motions] must be raised publically"

TSC members can vote via email positively, negatively, or abstain as
is
the case
today, but must voice their votes in writing on the public mailing
list.

Similarly 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.

Right, no vote == abstain.

This
will serve as the official written public record of their vote.
Members or their proxies and designates that do not vote or have their
votes received by the chair via the official mailing list will be
counted
as no-vote.

Why would we count not voting as a "no" vote?

You need some default state. It seems the most obvious route is no vote
== abstain to me.

Sorry, that's just me not being able to read. I read "no-vote" as a vote
for "no" rather than not voting.

thanks,
-chris