Difference between revisions of "Eligibility for Council"

Latest revision as of 21:31, 18 August 2008

Eligibility for Council: What it takes to be a full-fledged council member with the ability to block decisions.
List of Policies - Policy Development

Policy

as discussed by Council in July 2008, then referred to Laurel Hoyt for compilation.

Council needs broad input from the FreeGeek community to make decisions. This requires openness to many views and good judgment about how to use meeting time.

Attendance and Membership

Council meetings are open to guests from the public. Any active Free Geek volunteer, paid worker, or board member is welcome to participate fully except as limited by our conflict of interest policy. Definitions of these categories can be found elsewhere. Council membership is attained at a member's third consecutive meeting, and is lost if three consecutive meetings are missed.

Participation and Preparation

Full participation in council meetings includes attending (being there, listening), and contributing to conversation. To use time well, participants are expected to prepare for meetings with reading and discussion. A facilitator has the option of telling speakers with detailed questions and large needs for background information to refrain from taking meeting time for these needs. Guests and others who are not active council members are asked to minimize their time speaking, and to not weigh in strongly on concerns not shared by the rest of the group. In other words, guests and non-council members should not slow deliberations by being lone representatives of concerns they believe are weighty enough to block consensus on a proposal.

Previous Policy

as approved by council in September 2002, then revised as above:

One must attend two consecutive meetings to vote and miss three consecutive meetings to lose the privelege. Also, one must be on the council mailing list for voting eligibility. Exceptions can be made in advance for these eligibility requirements.

On blocking votes, we decided to allow unlimited blocking for each person unless this becomes an issue later on. Also, the blocking member needs to explain their blocking vote.

Notes

The voting language is an artifact of the time period this was written in, while we were almost all new to consensus.

Any community member is eligable to participate in discussion at the Community Council. "Eligibility," in practice, effects mostly just blocking ability.

When an unqualified member attends at least three meetings in a row, he or she becomes qualified at the third meeting.

The bit about requiring mailing list membership is usually overlooked in recent formulations of this policy.

@@ Line 1: / Line 1: @@
-Who is eligible for making decisions at the [[Community Council]]?
+{{Policy Header
+ | PolicyName = Eligibility for Council
+ | notes = What it takes to be a full-fledged council member with the ability to block decisions.
+}}
+== Policy==
+''as discussed by Council in [http://lists.freegeek.org/pipermail/council/2008-July/002373.html July 2008], then referred to Laurel Hoyt for compilation.''
+Council needs broad input from the FreeGeek community to make decisions. This requires openness to many views and good judgment about how to use meeting time.
+===Attendance and Membership===
+Council meetings are open to guests from the public. Any active Free Geek volunteer, paid worker, or board member is welcome to participate fully except as limited by our conflict of interest policy. Definitions of these categories can be found elsewhere.  Council membership is attained at a member's third consecutive meeting, and is lost if three consecutive meetings are missed.
+===Participation and Preparation===
+Full participation in council meetings includes attending (being there, listening), and contributing to conversation. To use time well, participants are expected to prepare for meetings with reading and discussion. A facilitator has the option of telling speakers with detailed questions and large needs for background information to refrain from taking meeting time for these needs. Guests and others who are not active council members are asked to minimize their time speaking, and to not weigh in strongly on concerns not shared by the rest of the group. In other words, guests and non-council members should not slow deliberations by being lone representatives of concerns they believe are weighty enough to block consensus on a proposal.
+== Previous Policy ==
+''as approved by council in [http://lists.freegeek.org/pipermail/council/2002-October/000265.html September 2002], then revised as above:''
+One must attend two consecutive meetings to vote and miss three consecutive meetings to lose the privelege.   Also, one must be on the council mailing list for voting eligibility.  Exceptions can be made in advance for these eligibility requirements.
+On blocking votes, we decided to allow unlimited blocking for each person unless this becomes an issue later on.  Also, the blocking member needs to explain their blocking vote.
+==Notes==
+The voting language is an artifact of the time period this was written in, while we were almost all new to consensus.
+Any community member is eligable to ''participate in discussion'' at the [[Community Council]]. "Eligibility," in practice, effects mostly just blocking ability.
-* Members who attend the first council meeting are automatically qualified to participate in decisions.
-* Once a member becomes qualified, he or she becomes unqualified if he or she misses three meetings in a row.
 * When an unqualified member attends at least three meetings in a row, he or she becomes qualified at the third meeting.
-NOTE: This effectively limits the ability of certain people to block decisions. It does not limit their ability to participate in the discussion or raise concerns.
+The bit about requiring mailing list membership is usually overlooked in recent formulations of this policy.
 [[Category:Policy]]