<div dir="ltr">I do like the format of one general meeting a month (to discuss all sudo room goings on) and then the other three meetings can be working/learning meetings. Maybe with a 15-30 min talk of something of interest so that we're all learning and sharing.<div>
<br></div><div style>Patrik suggested the split between general meeting and working meeting and it's helped us to slice up our time a little bit better to dive into different topics/subjects. I have really enjoyed Sudo rooms recent experiments with meeting formats though (I'm finding them more interesting and more valuable personally).</div>
<div style><br></div><div style>R</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Apr 25, 2013 at 5:06 PM, Naomi Most <span dir="ltr"><<a href="mailto:pnaomi@gmail.com" target="_blank">pnaomi@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">You still need to define "working on what", otherwise you end up having to waste a lot of time defining that in the moment.<div>
<br></div>General meetings still need structure, otherwise people lose sight of them having any purpose and they tend to expand in scope and time length geometrically.<span></span><div>
<br></div><div>I still think sudo room would do fine simply splitting out Bureaucracy and the current general meeting, which actually runs quite well most of the time.<div><div class="h5"><br><div><br><br>On Thursday, April 25, 2013, Anthony Di Franco wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-family:arial narrow,sans-serif">That's a great idea.<br>Or, just separate the weekly meeting into general and working time blocks so people can come to whichever they would like.<br>
</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Apr 25, 2013 at 8:33 AM, Patrik D'haeseleer <span dir="ltr"><<a>patrikd@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div>On Thu, Apr 25, 2013 at 7:51 AM, Marina Kukso <span dir="ltr"><<a>marina.kukso@gmail.com</a>></span> wrote:<br>
</div><div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">for
the biohackers is a working meeting a hacking meeting or a meeting
where business relating to the functioning of the group gets done?
because if it means the latter, then our meeting is supposed to be that
:P </div>
</blockquote><div><br></div></div></div><div>Typically more of the latter,
because of the stage the bio group is at, at the moment. But as long as
we're making significant progress towards having a functioning DIYbio
lab, it's all good. <br>
<br>We also have a "general meeting" for the East Bay DIYbio group
(every last friday - coming up tomorrow!) that is more about making
introductions, exchanging cool ideas, socializing, etc. Which is also
essential for building a community, but if we only have that kind of
meetings, we'd never get any of the boring logistics done. <br>
<br></div><div>"General meeting" and "working meeting" is just what I've
started calling them, and nobody has called me on it yet ;-) For the
first "working meeting", we set it up over email among some of the key
members, because we wanted it small and focused enough to actually get
anything done. But I think as long as we advertize that this is a
*working* meeting, and that people will be expected to contribute and
get something done, they will automatically self-select accordingly.<br>
<br></div>Maybe sudoroom needs a separate "general meeting" that is
more free-form, and not focused on rules issues etc? Heck, I might even
come to those! ;-)<span><font color="#888888"><br><br></font></span></div><span><font color="#888888">Patrik</font></span></div>
<br>_______________________________________________<br>
sudo-discuss mailing list<br>
<a>sudo-discuss@lists.sudoroom.org</a><br>
<a href="http://lists.sudoroom.org/listinfo/sudo-discuss" target="_blank">http://lists.sudoroom.org/listinfo/sudo-discuss</a><br>
<br></blockquote></div><br></div>
</blockquote></div></div></div></div><span class="HOEnZb"><font color="#888888"><br><br>-- <br>Naomi Theora Most<br><a href="mailto:naomi@nthmost.com" target="_blank">naomi@nthmost.com</a><br><a href="tel:%2B1-415-728-7490" value="+14157287490" target="_blank">+1-415-728-7490</a><br>
<br>skype: nthmost<br><br><a href="http://twitter.com/nthmost" target="_blank">http://twitter.com/nthmost</a><br>
</font></span><br>_______________________________________________<br>
sudo-discuss mailing list<br>
<a href="mailto:sudo-discuss@lists.sudoroom.org">sudo-discuss@lists.sudoroom.org</a><br>
<a href="http://lists.sudoroom.org/listinfo/sudo-discuss" target="_blank">http://lists.sudoroom.org/listinfo/sudo-discuss</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br>Ryan Bethencourt<br><br>Tel: (415) 794 6463<br><a href="mailto:ryan.bethencourt@gmail.com" target="_blank">ryan.bethencourt@gmail.com</a><br><br><a href="http://www.bamh1.com" target="_blank">www.bamh1.com</a><br>
<a href="http://www.linkedin.com/in/bethencourt" target="_blank">www.linkedin.com/in/bethencourt</a><br><a href="http://www.logos-press.com/books/biotechnology_business_development.php" target="_blank">www.logos-press.com/books/biotechnology_business_development.php</a><br>
</div>