<div class="gmail_quote">On Sun, Feb 20, 2011 at 10:03 PM, Dave Crossland <span dir="ltr"><<a href="mailto:dave@lab6.com">dave@lab6.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I think (1) is a long term goal</blockquote><div><meta http-equiv="content-type" content="text/html; charset=utf-8"><div>[...] </div><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
Wifi mesh seems to me a definite "yes but later" thing.</blockquote></div><div><br></div><div>I see your point, and prioritising is important - but I think the easiest (or most anarchistic) way of prioritising these independent subtasks is by parallelizing them (analogous to "Levin search" ;) ). Each person can choose which of the goals to work on, and that way, people can "vote by example". If everybody agrees that the most important part is, say, secure email, then that is what will be worked on most, and thus be finished first. Also, it is more fun because everybody chooses which part they feel is most important, and want to work on. And it is also a sure-fire way to avoid the danger of situations like this <a href="http://www.montypython.net/brianmm3.php#Scene 21">http://www.montypython.net/brianmm3.php#Scene 21</a> ;)</div>
<meta http-equiv="content-type" content="text/html; charset=utf-8"><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">
> Next week I'll do another Sunday Hackfest with whoever wants to join, and I<br>
> think we can make it a regular thing.<br>
<br>
</div>That sounds like a very good idea - I'll try to make it :)<br>
</blockquote></div><br><div>Great, see you there!</div>