Submitting Kwi to KDE Review

[Nate Graham]

For what it's worth, I tried daily driving the project right after the 
announcement blog post, and didn't stop, as I found no real issues for 
any of my normal terminal workflows.

I see all the relevant checkboxes in the review process are checked now. 
It looks good to go to me.

Nate


On 11/4/26 12:55 PM, Eike Hein wrote:
> Hi,
> 
> I'd like to submit utilities/kwi.git for KDE Review.
> 
> Kwi is a modern and fast terminal for KDE Plasma and other desktops.
> 
> See also: https://blogs.kde.org/2026/11/01/introducing-kwi/
> 
> 
> Kwi has completed every item on this checklist, aside from `Passing KDE neon build`, which I understand is no longer relevant given that `https://build.neon.kde.org` times out:
> 
> https://develop.kde.org/docs/getting-started/add-project/review/
> 
> 
> Additionally, Kwi is currently clean on:
> 
> - Linux and FreeBSD CI builds and smoke tests
> - Flatpak x86 and ARM builds
> - cppcheck, clang-format, reuse-lint, json-validation, yaml-lint and xml-lint CI jobs
> - clang-tidy
> - Clazy
> - qmllint
> 
> On those quality metrics this puts it above the average post-review repo.
> 
> 
> The requested project work item for this KDE Review is here: https://invent.kde.org/utilities/kwi/-/work_items/10
> 
> The check items await your review action.
> 
> 
> Further background:
> 
> Kwi currently has no open defect tickets.
> 
> About 10 or so have been resolved in the last week. Only one (a text layout issue with fallback fonts) was fairly important.
> 
> Kwi has already motivated upstream fixes and improvements in components such as Union.
> 
> 
> Initial user and press reports are generally happy:
> 
> https://www.reddit.com/r/kde/comments/1xkri9k/introducing_kwi_a_new_kde_terminal_emulator/
> https://www.youtube.com/watch?v=PSHai4Df_U4
> 
> 
> My plan is to generally handle incoming bug tickets throughout November, then tag and release a v0.1 relatively soon after KDE Review and an initial translation period, and then get it on Flathub.
> 
> In the months after I plan to address feature requests, collect additional translations, make interim releases accordingly and eventually aim for a v1.0 to coincide with libghosty-vt locking its 1.0 ABI/API, planned to happen within the next 4-6 months.
> 
> 
> 
> Cheers,
> Eike
> -
> KDE e.V. Vice President, Treasurer