How about we do a two-tier model, where decisions are brought to the mailing list for a general consensus (by hacking it out or by a list-wide vote) and if things aren't resolved amongst the larger community our smaller core group will break the deadlock with a vote.
On 8/31/07, Chad Z. Hower aka Kudzu <[EMAIL PROTECTED]> wrote: > > As a quick cautionary warning, the guidelines of small group dynamics > > a virtual setting (e.g. us, businesses who telecommute, etc) says that > > group should be no larger than 10 people, otherwise long discussions > > could drag out too long. We are already at eight with Chad and Matthijs > > being included. Personally, having previously headed a large online > > gaming group with a staff of 50+ to oversee a membership of 300-ish, > > and > > a core "senior staff board" of 14, discussions got out of hand often, > > simply because of the sheer amount of text flying around in the IRC > > room > > or on the mailing list. > > That's a good point - but if its borderline we might want to consider 11 or > 12... not everyone shows up to all meetings. For voting on Indy we did it > offline and all votes were allowed to go for x days. We also allowed > explicit abstain votes. Agreed. > When the team got bigger, we had a core board (Admin) and another. There > were voting hierarchies, ie the admin could override the others, etc. I think for the size of SharpOS right now, an open mailing list vote model followed by a core board override/deadlock-breaker would be a good sweet spot of getting everyone's voice heard while still keeping decision-making times down. > Im suggesting that this board we create is the admin - and if it gets really > big we have two in a hieararchy. While I don't doubt it's necessity later, I think we should stick with the 1-level for now to avoid beaurocratic delays. > > ------------------------------------------------------------------------- > 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 > -- fury long name: William Lahti handle :: fury freenode :: xfury blog :: http://xfurious.blogspot.com/ ------------------------------------------------------------------------- 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
