Qt Contributor Summit 2024 - Program

Event main page: Qt Contributor Summit 2024

Please, add your sessions/talks/presentations to the table by the end of the page.

→ If you have any issues while editing this page, please contact Pedro Bessa directly at pedro.bessa@qt.io

Qt Contributor Summit 2024 Program, to be updated

Thursday, September 5th

Morning: Keynote Sessions

Afternoon: Breakout rooms

Friday, September 6th

Morning: Keynote Sessions

Afternoon: Breakout rooms

Thursday, Sep 5th
Time (CEST)	Room A
08:30 - 09:30	Registration + Welcome Coffee
09:30 - 12:00	Keynote Session 1 Roadmap and state of the Qt Project Getting more external contributors, and increasing participation in the project Pitching of afternoon sessions
Time (CEST)	Room A	Room B	Room C	Common area
12:00 - 13:00	Lunch break
13:00 - 13:30	TaskTree CS23	Qt - Connected First
13:30 - 14:00	moc in 202x and beyond	RESTful Qt clients	QtGraphs API and architecture
14:00 - 14:30	Improve API review process	Qt Creator API	Qt Academy
14:30 - 15:00	VScode plugin demo	Feature planning and better involvement of external contributors
15:00 - 15:30	Evolving QIcon and theming		Present and future of Qt for Python
15:30 - 16:00		String Handling	Gerrit and CI plans
16:00 - 16:30	Coffee Break
16:30 - 17:00	Summary of Day 1

Friday, Sep 6th
Time (CEST)	Room A
08:30 - 09:30	Welcome Coffee
09:30 - 12:00	Keynote Session 2 Qt & Cyber Security Modern C++ Qt in Programming: Principles and Practices using C++, 3rd edition Qt and Senders/Receivers State of C++20 in Qt Pitching of afternoon sessions
Time (CEST)	Room A	Room B	Room C	Common Area
12:00 - 13:00	Lunch break
13:00 - 13:30	Qt & Cyber Security (Discussion)	QML: General purpose language or frontend for QtQuick	QtWayland Remaining Issues
13:30 - 14:00	QSharedMemory & QSystemSemaphore in Qt 7	More languages in the Qt Project	Stable Qt Creator API - Wishlist creation
14:00 - 14:30	From design to application as the new kid on the block	QMetaType and QVariant	Qt For WebAssembly
14:30 - 15:00	Qt Quick Effect Maker - Basics and advanced usage	Improving/extending QML type system	Build system news and feedback	Two-way BC in Patch Releases
15:00 - 15:30	Coffee Break
15:30 - 16:30	Summary of Day 2

