Qt Contributor Summit 2025 - Program: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
(Manually merging changes)
(Add slides for lightning talk "Qt and Libreoffice")
 
(18 intermediate revisions by 10 users not shown)
Line 20: Line 20:
|-
|-
! style="background-color:#41cd52" |Time (CEST)
! style="background-color:#41cd52" |Time (CEST)
! colspan="4" style="background-color:#41cd52" |Room
! colspan="4" style="background-color:#41cd52" |Room Nürnberg
|-
|-
| 8:30 - 9:15
| 8:30 - 9:10
| colspan="4" |Welcome, Registrations, Breakfast
| colspan="4" |Registrations, Breakfast
|-
|-
| 9:15 - 10:00
| 9:10 - 9:15
| colspan="4" | '''Roadmap Deep-Dive:''' Qt Company Goals and Priorities
| colspan="4" |Welcome
|-
| 9:15 - 9:45
| colspan="4" | '''Roadmap Re-cap:'''
* Qt Company Goals and Priorities
* Qt Bridges (Vladimir)
|-
| 9:45 - 10:00
| colspan="4" | '''Qt and LibreOffice'''
|-
|-
| 10:00 - 11:45
| 10:00 - 11:45
| colspan="4" | Lightning Talks (5-10 minutes each)
| colspan="4" | '''Lightning Talks''' (5-10 minutes each)


