[Qt5-feedback] Summary of the QtCS sessions on Qt5 structure, naming, releases, platform tiers

[henry.haverinen at nokia.com]

Hello everyone,

At QtCS, we had 4 sessions and countless hallway discussions about what we
have been calling the Qt 5 product definition. The sessions covered
general topics like the structure of Qt (the core part, add-ons etc.),
naming conventions, releasing principles, platform tier definitions,
cross-platform promise, and compatibility promise. Thanks a lot for the
very active participation and great discussions!

During the sessions, we made conclusions about platform tiers, releasing
principles, naming conventions for add-ons, cross-platform promise, and
compatibility. However, we did not find consensus on the structure of Qt.
On one hand, we wanted to have an extremely simple structure and a clear
definition of what parts of Qt must be available on all platforms. On the
other hand, we want to have a natural home for QWidget classes, and make
sure we're sending the correct message about the existing functionalities:
they are 1st class citizens on the desktop platforms, but not necessarily
available on embedded or mobile platforms.

We continued the talks until the very end of the summit, and during the
last hours, I believe we came up with a good proposal around "Qt
Essentials" and Qt Add-ons. Instead of detailed meeting minutes, I wrote
the results of all these sessions to this wiki page:

http://developer.qt.nokia.com/groups/qt_contributors_summit/wiki/Qt5Product
Definition


Please review! The whole text needs a lot of review and discussion. Do you
think that it is sending the correct messages about the direction of Qt?
Is it consistent? Is it clear and easy to understand?

Cheers,
Henry