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.
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	Status of WoA, Windows SDK integration, Custom titlebars, Windows Store deployment.
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	Jörg Bornemann	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	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 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.
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.
Documentation content	Jerome Pasion	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.
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?
QtGraphs 2D Data Performance	Sakaria Pouke	Lightning talk	Present performance benchmarks for displaying rapidly changing 2D data in QtGraphs with different graph types.