[Development] Status of the QtFeedback module

Aleix Pol aleixpol at kde.org
Wed May 5 16:43:22 CEST 2021

On Tue, Apr 27, 2021 at 2:28 AM Chris Adams <chris.adams at qinetic.com.au> wrote:
> Hi Jonah,
> I'm not part of the Qt Company, so please consider my comments as discussion only ;-)
> I'm the maintainer of the QtFeedback module, at least insofar as I am willing to review commits and keep things building.  Sailfish OS uses this module, which is why I am still interested in keeping it working etc.  Specifically in the case of QtFeedback, there has been no active development on it for a long time, as you mention, although no doubt many improvements would be possible given that we probably need not maintain BC/SC at this point...  Given that the rate of change in the repository is so slow, why is packaging from git snapshot difficult in this case?  And what sort of development do you see likely to occur, should it move under the KDE umbrella instead (and, out of curiosity, why could that development not occur under the Qt project?)
> Best regards,
> Chris.
> On Sat, Apr 24, 2021 at 7:12 AM Jonah BrĂ¼chert <jbb at kaidan.im> wrote:
>> Hi,
>> I'm one of the people working on the Plasma Mobile project. We are using
>> the QtFeedback module, and it would be very useful for us to have a
>> release of the module, as packaging git snapshots is making life harder
>> than necessary for packagers. I'm aware the module is currently not
>> actively developed, but it is commonly used in other mobile user
>> interfaces. Are there any plans for it?
>> If the Qt project is no longer interested in the module, we would
>> consider developing it under the KDE umbrella. If you are also using the
>> module, I'd be interested in which backend you are using, so we don't
>> end up with multiple forks but ideally something like a KDE tier 1
>> framework that anyone can use just like right now.
>> Thanks,
>> Jonah

I guess the biggest problem here is that the Qt project is not
releasing this component, so we're in a weird position when it comes
to developing it further.

If it moved to KDE, we could issue releases. If Qt project decides
that it's an interesting module and decides to release it, then that
could work as well.

We just need to get it out of this odd freeze in time it's in right now.


More information about the Development mailing list