Forum OpenACS Q&A: Re: Bootstrapping OpenACS governance

Collapse
Posted by Joel Aufrecht on
I think the decision-making system has these requirements:
  • Anybody can put stuff (name, description, links, etc) on the list
  • Anybody can see the status of anything on the list
  • The core team can act asynchronously on the list. This probably includes voting yes, voting no, marking stuff inappropriate (dupe, newbie question in the wrong place)
  • Things that get a no vote, or don't get any attention at all, get discussed and voted on within a week or two.
  • The list can be searched and browsed.
I think this mechanism, combined with the current core team members, would be a huge step forward with low cost. We have at our disposal mailing lists, forums, irc, bug systems, and a web community toolkit. So I envision something like a simplified bug system for tracking, plus weekly irc with a quorum (2/3 of core?) to keep things moving. If there's nothing on the list that needs group attention, there's no irc. I think core team members have an obligation to participate at least weekly, but does that participation mean dedicating an hour to IRC, or just being responsive to specific things via email/forums, or what?