On 04/18/2012 02:17 PM, ext Sivan Greenberg wrote: > On Wed, Apr 18, 2012 at 10:33 PM, Quim Gil<[email protected]> wrote: >> Please let's define the basics of the schedule: >> >> URGENT >> >> - Opening and closing times + coffe& lunch breaks on June 21, 22 and >> 23. Without this Kalkscheune can't organize themselves. > > How about we gather at 8:00 register etc tags shirt etc , start at > 9:00 , close at 18:00. > First c-break at 09:45 , lunch at 12:00, c-break again at 13:45, > 15:45, 17:45 to closing.
One iteration more, based on 50' sessions + 10 minutes break between sessions. 8:00 - Doors open. 9:00 - Sessions 1 10:00 - Sessions 2 11:00 - Sessions 3 12:00 - Wide lunch break, time for little meetings. 13:00 14:00 - Sessions 4 15:00 - Sessions 5 16:00 - Sessions 6 17:00 - Open floor, time for little meetings. 18:00 - Doors closed || Social event until 23h. >> >> - Main room sessions (video recorded) will be cherry-picked and >> scheduled in advance or not? > > I don't see how it can work out without in-advance scheduling, yes. OK, this is the assumption now. Ass soon as we agree on the total amount of slots we will need to find out the best way of scheduling those sessions. A thread apart. > >> >> - June 21 in the morning dedicated to plenary session only or not? >> > We could do that, but perhaps also allow them to happen throughout the > event if interesting guests arrive later? that said, we need to have a > device to announce them enough so people will know. Good point. Maybe we can have plenary session every day at 9am, 3 in total. If we need more we could go for the last slots of the day at 4pm (maybe not the last day, though). >> >> NOT SO URGENT >> >> - Any other activity that would be scheduled in advance or does all the >> rest go to unconference mode? >> > As mentioned before, having hacking sessions happen as per track and > in-schedule will relieve interested parties of having to decide > between attending a sessions, or sitting to hack/learn, given it is in > their track of interest. (we cannot help it if another track has a > hacking session that happens during another track's sessions.) Those > not interested in the hack session can attend a sessions of a > different track at that time. > > Also, some parts of Qt require/get a large number of participants > in-session, and require allocation of large enough rooms. I'd love to > see those scheduled in advance to not repeat last year's situation, > where those sessions were filled and people (myself included) gave up > attending since there was no space left to squeeze yourself in the > room ;) Maybe we don't want an unconference after all? ;) Something we did in a couple of Maemo Summits was to have an open wiki where people could schedule their own sessions as long as they were filling empty slots or negotiating swaps with other slots. A few people "content committee" could move talks to better spots, and there was some spots left empty on purpose for last minute sessions. No call for papers, but no unconference either. I personally liked it but FULL DISCLOSURE I came up with that proposal, and it received some criticism as well. No system is perfect. >> - How are session slots distributed over rooms and during the day? >> Everything in a regular grid or do we have longer& shorter sessions? >> > Judging by the experience of last year, I think it is not realistic to > have less than 45 minutes sessions simply because it is very hard to > achieve something (even a decisions) in less time than that. I also > personally think it'd be a good idea to try to confine to the one > duration to enable as many subjects to get discussed and not "hog" > room space. > > So we just have 45 mins sessions. If a group needs more than that they > can take it , but if the room is scheduled for something else, they > need to continue on their own somewhere else (I imaging there'd be > enough room for that other than the sessions rooms, like the benches > we had in the venue last year). Let's stick to 50' sessions followed by 10' break. This allows simpler schedules, more buffer between sessions for everybody to move on and decent frequent breaks saving us from the more complicated 30' breaks. There is a 2h break at midday, which already leaves plenty of non-scheduled time. -- Quim _______________________________________________ Marketing mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/marketing
