On 29 Mar 2015, at 23:48, Margarita Manterola margamanter...@gmail.com
wrote:
Please discuss it also with video, to see if they can manage the
schedule/which slots cannot be recorded.
I'm not sure what you mean here. 90 minutes should be enough time for
every member of the video team
Hi,
El 30/03/15 a las 08:23, Giacomo Catenazzi escribió:
On 29 Mar 2015, at 23:48, Margarita Manterola margamanter...@gmail.com
wrote:
Please discuss it also with video, to see if they can manage the
schedule/which slots cannot be recorded.
I'm not sure what you mean here. 90
Hi,
I won't be able to attend the meeting tomorrow, so here are my 2 cents.
On Sun, Mar 29, 2015 at 11:48:17PM +0200, Margarita Manterola wrote:
Hi,
On Sun, Mar 29, 2015 at 11:00 PM, Giacomo Catenazzi c...@debian.org wrote:
- Reduced lunch and dinner times to 90 minutes, which is more that
On 29/03/15 14:47, Maximiliano Curia wrote:
- Reduced lunch and dinner times to 90 minutes, which is more that enough for
all the attendees to eat, and gives us back one hour of activities (a
maximum of 7 vs the 6 previously, which is still less than a regular 8
hours day work).
I've
also sprach Maximiliano Curia m...@gnuservers.com.ar [2015-03-30 14:13 +0200]:
I wouldn't like to have a fixed time for non-video-recorded
events, nor promote them by requiring to have one of them each
day, nor demote them to second class events that occur while
people is eating.
I am really
Hi,
We have come back and forth with several details in the schedule, and at least
in the content team we would like to have a decision on it so we can rely on
it, knowing the event slots available, and I'm sure that other teams, like
facilities would prefer to have it already decided, so
Hey Maxy, Santiago, and the rest of your team:
the schedule looks really good I think. It's impressive how you
turned all the new stuff and special wishes into such a coherent and
clear schema. Thank you!
Regarding the 90 Minute lunch/dinner slots: it's a good idea and it
should probably
