On Fri, 2019-08-02 at 15:09 -0400, Jonathan Proulx wrote: > On Fri, Aug 02, 2019 at 07:44:13PM +0100, Marcin Kulisz wrote: > :On 2019-07-24 01:17:34, Tomasz Rybak wrote: > :> On Tue, 2019-07-23 at 10:13 +0200, Bastian Blank wrote: > :> > On Tue, Jul 23, 2019 at 12:01:05AM +0200, Tomasz Rybak wrote: > :> > > So - are there any objectsions to those dates, 2019-10-14 > (Monday) > :> > > to 2019-10-16 (Wednesday) at MIT? > :> > > :> > I'm most likely out for that days. I'll be in Dresden for the > :> > weekend, > :> > which would be a really tight fit to come to Boston in time. > :> > :> I really appreciate what you're doing regarding cloud images. > :> At the same time I believe that it'd be good for team to have > :> this knowledge spread over more people, and to involve more > :> Developers in daily tasks. > : > :As we're quite early in the process of organising the next Cloud > Sprint I'd > :hope that we can find date allowing all of us to attend at the same > time. If > :proposed dates not working for Bastian maybe we can manage to push > back with > :the date for a week or two to accommodate all of us. > :And just to make it clear for now all dates looks good for me. > > For MIT space September 30 -> Oct 2nd is the only other slot I see > within a couple weeks either side, if that's better. > Can you reserve this time also, so we have it just in case we want to move our meeting? As far as I remember, it was easier to cancel reservation than to find something. And then let's discuss who can come at which of those two dates (either 2019-09-30 -> 2019-10-02 or 2019-10-14 -> 2019-10-16). I cannot come at the former, but can at the latter. OTOH I could attend remotely - but let's first Maybe it would be good to discuss what we want to achieve during sprint, so it'd be easier to decide who is really needed in person and who can attend remotely. Best regards. -- Tomasz Rybak, Debian Developer <serpent@debian.org> GPG: A565 CE64 F866 A258 4DDC F9C7 ECB7 3E37 E887 AA8C
Attachment:
signature.asc
Description: This is a digitally signed message part