* <small>Qt AI Inference API PoC</small>
* <small>Qt AI Inference API PoC</small>
Line 35: Line 43:
* <small>Cross-language code generation with QtJenny</small>
* <small>Cross-language code generation with QtJenny</small>
* <small>Let's start using C++23! (in examples and some tests)</small>
* <small>Let's start using C++23! (in examples and some tests)</small>
* <small>Developer tools feedback (Kai)</small>
* <small>Roadmap: QtQml (Ulf)</small>
* <small>Roadmap: QtQml (Ulf)</small>
* <small>Roadmap: Qt Core (Thiago)</small>
* <small>Roadmap: Qt Core (Thiago)</small>
* <small>Roadmap: Qt WebChannel (Arno)</small>
* <small>Roadmap: Qt WebChannel (Arno)</small>
* <small>Roadmap: Qt Graphs</small>
* <small>Roadmap: Qt Graphs</small>
* <small>Developer tools feedback (short kick-off, feedback then during the day)</small>
* <small>Roadmap: Qt Android</small>
* <small>Roadmap: Qt Android</small>
* <small>Enabling QFile signals in the normal case</small>
* <small>State and Direction of Qt's i18n and l10n framework</small>
* <small>State and Direction of Qt's i18n and l10n framework</small>
* <small>Roadmap: Qt Wayland</small>
* <small>Roadmap: Qt Wayland</small>
* <small>Pioneering Local AI on RISC-V</small>
* <small>The state of Vector Graphics in Qt</small>
|-
|-
| 11:45 - 12:00
| 11:45 - 12:00
Line 53: Line 62:
|-
|-
! style="background-color:#41cd52" |Time (CEST)
! style="background-color:#41cd52" |Time (CEST)
! style="background-color:#41cd52" |Room
! style="background-color:#41cd52" |Room Nürnberg
! style="background-color:#41cd52" |Room
! style="background-color:#41cd52" |Room Ulm
! style="background-color:#41cd52" |Room
! style="background-color:#41cd52" |Room Stuttgart
! style="background-color:#41cd52" |Common area
! style="background-color:#41cd52" |Common area
|-
|-
|13:00 - 13:45
|13:00 - 13:45
|Using Qt Quick with other programming languages
|[[QtCS25 - Using Qt Quick with other programming languages|Using Qt Quick with other programming languages]]
|Qt Creator Extensions
|[[QtCS25 - Qt Creator Extensions|Qt Creator Extensions]]
|UnifiedStyling
|[[QtCS25 - Async 1:1 APIs|Async 1:1 APIs]]
|To Review and Be Reviewed
[[QtCS25 - Asynchrony and concurrency|Asynchrony and concurrency]]
|<del>To Review and Be Reviewed</del>
|-
|-
|13:45 - 14:15
|13:45 - 14:15
|Rich Text editing in Qt Quick
|[[QtCS25 - Rich Text editing in Qt Quick|Rich Text editing in Qt Quick]]
|Compile once; run everywhere
|[[QtCS25 - Compile once; run everywhere|Compile once; run everywhere]]
|QtTest: state of the module and the way forward
|[[QtCS25 - QtTest: state of the module and the way forward|QtTest: state of the module and the way forward]]
|Integer Overflow in Widgets
|<del>Integer Overflow in Widgets</del>
|-
|-
|14:15 - 15:00
|14:15 - 15:00
|QProperty and QBindable (take 2)
|[[QtCS25 - QProperty and QBindable|QProperty and QBindable (take 2)]]
|Fontations in Qt: Adding Rust to the build system
|[[QtCS25 - Fontations in Qt: Adding Rust to the build system|Fontations in Qt: Adding Rust to the build system]]
State and Direction of Qt's Build System
[[QtCS25 - State and Direction of Qt's Build System|State and Direction of Qt's Build System]]
|Async 1:1 APIs
|[[QtCS25 - UnifiedStyling|UnifiedStyling]]
Asynchrony and concurrency
|[[QtCS25 - Developer tools feedback|Developer tools feedback]]
|
|-
|-
|15:00 - 15:30
|15:00 - 15:30
Line 82: Line 91:
|-
|-
|15:30 - 16:00
|15:30 - 16:00
|Documentation content
|[[QtCS25 - Team-Driven Documentation|Team-Driven Documentation]]
|QGenericItemModel
|[[QtCS25 - QGenericItemModel|QGenericItemModel]]
|Qt AI Inference API PoC
|[[QtCS25 -Qt AI Inference API PoC|Qt AI Inference API PoC]]
|qml API review
|[[QtCS25 - Qml API review|qml API review]]
|-
|-
|16:00 - 16:30
|16:00 - 16:30
|State of Qt on Windows
|[[QtCS25 - State of Qt on Windows|State of Qt on Windows]]
|Qt & Cybersecurity
|[[QtCS25 - Qt & Cybersecurity|Qt & Cybersecurity]]
|High Performance Graphs & Painting
|[[QtCS25 - High Performance Graphs & Painting|High Performance Graphs & Painting]]
|State and Direction of Qt's i18n and l10n framework
|[[QtCS25 - State and Direction of Qt's i18n and l10n framework|State and Direction of Qt's i18n and l10n framework]]
|-
|-
|16:30 - 17:00
|16:30 - 17:00
| colspan="4" |Wrap-up, Summaries
| colspan="4" |Wrap-up, Summaries
|-
|-
|Evening
|Evening (18:30)
| colspan="4" |Dinner
| colspan="4" |Dinner
|}
|}
Line 115: Line 124:
|-
|-
|Integer Overflow in Widgets
|Integer Overflow in Widgets
|Marc Mutz
|<del>Marc Mutz</del> (not able to join)
|Discussion
|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.
|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
|To Review And Be Reviewed
|Marc Mutz
|<del>Marc Mutz</del> (not able to join)
|Discussion
|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.  
|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.  
Line 180: Line 189:
|Presentation & Discussion
|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.
|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
|Future of QtGraphs
Line 229: Line 232:
|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.
|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
|Team-Driven Documentation
|Alexei Cazacov
|Alexei Cazacov
|Presentation & Discussion
|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.
|To improve the quality of documentation content, we can establish a more collaborative workflow for creating and updating it. The talk will have several ideas, which we can then discuss and develop.  
|-
|-
|QSkinny
|QSkinny
Line 264: Line 267:
|Short talk about what we are planning to do to QML in the near future as part of the Roadmap session
|Short talk about what we are planning to do to QML in the near future as part of the Roadmap session
|-
|-
|Using Qt Quick with other programming languages
|Qt Bridges - Using Qt Quick with other programming languages
|Vladimir Minenko
|Vladimir Minenko
|Presentation & Discussion
|Presentation & Discussion
|At the last QtCS there was a discussion about "QML Next".  There has been quite some progress in The Qt Company on this since then. In this presentation, I will give an overview of what we currently have and how you can use and contribute to it in the (near) future.  
|At the last QtCS there was a discussion about "QML Next". Today, it is called "Qt Bridges".  There has been quite some progress in The Qt Company on this since then. In this presentation, I will give an overview of what we currently have and how you can use and contribute to it in the (near) future.  
|-
|-
|The state of Vector Graphics in Qt
|The state of Vector Graphics in Qt
Line 274: Line 277:
|Last year, I talked about the newly added features in Qt Svg as well as the new QML Component VectorImage, that loads an Svg file and render it as a part of the scene graph. This year, I will talk about supporting CSS animations in Qt Svg and by extension in VectorImage. I would also like to open a discussion on potential new features that could be added to Qt Svg.
|Last year, I talked about the newly added features in Qt Svg as well as the new QML Component VectorImage, that loads an Svg file and render it as a part of the scene graph. This year, I will talk about supporting CSS animations in Qt Svg and by extension in VectorImage. I would also like to open a discussion on potential new features that could be added to Qt Svg.
|-
|-
|Qt and LibreOffice
|Qt and LibreOffice  
[[File:2025-05-08 Qt and LibreOffice.pdf|alt=Slides of the lightning talk "Qt and LibreOffice"|none|thumb]]
|Michael Weghorn
|Michael Weghorn
|Lightning talk
|Lightning talk

