James Carlson wrote:
> Alan Burlison writes:
>
>> The new opensolaris.org membership system (https://auth.opensolaris.org)
>> is currently configured with the following "types" which are known by
>> the Auth app as "collective types":
>>
>> Community
>> Project
>> User Group
>> Electorate
>>
>
> That sounds good. The question I'm asking is whether operational
> rules can be tied to those types, such that each type has just _one_
> set of agreed-on procedures, rather than having each individual
> instance be different.
>
> A specific example of a problematic issue would be having some groups
> decide that voting should be done by majority rule, while another
> group decides on a representative system, and yet another comes up
> with some sort of weighting.
>
> I don't think it makes sense to have "recommendations," if that's all
> they are, because it essentially precludes the participants from
> keeping track of how all their various affiliations do business, and
> prevents the OGB from fairly mediating any disputes that may arise.
>
> I know we're all trying to make a nice harmonious system where
> everybody just gets along, but the real test of a structure is what
> happens when everything goes wrong.
>
>
Because there are several reviewers who feel as you do, I drafted a new,
but very familiar, section 3.1 that adds back a modified Article VIII
from the current Constitution and provides some new text related to
participation and promotion to Contributor and Leader, as follows:
1.3 Group Management Processes
Groups are expected and encouraged to document their development
methodologies and maintain records of their Contributors and Leaders.
In order to encourage consistency across the OpenSolaris community and
also for the purpose of mediating disputes, Groups should use the voting
procedures, participation guidelines, and requirements for becoming
contributors and leaders as described in the following sections.
1.3.1 Voting Procedures
Most of a Group's work is simply done by individual Contributors within
a climate of ongoing discussion, informal group consensus, and a general
desire to meet the group's shared objectives. However, occasional
conflict is an inevitable part of working together to solve complex
problems. The following Group voting procedures are designed to support
both friendly collaboration and individual innovation, while at the same
time providing adequate oversight for the OpenSolaris Community as a
whole by enabling equal participation in formal decisions regardless of
a person's location or time zone. The Group voting procedures determine
how future conflicts will be resolved so that volunteers on a project
need not fear differences of opinion: contrary ideas can be voiced
without derailing progress. The objective is to avoid /unnecessary/
conflict over changes, while at the same time encouraging opinions that
work towards producing quality products in a timely manner.
*1.3.2. Location.*
Decisions by a Group are made by vote or consensus on a public meeting
place of the Group that is most applicable to the action being
discussed. For example, Group decisions that are specific to a single
project are made through discussion and voting/consensus on the
asynchronous meeting place (e.g., mailing list) for that project,
whereas general Group decisions are made on the Group's general
discussion place. Some discussions, such as investigation of security
issues prior to their publication and nominations for Contributor
status, are expected to take place in private prior to any public vote
by the Group.
*1.3.3 Votes.*
Each Contributor of a Group has the right to one binding vote on each
proposed action of the Group. Other Participants may express their
opinions through non-binding votes. A Contributor may change their own
vote on a given action until such time as the action is no longer
applicable (e.g., decisions regarding a given product release are final
once the release is made public). Votes are expressed in the range
*[-1,1]* with the following meanings:
+1 *Yes*, "Agree," or "the action should be performed." A +1 vote
indicates that the voter is in favor of implementation of the proposed
action.
?0 *Abstain*, "no opinion," or "I am happy to let the other group
members decide this action." A vote in the interval between 0 and 1
(such as +0.5) can describe varying degrees of support for the proposal
but still counts as an abstention. A vote in the interval between 0 and
-1 (such as -0.9) can describe varying degrees of disagreement with the
proposal but still counts as an abstention.
-1 *No*, "Disagree," or "the action should not be performed." On
actions where consensus is required, this vote counts as a *veto* if it
includes an explanation of why the veto is appropriate and at least one
other Contributor agrees that the explanation is valid ( regardless of
their own vote).
*1.3.4. Voting Systems.*
Decisions of a Group are determined by several related voting systems,
chosen per action type based on the degree of consensus or quorum needed
to make the decision:
Voting System Approved by Action Types
Consensus At least three (3) binding +1 votes and no -1 votes (i.e.,
unanimous with a minimal quorum of three votes). Putbacks (when
subjected to vote). Initiate new project. Terminate project. Addition of
Contributor. Removal of Contributor (subject must abstain).
Majority At least three (3) binding +1 votes and more +1 votes than -1
votes (i.e., majority vote with a minimal quorum of three +1 votes).
Design choice. Release plan. Product release. Facilitator nomination.
Documentation (when subjected to vote).
Assumed Approval is assumed unless a -1 vote is received, after which
the action is reverted or the issue is decided by Majority or Consensus
vote, depending on the type of action. Putbacks. Documentation.
*
1.3.5. Participation Guidelines.*
How to participate:
1. Register on opensolaris.org
2. Join mailing list for a group
3. Contribute to the goals of the group
*1.3.6. Promotion Requirements.
* How to earn Contributor status:
1. Make at least three significant contributions to the goals of a group
2. Nominate yourself for Contributor status
3. Garner +1 votes from 3 existing group Contributors and no -1 votes
How to earn Leader status:
1. Make more than three significant contributions to the goals of a
group over an extended period of time
2. Nominate yourself for Leader status
3. Garner +1 votes from 3 existing group Leaders and no -1 votes
Thanks,
Michelle
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://mail.opensolaris.org/pipermail/ogb-discuss/attachments/20090206/0afb9011/attachment.html>
