Qt wiki will be updated on October 12th 2023 starting at 11:30 AM (EEST) and the maintenance will last around 2-3 hours. During the maintenance the site will be unavailable.
Qt Contributors Summit 2019 Program: Difference between revisions
mNo edit summary |
(New topic - code review: sharing the load.) |
||
| Line 123: | Line 123: | ||
With Qt 6 we want to be able to use some C++ 17 language and std library features. Not all compilers and platforms we are going to care about by the time Qt 6 comes around will support evertyhing, so this needs a balanced discussion of up- and down-sides, leading to a pragmatic subset that we can rely on. See https://bugreports.qt.io/browse/QTBUG-77477 for details. | With Qt 6 we want to be able to use some C++ 17 language and std library features. Not all compilers and platforms we are going to care about by the time Qt 6 comes around will support evertyhing, so this needs a balanced discussion of up- and down-sides, leading to a pragmatic subset that we can rely on. See https://bugreports.qt.io/browse/QTBUG-77477 for details. | ||
=== Code Review: Sharing the load === | |||
'''[[User:Eddy|Eddy]]''' | |||
Sometimes we wait and wait for anyone to review our changes. | |||
Sometimes we struggle to keep up with all the reviews we're asked to look at. | |||
How can we organise this so that no-one waits too long but all of us still have time to hack on code ? | |||
Time To Be Arranged. | |||
Revision as of 16:29, 30 September 2019
Back to Qt Contributors Summit 2019
Table of topics
Please add a longer session description with topic owner in the lower part of the page!
Tuesday, 2019-11-19
First day is reserved for topics that are of interest to the majority, and main location is the Assembly Hall. If you have something to present please coordinate beforehand on IRC or via mail.
| Time | Assembly Hall |
|---|---|
| 8:00 - 9:00 | Registration |
| 9:00 - 9:20 | Introduction and sponsors |
| 9:20 - 10:30 | Keynote: Towards Qt 6 (Lars Knoll) |
| 10:30 - 11:00 | Coffee Break |
| 11:00 - 11:30 | QML version 3 |
| 11:30 - 12:00 | CMake Port |
| 12:00 - 13:30 | Lunch Break |
| 13:30 - 14:00 | Branch policy for Qt 6 |
| 14:00 - 14:30 | Qt Marketplace |
| 14:30 - 15:00 | KDE experience in attracting and nurturing contributors |
| 15:00 - 15:30 | Coffee Break |
| 15:30 - 16:00 | Qt 6 Graphics Overview |
| 16:00 - 16:30 | Agenda Overview |
Wednesday, 2019-11-20
| Time | Assembly Hall | Meeting Room 1 | Meeting Room 2 | Meeting Room 3 |
|---|---|---|---|---|
| 9:00 - 10:00 | Qt Marketplace | |||
| 10:00 - 11:00 | Qt Marketplace | |||
| 11:00 - 12:00 | ||||
| 12:00 - 13:00 | Lunch Break | |||
| 13:00 - 14:00 | ||||
| 14:00 - 15:00 | ||||
| 16:00 - 17:00 | Plenary Session | |||
Thursday, 2019-11-21
| Time | Assembly Hall | Meeting Room 1 | Meeting Room 2 | Meeting Room 3 |
|---|---|---|---|---|
| 9:00 - 10:00 | ||||
| 10:00 - 11:00 | ||||
| 11:00 - 12:00 | ||||
| 12:00 - 13:00 | Lunch Break | |||
| 13:00 - 14:00 | ||||
| 14:00 - 15:00 | Plenary Session | |||
Sessions
Qt Marketplace
Tino Pyssysalo and Marko Finnig
Qt Marketplace status, existing and planned features, launch schedule, content publishing process, and content usage.
Qt 6 Graphics Overview
Laszlo & co.
Let's have an overview of graphics related changes in Qt 6. The keynote will probably mention some of these, the goal in this session is to expand on them a bit. There can then be deeper individual discussions on specific topics during the next two days, if there is interest.
C++17 language and std library features for Qt 6
Volker Hilsheimer
With Qt 6 we want to be able to use some C++ 17 language and std library features. Not all compilers and platforms we are going to care about by the time Qt 6 comes around will support evertyhing, so this needs a balanced discussion of up- and down-sides, leading to a pragmatic subset that we can rely on. See https://bugreports.qt.io/browse/QTBUG-77477 for details.
Code Review: Sharing the load
Sometimes we wait and wait for anyone to review our changes. Sometimes we struggle to keep up with all the reviews we're asked to look at. How can we organise this so that no-one waits too long but all of us still have time to hack on code ? Time To Be Arranged.