[liberationtech] Crowd wisdom in the service of the government

[Steven Clift]

I'd ask this question on the Democracies Online Exchange:
http://dowire.org/x

(It has 700+ people interested in gov/civil society use of tech for
democratic good.)

And if local in scope, also try the CityCamp Exchange:
http://e-democracy.org/citycamp

Steven Clift
clift at e-democracy.org  - +1 612 234 7072
http://stevenclift.com - @democracy
On Jan 14, 2012 4:21 AM, "Tarik Nesh-Nash" <tarikn at gmail.com> wrote:

> Dear friends,
>
> Thanks a lot for your feedback and examples.
>
> I wanted to come back to you and I ask a more detailed question.
>
> I am researching on how my government can use collective intelligence (or
> the wisdom of the crowd) to "better" function in general. I am more
> thinking of a platform where the government raises questions/problems, and
> asks the citizens for proposals and feedback.
> This is different from grassroot (or civil society) initiatives to use
> crowdsourcing, as this would be used by the government itself.
> Also, the question may be general or specific, but it is asked by the
> government.
>
> Are there similar initiatives that you may know of?
>
> Thanks,
> Tarik
>
>
> _______________________________________________
> liberationtech mailing list
> liberationtech at lists.stanford.edu
>
> Should you need to change your subscription options, please go to:
>
> https://mailman.stanford.edu/mailman/listinfo/liberationtech
>
> If you would like to receive a daily digest, click "yes" (once you click
> above) next to "would you like to receive list mail batched in a daily
> digest?"
>
> You will need the user name and password you receive from the list
> moderator in monthly reminders.
>
> Should you need immediate assistance, please contact the list moderator.
>
> Please don't forget to follow us on http://twitter.com/#!/Liberationtech
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.stanford.edu/pipermail/liberationtech/attachments/20120114/b9bc6431/attachment.html>