Topic	Speaker	Format	Summary
Topic Title	Add Your Name(s)	Discussion/Presentation/Workshop/...	Add a short paragraph about the scope of the proposed talk.
Whither QProperty? Wither, perpetuate or evolve?	Fabian Kosmale	Discussion session	We've added bindable C++ properties in Qt 6 – and then mostly ignored them except for bug fixes. Let's recap why we've added it to begin with, collect how it's currently . Then, investigate why we (mostly) went nowhere with it and whether we we want to change that.
std::format support in Qt	Ivan Solovev	Discussion session	We've started to provide support for formatting Qt types using std::format, but we might need some more features from the standard in order to use std::format *inside* Qt. Let's try to discuss what we need from the standard and how can we achieve that.
Qt for Python	Friedemann Kleint	Discussion session	Discuss Qt for Python development and explore ways to enhance its interoperability with other Qt products through feedback, ideas, and constructive criticism.
QtScrypt/QtPythonScripting	Friedemann Kleint	Presentation + Discussion	Present a research project which has been under way providing a more light-weight way for Python bindings.
Deprecation vs Compatibility	Eddy	Discussion session	Follow up on Peppe, Andre' and others discussing SC/BC and the impact of deprecations on users.
What's new in QtGraphs	Tomi Korpipää	Presentation + Discussion	A look into what has changed between QtDataVisualization and QtGraphs, which will be out of TP in Qt 6.8. A short presentation followed by a discussion of where we can / should take it next.
Quo Vadis, TTLOFIR?	Marc Mutz	Discussion	"Things to look out for in review" (https://wiki.qt.io/Things_To_Look_Out_For_In_Reviews) started as a low-entry-barrier way to collect guidelines surrounding code^Wgit-versioned contributions, to be distributed to "official" documents as time goes by. While I believe it had a positive impact on many Qt contributors already in the present form, I still see (too) many of the issues, discussed there, in approved code, suggesting that it may be time to migrate some of the content to said "official" format (QUIP? Qt Coding Standard (no, not the whitespace formatting guideline that currently carries the name)). Also, the number of contributions to TTLOFIR from others than myself remains relatively small (with an explicit shout-out to those who did contribute!). Seeing as the number of Qt contributors only continues to grow (itself a very healthy sign), I think the project is facing a bit of "didn't know; if known, didn't read; if read; didn't understand; if understood, didn't apply" going on. So this session is both to spread awareness, as well as discuss how the process to migrate TTLOFIR items to a more "official" format could look like.
Future of QtLanguageServer repo / Proper CI for non-mainline repos?	QML Team	Discussion	The Qt Language Server repository contains an implementation of JSON RPC and skeleton functionality to implement a language server. It is a non-essential module, which led to https://bugreports.qt.io/browse/QTBUG-115252 , causing it's main user qmlls to not work. While this issue has been resolved, we should ponder a few questions: Do we really need a proper Qt module for it? Should JSON RPC move to QtBase? Would anything besides qmlls benefit from having generic language server support? Can we have "non-mainline" repos which still get the full gerrit+CI workflow (the main reason Qt Language Server became an official module)?
Error handling in Qt (and C++)	Volker Hilsheimer	Discussion	We have several ways of handling errors in Qt: fail with runtime warning, return false with errorString() getter, or emit errorOccurred() signals - often combinations of those. We don't throw exceptions, and we rarely return std::optional. C++23 has introduced std::expected as the vocabulary type for error handling, but we likely won't be able to require C++23 for several more years. Various alternatives that are (or have been) discussed in the C++ committee (such as throwing value-type exceptions) are decades out, if they ever get anywhere at all. However, we have had several attempts to implement something along the lines of std::expected, esp in cases where we needed better tools to handle errors from system API calls: QSystemResult for I/O: https://codereview.qt-project.org/c/qt/qtbase/+/546896 [1] In Qt Multimedia: https://codereview.qt-project.org/c/qt/qtbase/+/437291 To opt-out of QJniObject's overly aggressive exception-clearing: https://codereview.qt-project.org/c/qt/qtbase/+/511466 As pointed out in [1], C++17 compatible implementations of std::expected exist. Should we allow ourselves to use one of them internally? Can we have something that we can use in our own public API (e.g. for QJniObject)?
Qt Documentation	Nicholas Bennett	Presentation and Discussion	Qt Documentation State of the Union How do I contribute? Where do I find the documentation I need? How do I give feedback? Qdoc The recommended way to use this today is via CMake. libclang version New features Future features Look at its great docs! How to make suggestions.
C++26 Reflection and Qt	Thiago Macieira	Discussion	C++26 will come with the first release of reflection. It's probably not enough for Qt's needs to replace moc, but we should know what is missing so we can recommend to the committee our use-cases. We also need to know if there are any design issues that would make the replacement completely impossible.
Qt Lottie : Where it is, where to go	Kwanghyo Park	Presentation and Discussion	A brief introduction of the Qt Lottie module and presents the current status. Following up with a suggestions and discussions on how it could be improved and updated.
Flaky tests	Eddy	Discussion	We currently blacklist flaky tests, which means real failures they might have brought to our attention can get ignored. This should be a temporary state, but some have been blacklisted for many years. Each should be associated with a Jira ticket that won't be closed until the test is fixed and blacklisting removed; it's not clear that's always followed, though. How can we improve on this situation ? See also: QTQAINFRA-6400 and QTBUG-96295.
QFuture/QPromise: ’sup?	Kai Uwe Broulik	Discussion	QFuture capabilities have been much expanded in Qt 6, yet it’s not seeing much use within Qt itself. In the scope of Qt OPC UA, which is inherently asynchronous, we’re investigating the use of QFuture/QPromise to make the APIs more convenient. This discussion session is about setting standards for QFuture/QPromise-based APIs throughout Qt to ensure consistent naming and error handling before their use within Qt expands further.