| Re: [eclipse.org-architecture-council] Working Session @ EclipseCon Europe in Ludwigsburg |
> Speaking for myself, a conference day can be very long. I'm mostly brain dead after end of sessions (I'm old)
Well, I'm old too and my brain does not boot at 7:45 ;-)
Dani
From: Gunnar Wagenknecht <gunnar@xxxxxxxxxxxxxxx>
To: "eclipse.org-architecture-council" <eclipse.org-architecture- council@xxxxxxxxxxx >
Date: 17.08.2018 18:49
Subject: Re: [eclipse.org-architecture-council] Working Session @ EclipseCon Europe in Ludwigsburg
Sent by: eclipse.org-architecture-council-bounces@xxxxxxxxxxx
> On Aug 17, 2018, at 17:58, Daniel Megert <daniel_megert@xxxxxxxxxx> wrote:
>
> Hi Gunnar
>
> > It looks like the best option would be Tuesday morning 7:45-8:45.
>
> Thanks for finding that date. Would it be possible to also offer/find alternatives over lunchtime or at the end of the day?
There is no free room during lunch time. We could have a lunch table, though. Although this would not allow us to draw something on a whiteboard.
Evening is possible but conflicts with BOFs and social time. From my experience this has an impact on participation and attention. Speaking for myself, a conference day can be very long. I'm mostly brain dead after end of sessions (I'm old). Should we still go for an evening slot?
-Gunnar
_______________________________________________ https://dev.eclipse.org/
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxx mailman/listinfo/eclipse.org- architecture-council
IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.
_______________________________________________
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org- architecture-council
IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.