[Marketing] Qt CS program

[Quim Gil]

Michael, thanks for the first stab at the wiki table.  :)

Still, 
http://qt-project.org/groups/qt-contributors-summit-2012/wiki/Program 
doesn't yet reflect the full proposal as we discussed,

- Plenary sessions take the first and last slot every day. All the rest 
are parallel sessions.

- The morning plenary sessions are about a big topic, inspiring (but not 
restricting) the rest of topics to be scheduled that day. Any topic 
raising fierce discussion could spin off an own, focused session:

June 21 - State of the Union: Qt 5 and Qt 5.1. Opening session 
summarizing where we are and where do we want to go.

June 22 - Qt Quick / Components / Theming... We want to invite the 
maintainers and a few users/contributors (Nokia, RIM, Canonical, who 
else?) to expose their thoughts and needs with the hope of bringing a 
common understanding.

June 23 - HTML5 & the Web. A pannel including Qt WebKit maintainers and 
other users/contributors driving this area (Digia, ICS comes to mind, 
who else?)


The afternoon plenary sessions are Hack'n'Tell: 5 minute demo sessions. 
No slides, no screenshots, no talking guy with empty hands: only demos 
with real code running.

For practical reasons we might group the demos into those runnning on 
devices to be shot with camera and those running from a same laptop - to 
avoid as much as possible Murphy's law by switching devices, laptops, etc.

A wiki page will be open for people to list their demos beforehand.


The Qt Essentials modules get all a pre-scheduled slot in the main room, 
but these are no plenary sessions.

This is something confusing in the current table, sicne they are indeed 
listed in the "plenary sessions" section. Michael, you could simply have 
one table for each day, with 5 columns for time and each of the rooms 
available. The plenaries and the pre-scheduled Essentials would all be 
placed in the main room.

We also selected some Add-ons modules based on their relevance in Qt 5. 
They could also be scheduled in the main room (if there are slots 
available) or in the second one.

Once these sessions are placed in a slot we can start discussing / 
swapping after specific proposals.


On 05/14/2012 01:43 AM, ext Sivan Greenberg wrote:
> On Mon, May 14, 2012 at 11:29 AM, Michael Hasselmann
> <michaelh at openismus.com>  wrote:
>> Questions are:
>> * Does it have to be a plenary session (i.e., targeting all attendees)?

As explained above, there are only 3 plenary sessions. Any new topic 
proposed needs to debunk one of the 3 topics proposed.


> My 0.02EU opinion says it does, in order to to discuss doc
> modularization and doc direction in general (I think we're on the edge
> of going from reference ->  task based docs and that concerns all
> maintainers and modules).
>
> I also think that targeting all attendees  will emphasis how important
> it is to the health and accessibility of qt-project (making it known
> good docs will be part of everyday life in Qt).

Still, I believe State of the Union, how to build UIs on top of Qt Quick 
and the role of HTML5 are bigger topics for the Qt Project now.


>> * Should it be pre-scheduled?
>>
> Not sure about that, but this might enable people to plan ahead for
> the session or,allow people to pre-schedule themselves to be available
> during it. ideas?

I'm happy pre-scheduling a session about documentation, yes. Sound like 
a good topic for June 21.

--
Quim