Public SourceMage Discussion List

[Seth Woolley <seth AT tautology.org>]

bylaws...

Do you propose to have bylaws?  If so, there should be a bylaws section
for specifying voting process on bylaws.  Does each team make their own
bylaws through modified consensus (go for consensus, then fallback on
majority vote)

Other than that, very thorough.

voting...

I propose single-seat voting should be done using "Instant Runoff" voting,
and multi-seat elections should be "Choice"/"Single Transferable"
voting.  (read fairvote.org)...  I ran the Oregon Pacific Green Party
elections this last year where we used Single Transferable/Choice voting.

If a lot of people prefer Condorcet voting, I'd be happy with that as
well, unless you want to use approval voting, which I'm less satisfied
with, but quite content with.  I'm just completely dead-set against
plurality elections that can't even produce a majority in a lot of
instances.

Seth

On Thu, 5 Sep 2002, Nick Jennings wrote:

> Date: Thu, 5 Sep 2002 10:34:06 -0700
> From: Nick Jennings <nkj AT namodn.com>
> To: Ryan Abrams <rabrams AT sourcemage.org>
> Cc: Source Mage Discuss <sm-discuss AT lists.ibiblio.org>
> Subject: Re: [SM-Discuss] The Constitution
>
> Woah, i'm overwhelmed already, and that's just the outline. :)
>
> Sorry, looks good to me! but I wouldn't know :)
>
> On Thu, Sep 05, 2002 at 10:11:21AM -0500, Ryan Abrams wrote:
> > Ok people,
> >
> > We need a constitution. I have repeatedly asked people to contribute
> > thoughts and ideas about what should be in it, but havent had much of a
> > response.
> >
> > Below is my rought outline for the draft I am working on. Please review it
> > and make sure it covers everything you think should be in the 
> > constitution.
> > Feedback is highly appreciated, as constitution writing isnt easy. :-/
> >
> > Thanks,
> >
> > Ryan
> >
> > The Constitution
> >
> > I.    Preamble
> > II.   Organization
> >     a. Positions
> >         1. Leader - 1 per team
> >         2. Developer
> >         3. Writer
> >         4. Tester
> >         5. Security Auditor
> >         6. Specialized
> >     b. Team Definitions
> >         1. Permanent Teams
> >             A) Security
> >             B) Release
> >             C) Sorcery
> >             D) Grimoire
> >             E) Docs
> >         2. Impermenant Teams
> >     c. Team Formation/Dissolution
> > III.  Communication
> >     a. Discussion
> >     b. Development
> >     c. Bugs
> >     d. Reports
> > IV.   Disputes
> >     a. Veto Powers
> >         1. Authority
> >         2. Veto Overrides
> >     b. Leadership Authority
> >     c. Voting Process
> >         1. Team Vote
> >         2. Distro Vote
> >         3. Public Vote
> > V.    Security
> >     a. Distro Security Policy Definitions
> >         1. Sourcemage tools
> >         2. External applications
> >     b. Contributor Access Policy Definitions
> >         1. cvs
> >     c. Site Access Policy Definitions
> >     d. Server Access Policy Definitions
> >     e. Key/Password Escrow
> > VI.   Licensing
> >     a. Social Contract
> >     b. Bundled Software
> > VII.  Releases
> >     a. Release Policy
> >     b. Release Management
> > VIII. Funding
> >     a. Non Profit
> >     b. Sources
> >         1. Donations
> >         2. Sales / Items
> >         3. Affiliates
> >     c. uses
> > IX.   Identity
> >     a. Logo / Name Usage
> > X.    Amendments
> >     a. How to define an amendment
> >     b. Rules for passing amendments
> >
> > _______________________________________________
> > SM-Discuss mailing list
> > SM-Discuss AT lists.ibiblio.org
> > http://lists.ibiblio.org/mailman/listinfo/sm-discuss
> >
> _______________________________________________
> SM-Discuss mailing list
> SM-Discuss AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/sm-discuss
>