On 15 February 2010 19:12, Richard Taylor
<[email protected]> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 15/02/2010 17:41, John Pinner wrote:
>> HI,
>>
>>
>> Well, we hven't really discussed this yet, but it's broadly correct, however:
>>
>> * Registration is only on Day One (Monday) and we will start earlier
>> on that day compared with others, so 8.00 on Monday and 8.30 for
>> coffee on Tu/Wed/Thu.
>> * I think we should have a longer lunch, at least 90 minutes.
>>
>
> OK, so we have something like this (just for starters):
>
> Monday
> ======
> 8:00 Registration / coffee
> 9:00 Plenary
> 10:00 Talk
> 11:00 Break
> 11:30 Talk
> 12:30 Lunch
> 14:00 Talk
> 15:00 Talk
> 16:00 Break
> 16:30 Talk
> 17:30 Break
> 18:00 Talk
> 19:00 End
>
> Tuesday
> =======
> 8:30 coffee
> 9:00 Plenary
> 10:00 Talk
> 11:00 Break
> 11:30 Talk
> 12:30 Lunch
> 14:00 Talk
> 15:00 Talk
> 16:00 Break
> 16:30 Talk
> 17:30 Break
> 18:00 Talk
> 19:00 End
>
> Wednesday
> =======
> 8:30 coffee
> 9:00 Plenary
> 10:00 Talk
> 11:00 Break
> 11:30 Talk
> 12:30 Lunch
> 14:00 Talk
> 15:00 Talk
> 16:00 Break
> 16:30 Talk
> 17:30 Break
> 18:00 End    <-- Early finish to give people change to get to dinner
>
> Thursday
> =======
> 9:30 coffee  <-- late start for hang overs
> 10:00 Talk
> 11:00 Break
> 11:30 Talk
> 12:30 Lunch
> 14:00 Talk
> 15:00 Talk
> 16:00 Break
> 16:30 Talk
> 17:30 Break
> 18:00 Talk  <-- presumably a plenary / finsh here.
> 19:00 End  <-- Maybe an earlier finish

Except that the general thinking is that Thursday will nearly all be
plenaries - keynotes, lightning talks, close down, draws etc.

But until we have all the talks submissions and keynote speakers, we
can't be too specific. Sorry.

BTW, In the time table, ultimately we will want to point to slides and
audio/video records if/when these are done.

Thanks,

John
--
PS your signature is still wrong!
_______________________________________________
Europython-improve mailing list
[email protected]
http://mail.python.org/mailman/listinfo/europython-improve

Reply via email to