Hi All,<div><br></div><div>I stumbled across votorola a few weeks ago and I've been listening in on the google group when time allows. I've been extremely busy so no time to get involved so far (plus not sure what I can bring to the table at this point) but this seems like a good time to poke my head in and say hello.</div>
<div><br></div><div>I'm studying voting-based interaction on the web towards a Sociology/Stats PhD at a UK University, but the reason I got into that initially was a strong interest in E-Democracy... I couldn't find any really interesting examples of e-democracy to study two years ago, so I've been studying mostly Social News sites until now. </div>
<div><br></div><div>I tried to make my own democratically run non-profit shop last year (still up at <a href="http://www.socapital.org">www.socapital.org</a>) before realising that I really don't have the programming/web-dev skills to advance e-democracy platforms myself in any meaningful way. </div>
<div><br></div><div>My background is in experimental psychology and I've produced a journal article or two while I was doing that. Experimentation and analysis is what I think I could bring to the Votorola project, although I don't know whether that's on the current list of priorities...</div>
<div><br></div><div>At the point where there's some sort of prototype of the software up and running I could recruit participants and run experimental instances of it (provided I can play with some of the variables of how it works). Or, if you get an instance of the software up and running for public consumption and provide me with detailed data on how its being used I could analyse that to see what I can learn. The goal in both cases would be to produce some findings to publish in a journal article or present at conferences... so it could conceivably help the project both by increasing understanding and increasing awareness among academics. </div>
<div><br></div><div>Like I say I'm very busy these days, but I'll continue to follow the project and if you think of some way that I can help out then let me know!</div><div><br></div><div>Richard</div><div><br><div class="gmail_quote">
On Wed, Oct 27, 2010 at 9:23 PM, Michael Allan <span dir="ltr"><<a href="mailto:mike@zelea.com">mike@zelea.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Alex understands the top-level design of the prototype. I think he<br>
also has domain requirements similar to yours David, because it<br>
appears that his use cases place similar stresses on the design. You<br>
guys should talk, as Alex says.<br>
<br>
David you mention "common goals". Just quickly, here are my<br>
longstanding goals:<br>
<br>
1. Start building the theory.<br>
a) Explore and document the theory in academic papers.<br>
b) Open a discourse with academics and other theoreticians.<br>
2. Finish prototyping the practice.<br>
a) Put the architectural documents in proper form.<br>
b) Prototype a UI client, such as crossforum theatre (hard).<br>
c) Prototype free-range drafting (easy).<br>
<br>
Alex may also need 2a and 2b, so we're trying to coordinate. I hope<br>
to start shifting my work in that direction by next week. (Just need<br>
to catch up on emails Alex (including yours) and post a theory outline<br>
first.)<br>
<br>
Same for you David. If you need anything under 1 or 2, then we can<br>
try to coordinate. But my intial impression is that you have other<br>
priorities ("delivering an outcome for a client") and you see 1 and 2<br>
as premature.<br>
<br>
David Bovill wrote:<br>
> ... the scope of any such project can easily be limited to<br>
<div class="im">> delivering an outcome for a client - after which everyone can go<br>
> back to their own thing taking whatever code, assets and experiences<br>
> were generated by the work (as these would be open).<br>
<br>
</div>Without a complete, functional prototype we have nothing in principle<br>
to deliver to anyone, never mind a paying client (if that's the hope).<br>
We're still exploring the design possiblities, still pioneering. I<br>
doubt we're anywhere near any kind of a production stage, yet. But I<br>
guess it depends on what we put into it. So if you want to accelerate<br>
things, please consider putting stuff into the prototyping effort -<br>
"after which", as you say, "everyone can go back to their own thing" -<br>
you to your clients, Alex to his co-ops, I to my theory, and so forth.<br>
<div class="im"><br>
--<br>
Michael Allan<br>
<br>
Toronto, +1 647-436-4521<br>
<a href="http://zelea.com/" target="_blank">http://zelea.com/</a><br>
<br>
</div><div><div></div><div class="h5">--<br>
You received this message because you are subscribed to the Google Groups "Votorola" group.<br>
To post to this group, send an email to <a href="mailto:votorola@googlegroups.com">votorola@googlegroups.com</a>.<br>
To unsubscribe from this group, send email to <a href="mailto:votorola%2Bunsubscribe@googlegroups.com">votorola+unsubscribe@googlegroups.com</a>.<br>
For more options, visit this group at <a href="http://groups.google.com/group/votorola?hl=en-GB" target="_blank">http://groups.google.com/group/votorola?hl=en-GB</a>.<br>
<br>
</div></div></blockquote></div><br></div>
<p></p>
-- <br />
You received this message because you are subscribed to the Google Groups "Votorola" group.<br />
To post to this group, send an email to votorola@googlegroups.com.<br />
To unsubscribe from this group, send email to votorola+unsubscribe@googlegroups.com.<br />
For more options, visit this group at http://groups.google.com/group/votorola?hl=en-GB.<br />