Latest revision as of 15:45, 24 May 2025

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 Nürnberg
8:30 - 9:10 Registrations, Breakfast
9:10 - 9:15 Welcome
9:15 - 9:45 Roadmap Re-cap:
  • Qt Company Goals and Priorities
  • Qt Bridges (Vladimir)
9:45 - 10:00 Qt and LibreOffice
10:00 - 11:45 Lightning Talks (5-10 minutes each)
  • Qt AI Inference API PoC
  • QSkinny
  • Cross-language code generation with QtJenny
  • Let's start using C++23! (in examples and some tests)
  • Developer tools feedback (Kai)
  • Roadmap: QtQml (Ulf)
  • Roadmap: Qt Core (Thiago)
  • Roadmap: Qt WebChannel (Arno)
  • Roadmap: Qt Graphs
  • Roadmap: Qt Android
  • State and Direction of Qt's i18n and l10n framework
  • Roadmap: Qt Wayland
  • Pioneering Local AI on RISC-V
  • The state of Vector Graphics in Qt
11:45 - 12:00 Friday Project Pitching
12:00 - 13:00 Lunch
Time (CEST) Room Nürnberg Room Ulm Room Stuttgart Common area
13:00 - 13:45 Using Qt Quick with other programming languages Qt Creator Extensions Async 1:1 APIs

Asynchrony and concurrency

To Review and Be Reviewed
13:45 - 14:15 Rich Text editing in Qt Quick Compile once; run everywhere QtTest: state of the module and the way forward Integer Overflow in Widgets
14:15 - 15:00 QProperty and QBindable (take 2) Fontations in Qt: Adding Rust to the build system

State and Direction of Qt's Build System

