That sounds pretty good. I might add that, to make this more manageable for BOD and members alike, a dashboard would be handy that lists available votes awaiting participation.
BOD have this, but it's not terribly usable right now -- as the handiest approach would be to provide a list of "items that need your attention" or somesuch to make it clear how members can make a difference (and what their dues are giving them access to!). Chris On Mon, Jan 26, 2009 at 10:49 AM, David Recordon <[email protected]> wrote: > While the specs council vote is designed as a recommendation to the > membership, I'm also trying to capture the current ad hoc involvement of > community members who are not members of the Foundation. I imagine it would > work something like this: > 1) Proposers work on building consensus around their proposal on the > [email protected] mailing list working toward the final version > 2) Propoers submit the proposal to the Specs Council which begins the 15 > day period > 3) Sometime within the 15 days (ideally as soon as possible) the Specs > Council creates the vote within the tool designating it as a Specs Council + > Community (anyone) vote > 4) An email is sent to the [email protected] list announcing the > recommendation vote, noting that only specs council members have binding > votes, but encouraging anyone who wants to to vote > 5) Once all of the Specs Council members have voted or 15 days have > elapsed, whichever comes first, the results are shown at a public URL > showing how each council member voted and aggregated counts of how the > community voted > 6) The Foundation Membership approval vote is created and runs normally > also providing a link to the results of the Specs Council + community vote > > --David > > > On Jan 26, 2009, at 9:48 AM, Martin Atkins wrote: > > David Recordon wrote: >> >>> I'm wondering what it would take to make the voting tool be able to help >>> out the specs council? Like other votes, some of the challenges are sifting >>> through an email thread collecting votes, getting people to realize that >>> they're supposed to vote in a certain thread and mixing the input between >>> the community and council members. What I'd propose is that we add the >>> ability to vote on proposals to the voting tool in such a way where anyone >>> (including non-members) can vote though the results are displayed split up >>> between the council member votes and the wider community votes (a bit like >>> how the US election has the popular vote and the electoral vote). Ideally >>> this would be extended to the final approval vote as well so that anyone >>> could vote but only the votes from Foundation members would be counted. >>> Who should I work with to make this happen? Other ideas on how this >>> should work? >>> >> >> It was my understanding that the specs council vote was essentially a >> recommendation to the community on how to vote, so it seems like the specs >> council vote ought to happen first, rather than in parallel with the >> community vote. >> >> Displaying the specs council result on the voting page for the community >> vote would be good, though. I assume that right now that could be done less >> elegantly by simply including the specs council result in the text that >> introduces the vote. >> >> >> _______________________________________________ >> board mailing list >> [email protected] >> http://openid.net/mailman/listinfo/board >> > > -- Chris Messina Citizen-Participant & Open Web Advocate-at-Large factoryjoe.com # diso-project.org citizenagency.com # vidoop.com This email is: [ ] bloggable [X] ask first [ ] private
_______________________________________________ board mailing list [email protected] http://openid.net/mailman/listinfo/board
