Re: Scheduling the First Interop sponsored by The Calendaring and Scheduling Consortium

Cyrus,

A good point and one I hadn't thought of.  Or if we stuck to
Thursday/Friday and the host was anywhere on the West Coast (for example)
it would still be possible for people to easily get down to San Diego for
the IETF meeting, on an air ticket that spanned a Saturday night.  Unless
we actually had the event in San Diego and probably at the hotel I would
think we'd want to give people a day in between -- especially us, as we
have to take down the site and bundle ourselves up.

That would argue for EITHER waiting until the end of July, OR having the
first one asap and then the second one at the end of July.  By this
reasoning the early July date would be least useful.

Dave Thewlis


*********** REPLY SEPARATOR  ***********

On 4/19/2004 at 12:38 Cyrus Daboo wrote:

>Hi David,
>
>--On Sunday, April 18, 2004 05:24:12 PM -0700 "David C. Thewlis" 
><[email protected]> wrote:
>
>| (c) 29-30 July.
>
>This is right before the IETF meeting in San Diego (1 - 6 August) so it 
>could be tied to that, in which case doing it 30/31 (Friday/Saturday)
>would 
>be better. Ideally having it at the IETF hotel would be good too. If the 
>calsch WG meeting could be scheduled early in the week that might
>encourage 
>a larger attendance from those at the interop who might stay over.
>
>-- 
>Cyrus Daboo