Well, now that all of the active core people have equally pissed each
other off, we're back on equal ground. :) Given that there are some
critical answers to be determined governing this project, the first of
which has to be voting rights / resolution and general project governance.

As this project was not started by any one person, I personally like the
FreeBSD Core Board model. At first, until we have a working kernel and
bootable OS, we would consist of a provisional board consisting of the
active core people as generally determined by this mailing list and IRC
(so far, looks to be me, William, Chriss, Bruce, and Chad. Please add /
delete if otherwise). Other members may be added with a simple majority
agreement of the existing board members, with revotes in case we get tied
or otherwise too emotionaly testy. Removals must be approved unanimously
by the other remaining board members.

In terms of general business, voting by the board should be a last resort.
Unanimous consensus should be attempted, and an informal approval by 75%
of the board's members will qualify as being accepted. A simple majority
vote with tie-break revotes will suffice as a last resort.

As soon as we have a 0.1 release of a bootable kernel with minimal
drivers, scheduler, etc, the provisional board will dissolve. The
permanent board, consisting of the heads of each major system component
(head of core kernel, compiler, scheduler, filesystems, etc), would then
be formed. When a component head steps down, the next component head will
either be selected or confirmed by the other board members, again with a
majority vote and revotes if necessary. 75% majority vote of remaining
board members will qualify to remove someone from a component head
position.

Excuse the length and detail, but I imagine at least someone will call me
on the carpet for some missing piece.

--S



-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
SharpOS-Developers mailing list
SharpOS-Developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sharpos-developers

Reply via email to