Qt Contributor Summit 2025 - Program

Event main page: Qt Contributor Summit 2025

Please, add your sessions/talks/presentations to the Table of Session Details at the end of the page.

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

Our Program

May 7th: Welcome Event (Evening, 7pm)

May 8th: Contributor Summit Sessions + Dinner

May 9th: Hacking Day

Please note times are subjected to change.

Thursday, May 8th
Time (CEST)	Room
8:30	Registrations, Breakfast
9:00	Welcome
9:15	Roadmap deep dive and discussions: What are The Qt Company goals for Qt?
10:30	Lightning talks from projects and maintainers
Time (CEST)	Room	Room	Room	Common area
Afternoon	Sessions, Lunch and Coffe Break
Evening	Dinner at the Event Venue

Table of Session Details

FYI: this year, we would like to try a new format of talks to cover more ideas for Qt: "lightning talks". Those talks should cover development works which extend Qt in one or another way and bring this functionality to other users internally or externally. These talks will be held in one joined slot all together and are limited to 5 min each. Please mark such talks with "lightning" in the column "Format".

Add your talk here:

Topic	Speaker	Format	Summary
Topic Title	Add Your Name(s)	Discussion/Presentation/Workshop/...	Add a short paragraph about the scope of the proposed talk.
Integer Overflow in Widgets	Marc Mutz	Discussion	Coverity and UBSAN have pointed out that we suffer from signed integer overflows in QtWidgets. To avoid shotgun-surgery, where each author fixes things differently, we should decide on a common strategy for dealing with these issues. Simply ignoring it won't fly in a world of increased scrutiny on software safety. Alternatives include limiting property values more (at setter time), continue to accept them and handle overflows manually or using Peppe's SafeInt more.
To Review And Be Reviewed	Marc Mutz	Discussion	The Qt project is so large these days that no one person can be an expert in all areas. With this in mind, it becomes more and more important for commits to describe not just what they do, but also why they do it, and for reviewers to demand rationale before they review, and to verify that the claims made in the commit message match the code and vice versa. Unfortunately, this absolutely necessary fact it still ignored by many authors and reviewers. I would like to discuss how the role of author and reviewer differ, and how to reach a point at which good commits with good commit messages become the norm, and not the exception.
Compile once. Run everywhere (2025 edition)	Cristian Adam	Presentation	Compiling and deploying of C++ applications on Windows, Linux, macOS for x86_64 and arm64 can be challenging. By using Cosmopolitan Libc we could have an alternative.
QProperty and QBindable, take 2	Ulf Hermann	Discussion	There are new proposals on what to do with them, and we haven't come to a conclusion last time around
State of Qt on Windows	Wladimir Leuschner	Presentation & Discussion	Part 1: Current State of Qt on Windows Current state of Windows on ARM, Windows App SDK integration, Custom titlebars, Webview, Windows Store deployment. Part 2: Discussion about further Futures for Qt on Windows What new futures do you want to see for Qt for Windows?
qml API review	Fabian Kosmale	Discussion	API reviews are already an arduous endeavour for our C++ API. On the QML side, we have the additional issue that textual diffs of qmltypes are used, but qmltypes are nowadays mostly meant for tooling, not to facilitate API review. Let's discusss how we can improve this
State and Direction of Qt's Build System	Alexandru Croitor, Cristian Le	Presentation & Discussion	What happened in Build System land, what are current challenges and future plans.
State and Direction of Qt's i18n and l10n framework	Masoud Jami, Jörg Bornemann	Presentation & Discussion	Recent work on i18n/l10n related tools and future plans.
Fontations in Qt: Adding Rust to the build system	Eskil Abrahamsen Blomfeldt	Discussion	Google are introducing a memory-safe replacement for Freetype called Fontations which is written in Rust. In general, many of their core components are being ported to Rust. If we would like to use this or other such components in Qt, we would need a build system capable of compiling the code. This will likely be needed by Qt Web Engine as well in near future.
QtTest: state of the module and the way forward	Tor Arne Vestbø, Eddy	Presentation & Discussion	An update on where we are and where we want to go
Async 1:1 APIs	Mårten Nordheim, Ivan Solovev	Presentation & Discussion	Proposal and discussion around how we may model future async API (using Async I/O as an example) where one-to-one is the focus with a smooth path to seamlessly using coroutines or std::execution sender/receivers.
Enabling QFile signals in the normal case	Mårten Nordheim	Lightning(?) discussion	There is interest in using QFile as it is today but with asynchronous read so it can work better in e.g. webassembly or with networked/cloud-backed files without blocking. Should this be done in the first place? There are concerns how this would work with pre-existing APIs expecting QFile's current-day semantics. How would it work? Using opt-in mechanism?
Future of QtGraphs	Tomi Korpipää, Sakaria Pouke, Kaj Grönholm	Discussion	To get the discussion going we'll go through the things we have already in the works or planned, and after that we hope that you'll join the discussion with your own wish-list of things you'd like to see in QtGraphs in the future. (This would probably work well as a common area discussion)
UnifiedStyling	Richard	Presentation & Feedback	The UI team is currently researching into an API for styling both Controls and Widgets (using QML). This to improve the work-flow and UX for those that mix Controls and Widgets in the same application. I will present the current state of this work.
Qt & Cybersecurity	Kai Köhne	Presentation & Discussion	The CRA is starting to be a hot topic for a lot of customers. We're trying to use this as a vehicle to actually improve the processes and tools for the Qt Project. Let's discuss where we are, and what are the next steps.
QGenericItemModel	Volker Hilsheimer	Presentation & Discussion	Users find it challenging to make their C++ data structures available to Qt Quick, and generally the model/view framework in Qt. QGenericItemModel has landed in dev for Qt 6.10, with the goal to make it trivial to expose any C++ range (or view thereof) to anything that operates on QAbstractItemModel. Let's have a look at the underlying design (and API, if any), and how it could be evolved further.
Qt Android Roadmap	Rami Potinkara	Presentation & Discussion	What are the key features of Qt for Android in versions 6.10 and 6.11 and later based on our vision? What would you like to see there and why?
High Performance Graphs & Painting	Sakaria Pouke Kaj Grönholm	Presentation & Discussion	Present performance benchmarks for displaying rapidly changing 2D data in QtGraphs with different graph types. Then introducing work-in-progress "Compact Painter", imperative C++ painting API on top of QRhi, as an alternative for custom graphs.
Qt AI Inference API PoC	Tommi Mänttäri	Lightning talk & Presentation & Discussion	Present the PoC for the new Qt AI Inference API and discuss about its usefulness, what is missing or dead wrong and how the backends should be implemented for different AI frameworks and services.
Rich Text editing in Qt Quick	Shawn Rutledge	Presentation & Discussion	A while back we added some features: TextDocument, loading and saving various formats: plain, HTML and Markdown. (I was going to discuss next steps at QtCS last year, but wasn't allowed to go, so this talk is delayed, and the work got delayed too.) Now we have default context menus, and think about how to make them more easily customizable. Possible future work could include improvements in JS automation: https://codereview.qt-project.org/c/qt/qtdeclarative/+/523731 ; typing shortcuts for emoji; making possible an outliner (some model for representing QTD to a TreeView); better table editing, and/or some way of embedding other views. If we could embed TableView, for example, maybe we wouldn't need to enhance the code for table editing in TextEdit. What else do we want? Let's discuss ideas.
Documentation content	Alexei Cazacov	Presentation & Discussion	Documentation is always changing and we want to gather ideas and feedback from the community about the things we are implementing. Topic ideas: translations, accessibility (W3C WCAG), re-visiting Qt Writing Guidelines, topic-based documentation, linting, and so on. Also, promote the team's services such as language reviews, content help, and wiki pages.