On 8 Aug 2010, at 00:52, Richard Jones wrote:
> On Sun, Aug 8, 2010 at 6:36 AM, Ben Hutchings wrote:
>> On Sat, 2010-08-07 at 20:55 +0100, Michael Sparks wrote:
>> [...]
>>> Regarding next time, I'm already also beginning to think and look at
>>> better ways of doing this. (Which will probably b
BTW, my solution to the manpower problem was to rope in non-Python people.
Specifically, my brother :-)
Richard
On 08/08/2010, at 11:37 AM, Michael Sparks wrote:
> Harder if the ratio is 0.3 people per room though.
>
> Michael
>
> On 8/8/10, Richard Jones wrote:
>> On Sun, Aug 8, 2010 a
Harder if the ratio is 0.3 people per room though.
Michael
On 8/8/10, Richard Jones wrote:
> On Sun, Aug 8, 2010 at 6:36 AM, Ben Hutchings wrote:
>> On Sat, 2010-08-07 at 20:55 +0100, Michael Sparks wrote:
>> [...]
>>> Regarding next time, I'm already also beginning to think and look at
>>> bet
On Sun, Aug 8, 2010 at 6:36 AM, Ben Hutchings wrote:
> On Sat, 2010-08-07 at 20:55 +0100, Michael Sparks wrote:
> [...]
>> Regarding next time, I'm already also beginning to think and look at
>> better ways of doing this. (Which will probably be something along the
>> lines of direct recording to
Hi,
Many thanks for the comments guys. I'm bowing out of this discussion
now, since it should be noted that _resources_ are the primary issue
really. (My understanding is that the Pycon US kit requires more than
one or two people trying to film all the tracks in parallel ...)
_People_ and kit spe
On Sat, 2010-08-07 at 20:55 +0100, Michael Sparks wrote:
[...]
> Regarding next time, I'm already also beginning to think and look at
> better ways of doing this. (Which will probably be something along the
> lines of direct recording to disk via HD webcams etc. But that's a
> different conversatio
