That may well be the trick: just get started sooner.<div><br></div><div>Overall I don't feel it was a big issue, I just felt we'd just gotten started by the time we packed up. :)</div><div><br></div><div>Josiah<br>
<br><div class="gmail_quote">On Sun, Jul 11, 2010 at 11:36 PM, Jeff Deville <span dir="ltr"><<a href="mailto:jeffdeville@gmail.com">jeffdeville@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
For my part, I thought the introductions were fine. The problem for me was that a lot of us showed up at 1. The introductions didn't start til after 2.<br>
<font color="#888888"><br>
-Jeff<br>
</font><div><div></div><div class="h5"><br>
On Jul 11, 2010, at 11:14 PM, Erik Hollensbe wrote:<br>
<br>
><br>
> On Jul 11, 2010, at 10:57 PM, Chris Nehren wrote:<br>
><br>
>><br>
>> On Jul 11, 2010, at 10:00 PM, Josiah Kiehl wrote:<br>
>><br>
>>> Think the only thing that can be improved is the time spent not hacking. ;) Next time we should get down to coding a bit quicker.<br>
>><br>
>> It was important to me to introduce everyone and give everyone a chance to talk about what they're doing. I want everyone to be on even footing, and splitting off into all our own projects sort of defeats that point. That said, next time round we can continue where we left off and have more time spent actually writing code and the like.<br>
><br>
> Cliff notes for below: give everyone the tools they need to hit the ground running after a 15 minute introduction period, unless they feel like mingling longer.<br>
><br>
> Aaaaand the long version:<br>
><br>
> Right, but I can see the mindset of Josiah, and I believe Mark expressed an interest in getting started immediately (hence his deliberate late arrival), but I don't want to put words into his mouth.<br>
><br>
> I think there's a solution that might make everyone happy -- being a part of the introduction process is optional, or we keep introductions deliberately short and allow people to interact while hacking, killing two birds with one stone.<br>
><br>
> I think this would actually be solved best by a pre-meeting project board (on the interuntz) where people can do what we spent the first hour doing over the week / next two weeks figuring out what they want help on and/or figuring out what they want to work on.<br>
><br>
> This boils the introduction down to, "I'm Joe, and I came here to help on X", and I think this would largely cull the problem of language barriers which I know kept a few people from contributing to certain projects today (e.g., learn what you can about topic $x between meetings).<br>
><br>
> -Erik<br>
> _______________________________________________<br>
> Hackadelphia mailing list<br>
> <a href="mailto:Hackadelphia@lists.scsys.co.uk">Hackadelphia@lists.scsys.co.uk</a><br>
> <a href="http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/hackadelphia" target="_blank">http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/hackadelphia</a><br>
<br>
<br>
_______________________________________________<br>
Hackadelphia mailing list<br>
<a href="mailto:Hackadelphia@lists.scsys.co.uk">Hackadelphia@lists.scsys.co.uk</a><br>
<a href="http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/hackadelphia" target="_blank">http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/hackadelphia</a><br>
</div></div></blockquote></div><br></div>