UnifiedStyling Developer tools feedback
15:00 - 15:30 Coffee Break
15:30 - 16:00 Team-Driven Documentation QGenericItemModel Qt AI Inference API PoC qml API review
16:00 - 16:30 State of Qt on Windows Qt & Cybersecurity High Performance Graphs & Painting State and Direction of Qt's i18n and l10n framework
16:30 - 17:00 Wrap-up, Summaries
Evening (18:30) Dinner

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 (not able to join) 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 (not able to join) 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.
Qt Creator Extensions Cristian Adam Presentation Qt Creator 17 comes with an Extension Repository. I have adopted a few open source extensions and will showcase the usage from the perspective of an extension maintainer.
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ø 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.
Future of QtGraphs 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.
Team-Driven Documentation Alexei Cazacov Presentation & Discussion To improve the quality of documentation content, we can establish a more collaborative workflow for creating and updating it. The talk will have several ideas, which we can then discuss and develop.
QSkinny Peter Hartmann Lightning talk A short demo showing how QSkinny does styling, uses animations and color palettes etc.
Asynchrony and concurrency Ville Voutilainen Presentation & Discussion I will give an update on what's currently there in QStdExec, and what the plan forward for that is, but I'll also talk about what we already have in Qt, and how we can already achieve the conceptual goals of Senders & Receivers and how our users can already avoid the typical pitfalls of concurrency, and I'll talk about some minimal additions that could make our current facilities reap some more of the benefits of Senders & Receivers - and how to do that in C++17, without requiring a newer standard.
Cross-language code generation with QtJenny Ville Voutilainen Lightning talk This talk will explain what is in the pipeline for QtJenny 1.1 and beyond, and how that changes the picture from 1.0. I'll also try to squeeze in some general ruminations of how to apply the same techniques for other cross-language binding situations.
Let's start using C++23! (in examples and some tests) Volker Hilsheimer Lightning talk We have to accept that for Qt APIs and library code we are mostly stuck with C++17 until the toolchains relevant for key industries allow us to move on, but nothing stops us from using modern in C++ in examples and test code!
Developer tools feedback Kai Köhne and Tuukka Turunen Discussion (and a bit of presentation) Qt has a very wide array of developer tools and also works with multiple different tools from others. Let's dive into some of the common jobs to be done by a developer and collect feedback and ideas on how well or not well you are able to do what you desired with the tools available.
Roadmap: QtQml Ulf Hermann Outburst Short talk about what we are planning to do to QML in the near future as part of the Roadmap session
Qt Bridges - Using Qt Quick with other programming languages Vladimir Minenko Presentation & Discussion At the last QtCS there was a discussion about "QML Next". Today, it is called "Qt Bridges". There has been quite some progress in The Qt Company on this since then. In this presentation, I will give an overview of what we currently have and how you can use and contribute to it in the (near) future.
The state of Vector Graphics in Qt Hatem ElKharashy Lightning talk Last year, I talked about the newly added features in Qt Svg as well as the new QML Component VectorImage, that loads an Svg file and render it as a part of the scene graph. This year, I will talk about supporting CSS animations in Qt Svg and by extension in VectorImage. I would also like to open a discussion on potential new features that could be added to Qt Svg.
Qt and LibreOffice
Slides of the lightning talk "Qt and LibreOffice"
Michael Weghorn Lightning talk This talk will give a quick overview of how LibreOffice makes use of Qt, mention some LibreOffice-related improvements to Qt, potential future steps and ideas to work together in the future. (Ideas welcome!)
Roadmap: QtWebChannel Arno Rehn Lightning talk Brief overview: Additional client languages, interaction with package registries (npm, pypi & co), planned features
Pioneering Local AI on RISC-V: Building Industry-Ready AI PCs for the Next Computing Era Yuning Liang & Danfeng Zhang Lightning Talk As AI rapidly evolves, we DeepComputing are reimagining personal computing by building the world’s first industry-ready AI PC based on RISC-V. Leveraging a chiplet-based SoC delivering up to '''50 TOPS''' of local AI performance, our solution is designed for '''real-world productivity and edge intelligence'''.

In this talk, we’ll share:

  • How the '''open RISC-V ISA''', combined with '''modular hardware like the Framework Laptop''', enables full-stack openness — from silicon to system
  • How '''open source software and hardware''' come together to accelerate innovation and reduce vendor lock-in
  • Practical AI use cases we’ve explored: local chatbots, AI-assisted media tools, and smart developer IDEs
  • Lessons learned in taking our AI PC from prototype to production — and what’s next for the open AI ecosystem on RISC-V